- Backend: FastAPI app with all models, services, schemas, routes - Admin Panel: Next.js dashboard with all modules (CRM, POS, repairs, warranties, billing, notifications, etc.) - Ecommerce: storefront (submodule) + product catalog - AI Agents: .agents/ skill library for Antigravity IDE - Docs: architecture, billing, notification gateway markdown - Submodules: Backend/OpenWA, Ecommerce/File 2/storefront
1.1 KiB
1.1 KiB
| name | description |
|---|---|
| Notion MCP | Tool adapter for reading and updating human-facing specifications and team knowledge base entries on Notion. |
Skill: Notion MCP
1. Purpose
Sync high-level requirements, decisions, and product specs between the code workspace and the team Notion portal.
2. When to Use
During initial planning (requirements gathering) or documentation wrap-up.
3. Preconditions
- Notion credentials and workspace mapping are configured.
4. Operational Rules
- DO NOT use Notion as the primary source of truth for technical code context, APIs, database schemas, or code snippets (use local markdown files inside the
docs/folder instead). - Limit calls to Notion to avoid excessive API latency and token waste.
5. Step-by-Step Checklist
- Search Notion for product specifications or business rules related to the active feature.
- Read the page content and map it to local design specifications.
- Once changes are completed, compile a human-readable release log.
- Append/update the release logs on the designated Notion dashboard.