design-html
Skill9 starsChanged 3 months agoMITView on GitHub
デザインSSOT JSONからドキュメント・共有用の静的HTMLを生成しdoc/input/design/html/に保存する。SSOTだけ先にある場合の視覚的確認や共有に使う。
27 other projects use a version of this.
Adopted by
Most recently taken up by
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- timurgaleev/vibestacktheir own version, first seen Nov 8, 2026
- trungtm78/ClaudeSkillstheir own version, first seen Oct 25, 2026
- Marco-Satis/claude-setuptheir own version, first seen Oct 20, 2026
- ignavm1/claude-skillstheir own version, first seen Oct 13, 2026
- leishifu666/skillstheir own version, first seen Oct 9, 2026
Used with
Projects with it also use plan-tune, ios-clean and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ShreyRaviSkillplan-tune
Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.
Also in 9 projects that use this
Saqlain-811Skillios-clean
Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)
Also in 5 projects that use this
Saqlain-811Skillios-fix
Autonomous iOS bug fixer. (gstack)
Also in 5 projects that use this
ShreyRaviSkilllanding-report
Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)
Also in 8 projects that use this
timurgaleevSkilldocument-generate
Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.
Also in 7 projects that use this
bastosSkillios-design-review
Review iOS app UI/UX design quality using Apple's design principles and the Liquid Glass-era design language from WWDC25/26. Use when asked for a design review, UX critique, visual design assessment, or evaluation of an app's interface quality, design intent, alignment with the new Apple design system, or usability. Triggers: "design review", "UX review", "visual design critique", "review the UI", "does this design work", "evaluate this interface", "design feedback", "Liquid Glass review".
Also in 5 projects that use this
- +1 more from Saqlain-811
- +5 more from ShreyRavi
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- garrytan/gstack★ 141ksame name
- podo/design-agent-skills★ 32same name
- timurgaleev/vibestack★ 8same name
- GTMify/claude-skills-starter★ 2same name
- abrb-dev/prime-workflow★ 1same name
- aryaniyaps/dot-ai★ 1same name
- chloropine/cgstack★ 1same name
- IyedBecheikh/bstack★ 1same name
- jpoindexter/theft-kit★ 1same name
- leishifu666/skills★ 1same name
17 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- accessibility-engineerSkill
- agent-browserSkill
- animation-principlesSkill
- architecture-expertSkill
- art-directionSkill
- auto-bugSkill
- auto-buildSkill
- auto-designSkill
- auto-taskSkill
- basic-reviewSkill
- biz-researcherSkill
- bug-fixSkill
- bug-investigateSkill
- bug-newSkill
- bug-proposeSkill
- build-context-siteSkill
- creative-coderSkill
- deep-reviewSkill
- design-assembleSkill
- design-componentsSkill
- design-critiqueSkill
- design-mockSkill
- design-ssotSkill
- design-uiSkill
- developer-specialistSkill
- docs-reverseSkill
- experience-planSkill
- frontend-implementationSkill
- image-prepSkill
- judgment-harnessSkill
- keyboard-shortcutsSkill
- manual-genSkill
- manual-guideSkill
- official-source-firstSkill
- pairSkill
- persona-designerSkill
- project-design-languageSkill
- project-initSkill
- proposition-reviewerSkill
- proto-loopSkill
- proto-mediumSkill
- pr-respondSkill
- repo-tourSkill
- security-expertSkill
- sensory-designSkill
- session-endSkill
- session-startSkill
- setupSkill
- task-detailSkill
- task-listSkill
- task-runSkill
- template-feedbackSkill
- template-inboxSkill
- testingSkill
- ui-designerSkill
- usability-psychologistSkill
The file
Files
[デザイン] (任意)SSOT → 静的HTML を生成し、doc/input/design/html/ に保存
コマンド: /design-html [$PAGE_KEY]
設計JSON(SSOT)から静的HTMLを生成し、doc/input/design/html/ に保存する。
いつ使う?(位置づけ)
- ドキュメント共有/レビュー用に「ブラウザで見られる見た目」が欲しいとき
- 実装スタックに依存しない形で、UIの骨格・トークン反映を目視確認したいとき
/design-mockで1枚ペラHTMLを作った後、ページ単位でイメージ確認したいとき/design-ssot・/design-mockのいずれかで SSOT が揃っている前提(このコマンドはSSOTを作らない)
次に何をする?
- 見た目の調整が必要なら、HTMLの差分/変更点を根拠に SSOT(tokens/components/context)へ反映する。 ⚠️ 反映の前に、SSOTの差分(どのキーをどの値に変えるか)を見せて合意を得る(ADR-027)
- 実装に進むなら
/design-ui→/design-components→/design-assemble(READMEのフローに合流)
旧
/design-splitの役割はこのスキルが担う:/design-mockが生成したSSOTからページ単位HTMLを生成するため、1枚ペラHTMLを手動で分割する必要はない
見た目の基準(ビューポート)について
- まず
doc/input/rdd.mdの「ターゲット表示環境(事実)」を参照し、生成HTMLの確認は そのビューポートを基準に行う - 未記入の場合は、以下を 推奨デフォルトとして仮置きする:
- desktop: 1440x900
- mobile: 390x844
- tablet: 834x1194
入力
- $PAGE_KEY(任意): 画面キー(
doc/input/design/design_context.jsonのpages[].key)- 省略時: 全ページを生成する(複数ページ対応の既定)
出力(差分のみ)
doc/input/design/html/{page}.html(tokens/variants/copy反映、外部依存なしで再現)
仕様
- 入力となるJSON(
doc/input/design/design-tokens.json,doc/input/design/components.json,doc/input/design/design_context.json)が存在する前提(通常は/design-ssotの成果物) doc/input/design/copy.json(文言のSSOT。一字一句固定)が存在する前提(不足時は推測で補わず停止)doc/input/design/assets/assets.jsonが存在する場合は必ず参照し、画像アセットを反映する(baseDir配下の相対パス)assets.jsonにstatus: "failed"がある場合は、必ずユーザーに不足(動画/画像等)を報告し、手元提供またはFigma Export設定の依頼をして停止する(推測で代替しない)
- React/Vue 等の実装に依存しない生成
- 画像は相対またはデータURIで完結
- RDD準拠のスタイルのみ(tokens必須)
- ここで停止
ゲート
- 主要ブレイクポイントでレイアウト崩れなし(簡易スナップ)
- tokens外の値(magic number)が混入していない
copyKeyの不足0件(design_context.jsonの参照がcopy.jsonで解決できる)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

