Before performing any write operation or making decisions, you must ensure that you have read and understood the latest content of the following documents:
-
P (Plan) - Requirement Analysis and Planning
- Read Documents: Confirm the content of and .
- Intent Extraction: Launch the interview and follow-up process to synchronize requirements.
- Solution Design: Use to plan the change list, and update the status with .
-
D (Do) - Development Implementation
- Core Implementation: Follow the Development Standards; if persistence is involved, prioritize developing entities with .
- Self-Inspection and Fixing: After development, eliminate Lint and type errors through .
-
A (Audit) - Code Audit
- Security Audit: Scan for injection, privilege escalation, and sensitive information leaks.
- Specification Audit: Compare with to confirm that function points are consistent with the plan.
-
C1 (Commit) - Feature Submission
- Atomic Commit: Use to perform the first commit.
-
V (Validate) - UI Validation
- Visual Guidelines: Verify the actual rendering effect in the browser. If automated tools fail, display screenshots to the user or request manual verification.
-
T (Test) - Automated Testing
- Targeted Testing: Write and run Vitest cases (test code must also pass the audit).
-
C2 (Commit) - Test Submission
- Final Delivery: Submit the test code.
-
F (Finish) - Task Completion
- Document Update: Update the status in and merge project change documents.
-
Quality Inspection and Review (Test/Review)
- Requirements: Before conducting tests, you must read the Testing Standards.
- Tasks: Run , and targeted/on-demand testing.
- Strategy: Follow the Efficient Testing Strategy, and do not perform full-scale testing unless necessary.
- Skills: , ,
-
Issue Fixing (Fix)
- Goal: Eliminate all defects found in the previous stage.
- Skills:
-
Feature Submission (Commit - Phase 1)
- Goal: Submit the business logic after passing the core quality inspection.
- Task: Submit following the Conventional Commits specification (Chinese version).
- Requirements: Follow Commit Scale & Atomic Changes, ensuring one commit corresponds to one Todo item and the number of files is less than 10.
- Skills:
-
Test Enhancement (Enhance)
- Goal: Complete test cases to improve code coverage.
- Task: Add positive, negative, and edge scenario Vitest cases for new features.
- Skills:
-
Test Submission (Commit - Phase 2)
- Goal: Store the enhanced test code in the repository.
- Skills:
-
Imperative & Structured
- Standardize the usage section of each step/skill with verb + target description.
- Prohibit lengthy nonsense and process introduction text.
-
Clear Input and Output
- Each step must specify the input dependencies and output products (such as file paths, document links).
- Example: Input: docs/plan/, Output: docs/design/xx.md.
-
Chainable Combination
- Each step skill should allow independent use or serve as a local fragment of the global master call chain.
- Some skills support multi-role collaboration (e.g., testing and documentation can be done in parallel).
-
Security Check and General Exception Handling
- Mandatorily insert quality checkpoints such as typecheck and lint, and prohibit entering the submission/release stage without detection.
- Clarify security levels and data protection points.
-
Internationalization and Documentation-First
- All workflows/skills should be created with default compatibility for i18n and standard document synchronization actions.