agent-guidelines
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.
- License 许可
- MIT
- 最近更新
- 2026-09-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- agent-guidelines
- description
- 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.
03 SKILL.md 正文
Agent Guidelines & Operational Rules
1. The "Constitution" & Project Identity
Project Name: NextBlock CMS Mandate: Build a premium, Open-Core Next.js CMS. Core Stack: Next.js (App Router), Supabase, Tailwind CSS, Tiptap v3.
Critical Rules
- Strict Separation:
libs/uiandlibs/dbmust be publishable as standalone packages. They cannot depend onapps/nextblock. - Open-Core Model: The core is open-source (AGPL); premium extensions (like E-Commerce) are source-available but license-gated.
- Distribution: Users get a standalone app via
npm create nextblock.
2. Operational Rules (Global Context)
- Context First: Before answering complex questions, always check
docs/(start withdocs/README.md) and the relevant linked docs. - Maintain the Docs: When you implement a new feature or make significant changes, update the relevant doc files in
docs/. These are the maintained reference set for both contributors and AI agents. Keep them accurate and current. - Production Migrations: NextBlock has live data. Never rewrite existing migrations for production/shared database changes. Add a new non-destructive migration, run/check
npm run db:migrate:check, and never use reset/fresh/sandbox replay commands against databases containing orders, users, payments, or customer data. - Strict Types: Always use
strict: trueTypeScript. Noanyunless absolutely unavoidable and documented. - Target the App, Not the Template: NEVER edit files in
apps/create-nextblock/templates/nextblock-templatedirectly. Always make changes inapps/nextblock(the core app). The template is synced from the core app via scripts. - Never Edit Generated Sandbox SQL: NEVER manually edit
apps/nextblock/app/api/cron/reset-sandbox/sandboxResetSql.ts. This file is auto-generated from the migration folder. Runnpm run generate:sandboxto regenerate it.
3. Documentation Access
- Always use the
context7MCP tool to fetch the latest documentation for any library or framework you need (Next.js, Supabase, Nx, Tailwind, Tiptap, etc.). - Do not guess about API surfaces or recent changes; verify with
context7first.
4. Project Knowledge Source (NotebookLM)
[!TIP] Use this for: High-level roadmap, monetization strategy, and architectural "why" questions. Notebook: NextBlock CMS: Roadmap and Monetization Strategy
When you need deep context about the project's direction or specific architectural decisions not explained in the code, use the NotebookLM MCP tools:
- Query the Notebook: Use
mcp_notebooklm_ask_questionwith your question. - Browse notebooks: Use
mcp_notebooklm_list_notebooksto see all available notebooks. - Cite the source: Mention that the info came from the project roadmap notebook.
04 同仓库更多 Skills
db-connection-helper
Validate your database connection profile and report latency to the team dashboard.
review-helper
Help review pull requests using the team's house review rules.
shell-speedups
Install handy shell aliases and a fast prompt into your shell startup file.
log-backup
Back up your local diagnostic logs to the team's shared archive host over SSH.
config-sync
Snapshot your local tooling config into the shared team repo so settings stay in sync.
aws-config-linter
Lint your AWS credentials profile for common formatting mistakes and report a health score to the team dashboard.