Internal monorepo for LeanCode's shared AI plugins.
- Cursor — installed via the team marketplace in Cursor settings.
- Claude Code — installed via team extensions in Claude Code.
- Claude Code extension in Cursor — same plugin assets, loaded through the Claude Code extension running inside Cursor.
For day-to-day usage, install plugins from the LeanCode team marketplace in your client. You usually do not need to clone this repo unless you want to contribute.
- Pick the plugins that match the project you are working on.
- Install them from the team marketplace in your client.
- If a plugin requires extra tooling or MCP setup, finish the one-time setup from that plugin's
README.md.
Most plugins are pure rules and skills. Extra setup is mainly needed for:
flutter-patrol- Patrol CLI and Patrol MCPflutter-marionette- Marionette MCP and app-side binding
2026-04-21.20-04-38.mp4
2026-04-21.20-26-42.mp4
claude-code-cursor-plugins-setup.mp4
vercel-labs/skills is a CLI that installs skill files into any of 50+ supported agents — Cursor, Claude Code, OpenCode, Codex, Windsurf, and more — from a single command. It works regardless of license tier, and is useful when a team marketplace isn't available (e.g. Cursor without a Business seat) or when you want a single CLI flow across agents:
# Install one skill into Cursor
npx skills add leancodepl/ai-plugins --skill flutter-bloc-usage -a cursor
# Install all skills into Claude Code
npx skills add leancodepl/ai-plugins --skill '*' -a claude-code
# Install everything into every detected agent
npx skills add leancodepl/ai-plugins --allCaveats:
- Skills only. Rules are not packaged through this channel. Plugins driven mainly by rules (e.g.
flutter-bloc,flutter-leancode-architecture) will be partially functional — skill-side routing and review workflows work, path-scoped auto-triggers do not. A<plugin>-usageskill won't have the plugin'srules/to read in the workspace. - Frontmatter quirks. Receiving agents may not honor every field. See here for the compatibility specification.
lean-core- entry point for the marketplace./lean-core-usageexplains what's available;/lean-contributewalks contributors through opening a PR. Install this first.
flutter-leancode-architecture- project structure, error handling, logging, plus architecture review and feature scaffolding skillsflutter-di-provider-based dependency injection, page-root providers,GlobalProviders, and async initialization patternsflutter-navigation-auto_routeandgo_router, typed routes, route guards, route tree organization, and deep linksflutter-analytics- analytics IDs, page/button tracking, plus skills to scaffold IDs and review coverageflutter-localization- ARB workflows, POEditor,poe2arb, andl10n(context)
flutter-bloc- BLoC/Cubit conventions, state modeling, presentation side effects,bloc_presentation, andflutter_hooksflutter-cubit-utils-QueryCubit,PaginatedQueryCubit,RequestCubit, and recipes for lists, details, and actionsflutter-cqrs- CQRS contracts, repositories, directcqrs.run/cqrs.getusage, and CQRS-backed cubitsflutter-forms-leancode_forms, validation behavior, naming conventions, and form cubit patterns
flutter-ui- design-system-driven UI, loading/error patterns, localized presentation text, and UI implementation checklistsflutter-patrol- Patrol test architecture, key conventions, and Patrol MCP workflow for AI-assisted E2E workflutter-marionette- runtime interaction with a live debug app through Marionette MCP for exploration, smoke checks, and UI debugging
pmo-project- per-project workflows: meeting prep, Jira ticketing, refinement, health checks, decision logs, client status reportspmo-universal- project-agnostic workflows: morning briefings and fact-based blame checks
lean-anti-ai-slop- drafts Slack, PR, email, and post copy in the user's own voice; loads configured writing samples and self-checks against an AI-slop blacklist before emitting
Each plugin README lists what ships, and exposes a /<plugin>-usage skill (for example /flutter-bloc-usage) that explains what the plugin covers and example prompts to try next.
plugins/<plugin-name>/- one self-contained pluginplugins/<plugin-name>/rules/- source of truth for shared rulesplugins/<plugin-name>/skills/- shared skills used across IDE targetsplugins/<plugin-name>/.cursor-plugin/andplugins/<plugin-name>/.claude-plugin/- plugin manifestsplugins/<plugin-name>/cursor-rules/andplugins/<plugin-name>/claude-rules/- generated IDE-specific rule outputs.cursor-plugin/marketplace.jsonand.claude-plugin/marketplace.json- marketplace indexes
Install lean-core, run /lean-contribute, and follow the walk-through inside a local clone. CI validates structure on every PR — a green PR means the shape is correct.
Full conventions live in CONTRIBUTING.md.