codebase-architect

Advise file placement and refactoring for vertical slice architecture.

4|1|Updated Jan 8, 2024

Search Tags:#architecture #dependency management #project structure #vertical slice #python modules #codebase refactoring #documentation taxonomy

Ready to run

npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill codebase-architect-opensourcepharmafoundation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codebase-architect
Source: https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg/tree/main/.claude/skills/codebase-architect
Command: npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill codebase-architect-opensourcepharmafoundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you prevent codebase sprawl by guiding where new files and modules should live, how they should be structured, and how to migrate legacy scripts into the intended vertical-slice layout.

Core Features & Use Cases

Vertical slice enforcement: Organizes code by domain/feature (e.g., scrapers, integration, analysis) rather than by technical layer.
Module boundary & dependency direction: Ensures src/ production code follows inward dependency flow toward utils/, while scrapers remain independent.
Migration guidance: Recommends how to adapt legacy code moved from scripts/ into src/ so it matches the project's module-per-feature pattern.
Documentation taxonomy: Places docs into the correct docs/ subdirectory type (e.g., investigations/, next-steps/, databases/) to reduce documentation sprawl.
Architecture decision support: Answers placement/refactoring questions using the project’s established module map and decision tree.

Quick Start

Ask the skill where a new scraper, analysis module, integration script, or doc should go and what structure it should follow based on the existing module map.

Frequently Asked Questions about codebase-architect

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

FAQPage Schema

How do I organize Python modules using vertical slice architecture?▼

Vertical slice architecture organizes Python modules by domain features like scrapers or analysis rather than technical layers. This Skill inspects your directory structure and project docs to recommend boundary-compliant file placement and inward dependency flow toward utils.

What is the best way to migrate legacy scripts into src packages?▼

Migrating legacy scripts into src packages requires adapting them to match a module-per-feature pattern. This Skill recommends specific refactoring decisions and structural changes to ensure migrated code follows established vertical slice boundaries and dependency directions.

How do I manage dependency direction between production code and scrapers?▼

Dependency direction ensures src production code flows inward toward utils while scrapers remain independent. This Skill applies your project's module map to verify boundaries and recommend correct structural relationships between integration, analysis, and RAG components.

How do I structure documentation taxonomy to reduce sprawl across project subdirectories?▼

Documentation taxonomy places docs into correct subdirectory types like investigations, next-steps, or databases to reduce sprawl. This Skill uses your project's established decision tree to classify and route documentation files to their appropriate directories.

When do I need vertical slice architecture for codebase refactoring?▼

You need vertical slice architecture when creating new modules, migrating legacy code from scripts into src packages, or reorganizing technical debt. This Skill inspects current directories to recommend boundary-compliant structure across scrapers, integration, and analysis components.

Can I use vertical slice architecture without an existing module map?▼

Vertical slice architecture enforcement requires reading existing project architecture docs and module maps. Without established documentation of your project's intended structure and decision tree, this Skill cannot accurately recommend boundary-compliant placement or dependency direction.