improve-codebase-architecture
/improve-codebase-architecture
Szuka możliwości pogłębienia architektury kodu zgodnie ze słownikiem z docs/CONTEXT.md i decyzjami z docs/adr/, by ułatwić testowanie.
- Autor
- yamcodes ↗
- Repozytorium
- arkenv ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 23.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 23.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Szuka możliwości pogłębienia architektury kodu zgodnie ze słownikiem z docs/CONTEXT.md i decyzjami z docs/adr/, by ułatwić testowanie.
Oryginalny opis (EN)
Find deepening opportunities in a codebase, informed by the domain language in docs/CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Jak działa
- Glossary
- Process
Podgląd SKILL.md
---
name: improve-codebase-architecture
description: Find deepening opportunities in a codebase, informed by the domain language in docs/CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
metadata:
internal: true
---
# Improve codebase architecture
Surface architectural friction and propose **deepening opportunities** - refactors that turn shallow modules into deep ones. The aim is testability and AI-navigability.
## Glossary
Use these terms exactly in every suggestion. Consistent language is the point - don't drift into "component," "service," "API," or "boundary." Full definitions in [LANGUAGE.md](LANGUAGE.md).
- **Module** - anything with an interface and an implementation (function, class, package, slice).
- **Interface** - everything a caller must know to use the module: types, invariants, error modes, ordering, config. Not just the type signature.
- **Implementation** - the code inside.
- **Depth** - leverage at the interface: a lot of behaviour behind a small interface. **Deep** = high leverage. **Shallow** = interface nearly as complex as the implementation.
- **Seam** - where an interface lives; a place behaviour can be altered without editing in place. (Use this, not "boundary.")
- **Adapter** - a concrete thing satisfying an interface at a seam.
- **Leverage** - what callers get from depth.
- **Locality** - what maintainers get from depth: change, bugs, knowledge concentrated in one place.
Key principles (see [LANGUAGE.md](LANGUAGE.md) for the full list):
- **Deletion test**: imagine deleting the module. If complexity vanishes, it was a pass-through. If complexity reappears across N callers, it was earning its keep.
- **The interface is the test surface.**
- **One adapter = hypothetical seam. Two adapters = real seam.**
This skill is *informed* by the project's domain model. The domain language gives names to good seams; ADRs record decisions the skill should not re-litigate.
## Process
### 1. Explore
Read the project's domain glossary and any ADRs in the area you're touching first.
Then use the Agent tool with `subagent_type=Explore` to walk the codebase. Don't follow rigid heuristics - explore organically and note where you experience friction:
- Where does understanding one concept require bouncing between many small modules?
- Where are modules **shallow** - interface nearly as complex as the implementation?
- Where have pure functions been extracted just for testability, but the real bugs hide in how they're called (no **locality**)?
- Where do tightly-coupled modules leak across their seams?
- Which parts of the codebase are untested, or hard to test through their current interface?
Apply the **deletion test** to anything you suspect is shallow: would deleting it concentrate complexity, or just move it? A "yes, concentrates" is the signal you want.
### 2. Present candidates
Present a numbered list of deepening opportunities. For each candidate:
- **Files** - which files/modules are involved
- **Problem** - why the current architecture is causing friction
- **Solution** - plain English description of what would change
- **Benefits** - explained in terms of locality and leverage, and also in how tests would improve
**Use docs/CONTEXT.md vocabulary for the domain, and [LANGUAGE.md](LANGUAGE.md) vocabulary for the architecture.** If `docs/CONTEXT.md` defines "Order," talk about "the Order intake module" - not "the FooBarHandler," and not "the Order service."
**ADR conflicts**: if a candidate contradicts an existing ADR, only surface it when the friction is real enough to warrant revisiting the ADR. Mark it clearly (e.g. *"contradicts ADR-0007 - but worth reopening because…"*). Don't list every theoretical refactor an ADR forbids.
Do NOT propose interfaces yet. Ask the user: "Which of these would you like to explore?"
### 3. Grilling loop
Once the user picks a candidate, drop into a grilling conversation. Walk the design tree with them - constraints, dependencies, the shape of the deepened module, what sits behind the seam, what tests survive.
Side effects happen inline as decisions crystallize:
- **Naming a deepened module after a concept not in `docs/CONTEXT.md`?** Add the term to `docs/CONTEXT.md` - same discipline as `/grill-with-docs` (see [CONTEXT-FORMAT.md](../grill-with-docs/CONTEXT-FORMAT.md)). Create the file lazily if it doesn't exist.
- **Sharpening a fuzzy term during the conversation?** Update `docs/CONTEXT.md` right there.
- **User rejects the candidate with a load-bearing reason?** Offer an ADR, framed as: *"Want me to record this as an ADR so future architecture reviews don't re-suggest it?"* Only offer when the reason would actually be needed by a future explorer to avoid re-suggesting the same thing - skip ephemeral reasons ("not worth it right now") and self-evident ones. See [ADR-FORMAT.md](../grill-with-docs/ADR-FORMAT.md).
- **Want to explore alternative interfaces for the deepened module?** See [INTERFACE-DESIGN.md](INTERFACE-DESIGN.md).
Pliki w paczce (4)
- DEEPENING.md 2 KB
- INTERFACE-DESIGN.md 3 KB
- LANGUAGE.md 4 KB
- SKILL.md 5 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · yamcodes/arkenv | 90 | MIT |
| TerminalSkills/skills | 100 | Apache-2.0 |
| callmeteus/gti-skills | 100 | MIT |
| akillness/jeo-skills | 100 | MIT |
| sammcj/agentic-coding | 100 | Apache-2.0 |
| drvoss/everything-copilot-cli | 100 | MIT |
| hachemsoft/ia-toolkit | 100 | MIT |
| niekcandaele/claude-helpers | 100 | MIT |
| runwield/runwield | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki f2093120fcc3 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100codebase-improve-architecture
Eksploruje bazę kodu w poszukiwaniu usprawnień architektury i zwiększa testowalność przez pogłębianie płytkich modułów oraz łączenie modułów ściśle ze sobą sprzężonych. - 100architecture
Wyszukuje możliwości usprawnienia architektury, płytkie moduły i szwy, konsoliduje ściśle sprzężone moduły i poprawia testowalność kodu. - 100deep-codebase-audit
Znajduje okazje do pogłębienia architektury kodu, wskazuje tarcia i proponuje refaktoryzacje zamieniające płytkie moduły w głębokie, dla lepszej testowalności i bezpieczniejszej pracy agentów AI. - 81architecture
Wskazuje płytkie moduły i hipotetyczne szwy w bazie kodu, szuka okazji do refaktoryzacji i konsolidacji ściśle sprzężonych modułów, by kod był lepiej testowalny i czytelny dla AI. - 100jidoka-improve-architecture
Przegląda bazę kodu pod kątem możliwości pogłębienia modułów, opisuje je w raporcie w czacie i zapisuje wybraną jako specyfikację. - 100improve-architecture
Wyszukuje tarcia architektoniczne w bazie kodu i proponuje możliwości pogłębienia, z ocenianymi propozycjami (głębokość, dźwignia, lokalność) dla refaktoryzacji i przeglądu.