Stats
Actions
Tags
From aidd-context
Generates a coding rule from intent and renders it per supported host tool. Use when adding, refactoring, or scanning for rules, conventions, or standards.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aidd-context:05-rule-generateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write one canonical rule from intent and render it per confirmed host tool that supports rules, or once as a plugin source.
Write one canonical rule from intent and render it per confirmed host tool that supports rules, or once as a plugin source.
| # | Action | Role | Input |
|---|---|---|---|
| 01 | capture-rule | Capture the topic, pick category and slug | user request |
| 02 | write-rule | Write the rule file per supported tool | the topic |
| 03 | validate | Check each rule file | the files |
Run the actions in order, 01 → 03, and run each action's ## Test before the next.
references/rule-authoring.md: the contract (taxonomy, naming, frontmatter, content).references/tool-paths.md: per-tool rules path, frontmatter, unsupported tools, the gate.assets/rule-template.md: rule file scaffold.npx claudepluginhub ai-driven-dev/framework --plugin aidd-contextGuides creation of .claude/rules/ files for path-scoped project conventions using TDD workflow: RED (test gaps), GREEN (write rule), REFACTOR (optimize). Triggers on 'add rule', 'create convention', 'scope guideline'.
Guides authoring .claude/rules/*.md files for auto-applied, file-pattern-scoped constraints on code conventions, quality standards, and project-specific guidance.
Interviews the user to capture a rule into `.chief/_rules/` or scaffolds the rules directory. Use when the user has a rule in mind and wants to write it proactively.