Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sediman-agent/architect
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
Passed 13 of 21 test cases with the skill, and 7 of 21 without it.
and 6 more in the full report
8 fixed6 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are designing a new payment settlement workflow engine. Identify the exact external runner models you dispatch during the design synthesis phase.
| Checked | Without skill | With skill |
|---|---|---|
| Includes gpt-5.5-high-fast in the design runner list | Missed | Passed |
| Includes composer-2.5-fast in the design runner list | Missed | Passed |
The instructions your model reads when the skill loads.
Design before implementing. Sketch types, function signatures, class shapes, and module boundaries with not implemented bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch. If implementation proves the sketch wrong, throw it out and redesign.
Open a todolist with one entry per phase before starting. Autonomous mode without checkpoints needs the list to show phase position and keep phases from silently disappearing.
Build a real mental model of every system the new code touches. Run the how skill over the relevant subsystems. Critique mode if existing structure is the constraint or the design must push back on it.
Naming a file isn't grounding. Produce the traced model how prescribes. If the design redefines ownership or layering, also run the why skill on the existing shape so the rationale becomes a constraint, not a guess.
Skip Phase A only when the work is genuinely greenfield with no surrounding system to integrate.
Run the arena skill with the design-sketch task and the Phase A grounding artifacts. Pass references/runner-prompt.md as each runner's prompt. Each candidate produces a design package shaped per references/rationale-template.md: the caller's usage written first, then the type sketch, function signatures, module map, and prose rationale derived from it.
Use these runner slugs: claude-opus-4-8-thinking-xhigh, gpt-5.3-codex-high-fast, gpt-5.5-high-fast, and composer-2.5-fast.
This is the exhaust-the-design-space principle skill made concrete. Whole-shape alternatives, not point fixes inside one shape.
Arena returns one synthesized design package. The synthesis decision populates the rationale's "Synthesis decision" section.
Default: proceed directly to implementation with the synthesized design. No human checkpoint.
Opt in to a checkpoint when the invoker explicitly asks: "/architect with checkpoint," "stop and show me before implementing," or similar. Then surface the synthesized design and pause for sign-off.
The synthesis can ship as its own commit either way. That's the "scaffold first" mode of the foundational-thinking principle skill; subsequent commits read as filling in bodies against a stable contract. Planned and scoped breakage during fill-in is fine, per the outcome-oriented-execution principle skill. For adversarial pressure on the design before implementing, run the interrogate skill on the synthesized sketch.
test cases passed, vs 7 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.