CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-05-05 05:05:08 +02:00
Code Issues Packages Projects Releases Wiki Activity

feat: integrate /design-html into design skill pipeline

Browse Source 
- design-shotgun: Step 6 option B now chains to /design-html
- design-consultation: suggests /design-html after shipping DESIGN.md
  (conditional on screen-level output, not tokens-only)
- plan-design-review: expanded chaining to include /design-shotgun
  and /design-html alongside review skills

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-03-29 22:54:41 -07:00
parent e6d5c24363
commit 38e9846d44
6 changed files with 28 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
design-consultation/SKILL.md
+4
View File
@@ -957,6 +957,10 @@ List all decisions. Flag any that used agent defaults without explicit user conf
- B) I want to change something (specify what)
- C) Start over
After shipping DESIGN.md, if the session produced screen-level mockups or page layouts
(not just system-level tokens), suggest:
"Want to see this design system as working Pretext-native HTML? Run /design-html."
---
## Important Rules
design-consultation/SKILL.md.tmpl
+4
View File
@@ -413,6 +413,10 @@ List all decisions. Flag any that used agent defaults without explicit user conf
- B) I want to change something (specify what)
- C) Start over
After shipping DESIGN.md, if the session produced screen-level mockups or page layouts
(not just system-level tokens), suggest:
"Want to see this design system as working Pretext-native HTML? Run /design-html."
---
## Important Rules
design-shotgun/SKILL.md
+1 -1
View File
@@ -723,7 +723,7 @@ If standalone, offer next steps via AskUserQuestion:
> "Design direction locked in. What's next?
> A) Iterate more — refine the approved variant with specific feedback
> B) Implement — start building from this design
> B) Finalize — generate production Pretext-native HTML/CSS with /design-html
> C) Save to plan — add this as an approved mockup reference in the current plan
> D) Done — I'll use this later"
design-shotgun/SKILL.md.tmpl
+1 -1
View File
@@ -283,7 +283,7 @@ If standalone, offer next steps via AskUserQuestion:
> "Design direction locked in. What's next?
> A) Iterate more — refine the approved variant with specific feedback
> B) Implement — start building from this design
> B) Finalize — generate production Pretext-native HTML/CSS with /design-html
> C) Save to plan — add this as an approved mockup reference in the current plan
> D) Done — I'll use this later"
plan-design-review/SKILL.md
+9 -1
View File
@@ -1223,10 +1223,18 @@ After displaying the Review Readiness Dashboard, recommend the next review(s) ba
**If both are needed, recommend eng review first** (required gate).
**Recommend design exploration skills when appropriate** — /design-shotgun and /design-html
produce design artifacts (mockups, HTML previews), not application code. They belong in
plan mode alongside reviews. If this design review found visual issues that would benefit
from exploring new directions, recommend /design-shotgun. If approved mockups exist and
need to be turned into working HTML, recommend /design-html.
Use AskUserQuestion to present the next step. Include only applicable options:
- **A)** Run /plan-eng-review next (required gate)
- **B)** Run /plan-ceo-review (only if fundamental product gaps found)
- **C)** Skip — I'll handle reviews manually
- **C)** Run /design-shotgun — explore visual design variants for issues found
- **D)** Run /design-html — generate Pretext-native HTML from approved mockups
- **E)** Skip — I'll handle next steps manually
## Formatting Rules
* NUMBER issues (1, 2, 3...) and LETTERS for options (A, B, C...).
plan-design-review/SKILL.md.tmpl
+9 -1
View File
@@ -441,10 +441,18 @@ After displaying the Review Readiness Dashboard, recommend the next review(s) ba
**If both are needed, recommend eng review first** (required gate).
**Recommend design exploration skills when appropriate** — /design-shotgun and /design-html
produce design artifacts (mockups, HTML previews), not application code. They belong in
plan mode alongside reviews. If this design review found visual issues that would benefit
from exploring new directions, recommend /design-shotgun. If approved mockups exist and
need to be turned into working HTML, recommend /design-html.
Use AskUserQuestion to present the next step. Include only applicable options:
- **A)** Run /plan-eng-review next (required gate)
- **B)** Run /plan-ceo-review (only if fundamental product gaps found)
- **C)** Skip — I'll handle reviews manually
- **C)** Run /design-shotgun — explore visual design variants for issues found
- **D)** Run /design-html — generate Pretext-native HTML from approved mockups
- **E)** Skip — I'll handle next steps manually
## Formatting Rules
* NUMBER issues (1, 2, 3...) and LETTERS for options (A, B, C...).