Skip to content

borghei/Claude-Skills / product-team/design-direction

design-direction

Verified

Turns a product brief into a design-system spec: style direction, contrast-checked palette, type pairing, tokens, UX rules and chart choices. Use when starting a new product's UI, picking a palette or fonts, or auditing a token file.

references/page-patterns.json

View on GitHub
{
  "version": 1,
  "note": "Page structures. landing = public pages that must persuade; screens = recurring in-product views. sections run top to bottom; cta says where the primary action sits; proof says what evidence the page needs before it asks; avoid_when names when the pattern misleads or underperforms. product-types.json points at these ids through landing and screens.",
  "patterns": [
    {"id": "problem-solution", "kind": "landing", "name": "Problem, solution, proof",
     "keywords": ["landing page", "homepage", "saas", "b2b", "explain value", "new category"],
     "sections": ["headline naming the outcome", "one-line problem the reader recognises", "how the product solves it (3 steps or 3 capabilities)", "product screenshot or short loop", "proof: customer logos with a quote or a number", "pricing teaser or plan summary", "single call to action", "footer with legal and contact"],
     "cta": "header button plus one repeat after proof; same label both times", "proof": "named customer quote or a measured result, not a logo wall alone",
     "avoid_when": "the reader already knows the category and only compares prices", "motion": "calm"},
    {"id": "product-tour", "kind": "landing", "name": "Product tour by capability",
     "keywords": ["features", "product tour", "developer", "tool", "showcase", "capabilities", "demo"],
     "sections": ["headline and sub-line", "hero visual of the real interface", "one section per capability, alternating image and text", "integration or ecosystem strip", "proof", "call to action"],
     "cta": "header plus end of page; a secondary 'see docs' link for technical buyers", "proof": "real screenshots and a usage number; docs link for developers",
     "avoid_when": "more than five capabilities; group them or the page becomes a feature list", "motion": "standard"},
    {"id": "comparison-pricing", "kind": "landing", "name": "Plans and comparison",
     "keywords": ["pricing page", "plans", "comparison", "tiers", "compare", "upgrade"],
     "sections": ["headline stating who each plan is for", "billing period toggle with the saving in words", "plan cards (three at most, one marked as most chosen)", "full feature comparison table", "billing and cancellation FAQ", "sales or support contact"],
     "cta": "one button per plan card; the table repeats the buttons in a sticky header row", "proof": "total price including tax or fees, renewal terms, refund policy",
     "avoid_when": "price depends entirely on a sales call; show a range or a worked example instead", "motion": "calm"},
    {"id": "waitlist", "kind": "landing", "name": "Waitlist or pre-launch",
     "keywords": ["waitlist", "pre-launch", "prelaunch", "coming soon", "early access", "beta signup", "launch"],
     "sections": ["headline with the promise and the launch window", "three-line explanation or a short visual", "email field with one button", "what happens after signup (confirmation, timing)", "privacy line"],
     "cta": "the email field itself, above the fold; nothing else competes", "proof": "founder name or backing, not invented signup counts",
     "avoid_when": "the product is live; a waitlist for an available product reads as artificial scarcity", "motion": "calm"},
    {"id": "lead-capture", "kind": "landing", "name": "Lead capture for a considered purchase",
     "keywords": ["lead generation", "enterprise", "request demo", "quote", "consultation", "b2b sales", "insurance quote"],
     "sections": ["headline naming the business outcome", "who it is for", "three outcomes with evidence", "short form (five fields or fewer) beside the copy", "security and compliance badges with links", "case study excerpt"],
     "cta": "form visible on first screen on desktop; sticky button on mobile that scrolls to the form", "proof": "case study with a named company and a number; certifications that can be verified",
     "avoid_when": "self-serve signup is possible; a demo gate slows buyers who are ready", "motion": "calm"},
    {"id": "storefront", "kind": "landing", "name": "Storefront home",
     "keywords": ["ecommerce", "shop", "store", "retail", "catalogue", "products", "collection"],
     "sections": ["search and category navigation", "current campaign or season (one, not a carousel of five)", "featured categories as large image tiles", "bestsellers grid with price and rating", "delivery, returns and payment promises", "newsletter signup", "footer with help links"],
     "cta": "add to bag on every product card; search always reachable", "proof": "ratings with counts, delivery and returns terms in plain words",
     "avoid_when": "the catalogue has fewer than ten items; use a product-led page instead", "motion": "standard"},
    {"id": "single-product", "kind": "landing", "name": "Single product story",
     "keywords": ["single product", "hardware", "device", "launch", "physical product", "gadget", "direct to consumer"],
     "sections": ["hero image of the product in use", "price and buy button in the first screen", "three reasons with photography", "specification table", "reviews", "delivery, warranty and returns", "repeat buy button"],
     "cta": "buy button in the hero and a sticky bar after the first scroll", "proof": "independent reviews and the warranty terms",
     "avoid_when": "buyers need to compare variants side by side; use storefront", "motion": "standard"},
    {"id": "content-hub", "kind": "landing", "name": "Content-first home",
     "keywords": ["news", "blog", "magazine", "publication", "newsletter", "articles", "documentation", "media"],
     "sections": ["lead story or most useful article", "latest articles in a scannable list", "topics or sections", "newsletter signup between sections, not as an entry modal", "about and contact"],
     "cta": "subscribe; placed after the reader has read something", "proof": "author names, dates and corrections policy",
     "avoid_when": "the site sells one product; content belongs on a blog subpage", "motion": "calm"},
    {"id": "trust-service", "kind": "landing", "name": "Professional or regulated service",
     "keywords": ["law firm", "clinic", "bank", "insurance", "government", "dentist", "accountant", "healthcare", "local business"],
     "sections": ["who you help and where", "primary task links (book, call, find a branch, check status)", "services with plain descriptions", "people with names and credentials", "how it works and what it costs", "location, hours and contact", "regulatory information"],
     "cta": "the main task (book, call, apply) in the header and the first screen", "proof": "licences, registration numbers, real staff photos, reviews from a third party",
     "avoid_when": "never avoided for regulated services; adapt the tone rather than dropping the proof", "motion": "calm"},
    {"id": "showcase-portfolio", "kind": "landing", "name": "Work showcase",
     "keywords": ["portfolio", "agency", "studio", "photographer", "designer", "architect", "creative"],
     "sections": ["name and one-line positioning", "selected work as large tiles with client and outcome", "case study pages with problem, process, result", "services or capabilities", "contact with availability"],
     "cta": "contact or enquiry, repeated after the work", "proof": "client names and outcomes on each case study",
     "avoid_when": "the work cannot be shown (NDA); lead with services and testimonials instead", "motion": "expressive"},
    {"id": "event-signup", "kind": "landing", "name": "Event or ticketing",
     "keywords": ["event", "conference", "festival", "webinar", "meetup", "tickets", "concert"],
     "sections": ["name, date, place and time zone in the first screen", "ticket or register button", "programme or line-up", "speakers or artists", "venue, travel and accessibility information", "ticket types and refund policy", "FAQ"],
     "cta": "register or buy in the first screen and a sticky button on mobile", "proof": "past attendance, named speakers, refund terms",
     "avoid_when": "dates are not fixed; use waitlist", "motion": "standard"},
    {"id": "app-download", "kind": "landing", "name": "Mobile app download",
     "keywords": ["mobile app", "download", "app store", "ios app", "android app", "consumer app"],
     "sections": ["headline and device frame showing the main screen", "store badges", "three core moments, each with a screen", "ratings from the stores", "privacy summary", "repeat store badges"],
     "cta": "store badges in the hero and at the end; a QR code on desktop", "proof": "store rating with count, privacy label summary",
     "avoid_when": "the main job also works on the web; offer the web path first", "motion": "standard"},
    {"id": "mission-donate", "kind": "landing", "name": "Mission and donation",
     "keywords": ["nonprofit", "charity", "donation", "fundraising", "cause", "volunteer", "church", "community"],
     "sections": ["the cause in one sentence with a real photograph", "donate button and one alternative (volunteer)", "what a gift achieves, in concrete amounts", "impact report numbers with source", "stories from people helped (with consent)", "financial transparency", "contact"],
     "cta": "donate in the header and after the impact numbers; amounts pre-set but editable", "proof": "audited accounts, registration number, how money is split",
     "avoid_when": "never use guilt countdowns or fake matching deadlines", "motion": "calm"},
    {"id": "dashboard-home", "kind": "screen", "name": "Dashboard home",
     "keywords": ["dashboard", "overview", "home screen", "analytics", "kpi", "admin"],
     "sections": ["page title with date range and filters", "three to five KPI tiles with unit, period and comparison", "one primary trend chart", "table of items that need attention", "recent activity"],
     "cta": "the most common next action on the attention table; filters persist in the URL", "proof": "data freshness timestamp and source",
     "avoid_when": "users come for one task; land them on that task instead", "motion": "calm"},
    {"id": "list-detail", "kind": "screen", "name": "List and detail",
     "keywords": ["list", "table", "records", "inbox", "search results", "crm", "orders"],
     "sections": ["search and filter bar", "sortable list or table with sticky header", "bulk actions bar when rows are selected", "detail panel or page with the record", "activity history"],
     "cta": "primary action on the detail view; bulk actions only after selection", "proof": "row count and active filters always visible",
     "avoid_when": "fewer than ten records; show cards or a single page", "motion": "calm"},
    {"id": "onboarding", "kind": "screen", "name": "First-run onboarding",
     "keywords": ["onboarding", "first run", "setup", "welcome", "signup flow", "activation"],
     "sections": ["one question per step, three to five steps", "progress indicator", "skip for optional steps", "first useful result before any upsell", "checklist that persists until done"],
     "cta": "continue button in the same place on every step", "proof": "say why each question is asked",
     "avoid_when": "the product works without setup; let people start and ask later", "motion": "standard"},
    {"id": "checkout", "kind": "screen", "name": "Checkout",
     "keywords": ["checkout", "payment", "cart", "purchase", "billing", "order"],
     "sections": ["order summary with total including tax and delivery", "guest checkout option", "contact and delivery", "payment with wallet options first", "review and confirm", "confirmation with order number and next steps"],
     "cta": "pay button states the amount; one per step", "proof": "security, returns and contact visible near payment",
     "avoid_when": "never pre-tick add-ons or hide fees until the last step", "motion": "calm"},
    {"id": "settings", "kind": "screen", "name": "Settings and account",
     "keywords": ["settings", "preferences", "account", "profile", "billing settings", "notifications"],
     "sections": ["grouped navigation (account, notifications, billing, security, data)", "one group per page", "save state per section, or autosave with confirmation", "danger zone at the end, separated"],
     "cta": "save per section; destructive actions confirm by typing or offer undo", "proof": "show current plan, usage and renewal date",
     "avoid_when": "fewer than six settings; keep them inline where they apply", "motion": "calm"},
    {"id": "conversation", "kind": "screen", "name": "Conversation or assistant",
     "keywords": ["chat", "assistant", "messaging", "copilot", "ai", "support"],
     "sections": ["conversation list or history", "message thread with clear authorship", "composer fixed at the bottom with attach and send", "suggested starts for an empty thread", "stop, retry and edit controls on generated replies"],
     "cta": "send; stop replaces send while a reply streams", "proof": "sources and timestamps on answers that depend on them",
     "avoid_when": "the task is a form with known fields; a chat adds steps", "motion": "calm"},
    {"id": "editor-canvas", "kind": "screen", "name": "Editor or canvas",
     "keywords": ["editor", "canvas", "builder", "design tool", "whiteboard", "document editor"],
     "sections": ["top bar with file name, save state and share", "tool rail", "canvas with zoom and selection", "context panel for the selected object", "undo history and keyboard shortcuts"],
     "cta": "share or export in the top bar; save is automatic and visible", "proof": "save status and version history",
     "avoid_when": "users only fill a template; give a form",
     "motion": "calm"},
    {"id": "feed", "kind": "screen", "name": "Feed",
     "keywords": ["feed", "social", "timeline", "community", "posts", "stream"],
     "sections": ["compose entry point", "posts with author, time and actions", "load more or paginate with position kept", "filters or tabs (following, latest)", "end-of-feed message rather than endless scroll"],
     "cta": "compose; reactions sized as full touch targets", "proof": "report and block controls on every post",
     "avoid_when": "content is reference material; use list-detail", "motion": "standard"},
    {"id": "booking-flow", "kind": "screen", "name": "Booking or scheduling",
     "keywords": ["booking", "appointment", "reservation", "schedule", "calendar", "slots"],
     "sections": ["choose service or resource", "choose date and time with availability shown", "details and requirements", "price and cancellation terms", "confirm and add to calendar"],
     "cta": "confirm booking with date, time and price in the label", "proof": "time zone, cancellation deadline and contact",
     "avoid_when": "only one slot type and one resource; a direct form is shorter", "motion": "calm"},
    {"id": "player", "kind": "screen", "name": "Media player",
     "keywords": ["player", "video", "music", "podcast", "streaming", "watch"],
     "sections": ["artwork or video", "play, pause, seek and volume reachable by keyboard and touch", "captions and transcript controls", "queue or up next", "mini player that persists across navigation"],
     "cta": "play; autoplay of the next item can be turned off", "proof": "captions available and labelled",
     "avoid_when": "never autoplay with sound", "motion": "standard"}
  ]
}
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall