this-project-only-skill

To keep project governance rules consistent across AI sessions, you centralize repository-specific business rules to prevent drift. This ensures governance behavior stays aligned and avoids unreviewed or non-portable changes during automated tasks.

Portable-first governance guidance ensures governance changes remain framework and template friendly before becoming host-specific integrations. This approach maintains compatibility and prevents lock-in when applying automated repository rules across different environments.

You enforce security hygiene and traceability by promoting deterministic-first enforcement paths, which involves adding runnable checks alongside documentation. This establishes constraints for hook coverage and reduces operational risk.

Yes, you need YAML frontmatter containing a name and description to set context-loading constraints. This limits cold-boot read sets and session handoff size to maintain framework alignment during work.

Relying solely on documentation for policy enforcement risks governance drift and unreviewed changes. The framework mandates adding deterministic runnable checks to ensure consistent security hygiene and traceability across sessions.