PROJECT_ORGANIZATION.md

Project Prompt Library Organizational Strategy

1. Prompt Categories Directory Structure

prompts/
├── architecture/
│   ├── general/
│   └── assistant-specific/
├── code-analysis/
│   ├── general/
│   └── assistant-specific/
├── coding/
│   ├── general/
│   └── assistant-specific/
├── documentation/
│   ├── general/
│   └── assistant-specific/
├── learning/
│   ├── general/
│   └── assistant-specific/
├── maintenance/
│   ├── general/
│   └── assistant-specific/
├── planning/
│   ├── general/
│   └── assistant-specific/
├── requirements/
│   ├── general/
│   └── assistant-specific/
└── testing/
    ├── general/
    └── assistant-specific/

2. Workflow Categories Directory Structure

workflows/
├── general/                   # Generic workflows applicable across assistants
│   ├── sprint/                # Sprint workflows not tied to specific assistants
│   └── maintenance/           # Maintenance workflows not tied to specific assistants
└── assistant-specific/        # Assistant-specific workflows
    ├── aider/
    │   ├── sprint/
    │   └── maintenance/
    ├── github-copilot/
    │   ├── sprint/
    │   └── maintenance/
    └── claude/
        ├── sprint/
        └── maintenance/

3. Workflow Strategy

• Workflows are categorized by:
  • Development phase (sprint, maintenance)
  • Generality (general vs. assistant-specific)
• Each workflow represents a connected chain of prompts
• Workflows can:
  • Span multiple prompt categories
  • Include verification and validation steps
  • Support different development scenarios

4. Metadata Strategy

• Each prompt has a corresponding .meta.md file
• Metadata files provide:
  • AI assistant compatibility
  • SDLC phase information
  • Complexity ratings
  • Usage guidelines

5. Key Design Principles

• Flexibility: Easy to add new prompts and workflows
• Discoverability: Clear, intuitive structure
• Extensibility: Support for various development contexts
• Consistency: Standardized prompt and workflow organization