Skill

brownfield-index

Invoke when the user is new to an unfamiliar / legacy / brownfield codebase and wants a structural understanding — module map, component inventory, API surface, data flow. Triggers on "legacy code", "brownfield", "unfamiliar", "new to this code", "new to this project", "just joined", "inherited codebase", "explore codebase", "understand structure", "index code", "map modules", "tour", "onboard", "what is this project".

Install

npx claudepluginhub curdx/curdx-flow --plugin curdx-flow

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Preview

You are invoked when the user needs a structural map of an existing codebase they are not yet familiar with.

SKILL.md

Similar Skills

design-system

Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.

team-skills-platform

163.7k

ui-demo

Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.

team-skills-platform

163.7k

kotlin-patterns

Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.

team-skills-platform

163.7k

Stats

Stars0

Forks0

Last CommitApr 22, 2026

Actions

View Source View Plugin View on GitHub View README

Brownfield Index

You are invoked when the user needs a structural map of an existing codebase they are not yet familiar with.

Preconditions

The repository root is the current working directory (or a path the user specifies).
The project is not a new /curdx-flow:init-ed greenfield project (if it is, direct the user to /curdx-flow:start instead).

Workflow

Step 1: Detect project type

Read package.json / Cargo.toml / pyproject.toml / go.mod / pom.xml to classify the ecosystem and build tool. This determines which directory conventions to apply.

Step 2: Scan directory structure

Produce a top-level inventory:

Entry points (main / index / bin scripts)
Module directories (src/, lib/, internal/, pkg/ …)
Test directories
Config files
Tooling (CI, lint, format configs)

Step 3: Component inventory

For each module directory, list:

Files and their apparent role (inferred from names + top-of-file comments)
Public exports / exported symbols
Third-party dependencies imported

Step 4: API surface

If HTTP / RPC endpoints exist, index them: route → handler → middleware. For CLI tools, index commands → handlers.

Step 5: Write index document

Output .flow/codebase-index.md containing:

Overview (project purpose, build tool, runtime)
Directory tree (with per-directory one-liner descriptions)
Entry points (where execution starts)
Key abstractions (core types, interfaces, classes that everything else hangs off)
External dependencies (grouped: prod runtime / dev tooling / transitive)
Known gaps / red flags (missing tests, TODOs, suspicious patterns)

Step 6: Hand off

Point the user at the next useful action:

"Looking to add a feature here? Run /curdx-flow:start <name> to begin a spec."
"Debugging something specific? Run /curdx-flow:debug '<symptom>'."

Notes

This skill uses Read + Grep + Glob + Bash with no specialized agent — general tools are enough for structural discovery. The index is meant to be quick (5–10 minutes), not exhaustive.

For deep research into a specific library or framework, use context7 MCP directly.