Menu
Design a concrete target architecture from live contracts, execution paths, state ownership, and constraints.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build source-grounded, self-contained interactive HTML explainers as inspectable models. Use when the requested deliverable is an interactive explainer, simulator, state or sequence walkthrough, interactive comparison, or visual review surface.
Model authoritative state, lifecycle transitions, invariants, freshness, concurrency, replay, and recovery. Use when the task centers on correctness across persisted state, lifecycle transitions, or multiple actors.
Diagnose failures and regressions through a red-capable feedback loop and the first contract divergence. Use when behavior is broken, inconsistent, slow, throwing, failing tests, or reproducible through logs, traces, screenshots, or runtime state.
Map current systems through representative execution paths, state ownership, boundaries, contracts, and proof. Use when the requested deliverable is a current-system map, end-to-end trace, complete registered-surface inventory, or live-implementation contrast.
Turn a settled approach into a human-readable, implementation-ready packet.
Audit an implementation's engineering structure and propose evidence-backed corrections.
| name | yesh-architect |
| description | Design a concrete target architecture from live contracts, execution paths, state ownership, and constraints. |
Define the target shape before implementation.
Lead with a plain-language explanation of the target shape and why it fits. Follow with contract sketches, state ownership, boundary records, production and test call graphs, migration shape, risks, and open decisions.
Complete the architecture when contracts, ownership, dependency direction, failure behavior, migration, and production and test wiring are resolved enough to guide implementation.
