Project Rules Writer

Create rules that solve a specific problem in a specific project — never generic ones. Analyse the project first, design, confirm with AskUserQuestion, then generate.

Core discipline: understand the problem → analyse the project → design the rule → confirm → generate. No file lands without user confirmation.

Shared writing-discipline rules across this and the other writer skills (project-skill-writer / project-agent-writer / project-skill-installer): see ../project-skill-writer/references/writer-discipline.md.

When to use

• "create a rule", "for X create a rule", "set the code style"
• "make the AI always …", "enforce naming convention", "configure AI behaviour"
• User references .agents/rules/..., .trae/rules/..., or #RuleName syntax
• Constrain AI behaviour for a specific project or file pattern

When NOT to use