Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
Hack23 organization architecture documentation standards, C4 model requirements, future state planning
Install Hack23 Future Architecture Standards
$ npx skills add Hack23/cia --skill hack23-future-architecture-standards -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Hack23/cia hack23-future-architecture-standards --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/hack23-future-architecture-standards .claude/skills/hack23-future-architecture-standards && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hack23-future-architecture-standards" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-future-architecture-standards into .claude/skills/hack23-future-architecture-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-future-architecture-standards", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Hack23/cia/tree/master/.github/skills/hack23-future-architecture-standardsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Hack23/cia --skill hack23-future-architecture-standards -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Hack23/cia hack23-future-architecture-standards --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/hack23-future-architecture-standards .agents/skills/hack23-future-architecture-standards && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hack23-future-architecture-standards" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-future-architecture-standards into .agents/skills/hack23-future-architecture-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-future-architecture-standards", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Hack23/cia --skill hack23-future-architecture-standards -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Hack23/cia hack23-future-architecture-standards --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/hack23-future-architecture-standards .cursor/skills/hack23-future-architecture-standards && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hack23-future-architecture-standards" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-future-architecture-standards into .cursor/skills/hack23-future-architecture-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-future-architecture-standards", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Hack23/cia.git --path .github/skills/hack23-future-architecture-standards--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Hack23/cia --skill hack23-future-architecture-standards -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Hack23/cia hack23-future-architecture-standards --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/hack23-future-architecture-standards .gemini/skills/hack23-future-architecture-standards && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hack23-future-architecture-standards" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-future-architecture-standards into .gemini/skills/hack23-future-architecture-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-future-architecture-standards", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Hack23/cia hack23-future-architecture-standardsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Hack23/cia --skill hack23-future-architecture-standards -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/hack23-future-architecture-standards .github/skills/hack23-future-architecture-standards && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hack23-future-architecture-standards" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-future-architecture-standards into .github/skills/hack23-future-architecture-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-future-architecture-standards", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Hack23/cia --skill hack23-future-architecture-standards -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Hack23/cia hack23-future-architecture-standards --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Hack23/cia.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/hack23-future-architecture-standards .opencode/skills/hack23-future-architecture-standards && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hack23-future-architecture-standards" agent skill from https://github.com/Hack23/cia/tree/master/.github/skills/hack23-future-architecture-standards into .opencode/skills/hack23-future-architecture-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hack23-future-architecture-standards", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
hack23-future-architecture-standards- GitHub stars
- 239
- Token cost
- ~1.4k tokens
- SKILL.md length
- 361 words
- Files
- 1
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Hack23 organization architecture documentation standards, C4 model requirements, future state planning
- Works in 5 steps: Use consistent naming — ARCHITECTURE.md,… → Include C4 Level 1 at minimum in… → Maintain FUTURE_*.md documents for… → …
- Tasks that involve Architecture decision records
- SKILL.md covers Purpose, When to Use, C4 Model Requirements and Architecture Decision Records…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Hack23 Future Architecture Standards is an agent skill from Hack23/cia. Hack23 organization architecture documentation standards, C4 model requirements, future state planning
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Architecture decision records and Diagrams. The repository describes itself as: Citizen Intelligence Agency. Open-source intelligence platform analyzing Swedish political activities using AI and data visualization. Tracks politicians, government… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Architecture decision records
- Tasks that involve Diagrams
Example prompts
- “/hack23-future-architecture-standards”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Use consistent naming — ARCHITECTURE.md, not architecture.md
- Include C4 Level 1 at minimum in ARCHITECTURE.md
- Maintain FUTURE_*.md documents for forward planning
- Link related repos — cross-reference dependent systems
- Version diagrams — include date or version in diagram titles
What it can do on your machine
Read from SKILL.md and the folder at commit 6a9797b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are mermaid and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Hack23 Future Architecture Standards loads about 1.4k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 361 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Hack23/cia at commit 6a9797b, republished under its Apache-2.0 licence (© Hack23). 361 words, ~1,400 tokens.
Download SKILL.mdSave it as
.claude/skills/hack23-future-architecture-standards/SKILL.md (or your agent's skills folder).- name
- hack23-future-architecture-standards
- description
- Hack23 organization architecture documentation standards, C4 model requirements, future state planning
- license
- Apache-2.0
Hack23 Future Architecture Standards Skill
Purpose
Define and enforce architecture documentation standards across the Hack23 organization, using the C4 model for system decomposition, future state planning with ADRs (Architecture Decision Records), and consistent documentation patterns across all repositories.
When to Use
- ✅ Documenting system architecture for new or existing projects
- ✅ Creating Architecture Decision Records (ADRs)
- ✅ Planning future state architecture migrations
- ✅ Reviewing architecture documentation for completeness
- ✅ Generating C4 model diagrams for the CIA platform
Do NOT use for:
- ❌ Code-level documentation (use JavaDoc)
- ❌ Security-specific architecture (use security-documentation skill)
- ❌ Operational runbooks (use aws-cloudwatch-monitoring skill)
C4 Model Requirements
Level 1: System Context
Every Hack23 project must include a system context diagram showing:
- The system under description
- All external actors (users, systems)
- Data flows with protocols and formats
C4Context
title CIA Platform - System Context
Person(citizen, "Citizen", "Swedish citizen seeking political transparency")
Person(analyst, "Political Analyst", "Researches political patterns")
System(cia, "CIA Platform", "Political intelligence and analysis")
System_Ext(riksdag, "Riksdagen API", "Swedish Parliament open data")
System_Ext(val, "Val.se", "Swedish Election Authority")
System_Ext(worldbank, "World Bank", "Economic indicators")
System_Ext(esv, "ESV", "Swedish financial data")
Rel(citizen, cia, "Views political data", "HTTPS")
Rel(analyst, cia, "Analyzes political trends", "HTTPS")
Rel(cia, riksdag, "Fetches parliament data", "HTTPS/JSON")
Rel(cia, val, "Fetches election data", "HTTPS/JSON")
Rel(cia, worldbank, "Fetches economic data", "HTTPS/JSON")
Rel(cia, esv, "Fetches financial data", "HTTPS/JSON")Level 2: Container Diagram
Show major deployable units:
C4Container
title CIA Platform - Container Diagram
Container(webapp, "Web Application", "Vaadin/Spring", "Political data dashboards")
ContainerDb(db, "PostgreSQL", "Database", "Political data store")
Container(agent, "Data Agent", "Spring Integration", "Data import pipelines")
Rel(webapp, db, "Reads/Writes", "JDBC/JPA")
Rel(agent, db, "Writes imported data", "JDBC/JPA")Level 3: Component Diagram
Required for complex modules showing internal components.
Level 4: Code Diagram
Optional — only for critical/complex algorithms.
Architecture Decision Records (ADRs)
ADR Template
# ADR-{number}: {Title}
## Status
{Proposed | Accepted | Deprecated | Superseded by ADR-xxx}
## Context
{What is the issue? Why do we need to make a decision?}
## Decision
{What is the change that we're proposing and/or doing?}
## Consequences
### Positive
- {Benefit 1}
- {Benefit 2}
### Negative
- {Trade-off 1}
- {Trade-off 2}
### Risks
- {Risk 1 and mitigation}ADR Naming Convention
- File:
docs/adr/ADR-NNNN-short-title.md - Number: Sequential, zero-padded to 4 digits
- Title: Kebab-case, descriptive
Future State Planning
Documentation Requirements
Each Hack23 project must maintain:
| Document | Purpose | Update Frequency |
|---|---|---|
ARCHITECTURE.md | Current state architecture | Every major change |
FUTURE_ARCHITECTURE.md | Target state architecture | Quarterly review |
SECURITY_ARCHITECTURE.md | Security architecture | Every security change |
DATA_MODEL.md | Entity relationship diagrams | Every schema change |
FLOWCHART.md | Data processing workflows | When workflows change |
MINDMAP.md | Component relationships | Annually |
Show full SKILL.md (140 more words)Show less
Migration Planning Template
## Current State → Future State
### Phase 1: Foundation (Q1)
- [ ] Milestone 1: Description
- [ ] Milestone 2: Description
### Phase 2: Migration (Q2)
- [ ] Milestone 3: Description
### Phase 3: Optimization (Q3)
- [ ] Milestone 4: Description
### Rollback Plan
- Step 1: {rollback action}
- Step 2: {verification}Diagram Standards
Tool Chain
- Mermaid — primary diagramming tool (renders in GitHub Markdown)
- PlantUML — alternative for complex UML diagrams
- C4-PlantUML — C4 model diagrams with PlantUML
Diagram Checklist
- Title present and descriptive
- All elements labeled
- Relationships have descriptions and protocols
- Legend included for non-standard notation
- Consistent color scheme across diagrams
- Rendered preview verified in GitHub
Cross-Repository Consistency
Hack23 Organization Standards
All repositories under github.com/Hack23/ must:
- Use consistent naming —
ARCHITECTURE.md, notarchitecture.md - Include C4 Level 1 at minimum in
ARCHITECTURE.md - Maintain FUTURE_*.md documents for forward planning
- Link related repos — cross-reference dependent systems
- Version diagrams — include date or version in diagram titles
ISMS Alignment
| Control | Requirement |
|---|---|
| ISO 27001 A.5.1 | Policies for information security (documented) |
| ISO 27001 A.8.25 | Secure development lifecycle documentation |
| NIST CSF ID.AM-2 | Software platform inventory |
| CIS Control 2 | Inventory and control of software assets |
© Hack23, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/hack23-future-architecture-standards of Hack23/cia.
Open the folder on GitHubat commit 6a9797b
Compare with similar skills
Hack23 Future Architecture Standards next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hack23 Future Architecture Standards this skillHack23/cia | 239 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Design Doc MermaidSpillwaveSolutions/design-doc-mermaid | 175 | 1 repos | ~5.6k | Automated safety check: Pass | None | |
| Architecture Decisions and ADRsfirst-fluke/oh-my-agent | 1.3k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Opencharttryopendata/skills | 141 | — | ~11k | Automated safety check: Pass | MIT | |
| Docs Architecturejh941213/my-cc-harness | 126 | — | ~923 | Automated safety check: Notes | None | |
| Domain Modelingiurysza/module-graph | 419 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Architecture Decisions and ADRs
first-fluke/oh-my-agent
Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.
Openchart
tryopendata/skills
Generates OpenChart (https://github.com/tryopendata/openchart) chart, table, graph, sankey, tilemap, and geo map specs from data, and guides editorial design decisions.
Docs Architecture
jh941213/my-cc-harness
Generate/update architecture docs — ARCHITECTURE.md (codemap), architecture diagrams (C4 mermaid), ADRs (MADR), data model ERD.
Domain Modeling
iurysza/module-graph
Maintains project domain language, context maps, diagrams, and architectural decisions under ai-artifacts.
Senior Architect
alirezarezvani/claude-skills
This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan…
More from Hack23/cia
All 78 skills in this repoAccessibility Wcag Patterns
Hack23/cia
WCAG 2.1 AA compliance, ARIA attributes, keyboard navigation, screen reader optimization for accessible political data platforms
Advanced Data Visualization
Hack23/cia
Advanced chart types, D3.js/Vaadin Charts patterns, political data visualization, time series analysis
AI Governance
Hack23/cia
AI governance, EU AI Act compliance, OWASP LLM security, responsible AI practices for GitHub Copilot agents
API Integration
Hack23/cia
External API integration patterns, retry logic, circuit breakers, caching, rate limiting for government data APIs
AWS Cloudwatch Monitoring
Hack23/cia
AWS CloudWatch metrics, alarms, dashboards, log insights, and application monitoring for the CIA platform
AWS Security Architecture
Hack23/cia
AWS security best practices, VPC security, IAM, KMS, CloudTrail, GuardDuty for CIA platform deployment
Related
Categories
Questions about Hack23 Future Architecture Standards
What does Hack23 Future Architecture Standards do?
Hack23 organization architecture documentation standards, C4 model requirements, future state planning. Hack23 Future Architecture Standards is an agent skill from Hack23/cia.
When should I use Hack23 Future Architecture Standards?
Hack23 Future Architecture Standards fits situations like: tasks that involve Architecture decision records; tasks that involve Diagrams.
How do I install Hack23 Future Architecture Standards in Claude Code?
Run `npx skills add Hack23/cia --skill hack23-future-architecture-standards -a claude-code`. Or copy the skill folder (.github/skills/hack23-future-architecture-standards in Hack23/cia) into .claude/skills/hack23-future-architecture-standards in your project. Claude Code loads it when a task matches its description.
How do I install Hack23 Future Architecture Standards in Codex?
Run `npx skills add Hack23/cia --skill hack23-future-architecture-standards -a codex`. Or copy the skill folder (.github/skills/hack23-future-architecture-standards in Hack23/cia) into .agents/skills/hack23-future-architecture-standards in your project. Codex loads it when a task matches its description.
Can I use Hack23 Future Architecture Standards in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Hack23/cia --skill hack23-future-architecture-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hack23-future-architecture-standards, .gemini/skills/hack23-future-architecture-standards, .github/skills/hack23-future-architecture-standards and .opencode/skills/hack23-future-architecture-standards in your project.
What does Hack23 Future Architecture Standards need to run?
SKILL.md names no scripts, command-line tools or credentials: Hack23 Future Architecture Standards is instructions for the agent only.
Does Hack23 Future Architecture Standards access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Hack23 Future Architecture Standards safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Hack23 Future Architecture Standards use?
Hack23 Future Architecture Standards is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hack23 Future Architecture Standards use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Hack23 Future Architecture Standards?
Skills that share tags, products or a category with Hack23 Future Architecture Standards: Design Doc Mermaid (SpillwaveSolutions/design-doc-mermaid, 175 stars), Architecture Decisions and ADRs (first-fluke/oh-my-agent, 1.3k stars), Openchart (tryopendata/skills, 141 stars) and Docs Architecture (jh941213/my-cc-harness, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hack23 Future Architecture Standards?
Hack23 (a GitHub organization) maintains it in Hack23/cia, which has 239 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 6, 2026.
Source: Hack23/cia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.