workflow-template-seeder
Seed a new runnable template under templates/NNN-slug/ from a short spec by chaining existing skills (intake → ship-faster stages) while keeping it clean and shareable (no secrets, minimal scope). Use when creating a new template quickly.
Best use case
workflow-template-seeder is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Seed a new runnable template under templates/NNN-slug/ from a short spec by chaining existing skills (intake → ship-faster stages) while keeping it clean and shareable (no secrets, minimal scope). Use when creating a new template quickly.
Teams using workflow-template-seeder should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/workflow-template-seeder/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How workflow-template-seeder Compares
| Feature / Agent | workflow-template-seeder | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Seed a new runnable template under templates/NNN-slug/ from a short spec by chaining existing skills (intake → ship-faster stages) while keeping it clean and shareable (no secrets, minimal scope). Use when creating a new template quickly.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Workflow: Template Seeder (Skills → Templates) Goal: Turn a short template spec into a runnable, documented template under `templates/`. This workflow is **skills-first**: - Use skills as the primary execution engine - Treat templates as “frozen outputs” (examples + regression references), not the mainline product ## Input (pass paths only) - `repo_root`: Ship Faster repository root (where `templates/` lives) - `run_dir`: `runs/template-seeder/active/<run_id>/` - `template_spec.md`: One-page spec (what it is, target user, core pages, required integrations) ## Output (persisted) - `03-plans/template-plan.md` - `05-final/template-summary.md` - A new template directory: `templates/<NNN>-<slug>/` containing: - `README.md` (5‑minute runnable) - `.env.local.example` (keys only) - `metadata.json` ## Workflow ### 0) Initialize 1. Create `run_dir`. 2. Determine: - `<slug>` from spec (kebab-case) - `<NNN>` as the next available number under `templates/` (001, 002, …) 3. Write `01-input/context.json` for this workflow: - `entry_type: idea` - `repo_root: <path-to-new-template-dir>` - `need_deploy: false` (templates should not auto-deploy) - Enable only the integrations required by the spec (DB/billing/SEO) ### 1) Generate the template baseline (prefer clean + minimal) Preferred path: - Create a clean Next.js baseline in the new template directory, then run the same “Ship Faster chain” against it. Execution order (recommended): 1. `workflow-project-intake` (optional if spec is already complete) 2. `workflow-ship-faster` with the template directory as `repo_root` 3. If any steps are skipped (e.g., no DB/billing), record why in `00-index.md` / `05-final/template-summary.md` ### 2) Template hardening (shareable output) Must do: - Remove secrets; only keep env **key names** in `.env.local.example` - Ensure `README.md` includes: - Node version - install + dev - required env keys - optional integrations notes - Ensure `metadata.json` is accurate and generic (no private branding unless intended) ### 3) Verification At minimum (document results in `05-final/template-summary.md`): - install works - `dev` starts - `build` succeeds (if the template requires external credentials, document the minimal required keys) ## Constraints - Do not create a “kitchen sink” template. - Avoid large refactors; prefer small, clean baselines that are easy to adapt. - Never commit secrets.
Related Skills
workflow-ship-faster
Ship Faster end-to-end workflow for small web apps (default: Next.js 16.1.1): idea/prototype → foundation gate → design-system.md → lightweight guardrails + docs → feature iteration → optional Supabase + Stripe → optional GitHub + Vercel deploy → optional AI-era SEO (sitemap/robots/llms.txt). Resumable, artifact-first under runs/ship-faster/ (or OpenSpec changes/). Trigger: ship/launch/deploy/production-ready MVP.
workflow-project-intake
Use when you need to clarify requirements and route to the right workflow (idea → executable input). Project intake + routing: help the user brainstorm and clarify intent, persist goal/context artifacts, then dispatch to the right workflow or step skill. Default route is workflow-ship-faster (Next.js 16.1.1) for idea/prototype→launch. Triggers: project kickoff, requirements clarification, brainstorm, ideas, discovery, intake.
workflow-feature-shipper
Use when you need to ship a single PR-sized feature end-to-end (plan -> implement -> verify) with artifacts. Ship core product features quickly in a Next.js codebase: turn a feature idea into an executable plan, implement in PR-sized slices, and keep artifacts under runs/ (or OpenSpec changes/ when available). Supports plan-only mode for early scoping. For prototype UI work, include a demo-ready wow moment (animation/micro-interaction) by default unless user opts out.
workflow-creator
Create workflow-* skills by composing existing skills into end-to-end chains. Turns a user idea into a workflow_spec.md SSOT (via workflow-brainstorm), discovers available skills locally + from skills.sh, and generates a new workflow-<slug>/ skill package. Use when you want to design a new workflow, chain multiple skills into a flow, or turn scattered atomic skills into a resumable plan-then-confirm workflow.
workflow-brainstorm
Use when you need to turn a vague idea into a confirmed design spec before implementation (new feature/component/behavior change). First check project context, then ask one question at a time, provide 2-3 options with trade-offs, finally output design in segments (~200-300 words each) with confirmation after each. Triggers: brainstorm, clarify idea, design spec, refine concept, requirement clarification.
workflow-template-extractor
Extract a shareable runnable template under templates/NNN-slug/ from a real project: copy + de-brand + remove secrets + add env examples + docs, with minimal refactors. Use when you have a working project and want to turn it into a template.
workflow-execute-plans
Execute written implementation plans: first read and critically review the plan, then implement in small batches (default 3 tasks), produce verification evidence per batch and pause for feedback; must stop immediately and ask for help when blocked/tests fail/plan unclear. Trigger words: execute plan, implement plan, batch execution, follow the plan.
template-skill
Replace with description of the skill and when Claude should use it.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
turbo-sdk
Complete Arweave Turbo ecosystem including client SDKs, core upload infrastructure, payment service backend, and CLI tools for permanent decentralized storage
terraform-best-practices
Comprehensive best practices for Terraform infrastructure as code from Anton Babenko's community guide