Skip to content

a5c-ai/babysitter / library/specializations/backend-development/skills/growing-outside-in-systems

growing-outside-in-systems

Verified

Drive feature development using Outside-In TDD with Hexagonal Architecture. Design emerges through inline code, in-memory fakes, interface extraction, and deferred I/O. Use when building features, writing tests, or structuring backend services. Triggers on: TDD, outside-in, hexagonal, ports and adapters, emergent design, acceptance test, component test, walking skeleton, in-memory fakes, component, contract test, adapter, fast tests, sub-second feedback. Language-agnostic (Go, Rust, Python, TypeScript, Java, C#).

FileKindSize
README.mdmarkdown4.2 KB
SKILL.mdskill md8.2 KB
references/folder-structure.mdmarkdown5.9 KB
references/glossary.mdmarkdown1.0 KB
references/methodology.mdmarkdown9.5 KB
references/testing-strategy.mdmarkdown3.9 KB

references/glossary.md

View on GitHub
# Canonical Terms

Use these names consistently throughout conversation and code:

- **Bounded Context (Hexagon):** Primary modular unit. After first mention, use **Bounded Context**.
- **Domain Layer:** Private business rules, entities, and value objects inside a Bounded Context.
- **Application Layer:** Private orchestration/use-case logic inside a Bounded Context.
- **Ports:** Public interfaces of a Bounded Context (`inbound` and `outbound`).
- **DTOs:** Public data contracts used at boundaries.
- **Adapters:** External implementations of Ports.
- **Inter-Hexagon Bridge Adapter:** Adapter that translates one Bounded Context public contract to another.
- **Composition Root (Configurator):** Startup dependency wiring for production and tests; the "wiring diagram" that initializes the system.
- **Acceptance Test:** End-to-end behavior at the service/system boundary (in-process, with in-memory adapters).
- **Component Test:** Behavior inside one Bounded Context.
- **Contract Test:** Verifies a real adapter matches fake/port behavior.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall