Menu
When you need to understand the directory structure, open-core model, or where to add new code.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
When you need to understand the project's core mandate, operational rules, or "Constitution". Use this skill to align with the project's identity and strict coding standards.
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
When you need to modify the database schema, run migrations, or deploy Supabase changes. Use this for all SQL and Supabase-related tasks.
When you are creating or modifying UI components. Use this skill to ensure consistency with the design system and shadcn/ui.
When you are working on the Tiptap v3 block editor. Use this for extending the editor, adding nodes, or debugging rich text issues.
When you need to run tasks, build projects, or understand the workspace graph using Nx. Use this for all build, lint, and test operations.
| name | project-architecture |
| description | When you need to understand the directory structure, open-core model, or where to add new code. |
| Path | Type | Purpose | Import Alias |
|---|---|---|---|
apps/nextblock | Application | Primary Prod App (Admin + Public). | — |
apps/create-nextblock | Application | CLI Scaffolder. | — |
libs/ui | Library | Shared UI components. | @nextblock-cms/ui |
libs/utils | Library | Core utilities. | @nextblock-cms/utils |
libs/db | Library | Database layer (Supabase). | @nextblock-cms/db |
libs/editor | Library | Tiptap editor package. | @nextblock-cms/editor |
libs/sdk | Library | Public developer SDK surface. | @nextblock-cms/sdk |
libs/ecommerce | Library | Premium E-Commerce. Source-available, license-gated. | @nextblock-cms/ecommerce |
libs/ecommerce are present but require a License Key to activate.libs/ui.libs/utils.libs/db.apps/nextblock/app.apps/create-nextblock.libs/* can depend on other libs/* (e.g., ui depends on utils).apps/* depend on libs/*.libs/ui MUST NOT depend on apps/nextblock. This creates a circular dependency and breaks the build.apps/create-nextblock/templates/nextblock-template is generated code.apps/nextblock instead, then run npm run sync:create-nextblock to update the template.For questions about the intent behind the architecture, monetization strategy, or future roadmap that aren't clear from the directory structure itself:
Use the NotebookLM MCP tool:
mcp_notebooklm_ask_question({ question: "Why did we choose this architecture?" })
This queries the "NextBlock CMS: Roadmap and Monetization Strategy" notebook for high-level vision context.