agent-ops-project-sections
Identify and map different sections of a software project (API, frontend, database, CLI, domain). Use for context scoping and architecture documentation.
npx skills add majiayu000/claude-skill-registry --skill agent-ops-project-sections-weholt-script-cast --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Project Section Identification Workflow ## Purpose Analyze a software project to identify and categorize its logical sections (backend API, frontend, database layer, CLI, domain logic, etc.). This enables: - **Context scoping**: Focus agent work on specific project areas - **Architecture documentation**: Generate structured overview - **Dependency analysis**: Understand how sections relate - **Instruction optimization**: Input for optimizing prompt/skill context ## When to Use - Starting work on an unfamiliar codebase - Need to scope work to a specific layer (e.g., "just the API") - Generating architecture documentation - Preparing context for focused implementation - Input for `agent-ops-context-map` or instruction optimization ## Section Types | Section Type | Description | Common Indicators | |--------------|-------------|-------------------| | `api` | REST/GraphQL endpoints, route handlers | `/api/`, `/routes/`, `controllers/`, OpenAPI specs | | `frontend` | UI components, pages, client-side code | `/components/`, `/pages/`, `.tsx`, `.vue`, `.svelte` | | `backend` | Server-side logic, services | `/services/`, `/handlers/`, server entry points | | `database` | Data access, mig
- Purpose
- When to Use
- Section Types
- Procedure
- Phase 1: Project Discovery
- Phase 2: Section Identification
- Phase 3: Dependency Mapping
- Phase 4: Generate Output
- Output Locations
- Integration Points
- Scoped Context Mode
- Completion Criteria
- Anti-patterns (avoid)
- Examples
What does the agent-ops-project-sections skill do?
Identify and map different sections of a software project (API, frontend, database, CLI, domain). Use for context scoping and architecture documentation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill agent-ops-project-sections-weholt-script-cast --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.