Build rules
Under App Blueprint → Build Rules, GenieForge stores lasting conventions for how the AI should build your app (naming, UX preferences, domain constraints). They apply across Build conversations and travel with the app on export. Paste rules in plain language, or ask Build to record them when you are tired of repeating the same preference. Use rules for defaults you want every time, not one-off instructions in a single chat. Specific beats vague (“store ownership with immutable user ids” beats “be secure”). Example constraints people often keep as rules:Where it lives
App Blueprint → Build Rules.How to verify
- Open App Blueprint → Build Rules and confirm the text.
- Start a new Build turn that might violate a rule; the plan should surface conflicts when the prompt fights a rule.
- Override deliberately for one change when you mean it, then decide whether to update the rule.
Limits and notes
Treat rules as the default. When a prompt conflicts, choose consciously.

