Skip to main content
skill CX Codex

ds-design — Claude Code skill: what it does, how to install

ds-design — a Claude Code skill for setting a distinct visual direction for frontend work. It runs when creating a page, app screen, or component, and when restyling an existing interface.

MIT 548 installs ★ 320 updated 2026-10-28

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add aicodeking/deepseek-stack --skill ds-design -a claude-code
Open on GitHub

What ds-design does

The skill examines the brief, project, stack, brand, and available images, then writes a short note defining the visual direction. Before components are written, it sets typography, colors, and spacing. If the brief is vague, it records an interpretation and continues.

Next, it lays out the interface, builds its states, adds motion where it serves a purpose, and checks accessibility. Contrast must reach 4.5:1, and touch targets must be at least 44px. The skill captures screenshots at 1440px and 390px wide, compares them with the direction note, and fixes the issues it finds.

What it helps with

  • set a visual direction for a new page
  • restyle a templated app screen
  • define type, color, and spacing tokens before building components
  • check interface states and accessibility

Example prompts for the agent

  • Create a profile page with a distinct visual direction using /ds-design.
  • Restyle this screen while keeping its content and behavior with /ds-design.
  • Build a new component and check its states using /ds-design.

How to install ds-design

1Skills CLI (Vercel)

npx skills add aicodeking/deepseek-stack --skill ds-design -a claude-code

2Manually: put the files in place

~/.claude/skills/ds-design/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ds-design/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about ds-design

How do I install ds-design in Claude Code?

Run npx skills add aicodeking/deepseek-stack --skill ds-design -a claude-code. The skill file is at ~/.claude/skills/ds-design/SKILL.md.

What does ds-design do?

It guides the creation or restyling of an interface around a defined visual direction. The skill sets design tokens, plans interface states, and checks screenshots at different widths.

How does ds-design check accessibility?

It sets a minimum contrast ratio of 4.5:1, requires visible focus, labeled fields, and touch targets of at least 44px. It also accounts for image alt text and reduced-motion preferences.

Source text

SKILL.md · MIT
---
name: ds-design
description: "Builds a frontend with a clear visual direction instead of the generic AI look. Use when you create a new page, app screen, or component, or restyle one that looks templated. Run as /ds-design."
---

Build a UI that does not look like the default output for any similar prompt.

## Steps

1. Read the brief and the project. Find the subject, the audience, the one action you want the user to take, the stack, the existing brand, and the images you actually have. If the brief is vague, write down how you interpret it in one line and continue.
2. Write a direction note of five lines or fewer before you write code. Include the purpose, the audience, the tone, the one memorable thing, and the mode (persuade, operate, or read). Take it from the subject's own world, not the usual look of its category.
3. Define the tokens before you write components:
   - Type: a display font and a body font that are clearly different. Do not use a default font for display. Use a 5-7 step scale, body text of 16px or more, and lines under 80 characters.
   - Color: 4-6 named hex values. Use one dominant color for large areas and one sharp accent for actions only.
   - Use a 4px or 8px spacing base, one or two radius values, and one shadow style or none.
4. Ask: "Would I make this plan for any similar prompt?" Change each part where the answer is yes.
5. Lay out the page with intent. Choose a density: airy for persuading, compact for tools. Use asymmetry or scale contrast where it serves the content. Use real copy and plausible data. Do not use lorem ipsum.
6. Use motion only where it does a job. Use one orchestrated reveal, plus feedback on user actions.
7. Build every state: hover, focus-visible, disabled, empty, loading, error, and long content.
8. Meet the accessibility floor. Contrast must be 4.5:1, focus rings must be visible, and fields must have labels. Touch targets must be at least 44px, images need alt text, and reduced motion must be respected.
9. Take screenshots at about 1440px and 390px wide. Check them against the banned defaults and the direction note. Fix the problems in one batch, then take new screenshots. Remove one decoration that does no work.

## Banned defaults

Use one of these only if the brief asks for it:

- Purple-blue gradients and decorative gradient washes.
- Inter, Roboto, or the system font as the display face.
- Emoji used as icons. Use one set of SVG icons.
- A centered hero with three identical cards below it.
- Glassmorphism or glow on every surface.
- Gray text on a gray background with low contrast.
- Stock copy such as "Unlock your potential" or "Seamless".
- All-caps eyebrow labels above every heading.
- The same radius and soft shadow on every card.

## Stop when

- The direction note and the tokens exist, and the code uses the tokens.
- The screenshots at both widths show no banned default and no horizontal scroll.
- All the states are built and the accessibility floor is met.
- The one memorable thing is visible in the screenshot.

## Rules

- When the brief specifies a font, color, or style, use it, even if it is on the banned list.
- A refinement keeps the identity of the UI. A redesign keeps its content and function.

© aicodeking · MIT · aicodeking/deepseek-stack

Similar skills

All skills for Frontend and UI →

From the same set29

The whole set →
ds-principles Provides engineering principles for design, debugging, and verification. The agent applies them during code structure choices, diff sizing, or when typing /ds-principles. CX Codex +1 557installs ds-blast-radius The ds-blast-radius Claude Code skill checks what a change might break beyond its diff, then tests a key safety claim by running code. Use it to inspect risky or untrusted changes before shipping. CX Codex +1 550installs ds-help ds-help — a Claude Code skill that picks the right deepseek-stack tool for a task and explains how the pack fits together. CX Codex +1 549installs ds-design-audit ds-design-audit audits an interface using evidence from screenshots and code, fixes the highest-impact issues, and verifies the outcome. Runs before shipping UI work or when a screen looks cluttered. CX Codex +1 548installs ds-review-loop ds-review-loop — a skill for Claude Code that runs an author and a reviewer in an iterative loop until they agree on the code changes. CX Codex +1 548installs ds-unslop This Claude Code skill rewrites prose and code comments in plain, specific English. It activates while editing replies, docs, READMEs, PR descriptions or commit messages, and on /ds-unslop. CX Codex +1 547installs ds-blueprint Defines types, signatures, and module boundaries before writing code bodies. It triggers on /ds-blueprint or when asked to design the structure first. CX Codex +1 546installs ds-ledger This Claude Code skill logs decisions during long or unattended work. It is triggered for multi-phase tasks, work that a person will review later, or with /ds-ledger. CX Codex +1 545installs

Project sponsors

Companies that keep this analytics open