LeanCode AI Plugins

Internal mono-repo for LeanCode AI plugins used in Flutter projects.

This repo is the shared source of truth for the plugins published to our team marketplaces in Cursor and Claude Code. Instead of one large ruleset, guidance is split into small plugins that teams can install per project.

Install

For day-to-day usage, install plugins from the LeanCode team marketplace in Cursor or Claude Code.

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 IDE.
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:

• flutter-patrol - Patrol CLI and Patrol MCP
• flutter-marionette - Marionette MCP and app-side binding

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

Available plugins

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

Each plugin README lists the exact rules, skills, and setup details shipped with that plugin. Each plugin also exposes a /<plugin>-usage skill (for example /flutter-bloc-usage) that explains what the plugin covers, when to use it, 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 by both 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

• Keep plugins small, focused, and independently installable.
• Edit only plugins/<plugin-name>/rules/*.md as the rule source of truth.
• Never hand-edit cursor-rules/ or claude-rules/.
• When adding or changing rules or globs, run python scripts/generate-rules.py and commit the generated files.
• New rule files must include YAML frontmatter with description and globs.
• Each plugin should include skills/<plugin>-usage/SKILL.md (for example skills/flutter-bloc-usage/SKILL.md) as the user-facing entry point that explains the plugin and suggests next requests. Use the unique, plugin-scoped skill name so / commands never collide across installed plugins.
• Update the plugin README.md and both platform manifests when the plugin scope changes.