Document Mastery
This skill consolidates technical documentation standards and Mermaid diagram visualization to ensure high-impact delivery and technical consistency. Use this skill whenever producing written deliverables — reports, READMEs, studies, or any structured document.
1. Markdown Patterns (Premium Visuals)
Alerts (GitHub Style)
Use for highlighting critical information visually.
> [!NOTE]
> Additional context or neutral observations.
> [!TIP]
> Best practices and efficiency suggestions.
> [!IMPORTANT]
> Mandatory requirements or crucial steps.
> [!WARNING]
> Breaking changes or security warnings.
> [!CAUTION]
> Risks of data loss or critical failures.
Code Blocks and Links
- Code Blocks: Always specify the language and use the
language:path/to/fileformat if applicable. - Relative Links: Always use relative links
./file.mdfor internal movement between documents.
2. Visualization with Mermaid
Use Mermaid diagrams to explain complex flows, architectures, and data pipelines.
Common Patterns:
- Sequence Diagram: For interaction flows between systems/actors.
- Graph (Flowchart): For architectures and logical processes.
- ER Diagram: For data modeling and database schemas.
Diagramming References:
For technical syntax details and complex examples, consult the reference documents:
- Selection Guide: Which diagram to choose for each situation.
- Mermaid Syntax: Quick guide to commands and shapes.
- Practical Examples: Library of ready-to-use templates.
- Troubleshooting: How to fix rendering errors.
3. Standard Document Structure
Every reference document or report must follow this hierarchy:
- Title (H1): Clear objective.
- Overview: Executive summary of content.
- Mermaid Diagram: Visual representation of the concept.
- Technical Detail: Tables, code, or specifications.
- Workflow: Step-by-step guide or user manual.
- Maintenance Note:
> [!NOTE] Last updated: YYYY-MM-DD.
4. Report Enrichment Checklist
When producing a final report or documentation:
- Add relevant Mermaid diagrams to illustrate flows and architecture.
- Include tables for structured comparisons and data summaries.
- Use GitHub alerts for critical findings and recommendations.
- Embed charts from
data-vizskill outputs where applicable. - Ensure the document follows the Standard Document Structure (Section 3).
5. Academic & Research Standards
For scientific projects or academic theses, use the following specialized guides:
- CRISP-DM for Academia: Adapting data science cycles to research rigor.
- Thesis Defense Critic: Persona for challenging arguments and verifying data integrity.
[!TIP] When creating Mermaid diagrams, avoid node overload. If the diagram gets too large, break it into subgraphs or multiple files.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.