design-spec-writing — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited design-spec-writing (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Engineers don't read specs because specs are usually:
What this feature is, who it's for, and why it exists. Link to the product brief.
Flowchart or numbered steps showing the complete path. Include error paths and edge cases.
For each screen:
## [Screen Name]
**Entry point:** How does the user get here?
**Primary action:** What's the main thing they do?
**Exit points:** Where can they go from here?
### States
- Default: [description + link to Figma frame]
- Loading: [description]
- Empty: [description]
- Error: [description + error messages]
- Success: [description]
### Interactions
- [Element]: [Behavior on click/hover/focus]
- [Element]: [Behavior on click/hover/focus]
### Content
- [Field]: [Character limits, formatting rules]
- [Field]: [Validation rules, error messages]
### Edge Cases
- What happens when [unlikely but possible scenario]?
- What if the user [does something unexpected]?List of design system components used and any new components introduced.
How the layout adapts. Not "it stacks on mobile." Specific decisions: what changes, what hides, what reorders.
[Element]: [Trigger] → [Property] from [start] to [end]
Duration: [Xms], Easing: [curve], Delay: [Xms]Testable statements:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.