refactor: standardize formatting and improve readability across core documents (#211)
### CHANGES - Add newlines and spacing for improved readability - Standardize instructional text for consistency - Renumber lists within tasks for better clarity - Add language identifiers to various code blocks - Update placeholder text for improved consistency - Adjust descriptions and wording in multiple files - Update VS Code settings and dictionary words
This commit is contained in:
@@ -17,11 +17,13 @@ IMPORTANT: If any required documents are missing or inaccessible, immediately as
|
||||
|
||||
PROJECT TYPE DETECTION:
|
||||
First, determine the project type by checking:
|
||||
|
||||
- Does the architecture include a frontend/UI component?
|
||||
- Is there a frontend-architecture.md document?
|
||||
- Does the PRD mention user interfaces or frontend requirements?
|
||||
|
||||
If this is a backend-only or service-only project:
|
||||
|
||||
- Skip sections marked with [[FRONTEND ONLY]]
|
||||
- Focus extra attention on API design, service architecture, and integration patterns
|
||||
- Note in your final report that frontend sections were skipped due to project type
|
||||
@@ -433,4 +435,4 @@ Now that you've completed the checklist, generate a comprehensive validation rep
|
||||
- UI/UX specification coverage
|
||||
- Component design clarity
|
||||
|
||||
After presenting the report, ask the user if they would like detailed analysis of any specific section, especially those with warnings or failures.]]
|
||||
After presenting the report, ask the user if they would like detailed analysis of any specific section, especially those with warnings or failures.]]
|
||||
|
||||
Reference in New Issue
Block a user