[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"pack-detail-cursor-power-user-30min-es":3,"seo:pack:cursor-power-user-30min:es":101},{"code":4,"message":5,"data":6},200,"操作成功",{"pack":7},{"slug":8,"icon":9,"tone":10,"status":11,"status_label":12,"title":13,"description":14,"items":15,"install_cmd":100},"cursor-power-user-30min","🎯","#000000","new","Nuevo · esta semana","Configuración Power-User de Cursor en 30 Minutos","Diez picks opinados para el dev que instaló Cursor pero apenas lo usa — biblioteca de rules, generador MDC, dominio de Composer, MCP de GitHub + Linear, patrones autónomos. En orden de instalación.",[16,28,38,46,54,61,68,75,85,93],{"id":17,"uuid":18,"slug":19,"title":20,"description":21,"author_name":22,"view_count":23,"vote_count":24,"lang_type":25,"type":26,"type_label":27},23,"ca000374-f5d8-4d75-a30c-460fda0b6b0e","awesome-cursor-rules-ai-coding-standards-30-stacks-ca000374","Awesome Cursor Rules — AI Coding Standards for 30+ Stacks","Curated .cursorrules files for 30+ tech stacks. Drop into your project root so Cursor AI follows your coding standards automatically.","TokRepo精选",608,0,"en","skill","Skill",{"id":29,"uuid":30,"slug":31,"title":32,"description":33,"author_name":34,"view_count":35,"vote_count":24,"lang_type":25,"type":36,"type_label":37},721,"5686f25c-3177-4f6b-bb1d-4aef8be5d3d6","cursor-directory-community-cursor-rules-ai-prompts-5686f25c","Cursor Directory — Community Cursor Rules & AI Prompts","Community-curated directory of Cursor rules, AI coding prompts, and MCP configurations. Browse by framework, copy with one click, and improve your AI coding setup.","Prompt Lab",148,"prompt","Prompt",{"id":39,"uuid":40,"slug":41,"title":42,"description":43,"author_name":44,"view_count":45,"vote_count":24,"lang_type":25,"type":26,"type_label":27},766,"3b69856d-9cde-4c21-9b2e-094ebd2da7d9","cursor-rules-generator-ai-coding-config-builder-3b69856d","Cursor Rules Generator — AI Coding Config Builder","Generate optimized .cursorrules files for any tech stack. Automate Cursor IDE configuration with project-specific AI coding instructions and best practices.","Skill Factory",145,{"id":47,"uuid":48,"slug":49,"title":50,"description":51,"author_name":52,"view_count":53,"vote_count":24,"lang_type":25,"type":26,"type_label":27},41,"8ced00e7-b6b4-4ea8-adfb-3ddc0fe82620","cursor-rules-mdc-generator-auto-generate-docs-8ced00e7","Cursor Rules MDC Generator — Auto-Generate from Docs","Auto-generate Cursor .mdc rule files for any library using Exa semantic search and LLM-powered documentation extraction.","AI Open Source",207,{"id":55,"uuid":56,"slug":57,"title":58,"description":59,"author_name":34,"view_count":60,"vote_count":24,"lang_type":25,"type":36,"type_label":37},3070,"5d7d38b4-3945-4a83-9bd7-9d9b7777fe40","cursorrules-v5-cursor-rules-commands","cursorrules v5 — Cursor Rules + Commands","cursorrules v5 provides Cursor-ready rule files and workflow commands you can copy into .cursor\u002F to enforce guardrails and prompt-injection defenses.",64,{"id":62,"uuid":63,"slug":64,"title":65,"description":66,"author_name":34,"view_count":67,"vote_count":24,"lang_type":25,"type":36,"type_label":37},745,"b7e65852-71d5-4114-bf50-162d16348de3","cursor-tips-advanced-ai-coding-workflow-guide-b7e65852","Cursor Tips — Advanced AI Coding Workflow Guide","Comprehensive guide to advanced Cursor workflows. Covers Composer, multi-file edits, .cursorrules, codebase indexing, and prompt engineering for 10x AI coding productivity.",265,{"id":69,"uuid":70,"slug":71,"title":72,"description":73,"author_name":34,"view_count":74,"vote_count":24,"lang_type":25,"type":36,"type_label":37},687,"02967692-c4f6-4694-9470-12b32f5c517a","cursor-composer-tips-multi-file-ai-editing-mastery-02967692","Cursor Composer Tips — Multi-File AI Editing Mastery","Advanced tips and workflows for Cursor Composer mode. Multi-file editing patterns, context management, .cursorrules optimization, and keyboard shortcuts for 10x AI-assisted development.",107,{"id":76,"uuid":77,"slug":78,"title":79,"description":80,"author_name":81,"view_count":82,"vote_count":24,"lang_type":25,"type":83,"type_label":84},393,"679a2650-b97b-4e8e-af6e-b51bafcbf610","github-mcp-server-official-github-ai-integration-679a2650","GitHub MCP Server — Official GitHub AI Integration","GitHub's official MCP server that lets AI assistants manage repos, issues, PRs, Actions, and code search through the Model Context Protocol.","GitHub",186,"mcp","MCP",{"id":86,"uuid":87,"slug":88,"title":89,"description":90,"author_name":91,"view_count":92,"vote_count":24,"lang_type":25,"type":83,"type_label":84},2822,"ed6f4647-de3c-4b1d-bf90-5f19903641c6","linear-mcp-project-management-for-claude-code-cursor","Linear MCP — Project Management for Claude Code & Cursor","Linear's official MCP lets Claude Code, Cursor, Codex CLI manage Linear issues, projects, cycles. Search by status, create issues from chat, link PRs.","Linear",112,{"id":94,"uuid":95,"slug":96,"title":97,"description":98,"author_name":52,"view_count":99,"vote_count":24,"lang_type":25,"type":26,"type_label":27},482,"92824589-6223-492b-bd37-5aec9fa93e74","devin-cursorrules-turn-cursor-into-ai-engineer-92824589","Devin Cursorrules — Turn Cursor into an AI Engineer","A .cursorrules configuration that gives Cursor\u002FWindsurf Devin-like capabilities: automated planning, self-correction, web browsing, and multi-agent collaboration. 6,000+ GitHub stars.",193,"tokrepo install pack\u002Fcursor-power-user-30min",{"pageType":102,"pageKey":8,"locale":25,"title":103,"metaDescription":104,"h1":105,"tldr":106,"bodyMarkdown":107,"faq":108,"schema":124,"internalLinks":130,"citations":143,"wordCount":156,"generatedAt":157},"pack","Cursor 30-Minute Power-User Setup — 10 Configs to Install First","Installed Cursor but barely using it? Ten opinionated picks — rules library, MDC generator, Composer mastery, GitHub + Linear MCP, autonomous patterns. Install in this order and you're a power user before lunch.","Cursor 30-Minute Power-User Setup — From Smart Autocomplete to Power User","Ten picks in install order: rules library first (Cursor stops guessing your stack), then the directory + two generators (close the gaps), then advanced prompting and Composer mastery, then GitHub and Linear MCPs (Cursor talks to your real work), and finally an autonomous-engineer rules pack so Cursor stops asking you what to do every two minutes.","## What's in this pack\n\nYou installed Cursor, used tab-complete for a week, opened a chat panel twice, and now you're using it as a slightly smarter VS Code. The 10x productivity videos look like a different product. They are — those people configured it. You didn't, because the documentation buries the high-leverage stuff under feature tours.\n\nThis pack is the **30-minute power-user setup**: ten configurations and integrations a working engineer should drop in before they touch another feature tour. Every pick is **opinionated**, **earns its slot**, and **builds on the previous one**. By the time you finish step 10, Cursor knows your stack, your conventions, your GitHub, your Linear board, and how to drive itself for multi-file refactors without you babysitting each diff.\n\nWho this is for: a developer with Cursor already installed, working in a real repo, who has 30 minutes and zero patience for browsing 700 community rules to figure out which 10 actually matter.\n\n## Install in this order\n\n1. **Awesome Cursor Rules** — 38k-star library of `.cursorrules` files for 30+ stacks. Start here because every later step assumes Cursor already knows what framework you're in. Pick your stack (Next.js, FastAPI, Rails, whatever), drop the file in project root, done. **5 minutes. Single largest quality jump you will make.**\n2. **Cursor Directory** — Community index of rules + prompts beyond Awesome. When the official rules don't quite match your stack (Next.js + Drizzle + Clerk, say), the Directory is where the long tail lives. Bookmark it; you'll come back monthly.\n3. **Cursor Rules Generator** — Auto-generate a `.cursorrules` file for stacks the libraries don't cover. Internal DSL? Obscure framework combo? Feed it your dependency list, get a starter rule file in 30 seconds. This is your escape hatch.\n4. **Cursor Rules MDC Generator** — Cursor's modern rules format is `.mdc` (Markdown with frontmatter), not flat `.cursorrules`. MDC lets you scope rules to specific globs (`src\u002Fapi\u002F**\u002F*.ts`) and load them on demand. Generate MDCs from your existing docs. **This is the format Cursor is moving toward — don't get stuck on legacy `.cursorrules`.**\n5. **cursorrules v5 — Rules + Commands** — Adds custom slash commands on top of rules. Define `\u002Frefactor-to-tanstack` once and Cursor runs your whole migration pattern with the right context every time. The transition point from \"Cursor knows my code\" to \"Cursor knows my workflows.\"\n6. **Cursor Tips — Advanced Workflow Guide** — Composer mode, multi-file edits, codebase indexing, prompt engineering. The guide most people read after they realize tab-complete was only the beginning. Read this once; it changes how you ask for things.\n7. **Cursor Composer Tips — Multi-File Mastery** — Composer is the killer feature most users underuse. This pack is the specifics: how to scope context (don't `@codebase` everything — it dilutes attention), when to use Composer vs chat, keyboard shortcuts that turn 6-click flows into one. Pairs with #6.\n8. **GitHub MCP Server** — Connect Cursor to GitHub via MCP. Now Cursor can read PR diffs, check CI status, browse issues, and post comments without leaving the editor. This is the highest-frequency MCP for most devs; install it before any niche one.\n9. **Linear MCP** — Linear in Cursor. Pull issue context into a chat (\"implement LIN-423\" auto-grabs the description, acceptance criteria, linked PRs). If your team runs Linear, this single MCP closes the most common context-switch loop.\n10. **Devin Cursorrules** — The autonomous-engineer rules pack. Adds planning, self-correction, and multi-step execution patterns so Cursor stops asking you what to do every two minutes for medium-sized tasks. 6,000+ GitHub stars. **The graduation step**: from \"AI pair-programmer\" to \"AI engineer I review.\"\n\n## How they fit together\n\n```\nRules library (#1 Awesome) ──┐\n                             ├─ Cursor knows your stack\nDirectory (#2)               │\n                             │\nGenerators: Rules (#3) + MDC (#4)\n                             │\n                             └─ fill the gaps the libraries miss\n                                       │\ncursorrules v5 (#5)\n                                       │\n                                       └─ custom slash commands per workflow\n                                                  │\nAdvanced prompting: Tips (#6) + Composer (#7)\n                                                  │\n                                                  └─ multi-file editing without burning context\n                                                            │\nMCPs: GitHub (#8) + Linear (#9)\n                                                            │\n                                                            └─ Cursor talks to where your work lives\n                                                                       │\nDevin Cursorrules (#10) — autonomous patterns\n```\n\nThe **rules library + MDC + GitHub MCP** trio is the load-bearing wall. Steps 1, 4, 8 alone get you 70% of the value if you must stop early. Composer mastery (#7) is the single biggest workflow upgrade once the foundation is there.\n\n## Tradeoffs you'll hit\n\n- **`.cursorrules` vs `.mdc`** — `.cursorrules` is the legacy flat file (loads every chat, cheap, no scoping). `.mdc` is the new format (per-glob loading, frontmatter metadata, future-proof). New projects: go straight to MDC. Existing projects: keep your `.cursorrules` for global rules, add MDCs for path-scoped ones. Don't migrate for the sake of migration.\n- **Awesome Cursor Rules (#1) vs Cursor Directory (#2)** — Awesome is the curated 30-stack baseline (more polish, slower-moving). Directory is the long-tail community feed (more variety, more noise). Install Awesome first; check Directory only when Awesome's nearest match isn't close enough.\n- **Composer vs Chat** — Composer is for multi-file changes Cursor should execute itself. Chat is for single-file edits and questions. Most users overuse Chat — they ask, get an answer, then manually apply edits across 4 files. Composer was built for exactly that loop.\n- **MCP vs the CLI you already have** — `gh pr view` is faster than asking Cursor to fetch a PR. MCP wins when Cursor needs to *react* to the PR content (\"summarize this diff and check our coding standards\"). Use the CLI for human-driven lookups, MCP for AI-driven workflows. Don't pick one — install both.\n- **Devin Cursorrules (#10) vs hand-holding** — Devin patterns let Cursor act autonomously for medium tasks (5-15 file changes). Tradeoff: it'll occasionally do things you wouldn't have. Worth it for batch work, overkill for one-line fixes. Use it deliberately, not as default.\n\n## Common pitfalls\n\n- **`.cursorrules` 500-line monster** — Same trap as a giant CLAUDE.md. Keep it under 200 lines. Move stack-specific stuff to MDC files scoped to that path. Long rules dilute Cursor's attention every turn.\n- **Enabling every MCP at once** — Each MCP adds tools Cursor must reason about. 3-5 active MCPs is the sweet spot. Add GitHub + Linear first; only add a third when you have a concrete recurring task it solves.\n- **Composer with `@codebase` for small changes** — `@codebase` indexes the whole repo into the prompt. Useful for architecture questions, wasteful for \"rename this function across the auth module.\" Scope tightly with `@folder` or `@file`.\n- **Treating Cursor Tab as the product** — Tab-complete is the appetizer. Composer + rules + MCP is the meal. If you've been on Cursor for a month and haven't used Composer for a multi-file change, you're paying for a Ferrari to grocery-shop.\n- **Skipping #10 because it sounds gimmicky** — Devin Cursorrules sounds like a meme; it isn't. The planning + self-correction patterns matter most exactly when you're tired and shouldn't be reviewing every diff manually anyway.",[109,112,115,118,121],{"q":110,"a":111},"I already use Cursor every day for autocomplete. Do I really need 10 things?","If you're only using tab-complete, you're using maybe 20% of the product you're paying for. This pack is for the moment you realize the demo videos look like a different IDE — they're using rules, Composer, and MCP that you haven't configured. The minimum viable version is steps #1, #4, and #8 (rules library + MDC format + GitHub MCP), which takes about 10 minutes and changes everything. The remaining seven compound from there.",{"q":113,"a":114},"Which three would you install if I only have 10 minutes?","Awesome Cursor Rules (#1), Cursor Rules MDC Generator (#4), and GitHub MCP (#8). The rules library teaches Cursor your stack on first chat. MDC future-proofs you against the format migration. GitHub MCP connects Cursor to where your code actually lives. The other seven are upgrades — these three are the floor.",{"q":116,"a":117},"Should I migrate my existing `.cursorrules` to `.mdc`?","Not for migration's sake. `.cursorrules` still works and Cursor still reads it. The reason to add `.mdc` is *path-scoped* rules — when your `src\u002Fapi\u002F**\u002F*.ts` needs different conventions than your `src\u002Fcomponents\u002F**\u002F*.tsx`, MDCs let you apply each ruleset only where it matters. Keep your global rules in `.cursorrules` and use MDC for the scoped ones. Pure migration without that need is busywork.",{"q":119,"a":120},"Composer or Chat — when do I use which?","Chat for questions and single-file edits (\"why is this returning undefined?\", \"add input validation to this function\"). Composer for changes that span multiple files (\"convert this REST endpoint to tRPC across the route, the schema, and the client hook\"). Rule of thumb: if your prompt mentions more than one file, open Composer. Composer was designed for the loop where you'd otherwise ask Chat for code, then manually apply across files — and it removes the manual step.",{"q":122,"a":123},"Will Linear MCP work if my team uses Jira \u002F Asana \u002F ClickUp instead?","Linear MCP is Linear-specific; swap it for the relevant MCP from the ecosystem if you're on a different tracker (the awesome-mcp-servers list has Jira, Asana, ClickUp, and others). The principle is the same — pull issue context into Cursor so you stop alt-tabbing every five minutes to reread the ticket. Pick whichever your team actually uses; the rest of this pack stays identical.",{"@context":125,"@type":126,"name":127,"description":128,"numberOfItems":129,"inLanguage":25},"https:\u002F\u002Fschema.org","ItemList","Cursor 30-Minute Power-User Setup","Ten opinionated Cursor configurations and MCP integrations to install in deliberate order, taking a casual user to power-user level in 30 minutes.",10,[131,135,139],{"url":132,"anchor":133,"reason":134},"\u002Fen\u002Fai-tools-for\u002Fcoding","AI tools for coding","Compare Cursor with Claude Code, Codex CLI, Windsurf, and other AI coding agents",{"url":136,"anchor":137,"reason":138},"\u002Fen\u002Ffeatured","Featured assets on TokRepo","Browse the broader curated catalog of skills, agents, and MCP servers",{"url":140,"anchor":141,"reason":142},"\u002Fen\u002Ftopics","Browse other topic packs","Adjacent packs include Claude Code 30-Minute Onboarding and MCP Server Stack",[144,148,152],{"claim":145,"source_name":146,"source_url":147},"Awesome Cursor Rules is the largest open-source .cursorrules collection","PatrickJS\u002Fawesome-cursorrules on GitHub","https:\u002F\u002Fgithub.com\u002FPatrickJS\u002Fawesome-cursorrules",{"claim":149,"source_name":150,"source_url":151},"Cursor's MDC format supports path-scoped rules with frontmatter metadata","Cursor official documentation","https:\u002F\u002Fdocs.cursor.com\u002Fcontext\u002Frules",{"claim":153,"source_name":154,"source_url":155},"GitHub MCP Server is GitHub's official integration for AI editors","github\u002Fgithub-mcp-server","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgithub-mcp-server",1050,"2026-05-22T01:00:00Z"]