--- name: "frontend-design" description: "frontend-design workflow skill. Use this skill when the user needs Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics. Do NOT use for design review or audit (use web-design-guidelines or web-quality-audit) and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off." version: "0.0.1" category: "frontend" tags: - "frontend-design" - "create" - "distinctive" - "production-grade" - "frontend" - "interfaces" - "high" - "design" - "omni-enhanced" complexity: "advanced" risk: "caution" tools: - "codex-cli" - "claude-code" - "cursor" - "gemini-cli" - "opencode" source: "omni-team" author: "Omni Skills Team" date_added: "2026-04-14" date_updated: "2026-04-26" source_type: "omni-curated" maintainer: "Omni Skills Team" family_id: "frontend-design" family_name: "frontend-design" variant_id: "omni" variant_label: "Omni Curated" is_default_variant: true derived_from: "skills/frontend-design" upstream_skill: "skills/frontend-design" upstream_author: "Impeccable (Paul Bakaus), based on Anthropic frontend-design" upstream_source: "community" upstream_pr: "133" upstream_head_repo: "diegosouzapw/awesome-omni-skills" upstream_head_sha: "9f1c34bd96b4fc03578ceb26f6303d8bf2c13b42" curation_surface: "skills_omni" enhanced_origin: "omni-skills-private" source_repo: "diegosouzapw/awesome-omni-skills" replaces: - "frontend-design" --- # frontend-design ## Overview This public intake copy packages `packages/skills-catalog/skills/(design)/frontend-design` from `https://github.com/tech-leads-club/agent-skills` into the native Omni Skills editorial shape without hiding its origin. Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow. This intake keeps the copied upstream files intact and uses `metadata.json` plus `ORIGIN.md` as the provenance anchor for review. This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Design Direction, The AI Slop Test. ## When to Use This Skill Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request. - Use when the request clearly matches the imported source intent: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished.... - Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch. - Use when provenance needs to stay visible in the answer, PR, or review packet. - Use when copied upstream references, examples, or scripts materially improve the answer. - Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over. ## Operating Table | Situation | Start here | Why it matters | | --- | --- | --- | | First-time use | `metadata.json` | Confirms repository, branch, commit, and imported path before touching the copied workflow | | Provenance review | `ORIGIN.md` | Gives reviewers a plain-language audit trail for the imported source | | Workflow execution | `references/color-and-contrast.md` | Starts with the smallest copied file that materially changes execution | | Supporting context | `references/interaction-design.md` | Adds the next most relevant copied source file without loading the entire package | | Handoff decision | `## Related Skills` | Helps the operator switch to a stronger native skill when the task drifts | ## Workflow This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow. 1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task. 2. Read the overview and provenance files before loading any copied upstream support files. 3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request. 4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes. 5. Validate the result against the upstream expectations and the evidence you can point to in the copied files. 6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity. 7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify. ### Imported Workflow Notes #### Imported: Design Direction Commit to a BOLD aesthetic direction: - **Purpose**: What problem does this interface solve? Who uses it? - **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction. - **Constraints**: Technical requirements (framework, performance, accessibility). - **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember? **CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work—the key is intentionality, not intensity. Then implement working code that is: - Production-grade and functional - Visually striking and memorable - Cohesive with a clear aesthetic point-of-view - Meticulously refined in every detail ## Examples ### Example 1: Ask for the upstream workflow directly ```text Use @frontend-design to handle . Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer. ``` **Explanation:** This is the safest starting point when the operator needs the imported workflow, but not the entire repository. ### Example 2: Ask for a provenance-grounded review ```text Review @frontend-design against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why. ``` **Explanation:** Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection. ### Example 3: Narrow the copied support files before execution ```text Use @frontend-design for . Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding. ``` **Explanation:** This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default. ### Example 4: Build a reviewer packet ```text Review @frontend-design using the copied upstream files plus provenance, then summarize any gaps before merge. ``` **Explanation:** This is useful when the PR is waiting for human review and you want a repeatable audit packet. ### Imported Usage Notes #### Imported: Examples ### Example 1: Landing page with strong aesthetic User says: "Build a landing page for a developer tools product, something that doesn't look like every other SaaS." Actions: Pick a bold direction (e.g. brutalist or editorial); choose a distinctive type pairing and a cohesive palette; implement with fluid spacing and one clear focal point; avoid cards-in-cards and hero-metric clichés. Result: A single-page layout with clear hierarchy, memorable typography, and no generic AI tells (no purple gradients, no rounded cards with thick accent borders). ### Example 2: Dashboard or app UI User says: "Create a dashboard for viewing analytics with a dark theme." Actions: Commit to a specific dark aesthetic (e.g. refined dark with tinted neutrals, not default glow-on-black); use container queries for panels; add one considered motion moment (e.g. staggered list load); ensure empty states are helpful. Result: Functional dashboard that feels intentionally designed—distinct palette, no cyan/purple glow, clear data hierarchy and responsive behavior. ### Example 3: Poster or marketing artifact User says: "Make a poster for a conference talk about frontend performance." Actions: Choose a strong typographic or visual concept; use a modular type scale and limited palette; avoid generic stock-photo + headline layout. Result: A poster that could stand alone as a designed artifact—memorable type and composition, not a template fill-in. --- ## Best Practices Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution. - ### Typography → Consult typography reference for scales, pairing, and loading strategies. - Choose fonts that are beautiful, unique, and interesting. - Pair a distinctive display font with a refined body font. - DO: Use a modular type scale with fluid sizing (clamp) DO: Vary font weights and sizes to create clear visual hierarchy DON'T: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults DON'T: Use monospace typography as lazy shorthand for "technical/developer" vibes DON'T: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated ### Color & Theme → Consult color reference for OKLCH, palettes, and dark mode. - Commit to a cohesive palette. - Dominant colors with sharp accents outperform timid, evenly-distributed palettes. - DO: Use modern CSS color functions (oklch, color-mix, light-dark) for perceptually uniform, maintainable palettes DO: Tint your neutrals toward your brand hue—even a subtle hint creates subconscious cohesion DON'T: Use gray text on colored backgrounds—it looks washed out; use a shade of the background color instead DON'T: Use pure black (#000) or pure white (#fff)—always tint; pure black/white never appears in nature DON'T: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds DON'T: Use gradient text for "impact"—especially on metrics or headings; it's decorative rather than meaningful DON'T: Default to dark mode with glowing accents—it looks "cool" without requiring actual design decisions ### Layout & Space → Consult spatial reference for grids, rhythm, and container queries. ### Imported Operating Notes #### Imported: Frontend Aesthetics Guidelines ### Typography → *Consult [typography reference](references/typography.md) for scales, pairing, and loading strategies.* Choose fonts that are beautiful, unique, and interesting. Pair a distinctive display font with a refined body font. **DO**: Use a modular type scale with fluid sizing (clamp) **DO**: Vary font weights and sizes to create clear visual hierarchy **DON'T**: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults **DON'T**: Use monospace typography as lazy shorthand for "technical/developer" vibes **DON'T**: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated ### Color & Theme → *Consult [color reference](references/color-and-contrast.md) for OKLCH, palettes, and dark mode.* Commit to a cohesive palette. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. **DO**: Use modern CSS color functions (oklch, color-mix, light-dark) for perceptually uniform, maintainable palettes **DO**: Tint your neutrals toward your brand hue—even a subtle hint creates subconscious cohesion **DON'T**: Use gray text on colored backgrounds—it looks washed out; use a shade of the background color instead **DON'T**: Use pure black (#000) or pure white (#fff)—always tint; pure black/white never appears in nature **DON'T**: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds **DON'T**: Use gradient text for "impact"—especially on metrics or headings; it's decorative rather than meaningful **DON'T**: Default to dark mode with glowing accents—it looks "cool" without requiring actual design decisions ### Layout & Space → *Consult [spatial reference](references/spatial-design.md) for grids, rhythm, and container queries.* Create visual rhythm through varied spacing—not the same padding everywhere. Embrace asymmetry and unexpected compositions. Break the grid intentionally for emphasis. **DO**: Create visual rhythm through varied spacing—tight groupings, generous separations **DO**: Use fluid spacing with clamp() that breathes on larger screens **DO**: Use asymmetry and unexpected compositions; break the grid intentionally for emphasis **DON'T**: Wrap everything in cards—not everything needs a container **DON'T**: Nest cards inside cards—visual noise, flatten the hierarchy **DON'T**: Use identical card grids—same-sized cards with icon + heading + text, repeated endlessly **DON'T**: Use the hero metric layout template—big number, small label, supporting stats, gradient accent **DON'T**: Center everything—left-aligned text with asymmetric layouts feels more designed **DON'T**: Use the same spacing everywhere—without rhythm, layouts feel monotonous ### Visual Details **DO**: Use intentional, purposeful decorative elements that reinforce brand **DON'T**: Use glassmorphism everywhere—blur effects, glass cards, glow borders used decoratively rather than purposefully **DON'T**: Use rounded elements with thick colored border on one side—a lazy accent that almost never looks intentional **DON'T**: Use sparklines as decoration—tiny charts that look sophisticated but convey nothing meaningful **DON'T**: Use rounded rectangles with generic drop shadows—safe, forgettable, could be any AI output **DON'T**: Use modals unless there's truly no better alternative—modals are lazy ### Motion → *Consult [motion reference](references/motion-design.md) for timing, easing, and reduced motion.* Focus on high-impact moments: one well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions. **DO**: Use motion to convey state changes—entrances, exits, feedback **DO**: Use exponential easing (ease-out-quart/quint/expo) for natural deceleration **DO**: For height animations, use grid-template-rows transitions instead of animating height directly **DON'T**: Animate layout properties (width, height, padding, margin)—use transform and opacity only **DON'T**: Use bounce or elastic easing—they feel dated and tacky; real objects decelerate smoothly ### Interaction → *Consult [interaction reference](references/interaction-design.md) for forms, focus, and loading patterns.* Make interactions feel fast. Use optimistic UI—update immediately, sync later. **DO**: Use progressive disclosure—start simple, reveal sophistication through interaction (basic options first, advanced behind expandable sections; hover states that reveal secondary actions) **DO**: Design empty states that teach the interface, not just say "nothing here" **DO**: Make every interactive surface feel intentional and responsive **DON'T**: Repeat the same information—redundant headers, intros that restate the heading **DON'T**: Make every button primary—use ghost buttons, text links, secondary styles; hierarchy matters ### Responsive → *Consult [responsive reference](references/responsive-design.md) for mobile-first, fluid design, and container queries.* **DO**: Use container queries (@container) for component-level responsiveness **DO**: Adapt the interface for different contexts—don't just shrink it **DON'T**: Hide critical functionality on mobile—adapt the interface, don't amputate it ### UX Writing → *Consult [ux-writing reference](references/ux-writing.md) for labels, errors, and empty states.* **DO**: Make every word earn its place **DON'T**: Repeat information users can already see --- #### Imported: Implementation Principles Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices across generations. Remember: the AI is capable of extraordinary creative work. Don't hold back—show what can truly be created when thinking outside the box and committing fully to a distinctive vision. ## Troubleshooting ### Problem: The operator skipped the imported context and answered too generically **Symptoms:** The result ignores the upstream workflow in `packages/skills-catalog/skills/(design)/frontend-design`, fails to mention provenance, or does not use any copied source files at all. **Solution:** Re-open `metadata.json`, `ORIGIN.md`, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing. ### Problem: The imported workflow feels incomplete during review **Symptoms:** Reviewers can see the generated `SKILL.md`, but they cannot quickly tell which references, examples, or scripts matter for the current task. **Solution:** Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it. ### Problem: The task drifted into a different specialization **Symptoms:** The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. **Solution:** Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind. ## Related Skills - `@accessibility` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@ai-cold-outreach` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@ai-pricing` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@ai-sdr` - Use when the work is better handled by that native specialization after this imported skill establishes context. ## Additional Resources Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding. | Resource family | What it gives the reviewer | Example path | | --- | --- | --- | | `references` | copied reference notes, guides, or background material from upstream | `references/color-and-contrast.md` | | `examples` | worked examples or reusable prompts copied from upstream | `examples/n/a` | | `scripts` | upstream helper scripts that change execution or validation | `scripts/n/a` | | `agents` | routing or delegation notes that are genuinely part of the imported package | `agents/n/a` | | `assets` | supporting assets or schemas copied from the source package | `assets/n/a` | - [color-and-contrast.md](references/color-and-contrast.md) - [interaction-design.md](references/interaction-design.md) - [motion-design.md](references/motion-design.md) - [responsive-design.md](references/responsive-design.md) - [color-and-contrast.md](references/color-and-contrast.md) - [interaction-design.md](references/interaction-design.md) ### Imported Reference Notes #### Imported: The AI Slop Test **Critical quality check**: If you showed this interface to someone and said "AI made this," would they believe you immediately? If yes, that's the problem. A distinctive interface should make someone ask "how was this made?" not "which AI made this?" Review the DON'T guidelines above—they are the fingerprints of AI-generated work from 2024-2025. ---