rules-repo-conventions

Apply Rules Repository conventions and forward-only workflow. Use when generating or editing docs, prompts, or code in projects that consume this repository or when this repository is the active workspace. Ensure Pact → Rules → Guides → Implementation links are created and updated, and prefer linking to submodule guides over duplicating content.

⭐4stars🔀0forks📁View on GitHub🕐Updated Dec 21, 2025

When & Why to Use This Skill

This Claude skill automates the enforcement of Rules Repository conventions and a forward-only workflow. It ensures structural integrity across documentation and code by maintaining strict traceability between Pacts, Rules, Guides, and Implementations, while preventing content duplication through disciplined submodule linking.

Use Cases

  • Scaffolding new host projects with standardized READMEs that correctly reference core architectural documents like PACT.md and RULES.md.
  • Updating technical documentation using a forward-only policy to ensure conflicting legacy content and anchors are removed in a single pass.
  • Establishing bidirectional links between high-level technical commitments and their specific code implementations to ensure auditability.
  • Managing complex repository structures by enforcing relative path discipline and proper integration of documentation submodules.
  • Automating the registration of new technical guides within centralized observability and platform indexes.
namerules-repo-conventions
descriptionApply Rules Repository conventions and forward-only workflow. Use when generating or editing docs, prompts, or code in projects that consume this repository or when this repository is the active workspace. Ensure Pact → Rules → Guides → Implementation links are created and updated, and prefer linking to submodule guides over duplicating content.

Rules Repository Conventions

This Skill encodes the essential conventions for working with this repository (as a submodule or directly) so Claude can apply them automatically.

Instructions

  1. Load and apply the repository root skills catalog: see skills.md.
  2. Honor RULES.md anchors for behavior and technical commitments:
  3. Close loops between artifacts:
    • Pact → Rules → Guides → Implementation, and back-links from Implementation to its source guide and rule.
  4. Link discipline:
    • Use relative paths; do not place project-specific docs inside the Rules Repository submodule directory when used downstream.
  5. Observability defaults:
  6. When adding new topic docs under generative/:
    • Add the entry to the nearest topic index README and cross-link to related guides.
  7. When updating structure/content:
    • Apply the Forward-Only policy in one change: update or remove conflicting docs and links; no compatibility stubs.

Examples

  • When scaffolding a new host project README, include links to PACT.md, RULES.md, GUIDES.md, IMPLEMENTATION.md, and the Rules Repository submodule path.
  • When creating a new Observability guide, add it to generative/platform/observability/README.md and cross-link from related platform indexes.

Validation Checklist

  • Links resolve and remain relative
  • Loop closure present (forward/back links)
  • No project-specific files placed inside the submodule directory
  • Forward-only edits applied (no legacy anchors retained)

See also