Skip to content
Back to search

cc-design

MarketplaceWorks with Claude CodeGitHub

High-fidelity HTML design and prototype guidance skill for AI agents

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/zeroz-lab-cc-design/badge.svg)](/listings/zeroz-lab-cc-design)

HTML

<a href="/listings/zeroz-lab-cc-design"><img src="/api/listings/zeroz-lab-cc-design/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Code

# 1. Add the cc-design marketplace
/plugin marketplace add ZeroZ-lab/cc-design

# 2. Install the plugin
/plugin install cc-design@cc-design

# 3. Reload plugins to activate
/reload-plugins

After installation, cc-design activates via `/cc-design:design` command.

Codex

# 1. Add the cc-design marketplace from GitHub
/plugin marketplace add ZeroZ-lab/cc-design

# 2. Install the plugin
/plugin install cc-design@cc-design

# 3. Reload plugins to activate
/reload-plugins

After installation, cc-design activates via `$cc-design` reference.

Example prompts

"Design a landing page for our SaaS product"
"Create a 10-slide pitch deck for the Q3 board meeting"
"Build an interactive prototype of the checkout flow"
"Create an interactive explainer showing how our RAG pipeline works"
"Make a comparison explainer for React vs Vue"
"Build a decision tree for tech stack selection"
"Animate this logo reveal with the Pentagram style"
"Export the deck as editable PPTX"

cc-design handles context gathering, design planning, quality checks, and verification — you approve the plan, it builds.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 13 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "cc-design",
  3. "owner": {
  4. "name": "ZeroZ-lab"
  5. },
  6. "plugins": [
  7. {
  8. "name": "cc-design",
  9. "source": "./plugins/cc-design",
  10. "description": "High-fidelity HTML design skill — slide decks, landing pages, interactive prototypes, animations, design systems, and more"
  11. }
  12. ]
  13. }
README.md · README · 160 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # cc-design
  2. **High-fidelity HTML design for Claude Code & Codex.**
  3. Slide decks, landing pages, interactive prototypes, interactive explainers, animations, design systems, and more — powered by structured design thinking and built-in quality guardrails.
  4. [Demo](https://cc-design-demo.vercel.app) · [Examples](./EXAMPLES.md) · [Report Bug](https://github.com/ZeroZ-lab/cc-design/issues)
  5. ---
  6. ## Quick Start
  7. ### Claude Code
  8. ```bash
  9. # 1. Add the cc-design marketplace
  10. /plugin marketplace add ZeroZ-lab/cc-design
  11. # 2. Install the plugin
  12. /plugin install cc-design@cc-design
  13. # 3. Reload plugins to activate
  14. /reload-plugins
  15. ```
  16. After installation, cc-design activates via `/cc-design:design` command.
  17. ### Codex
  18. ```bash
  19. # 1. Add the cc-design marketplace from GitHub
  20. /plugin marketplace add ZeroZ-lab/cc-design
  21. # 2. Install the plugin
  22. /plugin install cc-design@cc-design
  23. # 3. Reload plugins to activate
  24. /reload-plugins
  25. ```
  26. After installation, cc-design activates via `$cc-design` reference.
  27. ### Example prompts
  28. ```
  29. "Design a landing page for our SaaS product"
  30. "Create a 10-slide pitch deck for the Q3 board meeting"
  31. "Build an interactive prototype of the checkout flow"
  32. "Create an interactive explainer showing how our RAG pipeline works"
  33. "Make a comparison explainer for React vs Vue"
  34. "Build a decision tree for tech stack selection"
  35. "Animate this logo reveal with the Pentagram style"
  36. "Export the deck as editable PPTX"
  37. ```
  38. cc-design handles context gathering, design planning, quality checks, and verification — you approve the plan, it builds.
  39. ## Showcase
  40. [![Demo Gallery](./screenshots/previews/cc-design-home-preview.png)](./screenshots/previews/cc-design-home-preview.png)
  41. <p align="center">
  42. <a href="./screenshots/previews/cc-design-enterprise-preview.png"><img src="./screenshots/previews/cc-design-enterprise-preview.png" alt="Enterprise Hero" width="32%"></a>
  43. <a href="./screenshots/previews/cc-design-scifi-preview.png"><img src="./screenshots/previews/cc-design-scifi-preview.png" alt="Sci-Fi Website" width="32%"></a>
  44. <a href="./screenshots/previews/cc-design-tesla-preview.png"><img src="./screenshots/previews/cc-design-tesla-preview.png" alt="Tesla 3D" width="32%"></a>
  45. </p>
  46. <p align="center">
  47. <a href="./screenshots/previews/cc-design-aether-preview.png"><img src="./screenshots/previews/cc-design-aether-preview.png" alt="AETHER" width="32%"></a>
  48. <a href="./screenshots/previews/cc-design-glass-preview.png"><img src="./screenshots/previews/cc-design-glass-preview.png" alt="Glass Dashboard" width="32%"></a>
  49. <a href="./screenshots/previews/cc-design-banking-preview.png"><img src="./screenshots/previews/cc-design-banking-preview.png" alt="Banking App" width="32%"></a>
  50. </p>
  51. ## Capabilities
  52. | Category | What you get |
  53. |---|---|
  54. | **Design outputs** | Landing pages, slide decks, interactive prototypes, interactive explainers (flow, compare, decision tree), wireframes, animations, design systems, motion studies |
  55. | **Design thinking** | 8-layer framework (Goal → Validation), 10 core principles, 20 philosophy schools |
  56. | **Brand cloning** | Progressive loading of 68+ brand design systems from [getdesign.md](https://getdesign.md) |
  57. | **Quality guardrails** | Always-loaded `core-constraints.md` layer (Iron Law + 12-item anti-slop quick-ref + delivery checklist), typography system, spacing scale, mandatory screenshot verification |
  58. | **Variations** | 3+ design directions across layout, interaction, visual intensity, and motion |
  59. | **Export** | PDF (multi-file + single-file), PPTX (image + editable), MP4 video, inline HTML |
  60. | **Audio** | Dual-track audio (SFX + BGM), 37 SFX catalog, ffmpeg mixing |
  61. | **Design review** | 5-dimension scoring: philosophy, hierarchy, craft, functionality, originality |
  62. | **Animation** | Stage+Sprite timeline engine, easing library, Seek-First numerical verification (`__seek` + `getComputedStyle`), signal protocol, pitfall guardrails |
  63. | **Prototyping** | React + Babel inline JSX, device frames (iOS, Android, macOS, browser) |
  64. ## Design Styles
  65. Mention a philosophy school to set the direction:
  66. ```
  67. "Use the Pentagram style for this infographic"
  68. "Apply Experimental Jetset minimalism to this poster"
  69. "Mix Takram restraint with Locomotive motion for the hero"
  70. ```
  71. 20 schools across 5 traditions — Information Architects, Motion Poets, Minimalists, Experimental Vanguard, Eastern Philosophy. See `references/design-styles.md`.
  72. ### Brand Style Cloning
  73. Mention a brand name to load its design system:
  74. ```
  75. "Create a pricing page with Stripe's aesthetic"
  76. "Notion-style kanban board"
  77. "Mix Vercel's minimalism with Linear's purple accents"
  78. ```
  79. ## How It Works
  80. ```
  81. Understand → Route → Plan → Approve → Build → Verify → Deliver
  82. ```
  83. 1. **Understand** — cc-design asks targeted questions to lock the output type, audience, and constraints
  84. 2. **Plan** — presents a visible execution plan with goals, facts, and assumptions
  85. 3. **Approve** — you approve before any code is written
  86. 4. **Build** — per-section preview pattern; you approve section by section
  87. 5. **Verify** — three-phase self-check (structural, visual, design excellence)
  88. 6. **Deliver** — screenshot-verified artifact ready to use
  89. Key behavioral guarantees:
  90. - Never builds without an approved plan
  91. - Never delivers without screenshot verification
  92. - Never uses AI slop patterns (banned gradients, emoji spam, generic layouts)
  93. - Follow-ups and minor edits skip the full discovery flow
  94. ## Optional Dependencies
  95. Core installation has no extra dependencies. For export features:
  96. ```bash
  97. # Playwright browser (for export and verification)
  98. npx playwright install chromium
  99. # Video and audio export
  100. brew install ffmpeg # macOS
  101. sudo apt install ffmpeg # Ubuntu/Debian
  102. choco install ffmpeg # Windows
  103. ```
  104. ## Platform Integration
  105. | Platform | Activation | Integration |
  106. |---|---|---|
  107. | **Claude Code** | `/design` command | Commands + SKILL.md |
  108. | **Codex / OpenAI** | `$cc-design` reference | `agents/openai.yaml` |
  109. ## Contributing
  110. 1. Fork the repo, create a feature branch
  111. 2. Keep `SKILL.md` under 200 lines — move technical content to `references/`
  112. 3. Add new references to `load-manifest.json` and the routing table in `SKILL.md`
  113. 4. Run `node scripts/lint-load-manifest.mjs` and `node scripts/generate-bundle-catalog.mjs`
  114. 5. If changing first-turn behavior: update `VERSION`, `SKILL.md`, `README.md`, `references/workflow.md`, then run `./scripts/check-behavior-contract.sh <base-ref>`
  115. ## License
  116. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.