{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreick76qmcf235v4humodqaiuzjejvovmgoxjxkqr3sjdrzjoofb2fq",
    "uri": "at://did:plc:25rdn5elo5izoxrmtis34zuk/app.bsky.feed.post/3moojdnu4aq22"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreih7bzvjmh6carwcb33jq2dbt2rrhkkylld55feb5hyhipshqgahgi"
    },
    "mimeType": "image/webp",
    "size": 64122
  },
  "path": "/sriram7/how-to-migrate-from-cursor-rules-to-agent-skills-1cl7",
  "publishedAt": "2026-06-19T23:10:00.000Z",
  "site": "https://dev.to",
  "tags": [
    "cursor",
    "ai",
    "agents",
    "agentskills",
    "agentskills.io",
    "what are Agent Skills",
    "CI auto-sync",
    "Cursor rules not working? Common fixes",
    "Configure every major AI tool for team conventions",
    "Codehabits quickstart",
    "codehabits.dev",
    "@codehabits"
  ],
  "textContent": "**Agent Skills** are the open standard (agentskills.io) for packaging team-specific instructions that any AI coding tool can discover.\n\nMigrating from hand-maintained Cursor rules means moving from static markdown you write once to structured, evidence-ranked intelligence your team already enforced in PR review — and (optionally) letting tooling generate the skill automatically.\n\n##  Why migrate?\n\nCursor rules live only in Cursor's tree. Copilot wants `.github/copilot-instructions.md`. Claude Code reads `CLAUDE.md`. Maintaining the same conventions in four places doesn't scale.\n\nAgent Skills provide one portable package. See what are Agent Skills for the full picture.\n\n##  What you're migrating from\n\n  * Legacy `.cursorrules` or `.cursor/rules/*.mdc`\n  * Ad-hoc pasted instructions in chat\n  * CONTRIBUTING.md sections nobody reads\n\n\n\n##  What you're migrating to\n\n  * `.codehabits/conventions.json` — structured, confidence-ranked\n  * `.cursor/skills/codehabits-team-intel/SKILL.md` — Agent Skill auto-discovered by Cursor and compatible tools\n  * `AGENTS.md` — fallback for agents that read AGENTS.md\n\n\n\n##  Migration path (manual audit + auto-generate)\n\n###  1. Audit existing rules\n\nExport your current `.cursor/rules` files. Mark each rule as either:\n\n  * **Evidence-backed** — appears in PR review\n  * **Aspirational** — you wish the team did it but PRs don't enforce it\n\n\n\nAutomated extraction handles evidence-backed patterns; keep aspirational rules as short manual additions if needed.\n\n###  2. Run Codehabits enable\n\n\n    npx @codehabits/cli login\n    npx @codehabits/cli enable\n\n\nCompare generated conventions against your audit. You'll often find rules you forgot to document — and gaps where your written rules didn't match PR reality.\n\n###  3. Commit intelligence to git\n\n\n    git add .codehabits/ .cursor/skills/ AGENTS.md\n    git commit -m \"chore: migrate team conventions to Agent Skills\"\n    git push\n\n\n###  4. Deprecate duplicate rule files\n\nRemove or slim down hand-written rules that now live in the generated skill. Keep only temporary or project-specific rules in `.cursor/rules/`. Document the change in your team channel so engineers know to pull latest.\n\n###  5. Keep intelligence fresh\n\nSet up CI auto-sync so merged PRs update conventions and regenerate the skill. Manual rules drift; PR-derived intelligence compounds.\n\n##  Before and after\n\nHand-written Cursor rules | Codehabits Agent Skills\n---|---\nYou write and maintain | Extracted from PR evidence\nCursor-only | Portable across 16+ tools\nStatic until someone edits | Syncs after each merged PR\nNo confidence scores | Ranked by review frequency\n\n##  Related guides\n\n  * Cursor rules not working? Common fixes\n  * Configure every major AI tool for team conventions\n  * Codehabits quickstart\n\n\n\n_Originally published at codehabits.dev._",
  "title": "How to Migrate from Cursor Rules to Agent Skills"
}