aitk-promptslisted

# Prompts Read `docs/prompts.md` for system overview and categories before editing. ## Structure - All-caps H1 title (`# BASH SCRIPT ARCHITECT`), all-caps H2 sections (`## ROLE`, `## CRITICAL CONSTRAINTS`), title case H3 subsections (`### Must Do`). - Every prompt must include `## ROLE`, `## CRITICAL CONSTRAINTS`, `## OUTPUT FORMAT`. - Add `## VALIDATION` when the output involves multi-step logic or edge cases. Omit for simple single-purpose prompts. ## Content - Prompts are machine-readable specs. Optimize for token efficiency and deterministic output, not prose readability. - Every constraint must be verifiable from the output. No subjective qualifiers like "appropriate" or "well-structured". - Do not duplicate general LLM knowledge. Focus on project-specific constraints and output shape. - Use imperative voice throughout. "Do X", never "You should" or "Try to". ## Exportable prompts - When adding an exportable prompt, register it under the appropriate category in `prompts.toml` using the file stem as the name. - `essentials` is the curated minimum for `aitk prompts install`. Keep it tight: only prompts that earn their weight on nearly every project. Slugs may overlap with other categories. ## Sync checklist When adding an exportable prompt: - Create the `.md` file in `prompts/` starting with a frontmatter block carrying `title` and `description`. See `standards/prose.md` for the style rule. - Add the name to the correct category in `prompts.toml` - If the prompt