improve-architecture skillA
improve-architecture is agent-read markdown (skill) from rohitg00/pro-workflow: Audit an area of the codebase and propose the smallest structural moves that improve it - untangle boundaries, kill duplication, fix seams, break cycles. Produces a prioritized plan and decision records, not a rewrite. Use when a codebase feels tangled, hard to change, or is becoming a ball of mud, or when asked to improve or refactor architecture..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# improve-architecture
Invest in the shape of the system a little at a time rather than paying for a
rewrite later. This skill diagnoses and proposes; it does not rewrite on its own.
## Method
1. **Map first.** Get the current shape before judging it - entry points,
modules, data flow, who calls whom. Reuse `module-map` for the one-screen
view; do not skip to opinions.
2. **Find the strain.** Look for the load-bearing problems, not style nits:
- God modules that everything imports and nothing can change safely.
- Leaky boundaries - a module reaching into another's internals instead of
its surface.
- Duplicated logic that drifts (the same rule implemented three ways).
- Wrong seams - the code is split where it does not bend and fused where it
does.
- Cyclic dependencies.
- A shape that fights the domain (see `domain-modeling` - boundaries in code
should track boundaries in the language).
3. **Propose the smallest move.** For each problem, the least change that
relieves it: extract a boundary, collapse a duplicate, invert a dependency,
move a seam. Prefer a sequence of safe steps over one big cut.
…Read the whole file at its exact version.
How to install
mdr add rohitg00/pro-workflow/improve-architecture@git:20260718.7f7209dmdr add rohitg00/pro-workflow/improve-architecture@sha256:d56f882339eaeed8Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_zoe27khh55sj7h5m)
0 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2563 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
rohitg00/pro-workflow · 2,879 stars · license none · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zoe27khh55sj7h5m GET https://markdownregistry.com/api/v1/resolve?ref=rohitg00/pro-workflow/improve-architecture GET https://markdownregistry.com/api/v1/blob/d56f882339eaeed8e6d6fc6944482abd932d5bc300827059e055128a5e389ffa
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from rohitg00/pro-workflow
Every file in rohitg00/pro-workflow