codebases

Document external codebase structure, dependencies, and architecture in Markdown files.

34|2|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/retran/meowary --skill codebases
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebases
Source: https://github.com/retran/meowary/tree/main/.shared/skills/codebases
Command: npx skills add https://github.com/retran/meowary --skill codebases

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It provides a standardized and living document format for maintaining key information about external codebases, ensuring consistency and easy updates.

Core Features & Use Cases

  • Centralized documentation: Hosts architecture, dependencies, and key decisions for each codebase.
  • On-demand context: Loads relevant details when working within a codebase to facilitate onboarding and knowledge sharing.
  • Use Case: When starting work on a new project, create codebases/<name>.md to quickly document its tech stack and structure for all team members.

Quick Start

Create or update the codebase file before working on a project to ensure all relevant details are readily available and structured.

Frequently Asked Questions about codebases

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

FAQPage Schema
How do I maintain consistent documentation for an external codebase?

Centralize codebase documentation by creating a standardized file to track architecture, dependencies, and conventions, ensuring consistency and easy updates across the team.

What is the best way to document tech stack and structure for developer onboarding?

Document the tech stack and structure by hosting architecture and key decisions in a centralized file that loads on demand to facilitate onboarding and knowledge sharing.

How do I standardize project workflows and decision tracking across multiple codebases?

Standardize workflows and decision tracking by enforcing a comprehensive format that captures structure, dependencies, architecture, and conventions for each codebase.

Can I use a single format to track architecture and dependencies for new projects?

Yes, you can use a standardized living document format to record dependencies and architecture, ensuring accurate context and decision tracking across new projects.

When do I need to create a centralized codebase documentation file?

Create a centralized documentation file when starting work on a new project, ensuring all relevant tech stack and structural details are readily available and structured.