agentsclimarketplace
Sign in

Architecture refactor guidance

Skill motao123/dev-workflow-kit/architecture-refactor-guidance

Use when the core problem is structural change: boundaries, coupling, module seams, interface extraction, or safe refactor sequencing. This skill helps decide how to reshape code without turning implementation into guesswork.From its SKILL.md

Install
npx -y skills add motao123/dev-workflow-kit --skill architecture-refactor-guidance

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 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.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, 335 tokens by cl100k_base, as published. Nobody here has run it

Architecture Refactor Guidance

Use this skill when the main uncertainty is structural rather than purely functional.

Trigger Conditions

Use this skill when:

  • the user asks how to split, extract, or reorganize a module
  • a refactor needs safer sequencing before implementation starts
  • coupling, boundaries, ownership, or interfaces are the real issue
  • a migration or structural cleanup should be staged carefully
  • the code works today, but the structure is becoming the bottleneck

Do not use this skill for generic feature planning, direct implementation, or root-cause debugging.

Workflow

  1. Read the current structure and identify the relevant boundaries.
  2. Find the main structural pain points: coupling, leakage, unstable contracts, or oversized modules.
  3. Identify seams where change can happen safely.
  4. Choose the safest staging order for the refactor.
  5. Define how behavior preservation will be verified.
  6. Recommend the next implementation path.

Output

For non-trivial work, provide:

  • current structural assessment
  • pain points and risks
  • proposed boundaries or seams
  • staged refactor order
  • preservation and verification strategy
  • recommended next step

Coordination

After structural guidance:

  • continue in the active implementation workflow for the implementation itself
  • use planning if broader scope or acceptance is still unclear
  • use ship-readiness before merging large structural changes

Invocation Examples

  • "Use architecture-refactor-guidance before we split this module into cleaner boundaries."
  • "Use architecture-refactor-guidance to decide how to stage this refactor safely."
  • "Use architecture-refactor-guidance to reduce coupling here without changing behavior."

What ships with it: 3 files

1.5 KB alongside SKILL.md

evals/

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.