Skip to content

miklschmidt/archboard / skills/archboard

archboard

Verified

Read, author, and visualize local architecture with the archboard CLI. Always use in repositories with an .archboard/vault directory: when planning, implementing, explaining, visualizing, refactoring, or improving the codebase or code in general. Load this skill when loading, reading, or using improve-codebase-architecture. Also use for architecture questions, request flows, proposals, and explicit migration of existing architecture vaults.

references/schemas.md

View on GitHub
# Canonical schemas

Before preparing a request, print its schema with the installed archboard CLI.
`archboard model schema` lists the names. `archboard model schema <name>` prints one schema.
The CLI renders them from its own validation, so they match the program that reads and writes the vault.
Neither command needs a server or a vault. Do not copy the schemas into the repository.
Use [canonical models](canonical-models.md) for operations and semantic rules beyond JSON structure.

| Name               | Use                                             |
| ------------------ | ----------------------------------------------- |
| `model-manifest`   | Model identity and current state                |
| `module`           | A module and its outgoing relationships         |
| `flows`            | An independent flow collection                  |
| `model-initialize` | Empty planning model request                    |
| `model-edit`       | Complete authoring intent                       |
| `model-import`     | Portable installation request                   |
| `model-migrate`    | Legacy migration request                        |
| `vault-config`     | Shared kinds, relationship evidence, and groups |

Canonical modules use containment without fixed levels.
Legacy levels exist only for explicit migration and exact retained history.
New authoring writes neither legacy board families nor levels.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall