feat: Add documentation meta-rule system with educational focus

- Create meta_documentation.mdc for comprehensive doc workflows
- Add meta_rule_usage_guide.md for practical meta-rule usage
- Enhance existing markdown rules with educational standards
- Transform docs from technical reference to educational resources

Emphasizes human competence over technical description, provides
systematic workflows for all documentation tasks.

.cursor/rules/README.md

@@ -86,6 +86,7 @@ Rules for creating and maintaining documentation.
 - **`markdown_templates.mdc`** - Document templates and examples
 - **`markdown_workflow.mdc`** - Markdown validation and workflow
 - **`documentation.mdc`** - Documentation generation principles
+- **`meta_rule_usage_guide.md`** - How to use meta-rules in practice
 
 ### **`templates/`** - Templates and Examples
 
@@ -98,6 +99,7 @@ Template files and examples for various documentation types.
 High-level meta-rules that bundle related sub-rules for specific workflows.
 
 - **`meta_core_always_on.mdc`** - Core rules that apply to every single prompt
+- **`meta_documentation.mdc`** - Documentation writing and education workflow
 - **`meta_feature_planning.mdc`** - Feature planning workflow bundling
 - **`meta_bug_diagnosis.mdc`** - Bug investigation workflow bundling
 - **`meta_bug_fixing.mdc`** - Bug fix implementation workflow bundling
@@ -111,6 +113,8 @@ High-level meta-rules that bundle related sub-rules for specific workflows.
 3. **Context-Specific**: Use rules from appropriate subdirectories based on
    your task
 4. **Meta-Rules**: Use workflow-specific meta-rules for specialized tasks
+   - **Documentation**: Use `meta_documentation.mdc` for all documentation work
+   - **Getting Started**: See `docs/meta_rule_usage_guide.md` for comprehensive usage instructions
 5. **Cross-References**: All files contain updated cross-references to
    reflect the new structure
 6. **Validation**: All files pass markdown validation and maintain
@@ -125,6 +129,7 @@ High-level meta-rules that bundle related sub-rules for specific workflows.
 5. **Consistent cross-references** - All file links updated and working
 6. **Workflow bundling** - Meta-rules provide high-level workflow guidance
 7. **Feedback integration** - Built-in feedback mechanisms for continuous improvement
+8. **Educational focus** - Documentation emphasizes human competence over technical description
 
 ## File Naming Convention