Livro de Regras
A studio's judgment inside the AI.
- Type
- System/SaaS
- Industry
- Design and AI
- Platforms
- App and MCP server
- Year
- 2026
The problem
AI generates pages fast, but without the judgment of people who ship.
People who use AI to build sites get pages that look like templates: too many shadows, color with no purpose, confusing hierarchy.
The Studio already had that judgment written down as rules. What was missing was turning the book into a product the AI could check on its own, before building and before delivering.
The live site, working. Scroll, click and try it.
The solution
What we did
We built a system with login through the purchase, a library with search and filters, and an MCP server: the buyer generates a key and connects their AI to the book.
The sales page puts the system itself running on the first screen. The window grows with the scroll, and a real page improves rule by rule.
Decisions
The 3 key decisions
What we decided before designing, and why.
No PDF
A living book: new rules reach everyone, and the AI reads the current version, not a file forgotten in a folder.
The AI looks up and checks
The MCP server serves the mandatory rules for the project type and the delivery checklist.
Access tied to Hotmart
A purchase unlocks access instantly; a refund cuts off access and key automatically.
Project
The result
01 The same page, improving rule by rule.
02 Each rule shows the mistake and the fix.
03 Live sites built with these rules.
04 The offer: everything in one payment.
Outcome
What changed
- 905
- design, content and code rules
- 46
- chapters
- 5
- connected AIs
- Web app
- MCP server
- Hotmart integration
- Sales page
- Admin dashboard
