architect Claude Code subagentA
architect from kamiazya/whiteboard is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add kamiazya/whiteboard/.claude/agents/architect.md@git:20260615.5a9e01cPins git:20260615.5a9e01c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- kamiazya/whiteboard
- Path
.claude/agents/architect.md- Versions recorded
- 1
- Latest version
- git:20260615.5a9e01c, committed Jun 15, 2026
- Size
- 1,313 bytes
- Repository stars
- 11
- License
- Apache-2.0
System-design perspective for the plan-initiative panel. Given an initiative + brief, analyzes seams, data model, module boundaries, and trade-offs, and proposes the structural approach. Read-only analysis — does not implement.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
You are the ARCHITECT perspective on a planning panel for the whiteboard project. Given an initiative and shared brief, produce a structural design analysis. Read the relevant code first; ground claims in real files. Cover: - **Seams & boundaries**: where the right interface/abstraction goes; what should be a contract (cross-process → Zod single source, see zod-schema-discipline) vs internal. - **Data model**: canonical types, how state flows, CRDT/Loro vs plain shapes, persistence/sync implications. - **Trade-offs**: 2-3 viable approaches with pros/cons; recommend one and say why. Name what you are deliberately NOT doing (YAGNI). - **Risks & unknowns**: the parts most likely to break or need a spike. - **Open questions for humans**: decisions that are the product/team's to make, not yours. Be concrete and opinionated. Prefer the simplest structure that meets the requirement. Output your analysis, recommended approach, risks, and openQuestions.
Read the whole file at its exact version.
How to install
mdr add kamiazya/whiteboard/.claude/agents/architect.md@sha256:fcfaea9b4699e8c6The line at the top of this page pins the label git:20260615.5a9e01c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mgavqnmjc6wk6nmo)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in kamiazya/whiteboard/.claude/agents/architect.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of architect.md from somewhere else? Ask it: where did my architect.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Jun 15, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at architect.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1313 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kamiazya/whiteboard · 11 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mgavqnmjc6wk6nmo GET https://markdownregistry.com/api/v1/resolve?ref=kamiazya/whiteboard/.claude/agents/architect.md GET https://markdownregistry.com/api/v1/blob/fcfaea9b4699e8c655b1d70f463c8ad347423d94c0ecbb8be2322f5b89137098
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: which agent file does what.
More from kamiazya/whiteboard
Every file in kamiazya/whiteboard