LeanCode's shared AI plugins for Claude Code, focused on Flutter development.
- Claude Code — installed via the LeanCode plugin marketplace in Claude Code.
These plugins are distributed as a Claude Code plugin marketplace. Installing is a two-step process — add the marketplace once, then install the plugins you want. You do not need to clone this repo for day-to-day usage. For the full reference, see Claude Code's Discover and install plugins docs.
In Claude Code, add this repository as a marketplace by its GitHub owner/repo:
/plugin marketplace add leancodepl/ai-plugins
This registers the catalog so you can browse it — nothing is installed yet. (The full git URL works too: /plugin marketplace add https://github.com/leancodepl/ai-plugins.git.)
Browse the catalog with /plugin (the Discover tab), or install directly by name. Plugins install from the leancode-ai-plugins marketplace:
/plugin install flutter-bloc@leancode-ai-plugins
Pick only the plugins that match your project — each is independently installable. After installing, run /reload-plugins to activate them.
Tip: Install
lean-corefirst and run/lean-core-usagefor a guided tour of the whole marketplace.
To have Claude Code prompt collaborators to install the marketplace automatically, add it to your project's .claude/settings.json:
{
"extraKnownMarketplaces": {
"leancode-ai-plugins": {
"source": {
"source": "github",
"repo": "leancodepl/ai-plugins"
}
}
}
}Most plugins are pure rules and skills with no setup. A few need one-time tooling or MCP setup — finish it from the plugin's README.md:
flutter-patrol- Patrol CLI and Patrol MCPflutter-marionette- Marionette MCP and app-side binding
lean-core- marketplace entry point:/lean-core-usageexplains what's available,/lean-contributewalks you through opening a PR
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
Once a plugin is installed, it exposes a /<plugin-name>-usage skill — for example /flutter-bloc-usage, /flutter-cqrs-usage, /flutter-ui-usage. Run it to see what the plugin covers, its conventions, and example prompts to try next. It's the fastest way to learn a plugin without reading its full README.md. If you're not sure where to begin, run /lean-core-usage for a tour of the whole marketplace.
plugins/<plugin-name>/- one self-contained pluginplugins/<plugin-name>/skills/- skills the plugin shipsplugins/<plugin-name>/skills/<skill>/references/- supporting reference material a skill loads on demandplugins/<plugin-name>/.claude-plugin/- plugin manifest.claude-plugin/marketplace.json- marketplace index
If you are interested in contributing, please see CONTRIBUTING.md