agentleFS
shinprshinpr/nautilus/.agents/skills/design-perspective/SKILL.md

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.

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
  1. Very specific:

    Before making a UX or product-design decision, read docs/product/design-principles.md when it exists.

    line 22
  2. Distinctive:

    Operable: All functionality available via keyboard, sufficient time for interactions, no content that causes seizures, clear navigation …

    line 43
  3. Distinctive:

    When they can change the design decision, reference:

    line 51
  4. Very specific:

    When creating or updating personas, use references/persona-template.md for decision-relevant context, jobs, behavioral evidence, and …

    line 55
  5. Distinctive:

    Treat design decisions without persona or context evidence as assumptions requiring validation.

    line 57
  6. Very specific:

    When docs/product/design/ exists, blueprint artifacts provide shared structural context:

    line 63
  7. Distinctive:

    When validating Usability risk through prototypes:

    line 74

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Design Perspective

Core Philosophy

Apply design evidence wherever it can change discovery, validation, requirements, or reflection.

ProcessDesign's Role
Opportunity DiscoveryJourney maps, pain point visualization
Solution GenerationDesign principle-driven ideation
Assumption ValidationPrototype generation → usability testing
PRD DefinitionUsability risk confirmation for user stories
ReflectionUX 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 navigation
  • content-model.md — entities, relationships, and stateful data
  • brand-direction.md — tone, visual direction, and Visual Tokens
  • flows/ — critical user flows and edge paths
  • ai-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:

  1. Define what "usable" means for this specific user story (tied to persona/context)
  2. Identify the critical interaction path to test
  3. Specify success criteria (task completion rate, time-on-task, error rate)
  4. Generate prototype with design context injected (see prototype-guide skill)
  5. Record results with specific UX learnings

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.