Hermeticormus Floraheritage
Flora Heritage is a Claude Code plugin for the Build phase that bundles 66 agent skills for botanical heritage preservation and education products.
by HermeticOrmus · github.com/HermeticOrmus/FloraHeritage
Install a large Claude Code plugin bundle oriented to botanical heritage, education, and content-heavy apps when you need broad agent skills in one repo.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install hermeticormus-floraheritage@HermeticOrmus/FloraHeritageBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:HermeticOrmus/FloraHeritage") and the paste-ready config with skillselion.get_install_config("plugin:HermeticOrmus/FloraHeritage").
What it does
Flora Heritage is a Claude Code plugin collection from HermeticOrmus/FloraHeritage described as botanical heritage preservation and education, shipped as a 66-plugin bundle rather than one narrow skill. Solo builders curating nature archives, field guides, or cultural-education products can register the pack and enable only the plugins that match each sprint—frontend, API docs, content audit, accessibility, pipelines, and more appear in the keyword index. Treat it as vertical agent tooling during Build: you are not buying a finished app but a toolbox that Claude can draw from while you model species data, publish stories, and harden APIs. Because scope is broad, start with explicit plugin names per task instead of loading everything. Confidence in any one capability should follow which child plugin you invoke, not the umbrella description alone.
Highlights
- 66-plugin Claude Code bundle for Flora Heritage–style botanical and education platforms
- Wide keyword surface: a11y, API design, CI/CD, content, analytics, and cloud patterns
- Suited to heritage preservation, educational content, and data-rich catalog apps
- Collection model—not a single-task skill; pick plugins per feature area
- HermeticOrmus monorepo-style distribution for vertical builders
Why builders use it
Heritage and education builders need dozens of disparate agent skills—content, APIs, a11y, DevOps—and assembling them one-by-one wastes solo-founder time.
You register one vertical plugin marketplace and selectively enable Claude skills aligned with your heritage platform roadmap.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is Flora Heritage for?
Solo builders and small teams creating botanical heritage, preservation, or education platforms who already use Claude Code and want a large pre-indexed plugin bundle.
When should I use Flora Heritage?
During Build when you are wiring agent tooling, APIs, content workflows, and quality checks for a heritage or education product—not when you only need one narrow audit.
How do I add Flora Heritage to my agent?
Add the HermeticOrmus/FloraHeritage Claude Code plugin source to your environment, then enable individual plugins from the 66-plugin set as your project needs them.
Comments
Share how you use hermeticormus-floraheritage, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.