Docs alignment
Documentation alignment rules for Engram. Trigger: Any code or workflow change that affects user or contributor behavior.From its SKILL.md
npx -y skills add Gentleman-Programming/engram --skill docs-alignmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
0.8 KB, as published. Nobody here has run it
When to Use
Use this skill when:
- Changing APIs, setup flows, or plugin behavior
- Updating CLI commands or examples
- Writing contributor guidance
Alignment Rules
- Docs must describe current behavior, not intended behavior.
- Update docs in the same PR as the code change.
- Validate examples before publishing.
- Remove references to deprecated files, endpoints, or scripts.
Verification
- Endpoint names match server routes
- Script names match repository paths
- Command examples execute as documented
- Cross-agent notes are still accurate