Improve codebase architecture
Skill kimtth/agent-skill-100-lines-or-less/skills/improve-codebase-architecture
Use when: propose structural improvements to a codebase without rewriting it wholesale.From its SKILL.md
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill improve-codebase-architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 216 tokens by cl100k_base, as published. Nobody here has run it
Goal: identify high-leverage architecture changes and sequence them safely.
Use for:
- tangled dependencies, leaky boundaries, or scattered logic
- modules that are hard to change or test in isolation
- recurring bugs that trace back to structure, not code
Workflow:
- Map the current modules, boundaries, and data flow.
- Locate the pain: what change is consistently hard or risky.
- Name the architectural cause, not the surface symptom.
- Propose a target structure with clearer boundaries.
- Sequence the move as small, independently shippable steps.
- Define how each step is verified before the next.
Look for:
- deep modules with simple interfaces vs. shallow leaky ones
- cyclic dependencies and god objects
- business logic mixed with I/O or framework code
- duplicated knowledge across layers
Rules:
- justify each change by a concrete pain it removes
- prefer incremental migration over big-bang rewrite
- keep public behavior stable unless change is the goal
- do not add abstraction without a second real use
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.