codebase-explorer

Maps Empathy Ledger data flows from database to API routes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Acurioustractor/empathy-ledger-v2 --skill codebase-explorer-acurioustractor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-explorer
Source: https://github.com/Acurioustractor/empathy-ledger-v2/tree/main/.claude/skills/local/codebase-explorer
Command: npx skills add https://github.com/Acurioustractor/empathy-ledger-v2 --skill codebase-explorer-acurioustractor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers understand the Empathy Ledger codebase architecture, data flows, and system relationships.

Core Features & Use Cases

  • Codebase mapping: Locate where data travels from database tables to API routes and services.
  • Architecture documentation: Map core components, data paths, and multi-tenant isolation.
  • Reference guidance: Provide quick references to types, migrations, and service boundaries.
  • Use Case: When you need to answer "where is X located?" or "how does X connect to Y?"

Quick Start

Ask the skill to identify where a feature is implemented, for example: "Show me the source location for the stories feature and its data flow from Supabase to UI components."

Frequently Asked Questions about codebase-explorer

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

FAQPage Schema
How do I trace data flow from database tables to API routes in a codebase?

Codebase mapping locates where data travels from database tables to API routes and core services. It identifies service boundaries and provides structured file references to track data paths from Supabase to UI components within the Empathy Ledger architecture.

How does multi-tenant isolation work in the Empathy Ledger architecture?

Multi-tenant isolation is mapped by documenting core components, service boundaries, and system relationships. The skill identifies these architectural patterns to show how tenant data separation is maintained across database schemas and API routes.

What is the best way to document database schemas, type definitions, and API routes for an existing project?

The best way to document database schemas, types, and API routes is to map core components and data paths using structured file references. This skill satisfies those requirements by identifying service boundaries and system relationships within the Empathy Ledger codebase.

Can I use this to find where a specific feature is implemented across services and UI components?

Yes, you can locate where a specific feature is implemented by asking the skill to identify its source location. It maps the data flow from the database through API routes to UI components, showing how different parts of the codebase connect.

Do I need to manually configure anything to start exploring the codebase architecture?

No manual configuration is required to start exploring the codebase architecture. You can immediately ask the skill to identify where a feature is implemented or how components connect, and it will use structured file references and patterns to provide answers.