agentsclimarketplace
Sign in

Improve codebase architecture

Skill roronoazoroshao369/vibe-coding-os/skills/core/improve-codebase-architecture

Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.From the repository description

Install
npx -y skills add roronoazoroshao369/vibe-coding-os --skill improve-codebase-architecture

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

  • 0 stars0 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.4 KB, 271 tokens by cl100k_base, as published. Nobody here has run it

Skill: Improve Codebase Architecture

Purpose

Improve architecture deliberately by finding high-leverage seams, simplifying concepts, and preserving behavior.

When to use

Use for planned architecture improvement, repeated pain, deep module confusion, or code that blocks future work.

Inputs

System context, pain points, domain language, ADRs, tests, constraints, and target quality attributes.

Workflow

  1. Zoom out and read context/ADRs.
  2. Identify architecture smells and the domain concepts behind them.
  3. Propose small safe improvements with tradeoffs.
  4. Prefer behavior-preserving refactors with tests.
  5. Capture significant decisions as ADRs.

Outputs

Architecture review, prioritized improvements, risks, test plan, ADR candidates, and follow-up slices.

Failure modes

Big-bang rewrites, aesthetic refactors without user value, ignoring tests, or changing domain terms casually.

Verification checklist

Improvement has a clear driver; behavior is protected; slices are reviewable; ADR/context updates are identified.

Ghi chú tiếng Việt

Cải thiện kiến trúc phải có lý do và kiểm chứng. File liên quan: templates/architecture-review-template.md, workflow architecture, ADR/context.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most architecture codebase skills give in 271 tokens

Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07

  • Ask the user which candidate to explorein 45 of 811, across 15 files
  • Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
  • Read any relevant architecture decision records firstin 31 of 811, across 8 files
  • Use exact glossary terms in every suggestionin 30 of 811, across 10 files
  • Accept dependencies instead of creating themin 24 of 811, across 5 files
  • Include before and after visualisations for each candidatein 24 of 811, across 5 files
  • Read the domain glossary before exploringin 24 of 811, across 6 files
  • Return results instead of producing side effectsin 23 of 811, across 4 files
  • Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
  • Introduce seams only where things varyin 22 of 811, across 3 files
  • Reduce the number of methodsin 21 of 811, across 2 files
  • Design deep modules with small interfacesin 21 of 811, across 3 files

Said here and by no other author read

  • read system context and ADRs
  • identify architecture smells and domain concepts
  • propose small safe improvements with tradeoffs
  • prefer behavior-preserving refactors with tests

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,629. 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.