improve-codebase-architecture

Identify architectural friction and propose module deepening opportunities aligned with ADRs and CONTEXT.md.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ClyptAI/Clypt-Frontend --skill improve-codebase-architecture-clyptai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/ClyptAI/Clypt-Frontend/tree/main/.agents/skills/mattpocock-skills/improve-codebase-architecture
Command: npx skills add https://github.com/ClyptAI/Clypt-Frontend --skill improve-codebase-architecture-clyptai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface architectural friction in a codebase and surface deepening opportunities to improve testability and AI-navigability.

Core Features & Use Cases

  • Explore codebase for shallow modules and misaligned seams guided by CONTEXT.md and ADRs.
  • Present concrete deepening candidates with involved files, problem, solution, and locality/leverage.
  • Conduct an interactive grilling loop to refine recommendations with user input and ADR alignment.

Quick Start

Ask me to explore the codebase and surface deepening opportunities aligned with CONTEXT.md and ADRs.

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 architectural friction in my codebase to improve testability?

You identify architectural friction by analyzing code for shallow modules and misaligned seams guided by CONTEXT.md and ADRs. This surfaces deepening candidates with involved files, problems, solutions, and locality to increase testability.

What is a deepening opportunity in codebase architecture?

A deepening opportunity is a concrete architectural change mapping to a deepened module interface with a defined seam and adapters. It targets misaligned seams to improve testability and AI-navigability based on domain-language guidance.

How do I refactor code to increase AI-navigability using domain language?

You refactor code by analyzing domain-language guidance in CONTEXT.md and ADRs to uncover deepening opportunities. Recommendations map to deepened module interfaces with defined seams, outputting change guidance aligned with architectural decisions.

Can I use ADRs to guide codebase refactoring decisions?

Yes, you use ADRs to guide refactoring through an interactive grilling loop that refines recommendations with user input and ADR alignment. It ensures proposed solutions map to deepened modules and outputs change guidance aligned with ADRs.

Does this codebase architecture analysis require any external dependencies?

No, this architecture analysis requires no external dependencies. It operates directly on your codebase files, analyzing CONTEXT.md and ADRs to surface deepening opportunities and output change guidance without needing additional libraries or tools.