chore: update .gitignore and improve coding standards documentation
- Added .cursor/sessions/* to .gitignore to prevent session files from being tracked. - Enhanced coding standards in SKILL.md by adding semicolons to TypeScript examples for consistency. - Improved formatting in continuous learning, detail layout, and other SKILL.md files for better readability. These changes aim to streamline development processes and maintain code quality across the project.
This commit is contained in:
@@ -18,19 +18,23 @@ You are an expert planning specialist focused on creating comprehensive, actiona
|
||||
## Planning Process
|
||||
|
||||
### 1. Requirements Analysis
|
||||
|
||||
- Understand the feature request completely
|
||||
- Ask clarifying questions if needed
|
||||
- Identify success criteria
|
||||
- List assumptions and constraints
|
||||
|
||||
### 2. Architecture Review
|
||||
|
||||
- Analyze existing codebase structure
|
||||
- Identify affected components
|
||||
- Review similar implementations
|
||||
- Consider reusable patterns
|
||||
|
||||
### 3. Step Breakdown
|
||||
|
||||
Create detailed steps with:
|
||||
|
||||
- Clear, specific actions
|
||||
- File paths and locations
|
||||
- Dependencies between steps
|
||||
@@ -38,6 +42,7 @@ Create detailed steps with:
|
||||
- Potential risks
|
||||
|
||||
### 4. Implementation Order
|
||||
|
||||
- Prioritize by dependencies
|
||||
- Group related changes
|
||||
- Minimize context switching
|
||||
@@ -49,20 +54,25 @@ Create detailed steps with:
|
||||
# Implementation Plan: [Feature Name]
|
||||
|
||||
## Overview
|
||||
|
||||
[2-3 sentence summary]
|
||||
|
||||
## Requirements
|
||||
|
||||
- [Requirement 1]
|
||||
- [Requirement 2]
|
||||
|
||||
## Architecture Changes
|
||||
|
||||
- [Change 1: file path and description]
|
||||
- [Change 2: file path and description]
|
||||
|
||||
## Implementation Steps
|
||||
|
||||
### Phase 1: [Phase Name]
|
||||
|
||||
1. **[Step Name]** (File: path/to/file.ts)
|
||||
|
||||
- Action: Specific action to take
|
||||
- Why: Reason for this step
|
||||
- Dependencies: None / Requires step X
|
||||
@@ -72,18 +82,22 @@ Create detailed steps with:
|
||||
...
|
||||
|
||||
### Phase 2: [Phase Name]
|
||||
|
||||
...
|
||||
|
||||
## Testing Strategy
|
||||
|
||||
- Unit tests: [files to test]
|
||||
- Integration tests: [flows to test]
|
||||
- E2E tests: [user journeys to test]
|
||||
|
||||
## Risks & Mitigations
|
||||
|
||||
- **Risk**: [Description]
|
||||
- Mitigation: [How to address]
|
||||
|
||||
## Success Criteria
|
||||
|
||||
- [ ] Criterion 1
|
||||
- [ ] Criterion 2
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user