Implementation validation
Open-source interaction-design intelligence for AI coding agents - securely discover, select, adapt and validate UI motion, effects and interaction patterns.
npx -y skills add Suraj787/motif --skill implementation-validationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use as the final acceptance gate to confirm an interaction is accessible, performant, responsive, design-system-consistent, and fully recorded before it is considered done.
SKILL.md
1.5 KB, as published. Nobody here has run it
Implementation Validation
Responsibility: Run the final acceptance gates and produce the "After implementation report". Nothing ships until this passes.
When to invoke
- After implementation and the accessibility/performance sub-checks (steps 12-16).
Inputs
- The implemented interaction and the sub-reports from
motion-accessibilityandmotion-performance.
Outputs
- A consolidated pass/fail with the required "After implementation report" fields: pattern/effect implemented, accessibility result, performance result, responsiveness result, design-system conventions preserved, dependencies added (with licence + cost) or none, and a decision-log + provenance entry.
Gates
- Accessibility gate passed (
motion-accessibility). - Performance gate passed (
motion-performance). - Responsiveness verified across breakpoints and input modes (pointer, touch, keyboard).
- Design-system conventions preserved.
- Provenance and decision log written via
source-governance.
How it connects
- Aggregates the specialist gates; writes the final record.
- Any failed gate returns the work to the relevant specialist, not forward.
Notes
Validation is binary per gate. Do not mark done with an open gate, and do not paper over a failed accessibility or performance gate with a comment.