prompt-template-generator

# Prompt Template Generator Turn any codebase into a **tailored prompt cookbook**: a single Markdown file of copy-paste-ready prompts (session kickoff, per-subsystem tasks, testing, bug fixes, optimization, deploy, feature/architecture/hotfix) where the project's real stack, paths, subsystems, and conventions are **already filled in**. The user copies a block, fills a couple of `[BRACKETS]`, and pastes it into Claude, Claude Code, or Cursor to start a task with full context loaded. This generalizes the hand-built "prompt template" documents developers make for a single project — but produced automatically for *any* project from its files. ## The one idea that matters Every template has two kinds of slots: - **Filled by you, from the analysis** — facts true for the whole project: name, stack, real source paths, subsystem names, test command, CI/deploy tooling, file-size/style conventions, the doc files that actually exist, and any standing user communication preferences. The user must never retype these. - **Left as `[BRACKETS]`** — per-task blanks: the specific feature, file, error message, component, or metric. A generic template leaves everything bracketed. This skill's output is valuable precisely because it already knows the project. If you ever write `[PROJECT_NAME]` or `[TECH_STACK]` into the output, stop — you have that fact; fill it in. ## Workflow Work in clear phases. ### Phase 1 — Locate the project Find the project root. It's usually an uploaded ...