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.
Best use case
agent-guidelines is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using agent-guidelines should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agent-guidelines/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-guidelines Compares
| Feature / Agent | agent-guidelines | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 1. **Strict Separation:** `libs/ui` and `libs/db` must be publishable as standalone packages. They cannot depend on `apps/nextblock`. 2. **Open-Core Model:** The core is open-source; premium extensions are private. 3. **Distribution:** Users get a standalone app via `npm create nextblock`. ## 2. Operational Rules (Global Context) - **Context First:** Before answering complex questions, always check `docs/README.md` and relevant linked docs. - **Strict Types:** Always use `strict: true` TypeScript. No `any` unless absolutely unavoidable and documented. - **Target the App, Not the Template:** NEVER edit files in `apps/create-nextblock/templates/nextblock-template` directly. Always make changes in `apps/nextblock` (the core app). The template is synced from the core app via scripts. ## 3. Maintenance Rule: 'Ghost Module Synchronization' > [!IMPORTANT] > **CRITICAL:** Whenever you modify the exports of `libs/ecommerce` (the private library), you **MUST** immediately update `tools/stubs/libs/ecommerce/index.ts` to export the same names (as stubs). > > **Why?** Failure to do this will break the public open-source build which relies on these stubs when the private library is not present. ## 4. Documentation Access - Use the **`context7` MCP tool** to fetch the latest documentation for Next.js, Supabase, Nx, Tailwind, etc. - Do not guess about API updates; verify with `context7` if unsure.
Related Skills
clack-guidelines
Comprehensive guide for building beautiful interactive command-line interfaces using Clack. Use when creating CLI tools with text input, selections, autocomplete, progress tracking, and streaming output.
agents-md-guidelines
Guidelines for writing small, stable AGENTS.md files. Use when creating, refactoring, or reviewing AGENTS.md.
documentation-guidelines
Write or update backend feature documentation that follows a repo's DOCUMENTATION_GUIDELINES.md (or equivalent) across any project. Use when asked to create/update module docs, API contracts, or backend documentation that must include architecture, endpoints, payloads, Mermaid diagrams, and seeding instructions.
developer-guidelines
Guidelines for the Developer role: strict adherence, no unsolicited refactoring, documentation, security.
artifact-guidelines
Guidelines for writing reports, organizing files, and generating code artifacts
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
vercel-web-design-guidelines
Reviews UI code for compliance with web interface best practices. Use when auditing accessibility, reviewing UI/UX patterns, checking performance, or improving web design quality. Triggers on "check my site", "audit design", "accessibility review", "UX best practices", or UI code review tasks. Covers 100+ rules for accessibility, performance, and user experience.
swift-human-guidelines
Comprehensive Swift 6 and SwiftUI development guidelines for building iOS 26, iOS 18, iPadOS, macOS, watchOS, visionOS, and tvOS applications. Covers Foundation Models API, BGContinuedProcessingTask, Call Translation API, Liquid Glass design system, data-race safety, typed throws, synchronization primitives, SwiftUI/UIKit interoperability, zoom transitions, and document-based apps. Use when building new Apple platform apps, implementing Apple Intelligence features, optimizing performance with Swift 6 concurrency, following Apple Human Interface Guidelines, creating cross-platform applications, or working with iOS 26/18 APIs. Triggers on Swift code, SwiftUI views, Xcode projects, app architecture, background processing, translation features, Foundation Models, synchronization, actors, Sendable types, or modern Apple platform development.
react-guidelines
React coding guidelines and best practices. MUST follow these rules. Use when reviewing or writing React code or tasks.
python-backend-guidelines
FastAPI/Django backend patterns and best practices
project-guidelines-example
Example project-specific skill template based on a real production application.
nextjs-frontend-guidelines
Next.js 15 frontend development guidelines for YGS (영영사) React 19/TypeScript application. Modern patterns including App Router, Server/Client Components, shadcn/ui components, Tailwind CSS 4, multi-method authentication (Firebase/Kakao/JWT), admin dashboard patterns, and Korean localization. Use when creating components, pages, API routes, fetching data, styling, or working with frontend code.