improve-codebase-architecture

Files (3)

• HTML-REPORT.md
• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Improve codebase architecture

Identify concrete friction that a deeper module could remove: callers coordinating internals, duplicated domain logic, leaky boundaries, or behavior that cannot be tested through a useful public interface. Trace the relevant code and use `codebase-design` for the module and seam vocabulary.

Consult the domain glossary and relevant ADRs when they constrain a proposed change. Read the affected subsystem, not the whole repository by default. Use independent readers only when distinct exploration angles make parallel work useful and the harness permits it.

For each worthwhile candidate, show the source evidence, proposed interface, complexity it would hide, deletion opportunity, and meaningful behavior check. Distinguish demonstrated friction from style preference.

Use a concise written report for ordinary reviews. Create an HTML/visual comparison when requested or when it materially clarifies the choice; select available local visualization tooling rather than requiring a CDN. Use `grilling` when the user requests an interactive design discussion or a consequential decision needs their input.

Complete the requested review. When implementation is authorized, carry the selected change through verification. Do not require a selection checkpoint if the user has already selected the target.

From jamesdebatty/skills, MIT.

More from jamesdebatty/skills