improve-codebase-architecture
Improve Codebase Architecture
Find architectural friction the way a future maintainer or coding agent experiences it. Favor deep modules: a small interface hiding substantial implementation complexity.
Read $SKILL_DIR/references/deepening-guide.md before classifying dependencies, judging test strategy, or drafting the RFC.
Workflow
- Decide scope. If the user gives a path, subsystem, ticket, or architectural theme, stay inside it. Otherwise explore until you can name the highest-friction areas.
- Explore the codebase using whatever discovery tools are available.
- If subagents are available, you may run one exploration pass and 2-4 design passes in parallel.
- If subagents are unavailable, do the same work sequentially. Do not fail just because parallelism is unavailable.
- Treat friction as evidence: cross-file bouncing, redundant adapters, shallow modules, hidden orchestration, and tests that protect internals instead of behavior.
- Surface 3-5 candidate deepening opportunities. For each candidate, report:
ClusterWhy they're coupledDependency categoryTest impactExpected leverage
More from bahayonghang/my-claude-code-settings
tech-design-doc
Generate technical design documents with proper structure, diagrams, and implementation details. Use when designing a new feature, documenting architecture decisions, or planning refactoring work. Default language is English.
106bidwriter
智能标书编写专家，专精工程咨询、建筑设计、市政工程领域的投标文件编写。
70article-cover
Generate article cover images as SVG. Use when creating cover/banner/header graphics for blogs, documentation, social media cards, or OG images. Trigger this skill whenever the user mentions article covers, blog banners, post thumbnails, social sharing images, or any visual header for written content — even if they don't explicitly say 'SVG'. Do not use it for full-scene illustrations, photo editing, or slide theme work.
63tech-blog
Write technical blog posts with source code analysis OR doc-driven research. Use when user wants to explain system internals, architecture, implementation details, or technical concepts with citations.
53git-commit-cn
Safely orchestrate Chinese Conventional Commits for staged Git changes, or for all working-tree changes when the user explicitly asks to include everything. Use when the user asks to write a commit message, split staged changes, split all changes, commit everything regardless of stage state, include untracked files in the commit set, organize a messy index before committing, prepare a Chinese commit, draft a Conventional Commit, or generate structured commit text without pushing by default.
47gemini-image
>-
46