check_skill_compliance
Verifies source files against checkable rules from design skill documents, ensuring compliance with composition, state, data-fetching, naming, and motion guidelines. Returns findings and summary.
Instructions
Check real source files for the objectively-checkable rules in skills/ATOMIC_DESIGN.md (composition, state, data-fetching, naming) and skills/MOTION_VIDEO_DESIGN.md (motion tokens, reduced-motion, GPU-safe properties) — a post-hoc, deterministic verification pass, the same mechanism a linter uses to enforce a style guide.
This does not read the skill docs at check time or make an agent obey markdown — the checkable rules are hand-extracted into regex/string checks. It closes the gap where nothing downstream ever notices whether an agent actually followed those docs. skills/DESIGN_SYSTEM_REFERENCE.md is a pure external-system catalog with zero checkable rules and contributes nothing here.
Prereq: none — no Figma, no AI, works entirely offline.
Returns: { version, target, generatedAt, findings: [{ severity, rule, file, message, fix?, docRef }], summary: { critical, warning, filesChecked } }.
Real enforcement requires wiring memi audit --skill-compliance into CI or a pre-commit hook — this MCP tool remains something an agent can choose not to call, same as any other tool.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| target | No | Local path to scan. Defaults to the current project root. | |
| maxFiles | No | Maximum source files to scan. |