
Edit Spec
When you need to change CLAUDE.md or AGENTS.md in a vigiles project, this is how you do it. Those instruction files are compiled artifacts with hash comments, so you edit the .spec.ts source instead. The skill reads your spec, makes the change you ask for (add a rule about error handling, update the architecture section, add a key file), and recompiles. It handles all three rule types: enforce() for linter-backed rules, check() for filesystem conventions like test pairing, and guidance() for prose-only rules. One thing I appreciate is it won't secretly escalate enforcement or flip on strict checks without telling you the cost first.
- skills.sh installs
- 2.1K
- GitHub stars
- 15
- last updated
- Aug 21, 2026
Install
$ npx -y skills add zernie/vigiles --skill edit-spec --agent claude-codeInstalls into .claude/skills of the current project.
Files
Edit a .spec.ts file to update the project's instruction files. The spec is the source of truth — CLAUDE.md and AGENTS.md are compiled build artifacts that must not be edited directly.
Arguments
$ARGUMENTS — What the user wants to change. Examples:
- "add a rule about always using the custom logger"
- "update the architecture section"
- "point the auth rule at src/services/auth.ts"
- "add npm run lint to commands"
- "change the testing guidance"
Instructions
Step 1: Find the Spec
Look for spec files in the repo root:
CLAUDE.md.spec.ts— source for CLAUDE.mdAGENTS.md.spec.ts— source for AGENTS.md- Any
*.spec.tsmatching instruction files
If no spec exists: if there's a hand-written CLAUDE.md, suggest the
adopt-spec skill; otherwise suggest npx vigiles init to scaffold one.
Step 2: Read and Understand the Spec
Read the spec file. It's a TypeScript file that exports a claude() call with these fields:
import { claude, enforce, guidance, check, every } from "vigiles/spec";
Sponsors
Details
- Repository
- github.com/zernie/vigiles
- First seen
- Jul 14, 2026