improve-codebase-architecture

Identify deepening opportunities in modular codebases using domain glossary and ADRs.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/MatheusBBarni/symphony-orchestrator --skill improve-codebase-architecture-matheusbbarni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/MatheusBBarni/symphony-orchestrator/tree/main/.agents/skills/improve-codebase-architecture
Command: npx skills add https://github.com/MatheusBBarni/symphony-orchestrator --skill improve-codebase-architecture-matheusbbarni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface architectural friction by surfacing deepening opportunities in a codebase to improve testability, AI-navigability, and long-term maintainability.

Core Features & Use Cases

  • Identify shallow modules by applying domain glossary and ADR decisions to surface high-leverage deepening opportunities.
  • Propose actionable refactor candidates with clear locality and leverage implications, aligned to CONTEXT.md vocabulary.
  • Support a grilling loop workflow to refine design decisions and reconcile ADR conflicts when needed.

Quick Start

Run the Agent tool with subagent_type=Explore to start identifying deepening opportunities.

Frequently Asked Questions about improve-codebase-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify shallow modules in a codebase for refactoring?

You can identify shallow modules by applying the domain glossary and ADR decisions to surface high-leverage deepening opportunities, proposing actionable refactor candidates with clear locality and leverage implications.

What is a deepening opportunity in software architecture?

A deepening opportunity in software architecture is a refactoring target that improves testability, AI-navigability, and maintainability by transforming shallow modules into deeper, more modular components with reduced coupling.

How do I reconcile ADR conflicts when refactoring a modular codebase?

To reconcile ADR conflicts during a codebase refactor, use a grilling loop workflow to refine design decisions and align proposed refactoring candidates with the vocabulary defined in CONTEXT.md and LANGUAGE.md.

Can I improve codebase testability by analyzing CONTEXT.md and LANGUAGE.md files?

Yes, you can improve codebase testability by analyzing CONTEXT.md and LANGUAGE.md files to surface deepening opportunities, which reduces component coupling and enhances AI navigation across modular software projects.

What's the best way to reduce coupling across components in a modular project?

The best way to reduce coupling across components is to apply the domain glossary and ADRs to identify shallow modules, proposing deepening candidates that improve locality, leverage, and long-term maintainability.