workflow-template-extractor
Workflow: Template Extractor (Real Project → Template)
Goal: Turn a real project into a shareable, runnable template in templates/ with minimal manual cleanup.
This is intended for “proven projects” you want to reuse as a baseline for future builds.
Input (pass paths only)
source_repo_root: Path to the real projecttarget_repo_root: Ship Faster repository root (wheretemplates/lives)run_dir:runs/template-extractor/active/<run_id>/extract_spec.md: What to keep/remove/generalize (brand, copy, assets, integrations, auth gates)
Output (persisted)
03-plans/extract-plan.md05-final/extract-summary.mdtemplates/<NNN>-<slug>/(runnable)
Workflow
0) Initialize
- Create
run_dir. - Decide
<slug>and<NNN>(next available template number). - Copy
source_repo_root→templates/<NNN>-<slug>/(no build outputs, no caches).
1) De-secrets + de-brand
Must do:
- Remove secret values from all files (
.env*, config, hard-coded tokens). - Replace project IDs (Stripe price IDs, Supabase URLs/keys, webhook secrets) with env var keys.
- Replace branding (names/domains/logos) with neutral placeholders unless the template is intentionally branded.
2) Normalize template entry docs
Required files:
README.md(5‑minute runnable).env.local.example(keys only)metadata.json(name + description)
Recommended:
- Ensure scripts exist for
dev,build,start - If lint/typecheck/format are missing and the repo is TS-heavy, add minimal guardrails (avoid heavy governance)
3) Verification
Document in 05-final/extract-summary.md:
- install works
devstartsbuildsucceeds (or clearly document why it can’t without credentials)
Constraints
- Never commit secret values.
- Extraction should be “copy + cleanup”, not a refactor project.
More from heyvhuang/ship-faster
mcp-supabase
Execute database operations via Supabase MCP (query/write/migration/logs/type generation). Triggers: query/statistics/export/insert/update/delete/fix/backfill/migrate/logs/alerts/type generation. Does not trigger for: pure architecture discussion or code planning. Write operations require confirmation; UPDATE/DELETE without WHERE is refused.
76tool-ast-grep-rules
Write AST-based code search and rewrite rules using ast-grep YAML. Create linting rules, code modernizations, and API migrations with auto-fix. Use when the user mentions ast-grep, tree-sitter patterns, code search rules, lint rules with YAML, AST matching, or code refactoring patterns.
55skill-evolution
Global evolution system for ship-faster skills. Uses hooks to capture context, failures, and session summaries, then generates patch suggestions (no auto edits) via skill-improver. Use when you want the skills to self-improve safely and continuously.
53review-doc-consistency
Documentation consistency reviewer that checks alignment between code implementation and documentation. Use when user requests reviewing documentation vs code consistency, checking if README/docs are outdated, verifying API documentation accuracy. Applicable for (1) reviewing README vs implementation consistency (2) checking if docs/ directory content is outdated (3) verifying API/config documentation accuracy (4) generating documentation consistency reports. Trigger words include doc review, documentation consistency, check outdated docs, verify docs.
53stripe
Billing and payment operations for Stripe: customers, products, prices, invoices, payment links, subscriptions, refunds, disputes, balance. Triggers: create customer, create product, create invoice, generate payment link, query transactions, process refunds, manage subscriptions, view disputes, check balance. Money operations require confirmation. MCP is optional — works with Dashboard/CLI too.
53tool-design-style-selector
Use when you need to define or converge a project's visual direction. Scan project documentation to identify intent, then produce a design-system.md (either preserve existing style or pick from 30 presets). Triggers: design system, design spec, UI style, visual style, design tokens, color palette, typography, layout. Flow: scan → intent → (gate) preserve vs preset → deploy design-system.md after confirmation → (default) implement UI/UX per design-system.md (plan first, then execute).
52