skills.rest
esxr
esxrCOMMUNITY
Explore all skills by this author →
Website𝕏@pranav_dhooliaGitHub

product-map

Verify existence of Prisma models, API routes, UI components, user stories, and EIS documents.

Updated Apr 20, 2026
Search Tags:#user stories#API routes#UI components#Prisma models#EIS documents#existence check
One-click install
npx skills add https://github.com/esxr/product-wiki --skill product-map
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-map
Source: https://github.com/esxr/product-wiki/tree/main/skills/entity-map
Command: npx skills add https://github.com/esxr/product-wiki --skill product-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill confirms the existence of key project components before creating wiki pages, avoiding speculative entries and maintaining accuracy.

Core Features & Use Cases

  • Entity Existence Check: Before creating a new wiki page, check if a Prisma model, API route, component, user story, or EIS document exists.
  • Prisma Schema Validation: Ensures consistency with the Prisma schema.
  • API Route Verification: Validates API endpoints before creating documentation.
  • Component Verification: Confirms the existence of UI components before adding them to the wiki.
  • Story and EIS Documentation: Ensures that user stories and EIS documents are accounted for in the wiki.

Quick Start

Run the product-map skill before creating a new page to ensure its source object exists.

Frequently Asked Questions about product-map

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

FAQPage Schema
What is the best way to verify UI components and user stories before adding them to a project wiki?▼

The best way to verify UI components and user stories is to perform an existence check against your project's codebase and tracking documents. This confirms the source objects exist, preventing inaccurate wiki entries and maintaining project knowledge base accuracy.

Can I validate EIS documents and user stories against my codebase before writing project documentation?▼

Yes, you can validate EIS documents and user stories by checking them against your project's existing documentation and tracking systems. This confirms they are accounted for before you create new wiki pages, avoiding duplicate or speculative entries.

How do I prevent speculative wiki entries when documenting new API endpoints and components?▼

To prevent speculative wiki entries, run an existence check against your Prisma schema, API routes, and UI components before creating new pages. This validates that the source objects actually exist in the codebase prior to documentation generation.

Does validating Prisma schema consistency help avoid duplicate documentation pages?▼

Validating Prisma schema consistency helps avoid duplicate documentation pages by confirming the exact existence of models before creating new wiki entries. This ensures your knowledge base accurately reflects the current project state without speculative duplicates.

Related Skills

Explore More Product & Management Skills→
CrazyDubyaCrazyDubya

api-documentation-generator

Generate OpenAPI 3.0 documentation from API route definitions in code.

Community
Intermediate
JustinBeaudryJustinBeaudry

extract

Extract wiki-worthy knowledge from unprocessed session summaries into wiki pages.

Community
Intermediate
bibo1243bibo1243

共享記憶系統

Orchestrate centralized shared memory for multi-agent AI systems.

Community
Advanced
majesticlabs-devmajesticlabs-dev
47

advanced-rails-patterns

Refactor Rails controllers, models, and service objects using Sandi Metz rules.

Official
Advanced