addyosmani--agent-skills
Federico Bartoli
a63f54b8ab
The repository was renamed from swe-skills to agent-skills but internal references were never updated. This caused: - session-start.sh to silently fail (path using-swe-skills/ did not exist; the directory is using-agent-skills/) - slash commands to invoke non-existent swe-skills: namespace - docs and setup guides to point at the old clone URL Rename all occurrences across 14 files: commands, CLAUDE.md, README tree, docs/, and hooks/.
68 行
2.6 KiB
Markdown
68 行
2.6 KiB
Markdown
# Using agent-skills with Cursor
|
|
|
|
## Setup
|
|
|
|
### Option 1: Rules Directory (Recommended)
|
|
|
|
Cursor supports a `.cursor/rules/` directory for project-specific rules:
|
|
|
|
```bash
|
|
# Create the rules directory
|
|
mkdir -p .cursor/rules
|
|
|
|
# Copy skills you want as rules
|
|
cp /path/to/agent-skills/skills/test-driven-development/SKILL.md .cursor/rules/test-driven-development.md
|
|
cp /path/to/agent-skills/skills/code-review-and-quality/SKILL.md .cursor/rules/code-review-and-quality.md
|
|
cp /path/to/agent-skills/skills/incremental-implementation/SKILL.md .cursor/rules/incremental-implementation.md
|
|
```
|
|
|
|
Rules in this directory are automatically loaded into Cursor's context.
|
|
|
|
### Option 2: .cursorrules File
|
|
|
|
Create a `.cursorrules` file in your project root with the essential skills inlined:
|
|
|
|
```bash
|
|
# Generate a combined rules file
|
|
cat /path/to/agent-skills/skills/test-driven-development/SKILL.md > .cursorrules
|
|
echo "\n---\n" >> .cursorrules
|
|
cat /path/to/agent-skills/skills/code-review-and-quality/SKILL.md >> .cursorrules
|
|
```
|
|
|
|
### Option 3: Notepads
|
|
|
|
Cursor's Notepads feature lets you store reusable context. Create a notepad for each skill you use frequently:
|
|
|
|
1. Open Cursor → Settings → Notepads
|
|
2. Create a new notepad named "swe: Test-Driven Development"
|
|
3. Paste the content of `skills/test-driven-development/SKILL.md`
|
|
4. Reference it in chat with `@notepad swe: Test-Driven Development`
|
|
|
|
## Recommended Configuration
|
|
|
|
### Essential Skills (Always Load)
|
|
|
|
Add these to `.cursor/rules/`:
|
|
|
|
1. `test-driven-development.md` — TDD workflow and Prove-It pattern
|
|
2. `code-review-and-quality.md` — Five-axis review
|
|
3. `incremental-implementation.md` — Build in small verifiable slices
|
|
|
|
### Phase-Specific Skills (Load as Notepads)
|
|
|
|
Create notepads for skills you use contextually:
|
|
|
|
- "swe: Spec Development" → `spec-driven-development/SKILL.md`
|
|
- "swe: Frontend UI" → `frontend-ui-engineering/SKILL.md`
|
|
- "swe: Security" → `security-and-hardening/SKILL.md`
|
|
- "swe: Performance" → `performance-optimization/SKILL.md`
|
|
|
|
Reference them with `@notepad` when working on relevant tasks.
|
|
|
|
## Usage Tips
|
|
|
|
1. **Don't load all skills at once** — Cursor has context limits. Load 2-3 skills as rules and keep others as notepads.
|
|
2. **Reference skills explicitly** — Tell Cursor "Follow the test-driven-development rules for this change" to ensure it reads the loaded rules.
|
|
3. **Use agents for review** — Copy `agents/code-reviewer.md` content and tell Cursor to "review this diff using this code review framework."
|
|
4. **Load references on demand** — When working on performance, reference `@notepad performance-checklist` or paste the checklist content.
|