claude-design

Translate design briefs into local HTML artifacts in CLI/API workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/HugoAlmeidaMoreira/zeus-agent --skill claude-design-hugoalmeidamoreira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-design
Source: https://github.com/HugoAlmeidaMoreira/zeus-agent/tree/main/skills/creative/claude-design
Command: npx skills add https://github.com/HugoAlmeidaMoreira/zeus-agent --skill claude-design-hugoalmeidamoreira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates Claude Design workflows into local HTML artifact generation within CLI/API contexts, enabling design work without the hosted Claude Design UI and its toolchain. It preserves design process and taste while removing hosted-tool plumbing.

Core Features & Use Cases

  • Process-led design for local HTML artifacts: landing pages, decks, prototypes.
  • Scope briefs, gather context, generate variants, and verify artifacts in a CLI/API workflow.
  • Use cases include rapid prototyping, design-system previews, and artifact generation for demos or documentation.

Quick Start

Provide a design brief and I will produce a complete local HTML artifact (landing page, deck, or prototype) that matches your context.

Frequently Asked Questions about claude-design

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

FAQPage Schema
How do I generate HTML landing pages from a design brief in a CLI workflow?▼

Generating HTML landing pages from a design brief in a CLI workflow involves scoping the brief, gathering context, generating variants, and verifying the output as self-contained local HTML artifacts.

What is the process for creating local HTML prototypes without a hosted design UI?▼

The process for creating local HTML prototypes without a hosted design UI applies a multi-step design workflow to gather context, scope briefs, generate variants, and verify self-contained artifacts directly in CLI/API environments.

Can I use CLI workflows to produce design-system previews and self-contained HTML decks?▼

Yes, CLI workflows support producing design-system previews and self-contained HTML decks by translating design briefs into local HTML artifacts for demos, documentation, and rapid prototyping.

Does generating local HTML artifacts require any external design tool dependencies?▼

Generating local HTML artifacts requires no external design tool dependencies, operating entirely within CLI/API contexts to preserve design process and taste without hosted-tool plumbing.

When should I use a CLI-based HTML artifact generator instead of a hosted design platform?▼

Use a CLI-based HTML artifact generator instead of a hosted design platform when stakeholders need rapid, self-contained prototypes and design-system explorations within local API or CLI workflows without UI hosting.

Why do my design prototypes need variant generation and context gathering before coding HTML?▼

Design prototypes need variant generation and context gathering before coding HTML to ensure the final local artifacts accurately match the scoped brief and maintain high design taste standards.