settings-2 Cross-Editor AI Setup
Ensure AI configuration works across Claude Code, Cursor, Copilot, Windsurf, and Codex. Use when creating AGENTS.md files, adding skills, setting up project rules, or discussing cross-editor compatibility. Enforces the @import convention and single-source-of-truth strategy.
Install this skill
git submodule add https://github.com/modh-labs/playbook.git .playbookOne submodule installs all 17 skills. Reference .playbook/skills/cross-editor-setup/SKILL.md from your AGENTS.md.
Cross-Editor Setup Skill
When This Skill Activates
This skill automatically activates when you:
- Create a new
AGENTS.mdfile in any directory - Create or modify a skill in
.claude/skills/ - Discuss Cursor vs Claude Code vs Copilot vs Windsurf configuration
- Set up project rules for a new directory or package
Core Rule: AGENTS.md is the Source of Truth
Every directory that needs AI context has two files:
AGENTS.md <- real file (source of truth, Cursor/Copilot/Codex read natively)
CLAUDE.md <- contains "@AGENTS.md" (Claude Code resolves the import)
Why: Most AI coding agents read AGENTS.md natively (root and subdirectories). Claude Code reads CLAUDE.md and uses @ import syntax to resolve the content from AGENTS.md. One source of truth, all editors served.
Cross-Agent Compatibility
| Agent | Config Location | Format | Notes |
|---|---|---|---|
| Claude Code | .claude/skills/ + CLAUDE.md | YAML frontmatter + MD | Reads CLAUDE.md, resolves @AGENTS.md imports |
| Cursor | .claude/skills/ (Import Agent Skills toggle) | Same | Reads AGENTS.md natively + .cursor/rules/ |
| GitHub Copilot | .github/copilot-instructions.md + AGENTS.md | Plain MD | Reads AGENTS.md natively in all directories |
| Windsurf | .windsurfrules or .windsurf/rules/ | Plain MD | Project-level rules file or rules directory |
| Codex | AGENTS.md | Plain MD | Reads AGENTS.md natively |
What Goes Where
| Config Type | Location | Claude Code | Cursor | Copilot | Windsurf | Action |
|---|---|---|---|---|---|---|
| Core project rules | AGENTS.md (root) | Via @AGENTS.md in CLAUDE.md | Native | Native | Copy to .windsurfrules | Edit AGENTS.md |
| Directory context | <dir>/AGENTS.md | Via <dir>/CLAUDE.md import | Native | Native | Not supported | Edit AGENTS.md |
| AI skills | .claude/skills/*/SKILL.md | Native | Native (toggle) | Not supported | Not supported | No duplication needed |
| Cursor-only rules | .cursor/rules/*.mdc | Not read | Native | Not read | Not read | Only Cursor-specific behavior |
| Copilot instructions | .github/copilot-instructions.md | Not read | Not read | Native | Not read | Copilot-specific overrides |
| Windsurf rules | .windsurfrules | Not read | Not read | Not read | Native | Windsurf-specific overrides |
When Creating New Directory Context
Follow this exact sequence:
- Write
AGENTS.mdwith the directory context content - Create
CLAUDE.mdin the same directory with just one line:@AGENTS.md - Verify:
cat AGENTS.mdshows your content,cat CLAUDE.mdshows@AGENTS.md
Setting Up Each Editor
Claude Code (works out of the box)
No extra setup needed. Claude Code reads:
- Root
CLAUDE.md(which importsAGENTS.md) - All
CLAUDE.mdfiles in subdirectories - All
.claude/skills/*/SKILL.mdfiles
Cursor
One manual step for team members:
Cursor Settings > Rules > "Import Agent Skills" -- Enable this toggle.
This makes Cursor scan .claude/skills/ for all SKILL.md files and use them the same way Claude Code does. Cursor also reads AGENTS.md natively in root and subdirectories.
GitHub Copilot
- Create
.github/copilot-instructions.mdwith project-wide instructions - Copilot reads
AGENTS.mdfiles natively in all directories - For skills, you may need to reference key rules in
copilot-instructions.mdsince Copilot does not read.claude/skills/
Windsurf
- Create
.windsurfrulesin the project root with core project rules (copy key content fromAGENTS.md) - Alternatively, create
.windsurf/rules/directory with multiple rule files - Windsurf does not read
AGENTS.mdor.claude/skills/, so critical rules must be duplicated
Codex (OpenAI)
No extra setup needed. Codex reads AGENTS.md natively. It does not read .claude/skills/, so skills are not available.
NEVER Do These
- NEVER put content directly in
CLAUDE.md— it should only contain@AGENTS.md. All content goes inAGENTS.md. - NEVER create
AGENTS.mdandCLAUDE.mdwith different content — that causes drift. - NEVER duplicate skills into
.cursor/rules/— Cursor reads.claude/skills/natively when "Import Agent Skills" is enabled. - NEVER skip creating
CLAUDE.mdwhen adding anAGENTS.md— Claude Code users won't get the context. - NEVER maintain the same rules in 4 different formats — pick
AGENTS.mdas the source of truth and only duplicate to editor-specific files when that editor cannot readAGENTS.md.
Skills: Zero Duplication (Claude Code + Cursor)
Skills in .claude/skills/*/SKILL.md work in both Claude Code and Cursor. The frontmatter format is compatible:
---
name: skill-name
description: When this skill activates...
allowed-tools: Read, Grep, Glob
---
Both Claude Code and Cursor use the description field to decide when to load the skill. No transformation or conversion needed.
For editors that do not support .claude/skills/ (Copilot, Windsurf, Codex), extract the most critical rules into their respective config files. Accept that full skill parity across all editors is not practical — focus on getting the core rules right everywhere.
Maintenance Checklist
When adding a new AGENTS.md to a directory:
-
AGENTS.mdcontains all the content -
CLAUDE.mdexists in the same directory with only@AGENTS.md - Content is tested in at least one editor (Claude Code or Cursor)
When adding a new skill:
- Created in
.claude/skills/<name>/SKILL.md - Has YAML frontmatter with
nameanddescription - Verified Cursor picks it up (Settings > Rules > Import Agent Skills)
Related Skills
Code Review
Run educational code reviews against your project's quality standards. Use when reviewing PRs, checking current branch before pushing, or doing batch quality sweeps across all open PRs. Applies observability, testing, SOLID, type safety, security, business logic, and clean code checks with pass/fail verdicts. Produces actionable findings with real-world impact explanations, not just "best practice" citations.
UniversalpalettePremium UI Design Engineering
Premium UI/UX design engineering skill. Overrides default LLM design biases with tunable dials for variance, motion, and density. Enforces anti-AI-tell patterns, strict typography rules, color calibration, layout diversification, performance guardrails, and comprehensive design audit checklists. Framework-agnostic.
Universallayout-dashboardInternal Tools Design
Use when building or modifying admin dashboards, internal tools, ops panels, or back-office UIs. Enforces scannability, data density, tactile feedback, and dark-mode-safe patterns calibrated for daily-use operational tools.
Universal