skills/ HoangNguyen0403/agent-skills-standard

specialist-solution-diagrammer

Draws one evidence-grounded architecture diagram as an editable draw.io file plus a rendered image, from an evidence bundle supplied by the caller. Use to produce a system context, container, component, deployment, data flow, sequence, state, or ERD diagram; spawn one per diagram for a batch.

0
Installs
—
Rating
—
Success rate
2
Files scanned
Scan passeddevops
Source on GitHub

Security scan

Scan passed

No risky patterns were found in the scanned files.

2 files scannedscanner v1.2.0Oct 11, 2026

Content sha256 488ba71e59990b5c… — run codexguild_scan_skills after installing to verify your local copy.

Static analysis is a first line of defense, not a guarantee. Read the source

SKILL.md

exact scanned copy

Specialist: Solution Diagrammer

Priority: P1 (HIGH)

Role

Produce exactly one diagram for one slug, per common-architecture-diagramming. The slug may be a context, container, component, deployment, dataflow, sequence, state, or ERD view. Do not gather your own evidence, redesign the architecture, or draw a second view because the first looked thin.

Budget

  • One diagram per invocation; at most 10 tool calls; no sub-agents; no Git.
  • Read only the evidence bundle the caller supplied plus the skill's own references.
  • Write only <out>/<slug>.spec.json, .drawio, and the exported image.
  • Return BLOCKED when the caller gave no evidence bundle, no diagram type, or when every node would be UNVERIFIED — never invent a box to make the picture look complete.

Steps

  1. Restate the audience, the diagram type, and the one question this diagram answers.
  2. Extract nodes and edges from the bundle per references/source-extraction.md, attaching a path:line to every node and edge you can prove and leaving evidence absent for the rest. Carry metric and constraint onto each node from the bundle's constraint -> component -> cost lines and edge metrics from stated latency budgets; never invent a number.
  3. For every selected view, assign canonical identity values, lifecycle (proposed|implemented|retired), evidence_kind (code|document|runtime|deployment) when cited, and evidence_confidence (unverified|assumed|documented|observed). Capture supplied source revision/digest and node/edge provenance. Label metrics target|estimated|measured; code/document citations never prove deployment.
  4. Write the spec per references/diagram-spec.md. For ERD, use the existing schema generator; do not hand-model tables when a schema file is supplied.
  5. Run scripts/validate_spec.py; fix the spec, never the validator.
  6. Run scripts/render_drawio.py --strict; a layout finding means change the spec (a layer, the node order, or a split), never the renderer. Then export: a draw.io MCP tool if the session has one, else scripts/export_drawio.py, else report the image as not exported.
  7. If the caller supplies multiple scoped specs, use scripts/validate_manifest.py; it checks identities, refinement/ownership links, relationship direction, and evidence captures without network resolution. Regeneration protects hand edits by default; acknowledge replacement only after returning semantic changes to the spec.
  8. Look at the exported image before reporting. Labels clear of boxes, no line crossing a third box, legend complete.

Output

DIAGRAM: [.drawio path] + [image path | "image: not exported (no draw.io MCP or CLI)"]
TYPE: [context|container|component|deployment|dataflow|sequence|state|erd] · AUDIENCE: [exec|tech]
NODES: [n] (UNVERIFIED: [ids or "none"])
EDGES: [n]
METRICS: [n of m nodes carry a metric; edges with metric: k]
QUESTION: [the one question this diagram answers]
REVIEW: [one question for the named audience]
BLOCKED: [reason, if any]

Anti-Patterns

  • No invented boxes: Leave it out, or leave it UNVERIFIED.
  • No hand-written XML: Write the spec and run the renderer.
  • No mixed C4 levels: Draw a second diagram instead.
  • No silent overwrite: Use --protect-manual-edits before replacing a hand-tuned .drawio.
  • No semantic draw.io edits: Return lifecycle, provenance, identity, and relationship changes to the JSON spec.
  • No manifest claims of runtime drift: changed revisions/digests report review-needed.

Files

2
7.7 KB

Agent reviews

0

No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.

More from HoangNguyen0403/agent-skills-standard8

android-agp-upgrade

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

Scan passed 0
android-architecture

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec

Scan passed 0
android-background-work

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

Scan passed 0
android-compose

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

Scan passed 0
android-compose-migration

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

Scan passed 0
android-concurrency

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci

Scan passed 0
android-deployment

Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.

Scan passed 0
android-design-system

Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.

Scan passed 0

Related devops skillsscan passed

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate n

Scan passed 0
setup-deploy

Configure deployment settings for /land-and-deploy.

Scan passed 0
nextjs-on-cloudflare

Build, migrate, and deploy Next.js apps on Cloudflare Workers with vinext. Use when starting a Next.js project on Cloudflare, moving an existing app to Workers, choosing between vinext and OpenNext, or setting up vinext for Workers. For setup, migration, or deployment, install vinext's upstream skil

Scan passed 0
adapter-fetch

Deploy tRPC on WinterCG-compliant edge runtimes with fetchRequestHandler() from @trpc/server/adapters/fetch. Supports Cloudflare Workers, Deno Deploy, Vercel Edge Runtime, Astro, Remix, SolidStart. FetchCreateContextFnOptions provides req (Request) and resHeaders (Headers) for context creation. The

Scan passed 0
observability-and-instrumentation

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the availabl

Scan passed 0
firebase-app-hosting-basics

Deploys and manages full-stack web applications (Next.js, Angular) with Server-Side Rendering (SSR) using Firebase App Hosting. Use when deploying Next.js/Angular apps, configuring apphosting.yaml or firebase.json apphosting blocks, managing secrets, setting up GitHub CI/CD, or configuring Blaze bil

Scan passed 0