Settle types and module shape before cross-boundary code — competing designs explored in parallel, compared on API surface and invariants, decision recorded with rejected alternatives and an accepted-deviations register.
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/architect/SKILL.mdDesign before steel. When a change crosses a function boundary, explore competing shapes first and commit to one with a written rationale — the cheapest moment to reject a design is before it has code on it.
reviewoh-my-claudecode:architect subagents, each producing: the core types, the module boundary, the API
surface, and how each invariant is preserved. Distinct shapes, not
variations of one idea.minimal-code-discipline).execute brief; implementation reconciles deviations rather than
rediscovering the design.Yeachan-Heo/oh-my-claudecode
453d3de
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.