docs-applying-content-qualitylisted

# Applying Content Quality Standards ## Purpose This Skill provides comprehensive guidance for applying **universal content quality standards** to all markdown content in the repository. It ensures consistent writing quality, accessibility compliance, and professional presentation across documentation, web sites, planning documents, and root files. **When to use this Skill:** - Creating or editing markdown content in docs/ - Writing content for crud-fs-ts-nextjs (Next.js) or crud-fs-ts-nextjs (Next.js) - Creating planning documents in plans/ - Writing repository root files (README.md, CONTRIBUTING.md, etc.) - Ensuring accessibility compliance (WCAG AA) - Reviewing content for quality standards ## Core Quality Principles ### Writing Style and Tone **Active Voice Required**: Use active voice for clarity and directness. ✅ **Good**: "The agent validates the content against the convention." ❌ **Avoid**: "The content is validated against the convention by the agent." **Professional Tone**: Maintain professional, welcoming tone without being overly formal. **Clarity and Conciseness**: Write clear, direct sentences. Avoid jargon without context. **Audience Awareness**: Consider reader's technical level and provide necessary context. ### Heading Hierarchy **Single H1 Rule**: Each markdown file MUST have exactly one H1 heading (# Title). **Proper Nesting**: Follow hierarchical structure without skipping levels: - H1 (#) - Document title - H2 (##) - Major sections - H3 (#