web-design
Apply a brand's defined visual system to a real, conversion-focused website — designing and building it in custom code, with real copy given its proper emphasis. Use when the user mentions 'website design,' 'design my site,' 'build a landing page,' 'homepage,' 'marketing site,' 'product page,' 'pricing page,' 'redesign our website,' 'hero section,' or wants to ship a site. This is where the approved identity becomes a live, shipped surface — not a mockup, working code.
zstvns · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add zstvns/design-skills --skill web-design技能说明
name: web-design description: "Apply a brand's defined visual system to a real, conversion-focused website — designing and building it in custom code, with real copy given its proper emphasis. Use when the user mentions 'website design,' 'design my site,' 'build a landing page,' 'homepage,' 'marketing site,' 'product page,' 'pricing page,' 'redesign our website,' 'hero section,' or wants to ship a site. This is where the approved identity becomes a live, shipped surface — not a mockup, working code." metadata: version: 1.7.1
Web Design
You apply a brand's defined visual system to a live website and ship the code — designing and building at the same time, in custom code. This is the first Application skill: the color roles, type rules, motif, and signature element from creative-direction become a real conversion surface, built around real copy.
Read design-principles first. This skill is where its rules meet a browser: hierarchy is the job, restraint protects the message, contrast-not-competition, "state why or the default stands." Most of what separates a designed site from an assembled one is here.
Position in the sequence: after
creative-direction(the system) andlogo-design(the mark), the first of the Application skills. It consumes the identity; it does not define one. Custom code is the medium — this skill builds bespoke HTML/CSS (and the project's framework if one exists), not Webflow or Framer.
Front-Door Diagnosis — Settled Brand, or Rework?
Before anything, diagnose where the brand is. Open .agents/design.md, .agents/brand.md, and .agents/product-marketing.md — by this stage all three should exist. Then ask one question:
Are we applying a settled brand, or reworking one from scratch?
Four routes, in the plain language a client uses:
- Refine the existing elements ("we like our brand, the site's just weak") → Optimization. Proceed — this is the skill's home.
- Light creative direction ("keep the name and logo; new type, color, graphics") → light Evolution. Proceed only if
design.mdalready records those new choices; if it doesn't, the deltas are undefined → route back tocreative-directionfor the light pass first. - Full rebrand ("new everything") → Revolution → stop and route back to
creative-direction. Do not design a site on an undefined system. - Heavy Evolution (the core system is genuinely changing) → route back too.
Routing back holds even if the user arrives with a logo already — a mark without the system around it isn't enough to build a coherent site; push them back. The rule of thumb: route back whenever the visual system is being defined or changed; proceed only when it's settled.
If .agents/design.md is missing, that is the "go back" signal — there's no system to apply yet. Route to creative-direction. If .agents/product-marketing.md is missing or the page has no copy, route to the marketing library's copywriting / website-copy first: the site is built around the copy, never the reverse.
Copy First — the System Is the Stage, Not the Show
The single most important input is the words. Read the copy in .agents/product-marketing.md (audience, voice, positioning, and the page copy itself). The designer's job is to take what's being said and give it proper emphasis, joy, and delight — not to build a template and pour copy into the gaps. Wireframe-first thinking is the fastest tell of an assembled page. If the copy isn't written, get it written first.
Size follows the content, not a template. The headline scale is dictated by what the copy actually is — a hook line that's meant to be completed by a second line (a typed continuation, a rotating phrase) means a smaller headline, not a giant one-liner sitting alone. A hero with a lone hook and no follow-through reads as unfinished. Design the content you have; don't force it into a fixed hero shell.
The visual system serves the message. Design serves the message. The site is the stage; the copy is the show.
When You Reference an Existing Site, Be Faithful to It
Redesigning a live site, or building "like" a reference? Then look at what's actually happening on that site — don't approximate it from memory. Full method in references/faithful-replication.md.
- Port every section. Inventory the source top to bottom and carry each section over — right copy, right order. A "redesign" that silently drops the terminal-signup, the capabilities section, or the orbital product visual isn't a redesign, it's a different site.
- Match the action the site is driving. Read what it's encouraging the visitor to do and reproduce that mechanism, not just the words. If the hero invites you to enter a URL and get a free plan, the redesign's hero needs that URL field and that button — the primary action is the point of the page.
- Pull the real assets. Integration/partner logos are real and available (a Relume or brand-asset library, the source's own markup, a brand-SVG source like simple-icons). Use the real logos — never substitute an icon-plus-text stand-in, and never ship a low-contrast logo strip.
- Tell the visual's real story. A product illustration has to communicate what the product does — e.g., an orbital that shows work (writing, optimizing, launching, researching) looping around the agent, not decoration that misses the point.
You are not producing a comp for someone else to implement. You design by building — the design decisions are the code. Output real, production front-end:
- Match the project's stack if one exists (Next.js / Tailwind / shadcn per the repo's conventions); otherwise ship clean, self-contained HTML/CSS. Framework-agnostic by default.
- No Webflow, no Framer. This skill exists because the work has moved to custom code — bespoke markup you can push as far as the craft demands,