メニュー
This skill should be used when the user asks about Mermaid diagram syntax, how to write flowchart, sequence, class, state, ER, Gantt, C4, mindmap, timeline, or other diagram types, node shapes, styling, theming, or rendering errors.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user wants to bulk-build ArcKit artefacts in parallel rather than running individual /arckit:* commands one at a time. Invoke manually with /arckit:arckit-build when the task sounds like 'kick off a build', 'build everything', 'generate all artefacts', 'run all the commands', 'rebuild this project from scratch', 'resume the build', 'pick up where we left off', 'refresh the artefacts', 'run the recipe', 'build the whole project end-to-end', or 'parallel build', or mentions `--plan`, `--resume`, `--target`, `--refresh`, `--recipe`, or `.arckit/state.json`. The skill orchestrates parallel /arckit:* generation using subagent isolation: reads project state, computes the artefact dependency DAG, dispatches one subagent per target per wave (each subagent invokes a /arckit:* skill in its own context), validates outputs, commits the wave, and persists progress to .arckit/state.json for resumability.
This skill should be used when the user asks about "ISO 27001", "Cyber Essentials", "NCSC principles", "cloud security", "what certifications", "SOC 2", "data protection", "UK GDPR", "security clearance", "PCI DSS", "compliance framework", "CSA STAR", "DSPT", "Technology Code of Practice", "AI Playbook", "what evidence do I need", "security certification", "NHS data", "BPSS", "SC clearance", "DV clearance", "what security do I need", "certification cost", "ISO 22301", or needs guidance on security certifications, compliance requirements, and evidence for G-Cloud submissions.
This skill should be used when the user asks about "character limit", "how many features", "what lots", "CCS questions", "service categories", "declaration questions", "word limit", "mandatory exclusion", "service name limit", "pricing format", "what questions does CCS ask", "lot 1 categories", "lot 2 categories", "lot 3 categories", "how many words", "features limit", "benefits limit", "service description limit", "framework questions", "marketplace questions", "G-Cloud question structure", or needs quick lookups on Digital Marketplace field constraints and lot structures.
This skill should be used when the user asks about "SFIA level", "SFIA skills", "day rate", "what level is", "solution architect level", "Lot 3 roles", "DDaT roles", "AI skills framework", "cloud migration roles", "consultancy rates", "SFIA mapping", "role to SFIA", "skill level", "cloud support roles", "what SFIA level", "rate card", "SFIA 8", "junior consultant rate", "senior consultant rate", "principal consultant", "DevOps engineer level", "security engineer level", "project manager SFIA", or needs guidance on SFIA levels, role mappings, day rates, and Lot 3 service team compositions.
Cut a new ArcKit release — bump versions in lockstep, regenerate non-Claude formats, validate plugin/marketplace agreement, tag, and push to standalone repos. Use when the user says 'cut a release', 'release ArcKit', 'ship vX.Y.Z', 'bump the version and release', 'do the release flow', 'tag and publish', or 'push the extensions'. This is a manual, high-consequence workflow: it never runs automatically.
Use when reviewing a PR to tractorjuice/arc-kit that adds or extends a community jurisdictional overlay (e.g. au-*, ca-*, uae-*, fr-*, at-*, eu-*, future state-level like au-vic-*) — produces a structured review with blockers, important issues, minor issues, and positive callouts.
| name | mermaid-syntax |
| description | This skill should be used when the user asks about Mermaid diagram syntax, how to write flowchart, sequence, class, state, ER, Gantt, C4, mindmap, timeline, or other diagram types, node shapes, styling, theming, or rendering errors. |
| paths | ["**/*.mmd","**/*.mermaid","**/ARC-*-DIAG-*.md"] |
A comprehensive reference for all 23 Mermaid diagram types plus configuration and theming. This skill provides official Mermaid syntax documentation sourced from the mermaid-skill project (auto-synced from upstream Mermaid docs).
This skill ships reference material, not runnable scripts. Read the relevant reference file with Read, apply the syntax, and write the diagram into the user's artefact. Do not Bash-execute anything from references/ — they are Mermaid syntax docs, not commands.
To look up syntax for a specific diagram type, identify the type from the table below and read the corresponding reference file.
Select the appropriate diagram type and read the corresponding reference file:
| Type | Reference | ArcKit Commands Using It |
|---|---|---|
| Flowchart | flowchart.md | /arckit:diagram, /arckit:dfd, /arckit:roadmap, /arckit:plan, /arckit:backlog, /arckit:strategy, /arckit:story, /arckit:jsp-936 |
| Sequence Diagram | sequenceDiagram.md | /arckit:diagram |
| Class Diagram | classDiagram.md | — |
| State Diagram | stateDiagram.md | — |
| ER Diagram | entityRelationshipDiagram.md | /arckit:data-model |
| Gantt Chart | gantt.md | /arckit:roadmap, /arckit:plan, /arckit:strategy, /arckit:story, /arckit:presentation |
| Pie Chart | pie.md | /arckit:story, /arckit:presentation |
| Mindmap | mindmap.md | /arckit:story |
| Timeline | timeline.md | /arckit:story |
| Git Graph | gitgraph.md | — |
| Quadrant Chart | quadrantChart.md | /arckit:presentation |
| Requirement Diagram | requirementDiagram.md | — |
| C4 Diagram | c4.md | /arckit:diagram, /arckit:presentation |
| Sankey Diagram | sankey.md | — |
| XY Chart | xyChart.md | — |
| Block Diagram | block.md | — |
| Packet Diagram | packet.md | — |
| Kanban | kanban.md | — |
| Architecture Diagram | architecture.md | — |
| Radar Chart | radar.md | — |
| Treemap | treemap.md | — |
| User Journey | userJourney.md | — |
| ZenUML | zenuml.md | — |
| Topic | Reference |
|---|---|
| Theming | config-theming.md |
| Directives | config-directives.md |
| Layouts | config-layouts.md |
| Configuration | config-configuration.md |
| Math | config-math.md |
| Tidy Tree | config-tidy-tree.md |
| Examples | examples.md |
For research-backed C4 diagram layout guidance (declaration ordering, edge crossing targets, colour standards, PlantUML directional hints), see c4-layout-science.md. This ArcKit-specific reference supplements the upstream C4 syntax reference with graph drawing science and layout optimisation techniques.
These are the most common Mermaid syntax errors encountered when generating diagrams:
| Gotcha | Problem | Fix |
|---|---|---|
<br/> in flowchart edge labels | Mermaid flowchart parser rejects HTML in edge labels | Use comma-separated text: -->|"Uses, HTTPS"| |
end as node ID | end is a reserved keyword in Mermaid | Use a different ID: EndNode["End"] |
| Gantt date formats | Gantt requires specific date format | Use YYYY-MM-DD (e.g., 2025-01-15) |
| Gantt task status | Invalid task status keywords | Valid: done, active, crit, milestone |
| Parentheses in labels | Unescaped () breaks node parsing | Wrap in quotes: Node["Label (with parens)"] |
| Special chars in IDs | Hyphens, dots, spaces in node IDs | Use camelCase or underscores: apiGateway, api_gateway |
| Missing semicolons in ER | ER diagram attributes need specific syntax | Follow entity { type name } pattern |
| Subgraph naming | Subgraph IDs with spaces need quotes | subgraph "My Group" |
This skill handles conversational Mermaid syntax questions — quick lookups, syntax examples, troubleshooting rendering issues, and learning about diagram types.
For formal architecture diagram generation with document control, project integration, C4 layout science, and governance compliance, use the /arckit:diagram command instead. It generates versioned diagram artifacts saved to your project directory with full traceability to requirements and architecture principles.
