prompt-conventions

Instruction Command

When this command is used, acknowledge that you understand these instructions and will follow them throughout the conversation. Then await the user's request.

---

📝 Prompt Conventions

💡 Established patterns and standards for creating modular, reusable prompts that follow the framework philosophy.

Naming Conventions

File Naming Pattern

All prompt files follow the verb-subject pattern with kebab-case:

• create-feature.md - For creating features
• update-story.md - For updating stories
• analyze-performance.md - For analyzing performance
• transform-data.md - For transforming data

Special Naming Patterns

• CMU Variants: create-[subject].md, update-[subject].md, make-[subject].md
• Meta Prompts: create-prompt.md, update-template.md, make-workflow.md
• Generic Utility Prompts: help.md, clarify.md, simplify.md

WHEN naming prompt files

• ALWAYS start with a verb (create, update, make, analyze, transform, etc.)
• ALWAYS use kebab-case for multi-word names
• ALWAYS keep names concise but descriptive
• NEVER use underscores or spaces
• NEVER start with nouns

Directory Organization

Standard Structure

prompts/
├── create-*.md          # Creation prompts
├── update-*.md          # Update/enhancement prompts
├── make-*.md            # Transformation prompts
├── analyze-*.md         # Analysis prompts
├── generate-*.md        # Generation prompts
├── validate-*.md        # Validation prompts
└── [verb]-*.md          # Other action prompts

WHEN organizing prompts

• ALWAYS place in the root @prompts/` directory
• ALWAYS group by verb prefix when listing
• NEVER create subdirectories for categories
• NEVER mix non-prompt files in the directory

Component Extraction Conventions

Evolution Path

Follow the standard progression:

1. Inline: Define all components within the prompt
2. Extract: Move reusable parts to separate files
3. Reference: Use [[wikilinks-wl-example]] for references
4. Embed: Use ![[wikilinks-wl-example]] for content inclusion