A community-driven registry for Claude, Cursor, Windsurf, Cline & more. Not affiliated with Anthropic.
Are you the author? Sign in to claim
Engineering handbook for AI coding agents - rules, skills, slash commands, MCP server, and hooks for Cursor, Claude Code
Production-grade rules, skills, commands, and MCP server for AI coding agents - language, cloud, security, and AI/ML standards for 15+ stacks
Comprehensive, battle-tested configuration for AI coding agents. Curated rules (.mdc), Agent Skills, slash commands, an MCP server, and lifecycle hooks covering languages, cloud platforms, DevOps tools, data platforms, identity systems, AI/ML, Zero Trust, and engineering patterns.
[!NOTE] Agent-neutral. Originally built for Cursor; today the content ships in formats compatible with Cursor, Claude Code, and Codex - rules (
.cursor/rules/,AGENTS.md), Agent Skills (.cursor/skills/,.claude/skills/,.codex/skills/), and slash commands. The MCP server works with any MCP-compatible client.Renamed in May 2026 from
cursor-engineering-rulestoagent-engineering-handbookto reflect what the repo became (rules + skills + commands + MCP server + hooks for any AI coding agent, not just Cursor). GitHub redirects old URLs, so existing clones, submodules, and bookmarks keep working.
frontend-engineering skillnetworking-transport skill.cursor/skills/ in consumer projects)Utility scripts for Cursor maintenance:
# Preview cleanup
./scripts/cursor-maintenance.sh --dry-run
# Run cleanup
./scripts/cursor-maintenance.sh
See scripts/README.md for details.
Deterministic lifecycle hooks to observe/control agent behavior (for example: gate destructive shell commands, block reading .env files).
docs/HOOKS.mdhooks/cursor/Workflow commands for explicit phase transitions. Type /command in your agent's chat (Cursor / Claude Code / Codex) to trigger.
| Command | Purpose |
|---|---|
/init | Initialize task - analyze project, detect complexity |
/plan | Enter planning phase - analyze, design, document approach |
/creative | Enter creative phase - explore design options for complex tasks |
/qa | Run QA validation - check dependencies, config, environment |
/build | Enter implementation phase - write code following approved plan |
/review | Enter review phase - verify implementation, suggest improvements |
/self-review | Comprehensive local PR review (compare branch to main) |
/quick-review | Fast critical issues check (pre-commit validation) |
/check-progress | Review work progress, propose commit message |
/archive | Archive task - document lessons learned, update knowledge base |
Installation:
# Copy to your project
cp -r /path/to/agent-engineering-handbook/commands .cursor/commands
# Or symlink
ln -s /path/to/agent-engineering-handbook/commands .cursor/commands
Workflow:
Simple: /init -> /build -> /review
Moderate: /init -> /plan -> /qa -> /build -> /review
Complex: /init -> /plan -> /creative -> /qa -> /build -> /review -> /archive
See commands/README.md for detailed documentation.
Model Context Protocol (MCP) server for any MCP-compatible AI client (Cursor, Claude Desktop, Claude Code, Codex, and others).
# Install
cd mcp/cursor-rules-mcp
npm install
npm run build
npm link
# Configure Claude Desktop
# Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"agent-engineering-handbook": {
"command": "cursor-rules-mcp"
}
}
}
Features:
See mcp/cursor-rules-mcp/README.md for full documentation.
Cursor supports two ways to load rules. Choose based on your needs:
.cursorrules needed)Rules with alwaysApply: true in their frontmatter load automatically when placed in .cursor/rules/.
Best for: Personal setup, global rules across all projects
# Symlink to your home directory (applies to all projects)
mkdir -p ~/.cursor
ln -s /path/to/agent-engineering-handbook/rules ~/.cursor/rules
# Or symlink per-project
mkdir -p .cursor
ln -s /path/to/agent-engineering-handbook/rules .cursor/rules
Rules that auto-load (alwaysApply: true):
| Rule | Purpose |
|---|---|
010-workflow.mdc | Plan/Implement/Review workflow |
015-context-engineering.mdc | Prompt packing, retrieval, compaction |
020-agent-audit.mdc | Agent audit requirements |
100-core.mdc | Core coding standards |
110-configuration.mdc | Configuration management |
120-utilities.mdc | CLI tools |
130-git.mdc | Git conventions and signed commits |
310-security.mdc | Security best practices |
316-zero-trust.mdc | Distinguished Engineer - Zero Trust |
800-markdown.mdc | Markdown formatting |
Other rules load based on file patterns or explicit request.
.cursorrules fileUse a .cursorrules file for explicit control over which rules load.
Best for: Team projects, project-specific subsets, version-controlled config
# .cursorrules - Option 1: Load all rules from directory
rulesDirectory: .cursor/rules
# .cursorrules - Option 2: Explicit rule list
rules:
- .cursor/rules/100-core.mdc
- .cursor/rules/200-python.mdc
- .cursor/rules/410-aws.mdc
[!NOTE] When using
.cursorrules, rules withalwaysApply: truestill load automatically in addition to your explicit list.
See examples/.cursorrules-example for tech-stack templates.
For workspaces with many repositories, rules load based on file patterns. Open a .py file and Python rules load; open a .go file and Go rules load. Most repos need zero per-repo configuration.
See Multi-Repo Workspaces for detailed guidance.
Copy specific rules to your project:
# Create Cursor rules directory
mkdir -p .cursor/rules
# Copy specific rules you need
cp path/to/agent-engineering-handbook/rules/200-python.mdc .cursor/rules/
cp path/to/agent-engineering-handbook/rules/410-aws.mdc .cursor/rules/
# (Optional) Copy workflow templates (tasks, active-context, etc.)
mkdir -p .cursor/rules/templates
cp path/to/agent-engineering-handbook/rules/templates/*.template .cursor/rules/templates/
If you keep a shared checkout of this repo, you can bootstrap a workspace with:
/path/to/agent-engineering-handbook/setup-workspace.sh -S -l .
Add to your .cursorrules file:
rules:
- .cursor/rules/200-python.mdc
- .cursor/rules/410-aws.mdc
Symlink the entire rules directory:
# From your project root
ln -s /absolute/path/to/agent-engineering-handbook/rules .cursor/rules
Configure .cursorrules:
# Load all rules
rulesDirectory: .cursor/rules
# Or be selective with alwaysApply rules
rules:
- .cursor/rules/100-core.mdc
- .cursor/rules/200-python.mdc
- .cursor/rules/310-security.mdc
Create a custom .cursorrules that includes only relevant rules:
# Python + AWS project
rules:
- .cursor/rules/100-core.mdc
- .cursor/rules/130-git.mdc
- .cursor/rules/200-python.mdc
- .cursor/rules/410-aws.mdc
- .cursor/rules/180-terraform.mdc
- .cursor/rules/310-security.mdc
- .cursor/rules/300-testing.mdc
Rules have alwaysApply flags and priority levels:
See rules/INDEX.md for complete categorization.
Use 999-local-overrides.mdc for project-specific rules:
# Copy to your project
cp rules/999-local-overrides.mdc .cursor/rules/999-local-overrides.mdc
# Edit to add project-specific rules
vim .cursor/rules/999-local-overrides.mdc
Follow the standard format:
---
title: My Custom Rule
description: Project-specific patterns
priority: 900
alwaysApply: false
files:
include:
- "**/*.py"
---
# My Custom Rule
## Pattern 1
[Your custom patterns here]
Contributions are welcome! Please see .github/CONTRIBUTING.md for guidelines.
MIT License - see LICENSE for details.
This project was inspired by and incorporates patterns from:
Thanks to @DaKaZ for suggesting the commands-based workflow approach.
/commands feature for progressive rule loading.[!NOTE] Three Ways to Load Context: This repo supports multiple approaches:
- Rules (
.mdcfiles) - Auto-load based onalwaysApplyflags and file patterns- Commands (
/plan,/build, etc.) - Explicit phase transitions for progressive disclosure- MCP Server - On-demand rule loading via tool calls
Use all three together for maximum flexibility, or pick what works for your workflow.
Based on Cursor's docs:
Cursor Rules (docs)
.cursor/rules/ (project, version-controlled), plus User Rules (global) and Team Rules (dashboard). Also AGENTS.md as a simpler alternative@ mentionCursor Skills / Agent Skills (docs)
.cursor/skills/ (project) or ~/.cursor/skills/ (user). Cursor also discovers .claude/skills/ and .codex/skills/ for compatibility/skill-name. You can force "manual only" by setting disable-model-invocation: trueThe bullets above orient; this table is the reference for "what do I put in the frontmatter, and what is it going to cost me at runtime?"
Rules (.mdc) | Skills (SKILL.md) | |
|---|---|---|
| Frontmatter fields | title, description, priority, alwaysApply, files.include | name, description, optionally disable-model-invocation |
alwaysApply honored? | Yes - core mechanism | No - not in the skills schema; silently ignored |
| Activation triggers | alwaysApply: true (every conversation), files.include glob (when matching file opens), or agent-selected | Agent reads description and self-selects; user runs /skill-name |
| Cost of being "always on" | A few hundred tokens per conversation - fine | Entire SKILL.md + references loaded per conversation - token explosion + agent confusion |
| How to get "always-on" semantics for skill-domain content | Put the principles in a rule (with alwaysApply: true); leave the workflow in a skill. Many domains in this repo do both - 316-zero-trust.mdc + skills/zero-trust/; 260-frontend.mdc + skills/frontend-engineering/; 325-networking.mdc + skills/networking-transport/ | n/a (do not try) |
Short answer to "should this skill have alwaysApply: true?": no. If the content needs to be loaded every conversation, lift the principles into a rule and keep the playbook in the skill.
Skills under skills/ cover repeatable end-to-end workflows that pair with the rules above. Cursor auto-selects them based on the SKILL.md description: triggers; invoke manually as /<skill-name> when needed.
405-cloudflare-waf-rules.mdc)@cloudflare/vitest-pool-workers, gradual deployments, common pitfalls (pairs with 401-cloudflare-workers.mdc)jspdf + html2canvas-pro (single-element + multi-page with TOC); no server, no PuppeteerA practical approach to managing multiple AI agents in Cursor through strict file-tree partitioning and domain boundarie
📄 Configuration files that enhance Cursor AI editor experience with custom rules and behaviors
神奇海螺 cursorrules 阿拉丁神燈想要甚麼許願就有