Skip to content

dvy1987/agent-loom / .agents/skills/design-direction

design-direction

Verified

Set a deliberate visual direction before any UI is built — the single biggest lever against generic AI output. Derives a posture from product-soul/PRD/specs, scores a curated archetype palette, then generates 2-3 GENUINELY DISTINCT directions and compares them side-by-side before committing to one. Load when the user asks to pick an aesthetic, choose a design direction, decide what a UI should feel like, explore visual options, says "what should this look like", "make it feel like [Linear/Apple/ Duolingo]", "give me design directions", "explore some looks", or when frontend-design routes here. Replaces design-archetype. Sub-skill of frontend-design.

references/ux-context-checklist.md

View on GitHub
# UX Context Checklist (pre-direction)

Capture what is known before generating directions. Missing items do not block
exploration — note gaps in DIRECTION.md under `## Context gaps`.

## Research (what do we know about users?)

- [ ] Target audience named with specificity (not "everyone")
- [ ] Problem validated or hypothesized with evidence level noted
- [ ] Competitive landscape: 2–3 reference products and what they get right/wrong
- [ ] User feedback or research artifacts referenced (if any)

## Plan (what is the job?)

- [ ] Primary user job-to-be-done stated in one sentence
- [ ] Critical user flows identified (max 3 for MVP)
- [ ] Success metric or outcome defined (even if approximate)

## Constraints (what bounds the design?)

- [ ] Technical stack or platform constraints
- [ ] Brand assets or existing design language to respect or break
- [ ] Accessibility or compliance requirements
- [ ] Timeline/MVP scope that limits exploration depth

## How to use

In Step 1, extract answers from `docs/product-soul.md`, PRD, specs. For any unchecked
item with no source, ask ONE bundled question if gaps would mislead direction choice:
"Who is this for, what job does it do, and which 2 products should it feel closest to
(or farthest from)?" Record unchecked items as context gaps — do not stall exploration.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall