菜单
Create production-grade frontend interfaces with design intelligence database (67 styles, 161 palettes, 57 fonts, 161 industry rules). TRIGGER: "build a landing page", "create a website", "design a UI", "frontend prototype". NOT FOR: web-design-review use cases.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Orchestrate the full AIDLC Autonomous Pipeline from a one-sentence requirement to a PR-ready delivery with TDD methodology. DDD drives judgment, SDD produces specs, TDD verifies delivery. Stages: Evaluate, Think, Plan, Build, Review, Test, Deliver, Reflect. Checkpoints on BLOCK or context limits. TRIGGER: "run pipeline", "autonomous pipeline", "pipeline for", "full pipeline". NOT FOR: single stages (use evaluate, deep-research, code-review, qa, deliver directly).
DDD-native autonomous dev loop — judge→execute→reflect on a SINGLE DDD via a bundled, decoupled engine (engine/artifact_cli.py, file-based .artifacts/ state, NO data.db, NO SwarmAI backend). Retains the moat: Gate-2 adversarial-before-commit + the 养成 ladder. DDD-native decouple of SwarmAI's s_autonomous-pipeline engine. TRIGGER: "ddd pipeline", "run the ddd loop", "build in this ddd". NOT FOR: SwarmAI's own multi-project pipeline (that's the native s_autonomous-pipeline).
Package a grown DDD into a distributable capability package — the last step of the DDD lifecycle (cultivate → version → DISTRIBUTE). Human-in-the-loop: reads the DDD's OWN declared reach (aim.json distribution block = the ceiling), confirms which declared target(s) to emit NOW, renders BOTH standard shapes on demand — an internal AIM capabilities package (Config+AIMBuild+agent-spec) and/or an Open-Plugins plugin (.plugin/plugin.json) — runs a fail-closed content-safety scan over the emitted tree, and returns the built package path. Never widens reach by inference; emit ≠ publish. TRIGGER: "distribute this ddd", "package ddd", "ship ddd to kiro/quick/claude code", "publish ddd", "make a plugin from this ddd". NOT FOR: creating/binding a DDD (s_ddd-manager); running the pipeline (s_ddd-pipeline); publishing content/media (s_ddd-pollinate).
Create, list, edit, rename, and delete DDD projects (Domain-Driven Design) — provisions the canonical six-section DDD structure. Each project gets 4 knowledge documents (PRODUCT.md, TECH.md, IMPROVEMENT.md, PROJECT.md) and an .artifacts/ directory for pipeline outputs. TRIGGER: "add project", "new project", "create project", "rename project", "create DDD". NOT FOR: radar-todo use cases.
Estimate token count for files using the bundled script. TRIGGER: "estimate tokens", "count tokens", "token usage", "context window size". DO NOT USE: for manual token math — always run the script.
Full SwarmAI release cycle: preflight checks, version bump, binary build, desktop package, smoke test, and GitHub publish. Supersedes s_release (which only does version bump + tag) by adding build/package/smoke stages. TRIGGER: "release", "cut release", "ship it", "发版". NOT FOR: s_swarm-build, s_release, s_swarm-hive use cases.
| name | frontend-design |
| description | Create production-grade frontend interfaces with design intelligence database (67 styles, 161 palettes, 57 fonts, 161 industry rules). TRIGGER: "build a landing page", "create a website", "design a UI", "frontend prototype". NOT FOR: web-design-review use cases. |
| version | 2.0.0 |
| tier | lazy |
This skill loads full instructions on activation. Read INSTRUCTIONS.md before proceeding.
TRIGGER: "build a landing page", "create a website", "design a UI", "frontend prototype", "interactive page", "HTML page", "web app mockup" DO NOT USE: for backend APIs (just code directly) or for reviewing existing UI (use web-design-review)
Before writing ANY frontend code, run the design system generator to get industry-specific style, color, typography, and anti-pattern recommendations:
python3 scripts/search.py "<product description>" --design-system -p "ProjectName" -f markdown
This is NOT optional. The database has 161 industry-specific reasoning rules that prevent generic AI aesthetics. Skip this step only if the user explicitly provides a complete design system (colors, fonts, style).