Maps out a project's domain objects (models, routes, components) to ensure documentation matches the actual codebase.
Install
mkdir -p .claude/skills/product-map && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14405" && unzip -o skill.zip -d .claude/skills/product-map && rm skill.zipInstalls to .claude/skills/product-map
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Canonical enumeration of project Prisma models, API routes, components, user stories, and EIS docs. Use before creating any docs/wiki/ page to verify the source object exists. Triggers on "entities", "which prisma models", "list endpoints", "wiki bootstrap", "does <Entity> exist", "enumerate domain", "product-wiki plugin".Key capabilities
- →Enumerate Prisma models from schema files
- →List API routes and their methods from route files
- →Identify UI components from specified directories
- →Read user stories from an index file and individual markdown files
- →Enumerate EIS documents from a designated folder
- →Verify the existence of source objects before creating documentation
How it works
This skill scans predefined project paths for Prisma schemas, API routes, UI components, user stories, and EIS documents to provide an authoritative enumeration of existing domain objects, preventing documentation of non-existent features.
Inputs & outputs
When to use product-map
- →List API endpoints
- →Verify prisma models
- →Bootstrap project documentation
About this skill
Entity Map
Authoritative enumeration of project domain objects. Never invent entities. If a model, endpoint, component, story, or EIS is not listed in one of the authoritative sources below, it does not exist yet — do not create a wiki page for it.
Config File Lookup
Before probing any paths, check whether the project has a config file at .claude/plugins/product-wiki/entity-map.json. If that file exists, read it — it may override any of the default probe paths below.
Authoritative Sources (in precedence order)
- Prisma schema — ground truth for entity names and fields. Probe in this order and use the first that exists:
src/prisma/schema.prismaprisma/schema.prisma
- API routes — ground truth for HTTP endpoints. Probe in this order and use the first that exists:
src/app/api/**/route.tsapp/api/**/route.ts
- UI components — ground truth for components. Probe in this order:
src/components/components/
- User stories index — ground truth for user stories:
docs/reference/stories/INDEX.md
- EIS documents — ground truth for EIS (Event / Integration Spec) documents:
docs/eis/EIS-*.md
How to Enumerate
Entities (Prisma models)
Probe for the schema file using the order above. Then:
Grep pattern: "^model\s+(\w+)\s*\{" in the located schema file
Endpoints
Glob the API routes directory using the probe order above:
Glob: src/app/api/**/route.ts (or app/api/**/route.ts if the src/ variant is absent)
Each file's path (minus the api/ prefix and /route.ts suffix) is the endpoint path. Methods (GET, POST, PATCH, DELETE) are exported as named functions inside each route.ts.
Components
Glob the components directory using the probe order above:
Glob: src/components/**/*.tsx (or components/**/*.tsx)
User stories
Read: docs/reference/stories/INDEX.md
Glob: docs/reference/stories/US-*.md
EIS documents
Glob: docs/eis/EIS-*.md
Wiki Page Mapping Rule
| Source object | Wiki page path |
|---|---|
Prisma model Foo | docs/wiki/entities/Foo.md |
Endpoint GET /x/y | docs/wiki/endpoints/get-x-y.md (lowercase, / -> -) |
Story US-123 | docs/wiki/stories/US-123.md |
EIS EIS-045 | docs/wiki/eis/EIS-045.md |
One page per source object. No speculative pages.
Currency Rule
The Prisma schema (whichever path resolves) is the single source of truth for entity names and field shapes. When a wiki page references a field, quote the schema (include the field name, type, and any @default / @db decorators). Re-read the schema at the start of every wiki update — do not rely on memory.
Never Hallucinate
If an agent considers writing a wiki page for an entity/endpoint/story/EIS that does not appear in the authoritative sources above, it must stop and either (a) find the source file, or (b) decline to create the page. Speculative wiki pages corrupt the map.
When not to use it
- →When the project does not use Prisma, API routes, or UI components as defined
- →When the goal is to create speculative documentation for non-existent features
- →When the user is not asking to enumerate domain objects or verify their existence
Limitations
- →Must not invent entities; only lists what exists in authoritative sources
- →Prisma schema is the ground truth for entity names and fields
- →Requires specific file paths and naming conventions for enumeration
How it compares
This skill provides a canonical, source-grounded enumeration of project entities, ensuring that documentation efforts are based on existing code and specifications, unlike creating wiki pages based on memory or speculation.
Compared to similar skills
product-map side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| product-map (this skill) | 0 | 3mo | No flags | Intermediate |
| messaging-decision | 0 | 1mo | No flags | Advanced |
| database-design | 6 | 6mo | Review | Intermediate |
| database-schema-designer | 6 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
messaging-decision
Brilhante29
Decide whether a portfolio repository should use no broker, transactional outbox, RabbitMQ, Kafka/Redpanda, Redis Streams, or NATS based on delivery semantics, ordering, replay, retry/DLQ, throughput, and benchmark evidence.
database-design
davila7
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
database-schema-designer
davila7
Design robust, scalable database schemas for SQL and NoSQL databases. Provides normalization guidelines, indexing strategies, migration patterns, constraint design, and performance optimization. Ensures data integrity, query performance, and maintainable data models.
schema-designer
clidey
Help design database schemas, create tables, and plan data models. Activates when users ask to create tables, design schemas, or model data relationships.
managing-database-sharding
jeremylongshore
Process use when you need to work with database sharding. This skill provides horizontal sharding strategies with comprehensive guidance and automation. Trigger with phrases like "implement sharding", "shard database", or "distribute data".
database-design
Harmitx7
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.