ai-customization

AI Customization Style Contract

Pick the right artifact

• Do not put global behavior in a rule if it belongs in AGENTS.md.
• Do not duplicate the same rule across AGENTS.md, rules, and skills.

Rules

• Keep frontmatter discoverable: description must state when to use the file.
• Remove routing noise: avoid vague descriptors that do not improve file selection.
• Use directive language: write mandatory rules with imperative verbs.
• Keep optional behavior explicit: mark optional rules with an explicit optional tag.
• Use one rule per bullet: each bullet must express one enforceable behavior.
• Split compound bullets: break combined requirements into separate rules.
• Keep sections purpose-specific: section title and rule scope must match.
• Move off-topic rules: relocate unrelated content to a dedicated section.
• Minimize low-signal wording: remove filler that does not change execution.
• Shorten verbose statements: keep the same meaning with fewer words.
• Preserve technical literals: do not alter commands, code, paths, URLs, identifiers, config keys, or versions unless incorrect.
• Resolve duplication deliberately: keep one canonical statement and reference it from secondary files.
• Resolve contradictions explicitly: define precedence or rewrite to remove conflict.
• State each constraint once in the strongest clear polarity; do not restate a Rules bullet as its negation in Safety Guards or in the same bullet.
• Do not append ; never … (or equivalent) inside a Rules bullet when that prohibition is already covered by the Must form or by Safety Guards.
• Prefer one canonical file for cross-cutting policy; secondary files use a one-line deferral and must not copy the rule.
• Before adding a preference: search for an existing rule covering the decision; merge or reference instead of appending. Add a rule only when it changes a default decision and does not duplicate an existing rule.