system-file-guardrails

Preventing accidental system-file edits requires live guardrails that enforce pre-edit validation and post-edit coherence across core project files. Safety checks verify inbound and outbound references before modifications are saved, reducing the risk of broken cross-file dependencies.

System-file guardrails are safety checks applied during edits to core project files like commands, skills, agents, and AGENTS.md. They ensure frontmatter integrity and validate outbound and inbound references to maintain cross-file coherence and prevent accidental destructive changes.

Validating cross-file references involves running pre-edit checks to verify inbound references across related directories and post-edit checks to confirm referenced commands, skills, or agents exist on disk. This ensures cross-file references resolve correctly after modifications.

Maintaining frontmatter integrity is supported by applying safety checks during edits to core project files. These guardrails enforce pre-edit validation and post-edit coherence, guiding modifications to ensure metadata structure remains consistent across related configuration files.

Ensuring coherence after editing multiple system files requires a post-session coherence check. This process confirms that cross-file references resolve correctly and maintains consistent terminology across all modified commands, skills, and agents.

Version control is not explicitly required to use safety checks for system-file edits. The guardrails operate by applying pre-edit validation and non-invasive tool loading to enforce frontmatter integrity and reference validation directly during the editing process.