ns-frontend-design — Claude Code skill for production UI without AI-slop aesthetics
ns-frontend-design — a skill for Claude Code, Codex, Cursor and other agents that builds production UI with deliberate typography, hierarchy and motion. Activates on pages, components, dashboards, forms and analytics views.
Apache-2.0 153 installs updated 2026-10-24
npx skills add nextstage-brasil/skills --skill ns-frontend-design -a claude-codeWhat ns-frontend-design does
Rather than producing purple-gradient, identical-card-grid output, it anchors work to a specific visual direction: type scale, spacing, accent color and motion level.
On load, the skill reads docs/context/design-brief.md when it exists, pulling tokens, typography rules and motion guidance from there. For React projects that include dashboards or analytics, it also loads references/react-analytics-ui.md; the default chart library is Recharts. The workflow runs in five steps: audit existing UI patterns, anchor to the design brief, design component states (hover, focus, empty, error) and responsive breakpoints, implement with a minimal diff, verify keyboard focus and color contrast. The skill depends on ns-harness being present.
It does not touch backend APIs or database schemas, and it does not replace ns-reviewer at MR gates. Without design-brief.md, the agent asks exactly one focused question about brand direction before starting large UI work.
What it helps with
- Strip generic AI aesthetics from pages and component libraries
- Build a KPI dashboard with charts using Recharts
- Apply design-brief tokens and typography to existing screens
- Add hover, focus, empty and error states to current components
- Check keyboard navigation and contrast on a finished view
Example prompts for the agent
- Rework the landing page against
docs/context/design-brief.mdand remove the duplicate card grid - Build a sales dashboard with a chart and a traffic-sources table
- Add loading and empty states to the
<DataTable />component
How to install ns-frontend-design
1Skills CLI (Vercel)
npx skills add nextstage-brasil/skills --skill ns-frontend-design -a claude-code2Manually: put the files in place
~/.claude/skills/ns-frontend-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ns-frontend-design/
1Skills CLI (Vercel)
npx skills add nextstage-brasil/skills --skill ns-frontend-design -a codex2Manually: put the files in place
.agents/skills/ns-frontend-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nextstage-brasil/skills --skill ns-frontend-design -a cursor2Manually: put the files in place
.cursor/skills/ns-frontend-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nextstage-brasil/skills skills/ns-frontend-design2Manually: put the files in place
.github/skills/ns-frontend-design/SKILL.md1Skills CLI (Vercel)
npx skills add nextstage-brasil/skills --skill ns-frontend-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/nextstage-brasil/skills --path skills/ns-frontend-designManually: put the files in place
.devin/skills/ns-frontend-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nextstage-brasil/skills --skill ns-frontend-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ns-frontend-design
How do I install ns-frontend-design in Claude Code?
Run npx skills add nextstage-brasil/skills --skill ns-frontend-design -a claude-code. The skill will then be available at ~/.claude/skills/ns-frontend-design/SKILL.md.
What does ns-frontend-design actually do?
It guides the agent through a full UI cycle: auditing existing patterns, anchoring to a design brief, implementing component states and responsive breakpoints with a minimal diff, then verifying accessibility. The goal is a production screen with a clear visual identity.
What does ns-frontend-design depend on?
ns-harness must be installed in the project. For React dashboard work, having references/react-analytics-ui.md in the repository gives the skill its chart and analytics guidance.
Source text
SKILL.md · Apache-2.0
--- name: ns-frontend-design description: "(NS) Distinctive production UI — layout, typography, motion, polish; avoids AI-slop aesthetics. Use when building/refining pages, components, dashboards, KPI/analytics views, charts, forms, design-brief work, or better UI/UX — even if they do not say \"design\". Load docs/context/design-brief.md when present. Do NOT use for backend-only, requirements writing, or full SDD (ns-spec-driven)." license: Apache-2.0 metadata: author: nextstage-brasil version: "1.1" depends: - ns-harness --- # Frontend Design Ship **distinctive, production-grade UI** — not interchangeable template aesthetics. ## Session boot See `../ns-harness/references/session-boot.md`. Read `.nextstage-harness/rules/architecture-rules.md` and layer-specific frontend rules when present. ## Context to load | File | When | | ---- | ---- | | `docs/context/design-brief.md` | Always check first — tokens, typography, motion | | `docs/context/stack-confirmed.md` | Framework and CSS approach | | `.nextstage-harness/rules/*frontend*` | Project conventions | | `references/react-analytics-ui.md` | React stack + KPIs, charts, timelines, tables, sources, alerts | If `design-brief.md` is missing, infer stack from architecture rules and ask **one** focused question on brand direction before large UI work. When the stack is **React** and the work includes dashboards or analytics UI, read `references/react-analytics-ui.md` before implementing — default chart library: **Recharts**. ## When to use - New pages, layouts, or component libraries - Visual refresh of existing screens - Design-brief alignment or token application - Reducing "generic AI UI" (purple gradients, identical card grids) ## Workflow 1. **Audit** — screenshot or read existing UI patterns in the codebase; note framework (React, Vue, Blade, etc.). 2. **Anchor** — apply `design-brief.md` or establish a minimal direction (type scale, spacing, accent, motion level). 3. **Design** — composition, hierarchy, states (hover, focus, empty, error), responsive breakpoints. 4. **Implement** — minimal diff; match project file structure and naming. 5. **Verify** — keyboard focus, contrast, reduced-motion respect. See `references/anti-slop.md` and `references/checklist.md`. ## Principles - **One strong visual idea** per screen — not every trend at once. - **Typography carries hierarchy** — do not rely on color alone. - **Motion with purpose** — micro-interactions for feedback, not decoration loops. - **Accessible by default** — semantic HTML, labels, focus rings. ## Integration with ns-spec-driven When invoked from the SDD face skill, stay scoped to UI tasks — do not expand into requirements or task generation. ## Forbidden - Backend API design or database schema - Replacing `ns-reviewer` for MR gates - Ignoring project CSS/component conventions when they exist
© nextstage-brasil · Apache-2.0 · nextstage-brasil/skills