What problem does it solve?
Extending the evlog map coverage scanner in @evlog/cli requires coordinated edits across rule source, registry, type unions, tests, docs, published skills, and changesets, and missing any touchpoint breaks the build or leaves the public contract inconsistent.
Core Features & Use Cases
- Rule Creation Workflow: Guides adding a requirement or opportunity rule through eight touchpoints including rule source, REGISTRY, CheckId union, tests, docs, and changesets.
- Design Decision Framework: Explains the requirement-versus-opportunity distinction, weight assignment, and gating on project features so rules never fire on perfectly good code.
- Framework Adapter Variant: Covers the heavier path of teaching
evlog map a new framework, from route extraction and detection to sandbox smoke tests.
- Use Case: A maintainer wants a new coverage check that scores entry points on structured error usage; the Skill walks them through creating the rule file, registering it, writing declarative test cases, updating docs tables, and verifying with lint, typecheck, and the CLI sandbox.
Quick Start
Add a new map rule to @evlog/cli that checks whether entry points use structured errors, following the touchpoints checklist.