napkin

To maintain a live operational playbook, keep a single source of actionable, high-value rules organized by category, read and enforced at the start of every session to prevent context loss and team divergence.

Repository operational guidelines are recurring, high-value rules organized by category that serve as a reference guide. You need them when you require a single source of truth to prevent divergence and loss of context across sessions and teams.

To enforce recurring repository rules at the start of every session, apply a living guide containing actionable instructions. Frontmatter requires name and description, while the body enforces the rules.

Yes, you can include external scripts and assets in your repository guidelines. The guide body supports optional references to scripts, references, and assets directories for extended operational use.

The best way to organize recurring PT-BR rules is by category within a living operational guide. This creates a quick reference source read at the start of each session, ensuring consistent guidelines across projects and teams.

Yes, this repository rules skill works without external dependencies. It relies on a markdown guide with required frontmatter for name and description, and an actionable body, needing no external components to function.