Skip to content

πŸŽ₯ Make videos programmatically with React

Skills: Restore stack design guidance

Jonny Burger627ea0d060f5
diff --git a/.agents/skills/gh-stack/references/stack-design.md b/.agents/skills/gh-stack/references/stack-design.md
index 5029e596df..1479b34fd3 100644
--- a/.agents/skills/gh-stack/references/stack-design.md
+++ b/.agents/skills/gh-stack/references/stack-design.md
@@ -20,12 +20,13 @@ means `unstack` and `init` again.
Decide the layers first, then write code into them:
```
-(main) <- todo-app/models <- todo-app/api <- todo-app/frontend
+(main) <- todo-app/models <- todo-app/api <- todo-app/frontend <- todo-app/integration
```
- `todo-app/models` β€” shared types and schema
- `todo-app/api` β€” routes that use the models
- `todo-app/frontend` β€” components that call the routes
+- `todo-app/integration` β€” tests exercising the whole feature
This is illustrative. Infer the stack topic and layer names from the actual task; do not reuse
`todo-app` or these layer names literally.
@@ -73,7 +74,7 @@ changes carry over to the new branch. Commit or stash first if you want the new
Add a branch when you start a **different concern that depends on what you have built so far**.
Signals:
-- Moving from backend to frontend, or from core logic to documentation or explicitly requested tests
+- Moving from backend to frontend, or from core logic to tests or documentation
- The next changes have a different reviewer audience
- The current branch's diff is already large enough to review on its own