design-perspective
Skill7 starsChanged 3 months agoMITView on GitHub
Integrates design principles, WCAG 2.2 AA accessibility, persona context, and state design into product decisions. Use when reviewing UX decisions, checking accessibility, applying design principles, or ensuring state coverage in acceptance criteria.
In this repository15 other files it gives its agents.
- blueprint-standardsSkill
- business-contextSkill
- hypothesis-disciplineSkill
- prd-standardsSkill
- product-principlesSkill
- prototype-guideSkill
- recipe-blueprintSkill
- recipe-defineSkill
- recipe-discoverSkill
- recipe-personaSkill
- recipe-prototype-promptSkill
- recipe-refine-visualsSkill
- recipe-reflectSkill
- recipe-validateSkill
- recipe-visionSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Before making a UX or product-design decision, read docs/product/design-principles.md when it exists.
- Distinctive: line 43
Operable: All functionality available via keyboard, sufficient time for interactions, no content that causes seizures, clear navigation …
- Distinctive: line 51
When they can change the design decision, reference:
- Very specific: line 55
When creating or updating personas, use references/persona-template.md for decision-relevant context, jobs, behavioral evidence, and …
- Distinctive: line 57
Treat design decisions without persona or context evidence as assumptions requiring validation.
- Very specific: line 63
When docs/product/design/ exists, blueprint artifacts provide shared structural context:
- Distinctive: line 74
When validating Usability risk through prototypes:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design Perspective
Core Philosophy
Apply design evidence wherever it can change discovery, validation, requirements, or reflection.
| Process | Design's Role |
| Opportunity Discovery | Journey maps, pain point visualization |
| Solution Generation | Design principle-driven ideation |
| Assumption Validation | Prototype generation → usability testing |
| PRD Definition | Usability risk confirmation for user stories |
| Reflection | UX learning accumulation |
Design Principles Reference
Before making a UX or product-design decision, read docs/product/design-principles.md when it exists. An accessibility-only check does not require it unless the check also changes a product-specific trade-off.
Design principles are product-specific guardrails that guide all design decisions. They are not generic best practices but choices that reflect this product's values and trade-offs.
State Design
See product-principles skill for the authoritative State Design definition (Loading / Empty / Error / Partial / Success).
Implement the states that can occur and affect the acceptance decision.
In practice:
- PRDs should specify behavior for the states relevant to each acceptance boundary
- Prototypes should demonstrate the states needed to test the current hypothesis
- User stories addressing Usability risk should consider all relevant states
Accessibility Standards
Baseline: WCAG 2.2 AA compliance
Key requirements:
- Perceivable: Text alternatives for non-text content, sufficient color contrast (4.5:1 for normal text, 3:1 for large text), content adaptable to different presentations
- Operable: All functionality available via keyboard, sufficient time for interactions, no content that causes seizures, clear navigation mechanisms
- Understandable: Readable text, predictable behavior, input assistance for error prevention
- Robust: Compatible with assistive technologies, valid markup
Accessibility is a Usability risk dimension — factor it into confidence scoring.
Persona and Context Integration
When they can change the design decision, reference:
- Personas (
docs/product/personas/) — Who is using this? What's their context, skill level, environment? - Journey Maps (
docs/discovery/journeys/) — Where in their journey does this interaction happen?
When creating or updating personas, use references/persona-template.md for decision-relevant context, jobs, behavioral evidence, and validation gaps.
Treat design decisions without persona or context evidence as assumptions requiring validation.
Blueprint Integration
See blueprint-standards Artifact Overview for the full blueprint artifact list.
When docs/product/design/ exists, blueprint artifacts provide shared structural context:
information-architecture.md— page hierarchy and navigationcontent-model.md— entities, relationships, and stateful databrand-direction.md— tone, visual direction, and Visual Tokensflows/— critical user flows and edge pathsai-interaction-model.md— AI interaction patterns, guardrails, and error taxonomy
Prototypes and PRDs should reference these artifacts when available instead of re-inferring structure from scratch.
Design in Hypothesis Validation
When validating Usability risk through prototypes:
- Define what "usable" means for this specific user story (tied to persona/context)
- Identify the critical interaction path to test
- Specify success criteria (task completion rate, time-on-task, error rate)
- Generate prototype with design context injected (see prototype-guide skill)
- Record results with specific UX learnings
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

