frontend-design
/frontend-design
Create distinctive, production-grade frontend interfaces with strong visual direction, polished typography, considered layout, and working HTML/CSS/JS or framework code. Use for websites, landing pages, dashboards, React components, application screens, and UI beautification.
- Author
- jhy0285 ↗
- Repository
- monofield ↗
- Licence
- Apache-2.0
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Create distinctive, production-grade frontend interfaces with strong visual direction, polished typography, considered layout, and working HTML/CSS/JS or framework code. Use for websites, landing pages, dashboards, React components, application screens, and UI beautification.
Original author description
Create distinctive, production-grade frontend interfaces with strong visual direction, polished typography, considered layout, and working HTML/CSS/JS or framework code. Use for websites, landing pages, dashboards, React components, application screens, and UI beautification.
How it works
- Workflow
- MonoField Integration
- Source
- License
SKILL.md preview
---
name: frontend-design
description: |
Create distinctive, production-grade frontend interfaces with strong visual direction, polished typography, considered layout, and working HTML/CSS/JS or framework code. Use for websites, landing pages, dashboards, React components, application screens, and UI beautification.
triggers:
- "frontend design"
- "ui design"
- "ux design"
- "web design"
- "production ui"
- "landing page"
- "dashboard design"
- "react component design"
license: Complete terms in LICENSE.txt
od:
mode: prototype
category: web-artifacts
craft:
requires: [typography, color, anti-ai-slop]
design_system:
requires: true
sections: [color, typography, layout, components]
example_prompt: "Design and build a production-quality SaaS analytics dashboard for a finance team, with real interaction states, refined typography, and a distinctive visual direction."
upstream: "https://github.com/anthropics/skills/tree/main/skills/frontend-design"
---
# frontend-design
> Adapted from Anthropic's official `frontend-design` skill for MonoField.
Use this skill when the user asks to build or improve a frontend interface: a website, landing page, dashboard, application screen, HTML/CSS artifact, React/Vue/Svelte component, or a visual redesign of an existing UI.
The goal is not just "make it nicer." The goal is to ship working frontend code with a clear design point of view, strong craft, and enough product detail that the result feels designed for the user's actual context.
## Workflow
1. Understand the brief before choosing the look.
- Identify the audience, primary job, domain, and emotional tone.
- Note any technical constraints: framework, existing styles, accessibility, performance, export target, or responsive requirements.
- If the repo already has design tokens, components, screenshots, or a `DESIGN.md`, use those as the source of truth.
2. Commit to one specific aesthetic direction.
- Pick a direction that fits the product: brutally minimal, editorial, luxury, playful, industrial, retro-futuristic, dense operational, calm enterprise, artful consumer, or another precise direction.
- Make the direction concrete through typography, spacing, color, hierarchy, motion, and component shape.
- Avoid generic AI defaults: purple-blue gradients, vague glass cards, interchangeable SaaS layouts, over-rounded cards, stock icon rows, and decorative blobs that do not serve the interface.
3. Design the real interface, not a placeholder poster.
- Include the controls, empty/loading/error states, tables, filters, navigation, and responsive behavior a real user would expect.
- Use honest content. If data is unknown, label it as sample, pending, or unavailable instead of inventing claims.
- Keep workflows efficient for the target user. Dashboards and tools should be scannable and dense enough for repeated use; marketing pages can be more expressive.
4. Build production-grade frontend code.
- Prefer the repository's existing framework, component conventions, icons, tokens, and styling approach.
- For standalone artifacts, create self-contained HTML/CSS/JS unless the user asked for a framework.
- Use semantic markup, keyboard-accessible controls, visible focus states, sensible contrast, and responsive layout constraints.
- Use CSS variables for repeated colors, spacing, shadows, and type scale.
5. Refine visual craft.
- Typography: choose expressive but readable type pairings. Avoid using default system stacks as the main visual idea unless the direction is intentionally utilitarian.
- Color: create a balanced palette with role clarity. Use accent color sparingly and deliberately.
- Layout: use alignment, rhythm, density, and negative space intentionally. Do not let cards, panels, or labels drift.
- Motion: add purposeful transitions for state changes, reveals, and feedback. Prefer transforms and opacity for performance.
- Details: use texture, borders, shadows, dividers, media, and iconography only when they support the concept.
6. Self-review before final delivery.
- The interface works at mobile and desktop widths.
- Text fits its containers and does not overlap adjacent UI.
- Interactive elements have hover/focus/active/disabled states.
- The design avoids obvious AI-generated visual tropes.
- The result has one memorable quality a user could describe after closing the page.
## MonoField Integration
When MonoField provides an active design system, treat it as the product's brand contract. Use the injected color, typography, layout, and component guidance first, then apply this skill's frontend craft rules where the design system is silent.
When MonoField injects craft references such as `typography`, `color`, and `anti-ai-slop`, apply those checks before finishing. If the user's brand guidance conflicts with a generic craft rule, the user's brand guidance wins.
## Source
- Upstream: https://github.com/anthropics/skills/tree/main/skills/frontend-design
- Category: `web-artifacts`
## License
This skill is adapted from Anthropic's official skills repository. See `LICENSE.txt` in this folder for the upstream Apache-2.0 license terms.
Files in this package (2)
- LICENSE.txt 10 KB
- SKILL.md 5 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jhy0285/monofield | 90 | Apache-2.0 |
| marcusrbrown/systematic | 100 | MIT |
| sparq-org/sparq | 100 | MIT |
| overmind-core/overmind | 100 | AGPL-3.0 |
| shaunjones-gh/lilystack | 100 | MIT |
| Navinspire-ia/navin | 100 | AGPL-3.0 |
| tantm97/ai-frontend-design-workflow | 100 | MIT |
| Reprograme/redevkit | 100 | MIT |
| anton-abyzov/vskill | 100 | MIT |
Database snapshot: 13.11.2026 · package version b9114b337123 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ia-frontend-design
Visual design and aesthetic direction for frontend interfaces. Use when building web pages, landing pages, dashboards, Next.js server components, or applications where visual identity matters. For React patterns and testing, use react-frontend. - 100ui-ux-design
Create production-grade frontend interfaces with strong UX and visual craft. Use when building web components, pages, dashboards, forms, landing pages, modals, or any UI. Use when user says 'build a form', 'create a dashboard', 'design a component', 'make a landing page', or… - 100frontend-design-quality
Design, implement, or improve a frontend interface with a clear visual direction and usable interaction states. Use for websites, landing pages, dashboards, product screens, and responsive component work when design quality matters. - 100ferrox-frontend-design
Use when building or restyling any frontend or UI surface - web pages, components, dashboards, landing pages, HTML mockups, or visual companion screens. Covers aesthetic direction, typography, layout, copy, the anti-template discipline, the design knowledge base, and the DESIGN.md contract. - 90frontend-design-direction
Set an ecc-specific frontend design direction for production UI work. Use when building or improving websites, dashboards, applications, components, landing pages, visual tools, or any web UI that needs stronger product-specific design judgment. - 90frontend-design-direction
Set an ECC-specific frontend design direction for production UI work. Use when building or improving websites, dashboards, applications, components, landing pages, visual tools, or any web UI that needs stronger product-specific design judgment.