Stacks
Stacks are human-facing composition guides for recurring delivery types.
They do not replace the runtime skill layer. They show which combinations make sense when the same delivery pattern keeps appearing in real work.
Current catalog
| Stack | Description | Uses |
|---|---|---|
frontend-feature | Ship product-facing frontend work with design, React architecture, and writing polish | designer, react-architect, humanizer, knowledge-writer |
landing-page | Build a landing page with copy, design, semantic structure, and prompt support | sales-copywriter, designer, html-architect, humanizer, prompt-engineer |
landing-page-react | Build a React-based landing page with conversion design, sales copy, and frontend structure | designer, sales-copywriter, humanizer, react-architect |
repository-docs | Improve repository docs, standards, and public-facing structure | knowledge-writer, humanizer, html-architect, designer |
publication | Distill source material into reusable published skills and stacks | knowledge-writer, prompt-engineer, humanizer |
When to create a stack
Create a stack when:
- the same combination of skills keeps happening
- the order of use matters
- the delivery type is stable enough to deserve a reusable guide
Do not create a stack just because two skills can technically work together.
If the reusable unit is still a single specialist, keep it as a skill. If the reusable unit is a sequence of specialists around one delivery, that is a stack.