design

Designs web interfaces through ranked visual boards, token contracts, and authorized implementation handoff.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill design-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/alvis/.agents/tree/main/plugins/web/skills/design
Command: npx skills add https://github.com/alvis/.agents --skill design-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Web design work often jumps straight from a vague brief to code, producing generic AI-looking layouts with no recorded rationale, no accessibility verification, and no clear ownership of who may edit production source. This Skill structures the entire flow: it captures a visual direction through rendered choice boards, records every decision in a design contract, and only routes implementation to a dedicated frontend-implementer after explicit sign-off. ## Core Features & Use Cases - Direction and area boards: Generates 3-5 ranked direction candidates and per-area variants as self-contained HTML boards, rendered and screenshotted in Chrome so choices are made visually, with a mix-and-match loop and quick mode for provisional auto-picks. - Surface-specific guidance: Loads dedicated subskill guidance for landing pages, blogs, dashboards, documentation, and onboarding, plus a facelift mode that preserves brand, content, and conversion paths. - Design contract and token system: Produces a design document covering two-tier light/dark color tokens, typography scale, spacing, radius roles, motion specs, and section separators that implementers consume instead of hardcoded values. - Independent evaluation: Runs a contrast protocol measuring rendered WCAG ratios in both modes, captures desktop and mobile evidence, and routes divergences back for up to three rework rounds. - Use Case: Redesign a marketing landing page: the Skill presents three rendered direction boards, captures your pick, generates ranked hero and pricing variants, then hands the signed-off contract to the implementer and verifies the built result against the design with measured contrast evidence. ## Quick Start Ask the agent to redesign your landing page using the design skill, for example: redesign the homepage at localhost:3000 with three variants per area and wait for my sign-off before implementing.

Frequently Asked Questions about design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I redesign a landing page with AI without getting generic results?

The Skill generates 3-5 materially distinct direction boards rendered as real HTML with your actual content, each ranked with rationale. You pick visually from screenshots, then per-area variant boards refine each section, so the result reflects explicit choices rather than default templates.

How does the design skill handle light and dark mode?

It defines a two-tier token system where components consume semantic --ui-* tokens fed by light and dark tier-1 values. Both modes are designed and contrast-verified with a rendered WCAG measurement script, never treated as an inverted afterthought.

Can the design skill edit my production source code directly?

No. Production source edits belong exclusively to the frontend-implementer role and only after explicit sign-off on the design contract. Without authorization, the Skill produces design artifacts and a context-complete handoff instead of editing application code.

Does the design workflow verify accessibility and contrast?

Yes. A contrast protocol measures rendered composited colors in the browser against WCAG AA thresholds (4.5:1 normal, 3:1 large text) in both light and dark modes. Keyboard focus, reduced-motion, responsive overflow, and touch target sizes are also verified before completion.

What is the difference between facelift mode and a full redesign?

Facelift mode preserves content meaning, brand intent, and conversion paths while modernizing the visual treatment, and adds critic and performance/accessibility lenses. A full redesign is free to replace the visual direction entirely through the standard direction board process.

When should I not use this design workflow?

Skip it for content writing, backend reporting, API implementation, or isolated logic fixes that merely appear on a designed surface. It is also blocked when no browser session is available for live visual work or when target and authorization cannot be resolved.