technical-writing-for-designers — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited technical-writing-for-designers (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.
## ComponentName
### Purpose
One sentence: what problem this solves.
### When to Use
- Specific scenarios (not 'when appropriate')
### When NOT to Use
- Common misuse cases with alternatives
### Props/API
| Prop | Type | Default | Description |
|------|------|---------|-------------|
| variant | 'primary' \| 'secondary' | 'primary' | Visual style |
| size | 'sm' \| 'md' \| 'lg' | 'md' | Component size |
| disabled | boolean | false | Disables interaction |
### States
- Default, Hover, Active, Focus, Disabled, Loading, Error
### Accessibility
- ARIA role and attributes
- Keyboard behavior
- Screen reader expectations
### Examples
[Code examples for common usage patterns]## DDR-001: [Decision Title]
Date: YYYY-MM-DD
Status: Accepted / Proposed / Deprecated
### Context
What situation prompted this decision?
### Decision
What did we decide?
### Alternatives Considered
What else was considered and why was it rejected?
### Consequences
What are the implications of this decision?~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.