.claude/skills/mermaid-charts/SKILL.md
Creates and standardizes Mermaid decision flowcharts in VA Design System documentation, including templates, node types, accessibility alternatives, and the standard Jekyll include pattern.
npx skillsauth add department-of-veterans-affairs/vets-design-system-documentation mermaid-chartsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill enables efficient creation and standardization of Mermaid decision flowcharts in the VA Design System documentation following established patterns and best practices.
/docs/ai-mermaid-implementation-guide.md - Complete AI implementation guide/docs/mermaid-chart-templates.md - Ready-to-use templates for common patterns/docs/mermaid-node-types.md - Standardized node types and styling reference/docs/mermaid-chart-data-driven.md - JSON-based approach for complex charts/src/assets/stylesheets/application.scss - Chart styling (lines 145-230)<b> tags<div class="mermaid-width-wide">
{% include mermaid-chart.html
id="unique-chart-id"
caption="Descriptive caption for accessibility"
chart="
flowchart TD
Start[\"<b>Main question</b>\"]:::node-start --> Decision{\"<b>Decision point?</b>\"}:::node-question
Decision --> Option1([\"<b>Option 1</b><br/>Examples:<br/>Example A, Example B\"]):::node-answer-primary
Decision --> Option2([\"<b>Option 2</b><br/>Examples:<br/>Example C, Example D\"]):::node-answer-secondary
Option1 --> Result1[\"<b>Outcome A</b><br/>Additional details\"]:::node-result-button
Option2 --> Result2[\"<b>Outcome B</b><br/>Additional details\"]:::node-result-link
" %}
</div>
<va-details label="View text-based decision list for [topic]" id="chart-id-decision-list">
<h4>Main question</h4>
<ul>
<li><strong>Decision point?</strong>
<ul>
<li><strong>Option 1</strong> (Example A, Example B) → <strong>Outcome A</strong></li>
<li><strong>Option 2</strong> (Example C, Example D) → <strong>Outcome B</strong></li>
</ul>
</li>
</ul>
</va-details>
documentation
Use when making documentation changes in the doc-queue workflow, writing new component/pattern/template guidance, or updating existing VADS documentation - ensures compliance with VADS templates and style standards
testing
Use when the user wants to merge all PRs they have approved - updates each branch from main, waits for CI checks to pass, merges, then summarizes results
documentation
Use after selecting a documentation issue from the doc-queue to groom it - analyzes the issue, identifies gaps, prompts the designer for clarity, and posts a structured grooming comment so the issue is ready for the writing-vads-guidance skill or an async agent
documentation
Use when a designer asks to work on guidance or documentation issues, process documentation queue, or close out doc tickets - fetches oldest issue from quarterly epic and guides through resolution