Skill

tools-visual-ascii-arch

Express product, service, or data architectures through layered ASCII diagrams suitable for terminals, PRs, and ADRs.

Install

npx claudepluginhub tjboudreaux/cc-visualization-skills --plugin visualization-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- Provide quick system overviews when graphical tools aren’t available.

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Stars1

Forks0

Last CommitFeb 17, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

ASCII Architecture Mapping

Intent

Provide quick system overviews when graphical tools aren’t available.

Maintain multiple zoom levels (context, container, component) in text form.

Inputs

List of components/services/contracts.

Interaction types (sync, async, queues, blockchain events).

Deployment/runtime context (devices, regions, environments).

Workflow

Choose framing

Context diagram (users ↔ system).
Container diagram (services, DBs, queues).
Component diagram (modules, classes, contracts).

Apply layout grid

Use +---+ boxes for nodes, |/- for edges.
Keep consistent spacing (2 spaces between layers).

Annotate flows

Label arrows with protocols (HTTP, gRPC, L1 tx).
Use ~> for async events, => for sync calls.

Layer metadata

Add footnotes for SLAs, owners, repos.
Indicate platform-specific components (e.g., [iOS], [Windows agent]).

Version and reuse

Store diagrams in .factory/diagrams/<topic>.txt.
Link from AGENTS.md or skills that need system context.

Verification

Diagram fits within 100 characters width; no tab characters.

All components labeled; directional arrows show data/control flow.

Latest version referenced in related skills/docs.

ASCII Architecture Mapping

Intent

Provide quick system overviews when graphical tools aren’t available.
Maintain multiple zoom levels (context, container, component) in text form.

Inputs

List of components/services/contracts.
Interaction types (sync, async, queues, blockchain events).
Deployment/runtime context (devices, regions, environments).

Workflow

Choose framing
- Context diagram (users ↔ system).
- Container diagram (services, DBs, queues).
- Component diagram (modules, classes, contracts).
Apply layout grid
- Use +---+ boxes for nodes, |/- for edges.
- Keep consistent spacing (2 spaces between layers).
Annotate flows
- Label arrows with protocols (HTTP, gRPC, L1 tx).
- Use ~> for async events, => for sync calls.
Layer metadata
- Add footnotes for SLAs, owners, repos.
- Indicate platform-specific components (e.g., [iOS], [Windows agent]).
Version and reuse
- Store diagrams in .factory/diagrams/<topic>.txt.
- Link from AGENTS.md or skills that need system context.

Verification

Diagram fits within 100 characters width; no tab characters.
All components labeled; directional arrows show data/control flow.
Latest version referenced in related skills/docs.