prjct-cli 0.10.10 → 0.10.11

package/templates/design/database.md

@@ -0,0 +1,78 @@
+---
+name: database-design
+description: Design database schema
+allowed-tools: [Read, Glob, Grep]
+---
+
+# Database Design
+
+Design database schema for the given requirements.
+
+## Input
+- Target: {{target}}
+- Requirements: {{requirements}}
+
+## Analysis Steps
+
+1. **Identify Entities**
+   - What data needs to be stored?
+   - What are the relationships?
+   - What queries will be common?
+
+2. **Review Existing Schema**
+   - Read current models/migrations
+   - Match naming conventions
+   - Use consistent patterns
+
+3. **Design Tables/Collections**
+   - Fields and types
+   - Indexes for queries
+   - Constraints and defaults
+
+4. **Plan Migrations**
+   - Order of operations
+   - Data transformations
+   - Rollback strategy
+
+## Output Format
+
+```markdown
+# Database Design: {target}
+
+## Entities
+
+### users
+| Column | Type | Constraints | Description |
+|--------|------|-------------|-------------|
+| id | uuid | PK | Unique identifier |
+| email | varchar(255) | UNIQUE, NOT NULL | User email |
+| created_at | timestamp | NOT NULL, DEFAULT now() | Creation time |
+
+### posts
+| Column | Type | Constraints | Description |
+|--------|------|-------------|-------------|
+| id | uuid | PK | Unique identifier |
+| user_id | uuid | FK(users.id) | Author reference |
+| title | varchar(255) | NOT NULL | Post title |
+
+## Relationships
+- users 1:N posts (one user has many posts)
+
+## Indexes
+- `users_email_idx` on users(email)
+- `posts_user_id_idx` on posts(user_id)
+
+## Migrations
+1. Create users table
+2. Create posts table with FK
+3. Add indexes
+
+## Queries (common)
+- Get user by email: `SELECT * FROM users WHERE email = ?`
+- Get user posts: `SELECT * FROM posts WHERE user_id = ?`
+```
+
+## Guidelines
+- Normalize appropriately
+- Add indexes for common queries
+- Document relationships clearly

package/templates/design/flow.md

@@ -0,0 +1,94 @@
+---
+name: flow-design
+description: Design user/data flow
+allowed-tools: [Read, Glob, Grep]
+---
+
+# Flow Design
+
+Design the user or data flow for the given feature.
+
+## Input
+- Target: {{target}}
+- Requirements: {{requirements}}
+
+## Analysis Steps
+
+1. **Identify Actors**
+   - Who initiates the flow?
+   - What systems are involved?
+   - What are the touchpoints?
+
+2. **Map Steps**
+   - Start to end journey
+   - Decision points
+   - Error scenarios
+
+3. **Define States**
+   - Initial state
+   - Intermediate states
+   - Final state(s)
+
+4. **Plan Error Handling**
+   - What can go wrong?
+   - Recovery paths
+   - User feedback
+
+## Output Format
+
+```markdown
+# Flow: {target}
+
+## Overview
+Brief description of this flow.
+
+## Actors
+- **User**: Primary actor
+- **System**: Backend services
+- **External**: Third-party APIs
+
+## Flow Diagram
+```
+[Start] → [Step 1] → [Decision?]
+                         ↓ Yes
+                    [Step 2] → [End]
+                         ↓ No
+                    [Error] → [Recovery]
+```
+
+## Steps
+
+### 1. User Action
+- User does X
+- System validates Y
+- **Success**: Continue to step 2
+- **Error**: Show message, allow retry
+
+### 2. Processing
+- System processes data
+- Calls external API
+- Updates database
+
+### 3. Completion
+- Show success message
+- Update UI state
+- Log event
+
+## Error Scenarios
+| Error | Cause | Recovery |
+|-------|-------|----------|
+| Invalid input | Bad data | Show validation |
+| API timeout | Network | Retry with backoff |
+| Auth failed | Token expired | Redirect to login |
+
+## States
+- `idle`: Initial state
+- `loading`: Processing
+- `success`: Completed
+- `error`: Failed
+```
+
+## Guidelines
+- Cover happy path first
+- Document all error cases
+- Keep flows focused