human-optimized-frontend
Generates a frontend interface that is visually pleasing and experientially sound by jointly optimizing aesthetics, motion graphics, and user experience (UX) using quantified evaluation. Use only when the user explicitly invokes this skill by name to redesign a frontend. Trigger keywords: use human-optimized-frontend, redesign frontend, redesign interface.
What this skill does
## Activation Criteria Activate this skill only when the user explicitly instructs the agent to redesign a frontend and references this skill by name. Do not activate for: - Conceptual discussion or critique only - Coding or implementation tasks - Inspiration, references, or visual examples - Partial or component-level design requests ## Execution Steps ### 1. Context Intake - Consume all provided information about the interface. - If context is missing, assume a neutral functional product with general-purpose usage. - Do not assume branding, audience psychology, or business goals unless explicitly stated. ### 2. Direction Lock (Aesthetic + UX) - Select exactly one aesthetic direction. - Select exactly one UX interaction philosophy (e.g. clarity-first, flow-driven, exploration-led). - All visual, motion, and interaction decisions must reinforce both. - Do not mix stylistic or interaction paradigms. ### 3. Initial Design Generation #### Typography - Body text baseline: 15–18px equivalent - Heading scale: - H1 = body × 2.2–2.6 - H2 = body × 1.6–1.9 - H3 = body × 1.3–1.5 - Line height: - Body: 1.45–1.6 - Headings: 1.15–1.3 - Font rule: - Serif + sans-serif pairing OR single family with ≥ 4 weights - Letter spacing: - Headings: -1% to -3% - Body: 0% to +1% - Prohibited fonts: system defaults, Inter, Roboto, Arial. #### Color & Theme - Palette: - 1 dominant - 1 secondary - 1 accent - 1 neutral base - Contrast: - Text ≥ 4.5:1 - Interactive elements ≥ 3:1 - Accent usage ≤ 10% of visible area - Only one saturated color allowed - Gradients allowed only as background fields #### Layout & Composition - Single spacing base unit (8px or 10px) - Visual weight distribution: - Primary: 40–55% - Secondary: 25–35% - Tertiary: ≤ 20% - Maximum two alignment axes per view - Symmetry allowed only with counterbalancing contrast #### Background & Depth - Background type: - Textured neutral OR - Low-contrast geometry OR - Layered planes - Max depth layers: 3 - Foreground contrast must exceed background by ≥ 20% #### Motion Graphics (Mandatory) - Required motion categories: - Entry motion - Hierarchy reinforcement - Interaction feedback - Timing: 180–420ms - Easing: - Primary: ease-out - Secondary: subtle cubic or linear - Max simultaneous moving elements per viewport: 3 - Motion must encode hierarchy, state, or spatial relation - Prohibited: decorative loops, idle animations, novelty motion #### UX Structure (Mandatory) - Define a primary user goal per view. - All visual and motion emphasis must support this goal. - Interaction rules: - One primary action per screen - Secondary actions visually subordinate - Navigation clarity: - Entry point must be obvious within 1 second - Next available action must be discoverable without exploration - Cognitive load: - No more than 3 competing focal points per view - Feedback: - All user actions must produce immediate visual or motion feedback - Error tolerance: - Interfaces must be forgiving; destructive actions must be visually distinguished ### 4. Quantitative Evaluation Loop Score each dimension from 0–10: **Typography** - ≥ 8: hierarchy instantly readable - ≤ 6: scale or spacing feels inconsistent **Color** - ≥ 8: dominance and emphasis are unambiguous - ≤ 6: accents compete or contrast is weak **Layout** - ≥ 8: eye flow resolves within 1–2 seconds - ≤ 6: multiple regions compete equally **Background** - ≥ 7: depth supports hierarchy - ≤ 5: background distracts or feels empty **Motion** - ≥ 8: motion improves comprehension and flow - ≤ 6: motion distracts or delays intent **UX** - ≥ 8: user intent is obvious, actions feel effortless - ≤ 6: hesitation, ambiguity, or friction introduced **Cross-Dimensional Harmony** - ≥ 8: visuals, motion, and UX reinforce the same hierarchy and intent - ≤ 6: any dimension contradicts another **Weighted Total Score** - Typography: 20% - Color: 20% - Layout: 20% - Motion: 15% - UX: 15% - Background: 10% - Harmony: mandatory ≥ 8 ### 5. Iteration Rules - Adjust lowest-scoring dimension first. - UX adjustments take priority if UX score < 8. - Never adjust more than two dimensions per iteration. - Maximum iterations: 5. - If harmony score drops, revert the last change. ### 6. Final Output Produce a single declarative frontend specification including: - Typography system - Color palette with roles - Layout structure and visual weights - Background and depth treatment - Motion graphics definitions - UX flow and interaction rules No alternatives. No explanations. No theory. ## Ambiguity Handling - Missing context defaults to neutral functional usage. - Defaults must still satisfy aesthetic, motion, and UX thresholds. - Never infer branding, emotional tone, or audience psychology. ## Constraints & Non-Goals - Do not generate code, assets, or mockups. - Do not critique existing designs unless redesign context requires it. - Do not reference trends, competitors, or popular products. - Do not provide multiple options. - Do not justify decisions. ## Failure Behavior If activation conditions are not met, output a minimal statement indicating the skill cannot be activated. If after maximum iterations UX or harmony thresholds are not met, output a minimal statement indicating that a satisfactory frontend cannot be generated under the given constraints and terminate.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.