zernie

Upgrade guidance() rules to enforce() by finding existing linter rules that match

Edit a vigiles spec file to update instruction files (CLAUDE.md, AGENTS.md)

Install vigiles and test a Claude Code harness — hooks, skills, settings, CLAUDE.md — by picking the right tier (unit / deterministic / eval) and writing a test that passes. Use when the user wants to check that a hook fires or blocks, that a skill triggers, that injected context lands, or that a harness change moves what the agent does.

Deep linter reference for authoring or debugging a vigiles enforce() rule — plugin tables, AST selectors, type-aware rules, auto-fix, and edge cases for ESLint, Ruff, Pylint, RuboCop, and Stylelint. Use when you need the exact rule name or config for a specific linter, not for running a linter.

Adopt a typed .spec.ts for an existing hand-written CLAUDE.md — start from the file you already have, non-destructively

Generate or iterate on the vigiles logo using ImageRouter API

Validate that all rules have proper enforcement classification (enforce/check/guidance)

Scan the current repo and score its feedback loop maturity for AI-assisted development

Convert a recurring PR review comment into an automated lint rule with tests and spec entry

Convert an existing hand-written CLAUDE.md into a typed .spec.ts file for incremental adoption