agentleFS
Sign inStart free
HeyvhuangHeyvhuang/ship-faster/skills/_archive/workflow-template-seeder/SKILL.md

workflow-template-seeder

Skill337 starsChanged 10 months agoMITView on GitHub

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.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use skills as the primary execution engine

    line 11
  2. Distinctive:

    Treat templates as “frozen outputs” (examples + regression references), not the mainline product

    line 12
  3. Very specific:

    Write 01-input/context.json for this workflow:

    line 37
  4. Very specific:

    Create a clean Next.js baseline in the new template directory, then run the same “Ship Faster chain” against it.

    line 46
  5. Very specific:

    If any steps are skipped (e.g., no DB/billing), record why in 00-index.md / 05-final/template-summary.md

    line 51
  6. Very specific:

    Remove secrets; only keep env key names in .env.local.example

    line 56
  7. Very specific:

    Ensure metadata.json is accurate and generic (no private branding unless intended)

    line 62
  8. Distinctive:

    Do not create a “kitchen sink” template.

    line 73
  9. Distinctive:

    Avoid large refactors; prefer small, clean baselines that are easy to adapt.

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free