npx claudepluginhub accionlabs/breezeai-claude-pluginBreeze AI — functional graph, code graph, and design analysis skills
accionlabsA Claude Code plugin that integrates with the Breeze AI platform for functional graph management, code analysis, design analysis, and requirement tracing.
/plugin marketplace add accionlabs/breezeai-claude-plugin
/breeze:setup-project
This will walk you through:
Your credentials are saved to .breeze.json in the project root (gitignored).
| Skill | Command | Description |
|---|---|---|
| Init | /breeze:setup-project | Set up API key, link project, check ontology status, optionally upload repo or documents |
| Analyze Functional | /breeze:analyze-functional | Analyze requirements against the existing functional graph — identifies coverage gaps, conflicts, dependencies, and impact |
| Analyze Architecture | /breeze:analyze-architecture | Analyze requirements against the existing architectural graph — identifies impacted layers and components across 8 architecture layers |
| Analyze Design | /breeze:analyze-design <Figma URL> | Analyze UI/UX designs from Figma frames — extracts functional summary, identifies components, maps to functional graph, flags gaps |
| Search | /breeze:search <query> | Search functional graph or code graph for feature discovery, impact analysis, and cross-cutting queries |
| Generate Functional from Code | /breeze:generate-functional-from-code | Generate a functional graph from the code graph using a three-pass pipeline — extracts intents, creates structure, generates scenarios |
| Generate Code | /breeze:generate-code <feature> | Generate code and test cases informed by the functional graph and code graph |
| Generate Spec | /breeze:generate-spec | Generate functional specification documents from the functional graph |
| Update Functional Graph | /breeze:update-functional-graph | Create/update nodes in the functional graph from documents, code, or Figma |
| Validate Functional Graph | /breeze:validate-functional-graph | Validate the functional graph for duplicates, gaps, quality issues |
To avoid passing --plugin-dir every time, add this to your project's .claude/settings.json:
{
"plugins": ["./breeze-claude-plugin"]
}
Place the breeze-claude-plugin/ folder in your project repo. Everyone who clones the repo has it.
Clone the plugin repo alongside your project:
git clone [email protected]:accionlabs/breeze-claude-plugin.git
claude --plugin-dir ../breeze-claude-plugin
.breeze.json contains your API key — add it to .gitignoreinit require a valid .breeze.json with apiKey and projectUuid