Cursor rule

1---
2alwaysApply: false
3---
4 
5# Content Validation Rules
6 
7## MANDATORY: Content Validation Before File Creation
8 
9**CRITICAL**: All generated content MUST be validated before writing to files to prevent parsing errors.
10 
11## ASCII Diagram Standards
12 
13**CRITICAL**: Before creating ANY file with ASCII diagrams:
14 
151. **LOAD** `common/ascii-diagram-standards.md`
162. **VALIDATE** each diagram:
17   - Count characters per line (all lines MUST be same width)
18   - Use ONLY: `+` `-` `|` `^` `v` `<` `>` and spaces
19   - NO Unicode box-drawing characters
20   - Spaces only (NO tabs)
213. **TEST** alignment by verifying box corners align vertically
22 
23**See `common/ascii-diagram-standards.md` for patterns and validation checklist.**
24 
25## Mermaid Diagram Validation
26 
27### Required Validation Steps
281. **Syntax Check**: Validate Mermaid syntax before file creation
292. **Character Escaping**: Ensure special characters are properly escaped
303. **Fallback Content**: Provide text alternative if Mermaid fails validation
31 
32### Mermaid Validation Rules
33```markdown
34## BEFORE creating any file with Mermaid diagrams:
35 
361. Check for invalid characters in node IDs (use alphanumeric + underscore only)
372. Escape special characters in labels: " → \" and ' → \'
383. Validate flowchart syntax: node connections must be valid
394. Test diagram parsing with simple validation
40 
41## FALLBACK: If Mermaid validation fails, use text-based workflow representation
42```
43 
44### Implementation Pattern
45```markdown
46## Workflow Visualization
47 
48### Mermaid Diagram (if syntax valid)
49```mermaid
50[validated diagram content]
51```
52 
53### Text Alternative (always include)
54```
55Phase 1: INCEPTION
56- Stage 1: Workspace Detection (COMPLETED)
57- Stage 2: Requirements Analysis (COMPLETED)
58[continue with text representation]
59```
60 
61## General Content Validation
62 
63### Pre-Creation Validation Checklist
64- [ ] Validate embedded code blocks (Mermaid, JSON, YAML)
65- [ ] Check special character escaping
66- [ ] Verify markdown syntax correctness
67- [ ] Test content parsing compatibility
68- [ ] Include fallback content for complex elements
69 
70### Error Prevention Rules
711. **Always validate before using tools/commands to write files**: Never write unvalidated content
722. **Escape special characters**: Particularly in diagrams and code blocks
733. **Provide alternatives**: Include text versions of visual content
744. **Test syntax**: Validate complex content structures
75 
76## Validation Failure Handling
77 
78### When Validation Fails
791. **Log the error**: Record what failed validation
802. **Use fallback content**: Switch to text-based alternative
813. **Continue workflow**: Don't block on content validation failures
824. **Inform user**: Mention simplified content was used due to parsing constraints
83