[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MK75E54KKRWPDEEKNYJZYF":3,"skill-same:01M6MK75E54KKRWPDEEKNYJZYF":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":74},"01M6MK75E54KKRWPDEEKNYJZYF","octopus-ui-ux-design",null,"Design UI\u002FUX systems with style guides, palettes, typography, and component specs for new interfaces","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Foctopus-ui-ux-design\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"ux","ui ux","ux design","ui","octopus ui ux design","ui ux design","design","new","design ui","systems","style","with","true","for","typography","component","guides","2026-11-10 10:12:30",false,"---\nname: octopus-ui-ux-design\ndescription: \"Design UI\u002FUX systems with style guides, palettes, typography, and component specs for new interfaces\"\ndisable-model-invocation: true\n---\n\n> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n## EXECUTION CONTRACT (MANDATORY - CANNOT SKIP)\n\n\u003CHARD-GATE>\n**CRITICAL: You MUST call the BM25 search engine (search.py) via native shell command tool before producing\nany design recommendations. Do NOT rely solely on your own design knowledge. The search engine\nprovides curated, data-driven design intelligence. If you produce a design system without\nat least 3 search.py calls, you have violated this contract.**\n\u003C\u002FHARD-GATE>\n\nThis skill uses **ENFORCED execution mode**. You MUST follow this exact sequence.\n\n### STEP 1: Interactive Questions (BLOCKING)\n\n**You MUST call AskUserQuestion before any other action.**\n\n```javascript\nAskUserQuestion({\n  questions: [\n    {\n      question: \"What type of product are you designing for?\",\n      header: \"Product Type\",\n      multiSelect: false,\n      options: [\n        {label: \"SaaS\u002FDashboard\", description: \"Analytics, admin panels, B2B tools\"},\n        {label: \"E-commerce\", description: \"Shopping, marketplace, product pages\"},\n        {label: \"Landing page\", description: \"Marketing, conversion, product launch\"},\n        {label: \"Mobile app\", description: \"iOS\u002FAndroid native or responsive\"}\n      ]\n    },\n    {\n      question: \"What tech stack are you using?\",\n      header: \"Stack\",\n      multiSelect: false,\n      options: [\n        {label: \"React + Tailwind (Recommended)\", description: \"React\u002FNext.js with Tailwind CSS\"},\n        {label: \"React + shadcn\u002Fui\", description: \"React with shadcn component library\"},\n        {label: \"HTML + Tailwind\", description: \"Static or server-rendered HTML\"},\n        {label: \"Vue\u002FNuxt\", description: \"Vue.js or Nuxt framework\"}\n      ]\n    },\n    {\n      question: \"What design deliverables do you need?\",\n      header: \"Deliverables\",\n      multiSelect: true,\n      options: [\n        {label: \"Design tokens\", description: \"Colors, spacing, typography as CSS\u002FTailwind config\"},\n        {label: \"Component specs\", description: \"Component anatomy, states, props\"},\n        {label: \"Page layouts\", description: \"Wireframe-level layout specifications\"},\n        {label: \"Style guide\", description: \"Visual style direction with rationale\"}\n      ]\n    },\n    {\n      question: \"How adventurous should the design be?\",\n      header: \"Dials\",\n      multiSelect: false,\n      options: [\n        {label: \"Conservative (v3 m2 d4)\", description: \"Familiar patterns, minimal motion — enterprise, gov, finance\"},\n        {label: \"Balanced (v5 m4 d5)\", description: \"Contemporary but safe — most SaaS and product work\"},\n        {label: \"Expressive (v7 m6 d5)\", description: \"Distinctive direction, noticeable motion — marketing, launch pages\"},\n        {label: \"Maximal (v9 m8 d6)\", description: \"Take real aesthetic risks — portfolios, creative brands\"}\n      ]\n    }\n  ]\n})\n```\n\nThe dial answer maps to `--variance\u002F--motion\u002F--density` values (v\u002Fm\u002Fd above) passed to\nevery `search.py` call and stated in the design direction. When the user's brief already\nnames a visual style (for example, \"brutalist\", \"playful\", or \"corporate\"), skip the\nDials question and infer all three values from that style. Record the inferred values.\nIf an explicit user answer is also available, the explicit user answer takes precedence\nover the inferred values. Otherwise, ask the Dials question normally.\n\nAll three dial values MUST be integers from 1 through 10. Use these presets when\ninferring from named styles; choose the closest row for synonyms and record the\nselected row with the values:\n\n| Style cues | Variance | Motion | Density |\n|---|---:|---:|---:|\n| Corporate \u002F enterprise \u002F conservative | 3 | 2 | 4 |\n| Clean \u002F modern \u002F balanced | 5 | 4 | 5 |\n| Playful \u002F expressive \u002F retro | 7 | 6 | 5 |\n| Brutalist \u002F maximal \u002F experimental | 9 | 8 | 6 |\n\nValidate the range before every `search.py` call. If an explicit or inferred value is\nmissing, non-numeric, or outside 1-10, stop and obtain a valid value rather than clamp it.\n\n### STEP 2: Display Banner\n\n**MANDATORY: You MUST use the native shell command tool to run this provider check BEFORE displaying the banner. Do NOT skip it. Do NOT assume availability.**\n\n```bash\nbash \"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fscripts\u002Fhelpers\u002Fcheck-providers.sh\"\n```\n\n**Use the ACTUAL results below. PROHIBITED: Showing only \"🔵 Claude: Available ✓\" without listing all providers.**\n\n```\n🐙 **CLAUDE OCTOPUS ACTIVATED** - UI\u002FUX Design Mode\n🎨 Design: [Brief description from user prompt]\n\nPipeline:\n🔍 Phase 1: Design Research (BM25 search + context detection)\n🎯 Phase 2: Design Direction (synthesis + style selection)\n🐙 Phase 2b: Design Critique (adversarial review before committing)\n🛠️ Phase 3: Design System (tokens, components, layouts)\n✅ Phase 4: Validation (accessibility, handoff specs)\n\nProviders:\n🔴 Codex CLI: [Available ✓ \u002F Not installed ✗] — Implementation critique\n🟡 Antigravity CLI: [Available ✓ \u002F Not installed ✗] — Ecosystem critique\n🧭 Antigravity CLI: [Available ✓ \u002F Not installed ✗] — Additional external-model challenge\n🔵 Claude (Sonnet): Available ✓ — Design + independent critique\n\nTools:\n🔍 BM25 Design Intelligence: [checking...]\n🎨 Figma MCP: [Available \u002F Not configured]\n🧩 shadcn MCP: [Available \u002F Not configured]\n```\n\n### STEP 3: Check Design Intelligence\n\n```bash\nSEARCH_PY=\"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fvendors\u002Fui-ux-pro-max-skill\u002Fsrc\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py\"\nif [ -f \"$SEARCH_PY\" ]; then\n    python3 -c \"import csv, re, math\" 2>\u002Fdev\u002Fnull && echo \"READY\" || echo \"MISSING_PYTHON\"\nelse\n    echo \"MISSING_SEARCH_PY\"\nfi\n```\n\n**If MISSING_SEARCH_PY**: The vendored design intelligence files are missing — tell the user to reinstall or update the plugin (the `vendors\u002Fui-ux-pro-max-skill\u002F` directory ships with it as plain files).\n**If MISSING_PYTHON**: Tell user python3 is required for design intelligence.\n\nBoth missing states terminate this workflow after reporting the remediation. Only\ncontinue to Step 4 when preflight returns `READY`.\n\n### STEP 4: Phase 1 — Discover (Design Research)\n\n**You MUST execute at least 3 of these searches. This is NOT optional.**\n\n```bash\nSEARCH_PY=\"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fvendors\u002Fui-ux-pro-max-skill\u002Fsrc\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py\"\n\n# 1. Product type search — what design patterns fit this product?\npython3 \"$SEARCH_PY\" \"\u003Cuser's product description>\" --domain product\n\n# 2. Style search — what visual styles match?\npython3 \"$SEARCH_PY\" \"\u003Cuser's aesthetic or product type>\" --domain style\n\n# 3. Color palette search — data-driven palette selection\npython3 \"$SEARCH_PY\" \"\u003Cuser's product type or mood>\" --domain color\n\n# 4. Typography search — font pairings\npython3 \"$SEARCH_PY\" \"\u003Cuser's product type>\" --domain typography\n\n# 5. UX guidelines search — relevant best practices\npython3 \"$SEARCH_PY\" \"\u003Ckey user flow>\" --domain ux\n\n# 6. Stack-specific search (if user specified a stack)\npython3 \"$SEARCH_PY\" \"\u003Cuser's requirements>\" --stack \u003Cstack>\n\n# 7. Full design-system draft with the dials from Step 1 (v2.11.0+)\npython3 \"$SEARCH_PY\" \"\u003Cuser's product description>\" --design-system \\\n  --variance \u003Cv> --motion \u003Cm> --density \u003Cd>\n```\n\n**If user provided a Figma URL**, also pull design context:\n- Use `get_design_context` from Figma MCP to pull existing designs\n- Use `get_screenshot` for visual reference\n\n**Collect all search results before proceeding to Phase 2.**\n\n### STEP 4b: Design Shotgun Mode (Auto-Activated When 3+ Providers Available)\n\n**This step runs automatically when the provider check in Step 2 detected 3 or more available providers (counting Claude as always available).** When fewer than 3 providers are available, skip to Step 5 and use standard single-direction mode.\n\nDispatch the same design brief to multiple providers in parallel. Each provider generates an independent design direction without seeing the others' work.\n\n**Launch 3+ variant agents in parallel using the host subagent tool with `background execution: true`:**\n\nEach agent receives:\n```\nDesign a visual direction for: [user's product description]\nProduct type: [from Step 1]\nStack: [from Step 1]\nSearch context: [key findings from Step 4 BM25 searches]\n\nProduce:\n1. A style name (2-3 words, e.g., \"Warm Minimalism\", \"Bold Industrial\", \"Cobalt Editorial\")\n2. Primary color palette (3-5 colors with hex values)\n3. Font pairing (heading + body)\n4. Layout philosophy (e.g., \"generous whitespace with card-based content\")\n5. One paragraph describing the overall feel\n\nBe distinctive — take a clear position rather than playing it safe.\n\nHard constraints (see skills\u002Fblocks\u002Fdesign-taste.md): do NOT produce any of the three\nAI-slop looks (cream+serif+terracotta, near-black+acid accent, purple-violet gradients),\nand do not default to Inter, Roboto, Space Grotesk, Fraunces, or Instrument Serif\nwithout a brief-tied reason.\n```\n\n**Dispatch to different providers for maximum diversity:**\n- 🔴 Codex: implementation-pragmatic direction (what builds fast and scales)\n- 🧭 Antigravity: trend-aware direction (what's current in the design ecosystem)\n- 🔵 Claude: user-centered direction (what serves the audience best)\n- 🟤 OpenCode \u002F 🟢 Copilot \u002F 🟣 Qwen: additional variants if available\n\n**After all variants return, bind each complete returned result to its provider.** Record\nthe providers as `VARIANT_A_PROVIDER`, `VARIANT_B_PROVIDER`, and `VARIANT_C_PROVIDER`,\nand record the corresponding complete outputs as `VARIANT_A_RESULT`,\n`VARIANT_B_RESULT`, and `VARIANT_C_RESULT`. Each result must contain the returned style\nname, palette, fonts, layout philosophy, and feel. If a field is missing, ask that agent\nto complete its result; do not invent or substitute example content. Present a\ncomparison board using those actual values:\n\n```text\n🎨 **Design Shotgun — 3 Variants**\n\n━━━ Variant A (${VARIANT_A_PROVIDER}) ━━━\n${VARIANT_A_RESULT}\n\n━━━ Variant B (${VARIANT_B_PROVIDER}) ━━━\n${VARIANT_B_RESULT}\n\n━━━ Variant C (${VARIANT_C_PROVIDER}) ━━━\n${VARIANT_C_RESULT}\n```\n\n**Then ask the user to choose:**\n```javascript\nAskUserQuestion({\n  questions: [{\n    question: \"Which design direction do you prefer?\",\n    header: \"Pick\",\n    multiSelect: false,\n    options: [\n      {label: \"Variant A\", description: \"[style name] — [one-line feel]\"},\n      {label: \"Variant B\", description: \"[style name] — [one-line feel]\"},\n      {label: \"Variant C\", description: \"[style name] — [one-line feel]\"},\n      {label: \"Mix & match\", description: \"Take elements from multiple variants\"}\n    ]\n  }]\n})\n```\n\n**After selection, proceed to Step 5 using the chosen variant as the design direction.** If \"Mix & match\", ask which elements to combine before proceeding.\n\n\n### STEP 5: Phase 2 — Define (Design Direction)\n\nSynthesize search results (and chosen variant if shotgun mode) into a design direction document:\n\n1. **Style recommendation** — which visual style best fits the product (cite search results)\n2. **Color palette** — selected palette with hex values and contrast ratios\n3. **Typography** — heading + body font pairing with Google Fonts import\n4. **Layout approach** — grid system, spacing scale, responsive strategy\n5. **Design principles** — 3-5 guiding principles derived from UX search results\n6. **Taste compliance** — one line confirming the direction passes `skills\u002Fblocks\u002Fdesign-taste.md` (not one of the three banned looks; no unjustified banned-default fonts; boldness spent in one place)\n\n**Output: Write the design direction as a structured section you can reference in the next step.**\n\n### STEP 5b: Design Critique — Three-Way Adversarial Review (MANDATORY)\n\n**This step runs by default.** Before committing to the design direction, it must survive adversarial critique from up to three independent perspectives. This catches accessibility failures, impractical choices, and BM25 blind spots before they get baked into tokens and components.\n\n**Critique prompt** (sent to all participants):\n```\nReview this proposed design direction and find problems. Be adversarial — your job is to catch flaws, not validate choices.\n\n[The full design direction from Step 5]\n\nCritique dimensions:\n1. ACCESSIBILITY — Do the proposed colors meet WCAG AA contrast ratios (4.5:1 text, 3:1 large text)? Are the font sizes readable at the proposed scale? Are touch targets viable?\n2. PRACTICALITY — Does this typography actually render well on the stated tech stack? Are the fonts available and performant (file size, loading)? Does the spacing scale work with the layout system?\n3. FIT — Does the visual style actually match the product type and audience? Would a user of [product type] feel comfortable with this aesthetic?\n4. GAPS — What did the research miss? Are there common UX patterns for this product type that aren't addressed? Are there competitive norms being ignored?\n5. SLOP — Run the checklist in skills\u002Fblocks\u002Fdesign-taste.md. Is this one of the three AI-slop looks (cream+serif+terracotta, near-black+acid, purple gradients)? Banned default fonts without a stated reason? Would another model given the same brief land on the same palette and fonts? Two or more checklist misses fail the direction.\n\nFor each issue found, state: what's wrong, why it matters, and what to do instead.\n```\n\n**Three participants, run in parallel:**\n\n```bash\n# Check provider availability\nproviders=()\ncommand -v codex >\u002Fdev\u002Fnull 2>&1 && providers+=(codex)\ncommand -v agy >\u002Fdev\u002Fnull 2>&1 && providers+=(agy)\n\nfor provider in \"${providers[@]}\"; do\n    safe_provider=$(printf '%s' \"$provider\" | tr -c '[:alnum:]_-' '_')\n    \"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fscripts\u002Forchestrate.sh\" spawn \"$provider\" \\\n      \"\u003Ccritique prompt>\" > \"\u002Ftmp\u002Fdesign-critique-${safe_provider}.md\" &\ndone\n\nwait\n```\n\n**🔵 Claude (Sonnet) — independent design critique.** You MUST also write your own adversarial critique. Do NOT just summarize what external providers said. Approach the design direction as if you didn't create it — actively look for problems across all five dimensions. This is your independent synthesis perspective, same as in `\u002Focto:debate`.\n\n**Display all critiques with provider indicators:**\n```\n🔴\u002F🧭\u002F🟡 **External Provider Critique:** [implementation, ecosystem, accessibility, and alternative approach concerns]\n🔵 **Claude Critique:** [design concerns — accessibility gaps, fit issues, missing patterns]\n```\n\nIf only 1-2 providers are available, run with what you have. Even Claude-only critique (minimum case) is valuable because you're explicitly switching from \"designer who made the choices\" to \"reviewer finding problems.\"\n\n**After collecting all critiques, synthesize and revise:**\n\n1. **Triage issues** — group by severity (must-fix, should-fix, acknowledged trade-off)\n2. **Fix must-fix items** — adjust colors for contrast, swap impractical fonts, add missing patterns\n3. **Address should-fix items** — incorporate where feasible, note rationale for deferrals\n4. **Log trade-offs** — document what you're keeping despite critique and why\n5. **Show the diff** — present what changed between original and revised direction:\n```\n📋 **Design Direction Revisions:**\n- [Changed] Primary blue #2563EB → #1D4ED8 (contrast ratio 4.2:1 → 5.8:1, per external critique)\n- [Added] Fallback font stack for body text (per external critique)\n- [Kept] Glassmorphism style despite provider concern — appropriate for SaaS dashboard audience\n```\n\n**The revised design direction feeds into Phase 3. Do NOT proceed with an uncritiqued direction.**\n\n### STEP 6: Phase 3 — Develop (Design System)\n\nGenerate the design system based on user's requested deliverables:\n\n**Design Tokens** (if requested):\n- CSS custom properties or Tailwind config\n- Color scales (50-950)\n- Spacing scale (4px base)\n- Typography scale with line heights\n- Shadow, border-radius, and transition tokens\n\n**Component Specs** (if requested):\n- Component anatomy diagrams (ASCII)\n- Props\u002Fvariants table\n- State variants (default, hover, active, disabled, error, loading)\n- Accessibility requirements (ARIA, keyboard, focus)\n\n**Page Layouts** (if requested):\n- Grid-based layout with responsive breakpoints\n- Content hierarchy and visual flow\n- Above-the-fold content strategy\n- Navigation and interaction patterns\n\n**Style Guide** (if requested):\n- Visual style rationale with evidence from search results\n- Do's and don'ts with examples\n- Icon and illustration guidelines\n- Motion and animation principles\n\nIf shadcn MCP is available, search for matching components:\n```javascript\n\u002F\u002F Search shadcn registries for components matching the design system\nmcp__shadcn__search_items_in_registries({ query: \"\u003Ccomponent name>\" })\n```\n\n### STEP 7: Phase 4 — Deliver (Validation)\n\n1. **Accessibility audit — run the checker, do not eyeball.** Every text\u002Fbackground pair in the token set goes through the contrast validator:\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fscripts\u002Fhelpers\u002Fcontrast-check.py\" \\\n  '\u003Ctext-hex>:\u003Cbg-hex>' '\u003Cheading-hex>:\u003Cbg-hex>:large' '\u003Cmuted-hex>:\u003Cbg-hex>' ...\n```\n\nExit 1 means at least one pair fails WCAG AA — fix the palette and re-run before delivering. Include the checker output in the final document as evidence.\n\n1. **Slop check** — run the pre-ship checklist in `skills\u002Fblocks\u002Fdesign-taste.md`; two or more misses means revise before delivering\n1. **Completeness check** — verify all requested deliverables are present\n1. **Implementation readiness** — confirm specs are detailed enough for frontend-developer\n1. **Figma push-back** (if connected) — offer to push design tokens to Figma\n\n### STEP 7b: AI Surface Audit (when the interface calls a model)\n\nRun this whenever the thing being designed sends input to a model and shows the\nresult, and especially when it then **acts** on that result. Style guides and\ncomponent specs do not answer what an AI feature must show and let the user\ncontrol; this step does. Skip it entirely for interfaces with no model in the\nloop.\n\nAsk each question and record an explicit answer. \"Not applicable\" is a valid\nanswer; silence is not.\n\n**1. Uncertainty.** Does the surface distinguish a confident answer from a\nguess? If it cannot, say so plainly rather than implying uniform reliability.\nDo not invent a numeric threshold — pick a representation the underlying system\ncan actually justify.\n\n**2. Provenance.** Can the user see what the answer was derived from? Retrieval\nand search features need citations; a summariser needs the source it summarised.\nAn answer with no traceable origin is unreviewable.\n\n**3. Interruption.** If output streams or the task is long-running, is there a\ncancel affordance, and does cancelling actually stop the work rather than just\nhiding it? A stop button that abandons a still-running job is worse than none,\nbecause it misreports the system's state.\n\n**4. The review gate.** Where does a human check the output, and is that\nplacement load-bearing? A gate after an irreversible action is decoration.\n`skill-intent-contract` already elicits initiative, control, and decision rights\nseparately — reuse those answers here rather than re-deriving them, and if they\ndisagree with the placement, the contract wins.\n\n**5. Failure and degradation.** What does the surface show when the model is\nslow, unavailable, rate-limited, or returns something unusable? Each needs a\ndistinct state. Collapsing them into one generic error teaches users to ignore\nit.\n\n**6. Consent and data use.** Does the user know what is sent, where, and whether\nit is retained? Required wherever input may contain someone else's data.\n\n**7. Rollback.** If the feature takes a real-world action — files, sends, pays,\ndeletes — what undoes it, and is that path visible before the action, not only\nafter it fails?\n\n**Output contract.** Answer all seven in the delivered document, each with the\ndecision and its rationale. Where a question is unanswerable because the\nunderlying system cannot support it, record that as a finding rather than\nleaving the row blank: an unanswerable question about rollback is a design\nconstraint, not an omission.\n\n**Attribution.** The framing follows the AI Interaction Atlas by Brandon Harwood\n(ai-interaction.com). Depend on it, do not copy it: the Atlas deliberately ships\nno thresholds — no confidence cutoffs, no latency budgets — and inventing them\nhere would attribute numbers to a source that does not publish them. State\ndirection, cite the source, and let the product supply its own values.\n\n### STEP 8: Present Results and Persist\n\nFormat the final design system as a structured document with:\n- Executive summary (style direction + rationale)\n- Design tokens (copy-paste ready)\n- Component inventory\n- Page layouts\n- Implementation notes for the development team\n- Sources (which search results informed each decision)\n\n**Persist the design system so it survives the session** (contract: `skill-design-lineage`):\n\n```bash\nSLUG=$(basename \"$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull || pwd)\")\nRAW_BRANCH=$(git branch --show-current 2>\u002Fdev\u002Fnull || true)\nREVISION=$(git rev-parse HEAD 2>\u002Fdev\u002Fnull || printf 'unborn')\nif [[ -n \"$RAW_BRANCH\" ]]; then\n  BRANCH_KEY=$(printf '%s' \"$RAW_BRANCH\" | tr '\u002F' '-')\nelse\n  RAW_BRANCH=\"detached:${REVISION}\"\n  BRANCH_KEY=\"detached-${REVISION}\"\nfi\nDATETIME=$(date -u +\"%Y%m%d-%H%M%S\")\nDESIGNS_DIR=\"${HOME}\u002F.claude-octopus\u002Fdesigns\u002F${SLUG}\"\nmkdir -p \"$DESIGNS_DIR\"\n\n# DESIGN_BODY must contain the complete structured design system from this step.\nif [[ -z \"${DESIGN_BODY:-}\" ]]; then\n  echo \"Design persistence failed: DESIGN_BODY is empty.\" >&2\n  exit 1\nfi\n\n# Serialize revision allocation per branch with an OS-managed lock. Closing the\n# descriptor releases the lock even after SIGKILL or a process\u002Fhost crash.\nLOCK_DIGEST=\"\"\nif command -v sha256sum >\u002Fdev\u002Fnull 2>&1; then\n  LOCK_DIGEST=$(printf '%s' \"$RAW_BRANCH\" | sha256sum | awk '{print $(1)}') || LOCK_DIGEST=\"\"\nelif command -v shasum >\u002Fdev\u002Fnull 2>&1; then\n  LOCK_DIGEST=$(printf '%s' \"$RAW_BRANCH\" | shasum -a 256 | awk '{print $(1)}') || LOCK_DIGEST=\"\"\nelse\n  echo \"Design persistence failed: no supported SHA-256 utility.\" >&2\n  exit 1\nfi\nif [[ ! \"$LOCK_DIGEST\" =~ ^[[:xdigit:]]{64}$ ]]; then\n  echo \"Design persistence failed: could not derive the branch lock key.\" >&2\n  exit 1\nfi\nLOCK_FILE=\"${DESIGNS_DIR}\u002F.${LOCK_DIGEST}.lineage.lock\"\nLOCK_HELD=false\nFILEPATH=\"\"\nTEMP_PATH=\"\"\ncleanup_design_persistence() {\n  [[ -n \"${TEMP_PATH:-}\" && -f \"$TEMP_PATH\" ]] && rm -f \"$TEMP_PATH\"\n  [[ -n \"${FILEPATH:-}\" && -f \"$FILEPATH\" && ! -s \"$FILEPATH\" ]] && rm -f \"$FILEPATH\"\n  if [[ \"$LOCK_HELD\" == true ]]; then\n    exec 9>&-\n    LOCK_HELD=false\n  fi\n}\ntrap cleanup_design_persistence EXIT\ntrap 'cleanup_design_persistence; exit 1' HUP INT TERM\n\nif ! exec 9>\"$LOCK_FILE\"; then\n  echo \"Design persistence failed: could not open the lineage lock.\" >&2\n  exit 1\nfi\nif command -v flock >\u002Fdev\u002Fnull 2>&1; then\n  if flock -n 9; then LOCK_STATUS=0; else LOCK_STATUS=$?; fi\nelif command -v lockf >\u002Fdev\u002Fnull 2>&1; then\n  if lockf -s -t 0 9; then LOCK_STATUS=0; else LOCK_STATUS=$?; fi\nelse\n  exec 9>&-\n  echo \"Design persistence failed: no supported file-lock utility (flock or lockf).\" >&2\n  exit 1\nfi\nif [[ \"$LOCK_STATUS\" -ne 0 ]]; then\n  exec 9>&-\n  echo \"Design persistence failed: another revision is being persisted for $RAW_BRANCH.\" >&2\n  exit 1\nfi\nLOCK_HELD=true\n\n# Discover the newest prior document for this exact branch or detached revision.\nPRIOR=\"\"\nfor candidate in \"$DESIGNS_DIR\"\u002F*.md; do\n  [[ -f \"$candidate\" ]] || continue\n  candidate_branch=$(awk -F ': ' '$(1) == \"branch\" { print $(2); exit }' \"$candidate\")\n  [[ \"$candidate_branch\" == \"$RAW_BRANCH\" ]] || continue\n  [[ -z \"$PRIOR\" || \"$candidate\" -nt \"$PRIOR\" ]] && PRIOR=\"$candidate\"\ndone\nSUPERSEDES=\"\"\n[[ -n \"$PRIOR\" ]] && SUPERSEDES=$(basename \"$PRIOR\")\n\nUSER_NAME=\"${USER:-$(whoami)}\"\nREVISION_ID=\"${DATETIME}-$$-${RANDOM}\"\nFILEPATH=\"${DESIGNS_DIR}\u002F${USER_NAME}-${BRANCH_KEY}-design-${REVISION_ID}.md\"\n\n# Reserve the final name atomically. The timestamp is readable; PID + RANDOM\n# prevents same-second runs from choosing the same immutable revision.\nif [[ -e \"$FILEPATH\" ]] || ! (set -o noclobber; : > \"$FILEPATH\") 2>\u002Fdev\u002Fnull; then\n  echo \"Design persistence failed: revision target already exists: $FILEPATH\" >&2\n  exit 1\nfi\n\nif [[ -n \"$SUPERSEDES\" && \"$SUPERSEDES\" == \"$(basename \"$FILEPATH\")\" ]]; then\n  rm -f \"$FILEPATH\"\n  echo \"Design persistence failed: a revision must not supersede itself.\" >&2\n  exit 1\nfi\n\nif ! TEMP_PATH=$(mktemp \"${FILEPATH}.tmp.XXXXXX\"); then\n  echo \"Design persistence failed: could not allocate a temporary file.\" >&2\n  exit 1\nfi\n\nif ! {\n  printf '%s\\n' '---'\n  printf 'branch: %s\\n' \"$RAW_BRANCH\"\n  printf 'user: %s\\n' \"$USER_NAME\"\n  printf 'created: %s\\n' \"$(date -u +\"%Y-%m-%dT%H:%M:%SZ\")\"\n  printf 'git_revision: %s\\n' \"$REVISION\"\n  [[ -n \"$SUPERSEDES\" ]] && printf 'supersedes: %s\\n' \"$SUPERSEDES\"\n  printf '%s\\n\\n' '---'\n  printf '%s\\n' \"$DESIGN_BODY\"\n} > \"$TEMP_PATH\"; then\n  echo \"Design persistence failed: could not write complete temporary document.\" >&2\n  exit 1\nfi\n\nif [[ ! -s \"$TEMP_PATH\" ]]; then\n  echo \"Design persistence failed: temporary document is missing or empty.\" >&2\n  exit 1\nfi\n\nPUBLISHED_PATH=\"$FILEPATH\"\nif ! mv \"$TEMP_PATH\" \"$FILEPATH\"; then\n  echo \"Design persistence failed: could not publish $FILEPATH.\" >&2\n  exit 1\nfi\nTEMP_PATH=\"\"\nFILEPATH=\"\"\nexec 9>&-\nLOCK_HELD=false\ntrap - EXIT HUP INT TERM\nprintf 'Persisted design: %s\\n' \"$PUBLISHED_PATH\"\n```\n\nLater sessions (and `flow-develop` \u002F `frontend-developer` handoffs) MUST filter\n`~\u002F.claude-octopus\u002Fdesigns\u002F\u003Cslug>\u002F` to documents whose `branch:` matches the current Git\nbranch before selecting the newest revision. Under detached HEAD, use the\n`detached:\u003Cfull-commit>` branch value and only select documents for that exact revision.\nFollow `supersedes` only within the filtered set. A revision supersedes rather than edits\nthe prior document.\n\n**Offer next steps:**\n- \"Want me to implement these specs?\" → hand off to frontend-developer persona\n- \"Want to refine the palette?\" → re-run color search with adjusted query\n- \"Want a full embrace workflow?\" → transition to `\u002Focto:embrace`\n","> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n## EXECUTION CONTRACT (MANDATORY - CANNOT SKIP)\n\n\u003CHARD-GATE>\n**CRITICAL: You MUST call the BM25 search engine (search.py) via native shell command tool before producing\nany design recommendations. Do NOT rely solely on your own design knowledge. The search engine\nprovides curated, data-driven design intelligence. If you produce a design system without\nat least 3 search.py calls, you have violated this contract.**\n\u003C\u002FHARD-GATE>\n\nThis skill uses **ENFORCED execution mode**. You MUST follow this exact sequence.\n\n### STEP 1: Interactive Questions (BLOCKING)\n\n**You MUST call AskUserQuestion before any other action.**\n\n```javascript\nAskUserQuestion({\n  questions: [\n    {\n      question: \"What type of product are you designing for?\",\n      header: \"Product Type\",\n      multiSelect: false,\n      options: [\n        {label: \"SaaS\u002FDashboard\", description: \"Analytics, admin panels, B2B tools\"},\n        {label: \"E-commerce\", description: \"Shopping, marketplace, product pages\"},\n        {label: \"Landing page\", description: \"Marketing, conversion, product launch\"},\n        {label: \"Mobile app\", description: \"iOS\u002FAndroid native or responsive\"}\n      ]\n    },\n    {\n      question: \"What tech stack are you using?\",\n      header: \"Stack\",\n      multiSelect: false,\n      options: [\n        {label: \"React + Tailwind (Recommended)\", description: \"React\u002FNext.js with Tailwind CSS\"},\n        {label: \"React + shadcn\u002Fui\", description: \"React with shadcn component library\"},\n        {label: \"HTML + Tailwind\", description: \"Static or server-rendered HTML\"},\n        {label: \"Vue\u002FNuxt\", description: \"Vue.js or Nuxt framework\"}\n      ]\n    },\n    {\n      question: \"What design deliverables do you need?\",\n      header: \"Deliverables\",\n      multiSelect: true,\n      options: [\n        {label: \"Design tokens\", description: \"Colors, spacing, typography as CSS\u002FTailwind config\"},\n        {label: \"Component specs\", description: \"Component anatomy, states, props\"},\n        {label: \"Page layouts\", description: \"Wireframe-level layout specifications\"},\n        {label: \"Style guide\", description: \"Visual style direction with rationale\"}\n      ]\n    },\n    {\n      question: \"How adventurous should the design be?\",\n      header: \"Dials\",\n      multiSelect: false,\n      options: [\n        {label: \"Conservative (v3 m2 d4)\", description: \"Familiar patterns, minimal motion — enterprise, gov, finance\"},\n        {label: \"Balanced (v5 m4 d5)\", description: \"Contemporary but safe — most SaaS and product work\"},\n        {label: \"Expressive (v7 m6 d5)\", description: \"Distinctive direction, noticeable motion — marketing, launch pages\"},\n        {label: \"Maximal (v9 m8 d6)\", description: \"Take real aesthetic risks — portfolios, creative brands\"}\n      ]\n    }\n  ]\n})\n```\n\nThe dial answer maps to `--variance\u002F--motion\u002F--density` values (v\u002Fm\u002Fd above) passed to\nevery `search.py` call and stated in the design direction. When the user's brief already\nnames a visual style (for example, \"brutalist\", \"playful\", or \"corporate\"), skip the\nDials question and infer all three values from that style. Record the inferred values.\nIf an explicit user answer is also available, the explicit user answer takes precedence\nover the inferred values. Otherwise, ask the Dials question normally.\n\nAll three dial values MUST be integers from 1 through 10. Use these presets when\ninferring from named styles; choose the closest row for synonyms and record the\nselected row with the values:\n\n| Style cues | Variance | Motion | Density |\n|---|---:|---:|---:|\n| Corporate \u002F enterprise \u002F conservative | 3 | 2 | 4 |\n| Clean \u002F modern \u002F balanced | 5 | 4 | 5 |\n| Playful \u002F expressive \u002F retro | 7 | 6 | 5 |\n| Brutalist \u002F maximal \u002F experimental | 9 | 8 | 6 |\n\nValidate the range before every `search.py` call. If an explicit or inferred value is\nmissing, non-numeric, or outside 1-10, stop and obtain a valid value rather than clamp it.\n\n### STEP 2: Display Banner\n\n**MANDATORY: You MUST use the native shell command tool to run this provider check BEFORE displaying the banner. Do NOT skip it. Do NOT assume availability.**\n\n```bash\nbash \"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fscripts\u002Fhelpers\u002Fcheck-providers.sh\"\n```\n\n**Use the ACTUAL results below. PROHIBITED: Showing only \"🔵 Claude: Available ✓\" without listing all providers.**\n\n```\n🐙 **CLAUDE OCTOPUS ACTIVATED** - UI\u002FUX Design Mode\n🎨 Design: [Brief description from user prompt]\n\nPipeline:\n🔍 Phase 1: Design Research (BM25 search + context detection)\n🎯 Phase 2: Design Direction (synthesis + style selection)\n🐙 Phase 2b: Design Critique (adversarial review before committing)\n🛠️ Phase 3: Design System (tokens, components, layouts)\n✅ Phase 4: Validation (accessibility, handoff specs)\n\nProviders:\n🔴 Codex CLI: [Available ✓ \u002F Not installed ✗] — Implementation critique\n🟡 Antigravity CLI: [Available ✓ \u002F Not installed ✗] — Ecosystem critique\n🧭 Antigravity CLI: [Available ✓ \u002F Not installed ✗] — Additional external-model challenge\n🔵 Claude (Sonnet): Available ✓ — Design + independent critique\n\nTools:\n🔍 BM25 Design Intelligence: [checking...]\n🎨 Figma MCP: [Available \u002F Not configured]\n🧩 shadcn MCP: [Available \u002F Not configured]\n```\n\n### STEP 3: Check Design Intelligence\n\n```bash\nSEARCH_PY=\"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fvendors\u002Fui-ux-pro-max-skill\u002Fsrc\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py\"\nif [ -f \"$SEARCH_PY\" ]; then\n    python3 -c \"import csv, re, math\" 2>\u002Fdev\u002Fnull && echo \"READY\" || echo \"MISSING_PYTHON\"\nelse\n    echo \"MISSING_SEARCH_PY\"\nfi\n```\n\n**If MISSING_SEARCH_PY**: The vendored design intelligence files are missing — tell the user to reinstall or update the plugin (the `vendors\u002Fui-ux-pro-max-skill\u002F` directory ships with it as plain files).\n**If MISSING_PYTHON**: Tell user python3 is required for design intelligence.\n\nBoth missing states terminate this workflow after reporting the remediation. Only\ncontinue to Step 4 when preflight returns `READY`.\n\n### STEP 4: Phase 1 — Discover (Design Research)\n\n**You MUST execute at least 3 of these searches. This is NOT optional.**\n\n```bash\nSEARCH_PY=\"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fvendors\u002Fui-ux-pro-max-skill\u002Fsrc\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py\"\n\n# 1. Product type search — what design patterns fit this product?\npython3 \"$SEARCH_PY\" \"\u003Cuser's product description>\" --domain product\n\n# 2. Style search — what visual styles match?\npython3 \"$SEARCH_PY\" \"\u003Cuser's aesthetic or product type>\" --domain style\n\n# 3. Color palette search — data-driven palette selection\npython3 \"$SEARCH_PY\" \"\u003Cuser's product type or mood>\" --domain color\n\n# 4. Typography search — font pairings\npython3 \"$SEARCH_PY\" \"\u003Cuser's product type>\" --domain typography\n\n# 5. UX guidelines search — relevant best practices\npython3 \"$SEARCH_PY\" \"\u003Ckey user flow>\" --domain ux\n\n# 6. Stack-specific search (if user specified a stack)\npython3 \"$SEARCH_PY\" \"\u003Cuser's requirements>\" --stack \u003Cstack>\n\n# 7. Full design-system draft with the dials from Step 1 (v2.11.0+)\npython3 \"$SEARCH_PY\" \"\u003Cuser's product description>\" --design-system \\\n  --variance \u003Cv> --motion \u003Cm> --density \u003Cd>\n```\n\n**If user provided a Figma URL**, also pull design context:\n- Use `get_design_context` from Figma MCP to pull existing designs\n- Use `get_screenshot` for visual reference\n\n**Collect all search results before proceeding to Phase 2.**\n\n### STEP 4b: Design Shotgun Mode (Auto-Activated When 3+ Providers Available)\n\n**This step runs automatically when the provider check in Step 2 detected 3 or more available providers (counting Claude as always available).** When fewer than 3 providers are available, skip to Step 5 and use standard single-direction mode.\n\nDispatch the same design brief to multiple providers in parallel. Each provider generates an independent design direction without seeing the others' work.\n\n**Launch 3+ variant agents in parallel using the host subagent tool with `background execution: true`:**\n\nEach agent receives:\n```\nDesign a visual direction for: [user's product description]\nProduct type: [from Step 1]\nStack: [from Step 1]\nSearch context: [key findings from Step 4 BM25 searches]\n\nProduce:\n1. A style name (2-3 words, e.g., \"Warm Minimalism\", \"Bold Industrial\", \"Cobalt Editorial\")\n2. Primary color palette (3-5 colors with hex values)\n3. Font pairing (heading + body)\n4. Layout philosophy (e.g., \"generous whitespace with card-based content\")\n5. One paragraph describing the overall feel\n\nBe distinctive — take a clear position rather than playing it safe.\n\nHard constraints (see skills\u002Fblocks\u002Fdesign-taste.md): do NOT produce any of the three\nAI-slop looks (cream+serif+terracotta, near-black+acid accent, purple-violet gradients),\nand do not default to Inter, Roboto, Space Grotesk, Fraunces, or Instrument Serif\nwithout a brief-tied reason.\n```\n\n**Dispatch to different providers for maximum diversity:**\n- 🔴 Codex: implementation-pragmatic direction (what builds fast and scales)\n- 🧭 Antigravity: trend-aware direction (what's current in the design ecosystem)\n- 🔵 Claude: user-centered direction (what serves the audience best)\n- 🟤 OpenCode \u002F 🟢 Copilot \u002F 🟣 Qwen: additional variants if available\n\n**After all variants return, bind each complete returned result to its provider.** Record\nthe providers as `VARIANT_A_PROVIDER`, `VARIANT_B_PROVIDER`, and `VARIANT_C_PROVIDER`,\nand record the corresponding complete outputs as `VARIANT_A_RESULT`,\n`VARIANT_B_RESULT`, and `VARIANT_C_RESULT`. Each result must contain the returned style\nname, palette, fonts, layout philosophy, and feel. If a field is missing, ask that agent\nto complete its result; do not invent or substitute example content. Present a\ncomparison board using those actual values:\n\n```text\n🎨 **Design Shotgun — 3 Variants**\n\n━━━ Variant A (${VARIANT_A_PROVIDER}) ━━━\n${VARIANT_A_RESULT}\n\n━━━ Variant B (${VARIANT_B_PROVIDER}) ━━━\n${VARIANT_B_RESULT}\n\n━━━ Variant C (${VARIANT_C_PROVIDER}) ━━━\n${VARIANT_C_RESULT}\n```\n\n**Then ask the user to choose:**\n```javascript\nAskUserQuestion({\n  questions: [{\n    question: \"Which design direction do you prefer?\",\n    header: \"Pick\",\n    multiSelect: false,\n    options: [\n      {label: \"Variant A\", description: \"[style name] — [one-line feel]\"},\n      {label: \"Variant B\", description: \"[style name] — [one-line feel]\"},\n      {label: \"Variant C\", description: \"[style name] — [one-line feel]\"},\n      {label: \"Mix & match\", description: \"Take elements from multiple variants\"}\n    ]\n  }]\n})\n```\n\n**After selection, proceed to Step 5 using the chosen variant as the design direction.** If \"Mix & match\", ask which elements to combine before proceeding.\n\n\n### STEP 5: Phase 2 — Define (Design Direction)\n\nSynthesize search results (and chosen variant if shotgun mode) into a design direction document:\n\n1. **Style recommendation** — which visual style best fits the product (cite search results)\n2. **Color palette** — selected palette with hex values and contrast ratios\n3. **Typography** — heading + body font pairing with Google Fonts import\n4. **Layout approach** — grid system, spacing scale, responsive strategy\n5. **Design principles** — 3-5 guiding principles derived from UX search results\n6. **Taste compliance** — one line confirming the direction passes `skills\u002Fblocks\u002Fdesign-taste.md` (not one of the three banned looks; no unjustified banned-default fonts; boldness spent in one place)\n\n**Output: Write the design direction as a structured section you can reference in the next step.**\n\n### STEP 5b: Design Critique — Three-Way Adversarial Review (MANDATORY)\n\n**This step runs by default.** Before committing to the design direction, it must survive adversarial critique from up to three independent perspectives. This catches accessibility failures, impractical choices, and BM25 blind spots before they get baked into tokens and components.\n\n**Critique prompt** (sent to all participants):\n```\nReview this proposed design direction and find problems. Be adversarial — your job is to catch flaws, not validate choices.\n\n[The full design direction from Step 5]\n\nCritique dimensions:\n1. ACCESSIBILITY — Do the proposed colors meet WCAG AA contrast ratios (4.5:1 text, 3:1 large text)? Are the font sizes readable at the proposed scale? Are touch targets viable?\n2. PRACTICALITY — Does this typography actually render well on the stated tech stack? Are the fonts available and performant (file size, loading)? Does the spacing scale work with the layout system?\n3. FIT — Does the visual style actually match the product type and audience? Would a user of [product type] feel comfortable with this aesthetic?\n4. GAPS — What did the research miss? Are there common UX patterns for this product type that aren't addressed? Are there competitive norms being ignored?\n5. SLOP — Run the checklist in skills\u002Fblocks\u002Fdesign-taste.md. Is this one of the three AI-slop looks (cream+serif+terracotta, near-black+acid, purple gradients)? Banned default fonts without a stated reason? Would another model given the same brief land on the same palette and fonts? Two or more checklist misses fail the direction.\n\nFor each issue found, state: what's wrong, why it matters, and what to do instead.\n```\n\n**Three participants, run in parallel:**\n\n```bash\n# Check provider availability\nproviders=()\ncommand -v codex >\u002Fdev\u002Fnull 2>&1 && providers+=(codex)\ncommand -v agy >\u002Fdev\u002Fnull 2>&1 && providers+=(agy)\n\nfor provider in \"${providers[@]}\"; do\n    safe_provider=$(printf '%s' \"$provider\" | tr -c '[:alnum:]_-' '_')\n    \"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fscripts\u002Forchestrate.sh\" spawn \"$provider\" \\\n      \"\u003Ccritique prompt>\" > \"\u002Ftmp\u002Fdesign-critique-${safe_provider}.md\" &\ndone\n\nwait\n```\n\n**🔵 Claude (Sonnet) — independent design critique.** You MUST also write your own adversarial critique. Do NOT just summarize what external providers said. Approach the design direction as if you didn't create it — actively look for problems across all five dimensions. This is your independent synthesis perspective, same as in `\u002Focto:debate`.\n\n**Display all critiques with provider indicators:**\n```\n🔴\u002F🧭\u002F🟡 **External Provider Critique:** [implementation, ecosystem, accessibility, and alternative approach concerns]\n🔵 **Claude Critique:** [design concerns — accessibility gaps, fit issues, missing patterns]\n```\n\nIf only 1-2 providers are available, run with what you have. Even Claude-only critique (minimum case) is valuable because you're explicitly switching from \"designer who made the choices\" to \"reviewer finding problems.\"\n\n**After collecting all critiques, synthesize and revise:**\n\n1. **Triage issues** — group by severity (must-fix, should-fix, acknowledged trade-off)\n2. **Fix must-fix items** — adjust colors for contrast, swap impractical fonts, add missing patterns\n3. **Address should-fix items** — incorporate where feasible, note rationale for deferrals\n4. **Log trade-offs** — document what you're keeping despite critique and why\n5. **Show the diff** — present what changed between original and revised direction:\n```\n📋 **Design Direction Revisions:**\n- [Changed] Primary blue #2563EB → #1D4ED8 (contrast ratio 4.2:1 → 5.8:1, per external critique)\n- [Added] Fallback font stack for body text (per external critique)\n- [Kept] Glassmorphism style despite provider concern — appropriate for SaaS dashboard audience\n```\n\n**The revised design direction feeds into Phase 3. Do NOT proceed with an uncritiqued direction.**\n\n### STEP 6: Phase 3 — Develop (Design System)\n\nGenerate the design system based on user's requested deliverables:\n\n**Design Tokens** (if requested):\n- CSS custom properties or Tailwind config\n- Color scales (50-950)\n- Spacing scale (4px base)\n- Typography scale with line heights\n- Shadow, border-radius, and transition tokens\n\n**Component Specs** (if requested):\n- Component anatomy diagrams (ASCII)\n- Props\u002Fvariants table\n- State variants (default, hover, active, disabled, error, loading)\n- Accessibility requirements (ARIA, keyboard, focus)\n\n**Page Layouts** (if requested):\n- Grid-based layout with responsive breakpoints\n- Content hierarchy and visual flow\n- Above-the-fold content strategy\n- Navigation and interaction patterns\n\n**Style Guide** (if requested):\n- Visual style rationale with evidence from search results\n- Do's and don'ts with examples\n- Icon and illustration guidelines\n- Motion and animation principles\n\nIf shadcn MCP is available, search for matching components:\n```javascript\n\u002F\u002F Search shadcn registries for components matching the design system\nmcp__shadcn__search_items_in_registries({ query: \"\u003Ccomponent name>\" })\n```\n\n### STEP 7: Phase 4 — Deliver (Validation)\n\n1. **Accessibility audit — run the checker, do not eyeball.** Every text\u002Fbackground pair in the token set goes through the contrast validator:\n\n```bash\npython3 \"${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${HOME}\u002F.claude-octopus\u002Fplugin}}\u002Fscripts\u002Fhelpers\u002Fcontrast-check.py\" \\\n  '\u003Ctext-hex>:\u003Cbg-hex>' '\u003Cheading-hex>:\u003Cbg-hex>:large' '\u003Cmuted-hex>:\u003Cbg-hex>' ...\n```\n\nExit 1 means at least one pair fails WCAG AA — fix the palette and re-run before delivering. Include the checker output in the final document as evidence.\n\n1. **Slop check** — run the pre-ship checklist in `skills\u002Fblocks\u002Fdesign-taste.md`; two or more misses means revise before delivering\n1. **Completeness check** — verify all requested deliverables are present\n1. **Implementation readiness** — confirm specs are detailed enough for frontend-developer\n1. **Figma push-back** (if connected) — offer to push design tokens to Figma\n\n### STEP 7b: AI Surface Audit (when the interface calls a model)\n\nRun this whenever the thing being designed sends input to a model and shows the\nresult, and especially when it then **acts** on that result. Style guides and\ncomponent specs do not answer what an AI feature must show and let the user\ncontrol; this step does. Skip it entirely for interfaces with no model in the\nloop.\n\nAsk each question and record an explicit answer. \"Not applicable\" is a valid\nanswer; silence is not.\n\n**1. Uncertainty.** Does the surface distinguish a confident answer from a\nguess? If it cannot, say so plainly rather than implying uniform reliability.\nDo not invent a numeric threshold — pick a representation the underlying system\ncan actually justify.\n\n**2. Provenance.** Can the user see what the answer was derived from? Retrieval\nand search features need citations; a summariser needs the source it summarised.\nAn answer with no traceable origin is unreviewable.\n\n**3. Interruption.** If output streams or the task is long-running, is there a\ncancel affordance, and does cancelling actually stop the work rather than just\nhiding it? A stop button that abandons a still-running job is worse than none,\nbecause it misreports the system's state.\n\n**4. The review gate.** Where does a human check the output, and is that\nplacement load-bearing? A gate after an irreversible action is decoration.\n`skill-intent-contract` already elicits initiative, control, and decision rights\nseparately — reuse those answers here rather than re-deriving them, and if they\ndisagree with the placement, the contract wins.\n\n**5. Failure and degradation.** What does the surface show when the model is\nslow, unavailable, rate-limited, or returns something unusable? Each needs a\ndistinct state. Collapsing them into one generic error teaches users to ignore\nit.\n\n**6. Consent and data use.** Does the user know what is sent, where, and whether\nit is retained? Required wherever input may contain someone else's data.\n\n**7. Rollback.** If the feature takes a real-world action — files, sends, pays,\ndeletes — what undoes it, and is that path visible before the action, not only\nafter it fails?\n\n**Output contract.** Answer all seven in the delivered document, each with the\ndecision and its rationale. Where a question is unanswerable because the\nunderlying system cannot support it, record that as a finding rather than\nleaving the row blank: an unanswerable question about rollback is a design\nconstraint, not an omission.\n\n**Attribution.** The framing follows the AI Interaction Atlas by Brandon Harwood\n(ai-interaction.com). Depend on it, do not copy it: the Atlas deliberately ships\nno thresholds — no confidence cutoffs, no latency budgets — and inventing them\nhere would attribute numbers to a source that does not publish them. State\ndirection, cite the source, and let the product supply its own values.\n\n### STEP 8: Present Results and Persist\n\nFormat the final design system as a structured document with:\n- Executive summary (style direction + rationale)\n- Design tokens (copy-paste ready)\n- Component inventory\n- Page layouts\n- Implementation notes for the development team\n- Sources (which search results informed each decision)\n\n**Persist the design system so it survives the session** (contract: `skill-design-lineage`):\n\n```bash\nSLUG=$(basename \"$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull || pwd)\")\nRAW_BRANCH=$(git branch --show-current 2>\u002Fdev\u002Fnull || true)\nREVISION=$(git rev-parse HEAD 2>\u002Fdev\u002Fnull || printf 'unborn')\nif [[ -n \"$RAW_BRANCH\" ]]; then\n  BRANCH_KEY=$(printf '%s' \"$RAW_BRANCH\" | tr '\u002F' '-')\nelse\n  RAW_BRANCH=\"detached:${REVISION}\"\n  BRANCH_KEY=\"detached-${REVISION}\"\nfi\nDATETIME=$(date -u +\"%Y%m%d-%H%M%S\")\nDESIGNS_DIR=\"${HOME}\u002F.claude-octopus\u002Fdesigns\u002F${SLUG}\"\nmkdir -p \"$DESIGNS_DIR\"\n\n# DESIGN_BODY must contain the complete structured design system from this step.\nif [[ -z \"${DESIGN_BODY:-}\" ]]; then\n  echo \"Design persistence failed: DESIGN_BODY is empty.\" >&2\n  exit 1\nfi\n\n# Serialize revision allocation per branch with an OS-managed lock. Closing the\n# descriptor releases the lock even after SIGKILL or a process\u002Fhost crash.\nLOCK_DIGEST=\"\"\nif command -v sha256sum >\u002Fdev\u002Fnull 2>&1; then\n  LOCK_DIGEST=$(printf '%s' \"$RAW_BRANCH\" | sha256sum | awk '{print $(1)}') || LOCK_DIGEST=\"\"\nelif command -v shasum >\u002Fdev\u002Fnull 2>&1; then\n  LOCK_DIGEST=$(printf '%s' \"$RAW_BRANCH\" | shasum -a 256 | awk '{print $(1)}') || LOCK_DIGEST=\"\"\nelse\n  echo \"Design persistence failed: no supported SHA-256 utility.\" >&2\n  exit 1\nfi\nif [[ ! \"$LOCK_DIGEST\" =~ ^[[:xdigit:]]{64}$ ]]; then\n  echo \"Design persistence failed: could not derive the branch lock key.\" >&2\n  exit 1\nfi\nLOCK_FILE=\"${DESIGNS_DIR}\u002F.${LOCK_DIGEST}.lineage.lock\"\nLOCK_HELD=false\nFILEPATH=\"\"\nTEMP_PATH=\"\"\ncleanup_design_persistence() {\n  [[ -n \"${TEMP_PATH:-}\" && -f \"$TEMP_PATH\" ]] && rm -f \"$TEMP_PATH\"\n  [[ -n \"${FILEPATH:-}\" && -f \"$FILEPATH\" && ! -s \"$FILEPATH\" ]] && rm -f \"$FILEPATH\"\n  if [[ \"$LOCK_HELD\" == true ]]; then\n    exec 9>&-\n    LOCK_HELD=false\n  fi\n}\ntrap cleanup_design_persistence EXIT\ntrap 'cleanup_design_persistence; exit 1' HUP INT TERM\n\nif ! exec 9>\"$LOCK_FILE\"; then\n  echo \"Design persistence failed: could not open the lineage lock.\" >&2\n  exit 1\nfi\nif command -v flock >\u002Fdev\u002Fnull 2>&1; then\n  if flock -n 9; then LOCK_STATUS=0; else LOCK_STATUS=$?; fi\nelif command -v lockf >\u002Fdev\u002Fnull 2>&1; then\n  if lockf -s -t 0 9; then LOCK_STATUS=0; else LOCK_STATUS=$?; fi\nelse\n  exec 9>&-\n  echo \"Design persistence failed: no supported file-lock utility (flock or lockf).\" >&2\n  exit 1\nfi\nif [[ \"$LOCK_STATUS\" -ne 0 ]]; then\n  exec 9>&-\n  echo \"Design persistence failed: another revision is being persisted for $RAW_BRANCH.\" >&2\n  exit 1\nfi\nLOCK_HELD=true\n\n# Discover the newest prior document for this exact branch or detached revision.\nPRIOR=\"\"\nfor candidate in \"$DESIGNS_DIR\"\u002F*.md; do\n  [[ -f \"$candidate\" ]] || continue\n  candidate_branch=$(awk -F ': ' '$(1) == \"branch\" { print $(2); exit }' \"$candidate\")\n  [[ \"$candidate_branch\" == \"$RAW_BRANCH\" ]] || continue\n  [[ -z \"$PRIOR\" || \"$candidate\" -nt \"$PRIOR\" ]] && PRIOR=\"$candidate\"\ndone\nSUPERSEDES=\"\"\n[[ -n \"$PRIOR\" ]] && SUPERSEDES=$(basename \"$PRIOR\")\n\nUSER_NAME=\"${USER:-$(whoami)}\"\nREVISION_ID=\"${DATETIME}-$$-${RANDOM}\"\nFILEPATH=\"${DESIGNS_DIR}\u002F${USER_NAME}-${BRANCH_KEY}-design-${REVISION_ID}.md\"\n\n# Reserve the final name atomically. The timestamp is readable; PID + RANDOM\n# prevents same-second runs from choosing the same immutable revision.\nif [[ -e \"$FILEPATH\" ]] || ! (set -o noclobber; : > \"$FILEPATH\") 2>\u002Fdev\u002Fnull; then\n  echo \"Design persistence failed: revision target already exists: $FILEPATH\" >&2\n  exit 1\nfi\n\nif [[ -n \"$SUPERSEDES\" && \"$SUPERSEDES\" == \"$(basename \"$FILEPATH\")\" ]]; then\n  rm -f \"$FILEPATH\"\n  echo \"Design persistence failed: a revision must not supersede itself.\" >&2\n  exit 1\nfi\n\nif ! TEMP_PATH=$(mktemp \"${FILEPATH}.tmp.XXXXXX\"); then\n  echo \"Design persistence failed: could not allocate a temporary file.\" >&2\n  exit 1\nfi\n\nif ! {\n  printf '%s\\n' '---'\n  printf 'branch: %s\\n' \"$RAW_BRANCH\"\n  printf 'user: %s\\n' \"$USER_NAME\"\n  printf 'created: %s\\n' \"$(date -u +\"%Y-%m-%dT%H:%M:%SZ\")\"\n  printf 'git_revision: %s\\n' \"$REVISION\"\n  [[ -n \"$SUPERSEDES\" ]] && printf 'supersedes: %s\\n' \"$SUPERSEDES\"\n  printf '%s\\n\\n' '---'\n  printf '%s\\n' \"$DESIGN_BODY\"\n} > \"$TEMP_PATH\"; then\n  echo \"Design persistence failed: could not write complete temporary document.\" >&2\n  exit 1\nfi\n\nif [[ ! -s \"$TEMP_PATH\" ]]; then\n  echo \"Design persistence failed: temporary document is missing or empty.\" >&2\n  exit 1\nfi\n\nPUBLISHED_PATH=\"$FILEPATH\"\nif ! mv \"$TEMP_PATH\" \"$FILEPATH\"; then\n  echo \"Design persistence failed: could not publish $FILEPATH.\" >&2\n  exit 1\nfi\nTEMP_PATH=\"\"\nFILEPATH=\"\"\nexec 9>&-\nLOCK_HELD=false\ntrap - EXIT HUP INT TERM\nprintf 'Persisted design: %s\\n' \"$PUBLISHED_PATH\"\n```\n\nLater sessions (and `flow-develop` \u002F `frontend-developer` handoffs) MUST filter\n`~\u002F.claude-octopus\u002Fdesigns\u002F\u003Cslug>\u002F` to documents whose `branch:` matches the current Git\nbranch before selecting the newest revision. Under detached HEAD, use the\n`detached:\u003Cfull-commit>` branch value and only select documents for that exact revision.\nFollow `supersedes` only within the filtered set. A revision supersedes rather than edits\nthe prior document.\n\n**Offer next steps:**\n- \"Want me to implement these specs?\" → hand off to frontend-developer persona\n- \"Want to refine the palette?\" → re-run color search with adjusted query\n- \"Want a full embrace workflow?\" → transition to `\u002Focto:embrace`\n",{"name":5,"description":7,"disable-model-invocation":51},true,"main","f620abaff09061f8c8b1f1559dca3fdd031a32e5","plugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Foctopus-ui-ux-design",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":51},[64,67,70],{"tool":65,"command":66},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill octopus-ui-ux-design",{"tool":68,"command":69},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill octopus-ui-ux-design",{"tool":71,"command":72},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill octopus-ui-ux-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Foctopus-ui-ux-design\u002FSKILL.md",[75],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"agents\u002Fopenai.yaml","REFERENCE","参考文档",173,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Foctopus-ui-ux-design\u002Fagents\u002Fopenai.yaml",[82,92,100,108,116,124],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":91},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":91},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":91},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":91},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":91},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]