Claude Code governance plugins for TypeScript, Expo, NestJS, CDK, and Rails projects
npx claudepluginhub codyswanngt/lisaUniversal governance — agents, skills, commands, hooks, and rules for all projects
TypeScript-specific hooks — Prettier formatting, ESLint linting, and ast-grep scanning on edit
Expo/React Native-specific skills, agents, rules, and MCP servers
NestJS-specific skills (GraphQL, TypeORM)
AWS CDK-specific plugin
Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit
Claude Code marketplace entries for the plugin-safe Antigravity Awesome Skills library and its compatible editorial bundles.
Production-ready workflow orchestration with 79 focused plugins, 184 specialized agents, and 150 skills - optimized for granular installation and minimal token usage
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations
Lisa is a governance layer for AI-assisted software development. It ensures that AI agents — whether running on a developer's machine or in CI/CD — follow the same standards, workflows, and quality gates.
When a request comes in (from a human, a JIRA ticket, or a scheduled job), Lisa classifies it and routes it to the appropriate flow. Flows are ordered sequences of specialized agents, each with a defined role.
A request to fix a bug routes to a different flow than a request to build a feature or reduce code complexity. The routing is automatic based on context, but can be overridden explicitly via slash commands.
A flow is a pipeline. Each step in the pipeline is an agent — a scoped AI with specific tools and skills. One agent investigates git history, another reproduces bugs, another writes code, another verifies the result.
Agents delegate domain-specific work to skills — reusable instruction sets that can be invoked by agents, by slash commands, or by CI workflows. The same skill that triages a JIRA ticket interactively is the same skill invoked by the nightly triage workflow.
Flows can nest. A build flow includes a verification sub-flow, which includes a ship sub-flow. This composition keeps each flow focused while enabling complex end-to-end workflows.
Lisa enforces quality through layered gates:
The same rules, skills, and quality gates apply everywhere:
The analytical logic lives in skills. The enforcement lives in hooks and rules. The orchestration adapts to context — using MCP integrations locally and REST APIs in CI — but the standards don't change.
Lisa distributes its standards to downstream projects as templates. When a project installs Lisa, it receives:
Templates follow governance rules: some files are overwritten on every update (enforced standards), some are created once and left alone (project customization), and some are merged (shared defaults with project additions).
curl -fsSL https://claude.ai/install.sh | bash
Ask Claude: "I just cloned this repo. Walk me through setup."
Ask Claude: "I have JIRA ticket [TICKET-ID]. Research, plan, and implement it."
Or use slash commands directly:
/fix — route through the bug fix flow/build — route through the feature build flow/improve — route through the improvement flow/investigate — route through the investigation flow/jira:triage <TICKET-ID> — analytical triage gate: detect ambiguities, edge cases, and verification methodology/plan:improve-tests <target> — improve test quality by analyzing and strengthening weak or brittle testsAsk Claude: "What commands are available?"