Standard Prompts

Generate comprehensive project documentation following YOLO methodology

As my developer, I want you to document everything we just did using the YOLO methodology, which is based on the yolo folder in this project, having all epics, features and tasks, the README, CHANGELOG, with standard commit and semver standards, and the history.yaml documenting everything we have done. Plus the WISHES having all that will come, organized from the epics, features and tasks in the yolo folder. Remember we never delete anything, we just mark as implemented, completed, deprecated, deleted, etc.

📁 .yolo/
├── epics/
│   └── E001-project-setup.md
├── features/
│   └── F001-initial-structure.md
├── tasks/
│   └── T001-create-folders.md
├── history.yaml
├── README.md
├── CHANGELOG.md
└── WISHES.md

Generate semantic commit messages with detailed descriptions

Analyze the following changes and generate a commit message following conventional commits format. Include a detailed description of the changes, breaking changes if any, and related issue references. The message should be clear, concise, and follow semver standards.

Changes to analyze:
[paste changes or provide context]

feat(auth): implement JWT authentication system

- Add token generation and validation
- Implement refresh token logic
- Add middleware for route protection

BREAKING CHANGE: Auth header format changed
Fixes #123

Create a detailed history.yaml entry for tracking changes

Create a history.yaml entry for the following changes. Include timestamp, type (epic/feature/task), summary, impact, status, and any related items. The entry should be detailed enough to understand the context and purpose of the changes later.

Changes to document:
[paste changes or provide context]

entries:
  - timestamp: "2025-01-23T16:15:00+01:00"
    type: feature
    id: F001
    summary: "Add authentication system"
    impact: "Improved security"
    status: "implemented"
    related:
      epic: E001
      tasks: [T001, T002]
    note: "JWT-based auth system added"

Break down features into actionable tasks

Break down the following feature into specific, actionable tasks. Each task should be small enough to be completed in one sitting, have clear success criteria, and maintain relationships with the parent feature. Consider technical dependencies and suggest a logical order.

Feature to break down:
[feature description]

Tasks:
1. T001: Set up database schema
   - Success: Tables created
   - Dependencies: None

2. T002: Implement API endpoints
   - Success: Endpoints tested
   - Dependencies: T001

3. T003: Add validation
   - Success: Input validated
   - Dependencies: T002

Document feature requests in WISHES.md

Document the following feature request in WISHES.md format. Include a clear description, potential impact, suggested implementation approach, and any related existing features or epics. Remember to maintain relationships and keep the history traceable.

Feature request:
[feature description]

## Feature: Enhanced Search
Status: proposed
Priority: high
Related: E002, F005

### Description
Implement elasticsearch for better search

### Impact
- Improved performance
- Better user experience

### Implementation Notes
Consider using elastic cloud

Get AI-powered suggestions for improvements

Analyze the current implementation and suggest improvements. Consider code quality, performance, security, and user experience. Provide specific, actionable suggestions with examples where possible. Remember to maintain the project's existing patterns and standards.

Area to analyze:
[code or feature to analyze]

Suggestions:
1. Performance
   - Add caching layer
   - Implement pagination

2. Security
   - Add rate limiting
   - Enhance validation

3. Code Quality
   - Extract common logic
   - Add unit tests