prompt-engineering

To keep agent instructions current as code evolves, use a frontmatter schema with name and description, separate WHAT guidance from HOW logic, and link instructions to current codebase references to prevent stale guidance.

Documentation rot occurs when agent instructions lose alignment with evolving code requirements. Fix it by applying reference-backed instructions that link to current modules, templates, and decision patterns via dynamic discovery.

Write agent instructions by defining the WHAT as dynamic guidance that updates without rewriting core logic, and the HOW as implementation details. Enforce a frontmatter schema exposing a name and description for each skill.

Your evolving codebase needs a frontmatter schema if agent behavior must reflect current requirements. The schema ensures each skill exposes a synchronized name and description to prevent documentation misalignment.

Use reference-backed instructions instead of static guidance when your codebase evolves frequently. Linking to current modules, templates, and state ensures agent behavior reflects current requirements and prevents stale decision patterns.