メニュー
Use when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks (React, Next.js, Drizzle, Tailwind, etc.).
Afenda metadata-driven EUI polish workflow. Use automatically when implementing, reviewing, or refining governed renderers (packages/governed-surface/src/metadata/renderers), surface builders (packages/kernel/src/modules/list-surfaces.ts), Pattern A/B/C ERP pages, or the dev metadata-renderer-gallery. Composes shadcn-metadata, governed-renderer contracts, and Vercel web-design/composition skills. Do not invoke sibling skills separately for the same task.
Refactor And Fold duplicate Afenda feature areas into a canonical module. Use when the user invokes /raf, asks to merge duplicate system-admin sections, consolidate overlapping routes, or remove a feature folder after folding its unique fields into the surviving area. No redirects unless explicitly requested.
Afenda Ask-Docs Quality Standard workflow. Use automatically when authoring, reviewing, or improving content/ask-docs MDX. Composes documentation-audit (code-verified accuracy) and technical-writing (internal-guide prose) with the six-dimension ADQS rubric. Do not invoke sibling skills separately.
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
Find unused functions and dead code in the codebase
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
| name | context7-mcp |
| description | Use when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks (React, Next.js, Drizzle, Tailwind, etc.). |
When the user asks about libraries, frameworks, or needs code examples, use the Context7 MCP tools (resolve-library-id, query-docs) instead of relying on training data.
API key: Anonymous Context7 usage hits low monthly quotas. Operators should set CONTEXT7_API_KEY (ctx7sk… from context7.com/dashboard) in global ~/.cursor/mcp.json and/or .env.config §L + pnpm env:sync:cursor on Windows. See docs/development/env.md.
Call resolve-library-id with:
libraryName: library name from the questionquery: the user's full question (improves ranking)Prefer exact name matches, higher benchmark scores, and version-specific IDs when the user names a version.
Call query-docs with:
libraryId: e.g. /vercel/next.jsquery: the specific questionUse current documentation and cite versions when relevant.
For tenancy, governed UI, package boundaries, and ARCH docs, use repo doctrine (docs/architecture/, .cursor/rules/) before Context7. See rule afenda-external-context.
Stack library hints: .agents/stack-context.md.