Skip to content

Latest commit

 

History

History
107 lines (67 loc) · 6.04 KB

File metadata and controls

107 lines (67 loc) · 6.04 KB

LeanCode AI Plugins

Internal monorepo for LeanCode's shared AI plugins.

Supported clients

  • 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.

Install

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.

  1. Pick the plugins that match the project you are working on.
  2. Install them from the team marketplace in your client.
  3. 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:

Cursor

2026-04-21.20-04-38.mp4

Claude Code

2026-04-21.20-26-42.mp4

Claude Code extension in Cursor

claude-code-cursor-plugins-setup.mp4

vercel-labs/skills (cross-client alternative)

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 --all

Caveats:

  • 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>-usage skill won't have the plugin's rules/ to read in the workspace.
  • Frontmatter quirks. Receiving agents may not honor every field. See here for the compatibility specification.

Available plugins

Start here

  • lean-core - entry point for the marketplace. /lean-core-usage explains what's available; /lean-contribute walks contributors through opening a PR. Install this first.

Project foundations

  • flutter-leancode-architecture - project structure, error handling, logging, plus architecture review and feature scaffolding skills
  • flutter-di - provider-based dependency injection, page-root providers, GlobalProviders, and async initialization patterns
  • flutter-navigation - auto_route and go_router, typed routes, route guards, route tree organization, and deep links
  • flutter-analytics - analytics IDs, page/button tracking, plus skills to scaffold IDs and review coverage
  • flutter-localization - ARB workflows, POEditor, poe2arb, and l10n(context)

State and data

  • flutter-bloc - BLoC/Cubit conventions, state modeling, presentation side effects, bloc_presentation, and flutter_hooks
  • flutter-cubit-utils - QueryCubit, PaginatedQueryCubit, RequestCubit, and recipes for lists, details, and actions
  • flutter-cqrs - CQRS contracts, repositories, direct cqrs.run / cqrs.get usage, and CQRS-backed cubits
  • flutter-forms - leancode_forms, validation behavior, naming conventions, and form cubit patterns

UI and verification

  • flutter-ui - design-system-driven UI, loading/error patterns, localized presentation text, and UI implementation checklists
  • flutter-patrol - Patrol test architecture, key conventions, and Patrol MCP workflow for AI-assisted E2E work
  • flutter-marionette - runtime interaction with a live debug app through Marionette MCP for exploration, smoke checks, and UI debugging

PMO

  • pmo-project - per-project workflows: meeting prep, Jira ticketing, refinement, health checks, decision logs, client status reports
  • pmo-universal - project-agnostic workflows: morning briefings and fact-based blame checks

Writing

  • 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.

Repo layout

  • plugins/<plugin-name>/ - one self-contained plugin
  • plugins/<plugin-name>/rules/ - source of truth for shared rules
  • plugins/<plugin-name>/skills/ - shared skills used across IDE targets
  • plugins/<plugin-name>/.cursor-plugin/ and plugins/<plugin-name>/.claude-plugin/ - plugin manifests
  • plugins/<plugin-name>/cursor-rules/ and plugins/<plugin-name>/claude-rules/ - generated IDE-specific rule outputs
  • .cursor-plugin/marketplace.json and .claude-plugin/marketplace.json - marketplace indexes

Contributing

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.