Design Maintainable Code
Design implementation-ready module boundaries, interfaces, and dependency direction from current project evidence.
Use when: Design implementation-ready code boundaries, interfaces, and dependency direction from current repository evidence. Use before a non-trivial implementation or structural change; do not edit code.
Install only this skill
Section titled “Install only this skill”arcantry skills link design-maintainable-code --scope userThis links only design-maintainable-code to the standard user location, ~/.agents/skills. Use --scope repo for one repository, or add --compat claude when that optional alias is needed.
What it helps with
Section titled “What it helps with”- Choose the smallest maintainable structure that fits current behavior and repository conventions.
- Define responsibilities, interfaces, state ownership, failures, increments, and tests before implementation.
History
Section titled “History”- 2026-09-14 - Add focused code-quality workflows: Arcantry separates evidence-backed code assessment, maintainable structural design and authorized behavior-preserving refactoring into three focused public skills.
Examples
Section titled “Examples”Design a cross-module feature
Section titled “Design a cross-module feature”Prompt
Use the design-maintainable-code skill to design this non-trivial feature before any source files are edited.
Expected outcome
The result fixes concrete module and dependency decisions using the project’s existing conventions.
Evaluate a proposed abstraction
Section titled “Evaluate a proposed abstraction”Prompt
Use the design-maintainable-code skill to decide whether this new interface is justified by the current callers.
Expected outcome
The design keeps or rejects the interface from verified variation and maintenance cost rather than preference.