The first Claude Code plugin for Divi 5 development. Validates CSS compatibility, generates Divi-ready code, scaffolds page sections, audits project health, checks accessibility, audits Core Web Vitals performance, diagnoses symptoms, learns from errors, and
FAQ
divi5-toolkit is a Claude Code plugin with 3 hand-picked skills for development work, indexed on Flowy. Install it with the command on its page. It includes divi5-compatibility, divi5-css-patterns, divi5-performance. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
> /plugin marketplace add cjsimon2/Divi5-ToolKit> /plugin install divi5-toolkit@divi5-local
The first Claude Code plugin for Divi 5 development. Validates CSS compatibility, generates Divi-ready code, scaffolds page sections, audits project health, checks accessibility, audits Core Web Vitals performance, diagnoses symptoms, learns from errors, and stays current with Divi 5 updates β all powered by Claude instead of GPT-3.5.
For Divi 5.6+ (5 new modules β Timeline, Breadcrumbs, SVG, Table of Contents, Instagram Feed β plus Aspect Ratio/Framing, Variable Generators, pseudo-class editing, Composable Settings, Canvas system, Loop Builder)
Divi AI uses GPT-3.5 and only works inside the Visual Builder. This plugin gives you Claude's superior code generation with deep Divi 5 knowledge β from your terminal, editor, or CI/CD pipeline. It knows Divi's selectors, specificity rules, breakpoints, Design Variables, Free-Form CSS, Composable Settings, Canvas system, and the full module library so you don't have to provide that context manually.
!important usage, CSS variable scope, format correctness, accessibility/divi5-toolkit:research refreshes the plugin's own knowledge base from upstream Divi sources on demand (recommended weekly β check last_research in your config)Already have the plugin loaded? (See Installation if not.)
# 1. From your project root, copy the config template
mkdir -p .claude
cp /path/to/Divi5-ToolKit/plugins/divi5-toolkit/templates/divi5-toolkit.local.md .claude/divi5-toolkit.local.md
Edit .claude/divi5-toolkit.local.md and set css_prefix to your project's class prefix (e.g., acme). Leave the other defaults alone.
In Claude Code, type /divi5-toolkit: β autocomplete should show all 8 commands. Try one:
/divi5-toolkit:generate primary button with gold hover state
You should get back Divi 5-ready CSS with body prefix, !important, your custom prefix, and paste instructions. That's it β you're up and running.
Next steps:
docs/workflows.md β Build a full landing page, migrate from Divi 4, audit a project, add dark mode, etc.docs/usage.md β What every command, agent, and skill does in detaildocs/configuration.md β Tune the plugin for your project type| Command | Description |
|---|---|
/divi5-toolkit:generate | Generate Divi 5-ready CSS for any component |
/divi5-toolkit:validate | Validate CSS for Divi 5 compatibility |
/divi5-toolkit:convert | Convert existing CSS to Divi 5 format |
/divi5-toolkit:diagnose | Diagnose a Divi 5 symptom/error and return root cause + fix |
/divi5-toolkit:research | Research latest Divi 5 updates |
/divi5-toolkit:scaffold | Generate complete page section templates |
/divi5-toolkit:audit | Run a full project CSS audit with scoring |
/divi5-toolkit:responsive | Check a page across device sizes (phones, tablets, laptops, widescreen) β live browser testing via MCP, or static CSS analysis |
| Agent | Triggers When |
|---|---|
divi5-validator | After writing/editing CSS files (via PostToolUse hook, if auto_validate: true) |
divi5-error-learner | When you paste Divi error messages or describe CSS issues |
divi5-researcher | On-demand via /divi5-toolkit:research or when unknown Divi errors need research |
divi5-accessibility | When reviewing CSS for accessibility, or when writing interactive element styles |
divi5-performance | When the user mentions performance, Core Web Vitals (LCP, INP, CLS), slow Divi pages, render-blocking CSS, font loading, or cache-plugin conflicts |
| Skill | Activates When |
|---|---|
divi5-css-patterns | Writing CSS for Divi, styling Divi modules |
divi5-compatibility | Validating CSS, troubleshooting Divi issues |
divi5-performance | Optimizing Divi performance, working with Critical CSS / Dynamic CSS / Inline Stylesheets, debugging LCP/INP/CLS, configuring local fonts and image preloading |
The tables above are quick references. For depth, see the docs/ directory:
| Doc | What's Inside |
|---|---|
docs/usage.md | Detailed reference: every command (purpose, args, example, output), every agent (triggers, behavior, output), every skill (when it activates, what it provides), every CSS example, every hook |
docs/configuration.md | Every config setting explained, with rationale and recommended values for solo dev, agency, government, WooCommerce, prototype, and legacy project types |
docs/workflows.md | Step-by-step guides: first-time setup, build a landing page, migrate from Divi 4, audit an inherited project, add dark mode, build a WooCommerce grid, off-canvas menu, accessibility compliance, debug "styles not applying", refresh knowledge base, check a page across device sizes |
docs/troubleshooting.md | FAQ + diagnostic steps for plugin issues, Divi CSS issues, builder issues, plugin conflicts, migration issues, performance, and accessibility |
Internal docs:
CLAUDE.md β Developer guidance for working ON the plugin (architecture, conventions, contributing)STATE.md β Project state snapshot (current version, component inventory, knowledge topics)et_pb_* classesselector keyword (new in D5)<style> tags)No MCP servers required. For extended capabilities, add to your .mcp.json:
{
"mcpServers": {
"context7": {
"command": "npx",
"args": ["-y", "@upstash/context7-mcp@latest"]
}
}
}
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["-y", "@playwright/mcp@latest"]
}
}
}
{
"mcpServers": {
"a11y": {
"command": "npx",
"args": ["-y", "a11y-mcp"]
}
}
}
Windows users: Wrap in "command": "cmd", "args": ["/c", "npx", "-y", "..."]
Create .claude/divi5-toolkit.local.md in your project root. Full template at plugins/divi5-toolkit/templates/divi5-toolkit.local.md.
Key settings:
validation_mode: advisory # "advisory" (warnings) or "strict" (blocking errors)
default_format: theme-options # "theme-options" | "code-module" | "child-theme" | "free-form"
auto_validate: true # validate CSS files automatically after Write/Edit
divi_version: "5.6" # target Divi version β read by /research and the validators
css_prefix: my # your custom CSS class prefix
active_breakpoints: # which of Divi 5's 7 breakpoints to use
- phone
- tablet
- desktop
accessibility_level: aa # "aa" | "aaa" | "off" β strictness of accessibility checks
flag_composable_alternatives: true # suggest builder-native alternatives to custom CSS (Divi 5.2+)
scaffold_style: light # "light" | "dark" | "brand" β default color scheme for /scaffold
last_research: 2026-05-27 # auto-updated by divi5-researcher
What each setting affects:
| Setting | Read by |
|---|---|
validation_mode | /validate, divi5-validator |
default_format | /generate, /scaffold, /convert |
auto_validate | PostToolUse hook |
divi_version | /generate, /audit, /diagnose, /responsive, divi5-performance |
css_prefix | /generate, /scaffold, /convert, /diagnose, /responsive |
active_breakpoints | /generate, /scaffold, /responsive |
accessibility_level | /validate, /audit, /diagnose, /responsive, divi5-accessibility |
flag_composable_alternatives | /validate, /convert, /audit |
scaffold_style | /scaffold |
last_research | /research, divi5-researcher |
There are two ways to load the plugin: per-session (one-off) or persistent (auto-loads in specific projects or globally).
From your project directory, start Claude Code with the --plugin-dir flag:
claude --plugin-dir "/path/to/Divi5-ToolKit/plugins/divi5-toolkit"
The plugin loads for that session only. Use this for testing or occasional use.
Auto-load the plugin whenever you start Claude Code in a specific project. This uses Claude Code's local marketplace mechanism β no actual marketplace publication required.
In your website project root, create .claude/settings.local.json (gitignored β keeps your absolute path machine-local):
{
"extraKnownMarketplaces": {
"divi5-local": {
"source": {
"source": "directory",
"path": "/absolute/path/to/Divi5-ToolKit"
}
}
},
"enabledPlugins": {
"divi5-toolkit@divi5-local": true
}
}
Make sure .claude/settings.local.json is in your project's .gitignore so the absolute path doesn't get committed:
.claude/settings.local.json
.claude/*.local.json
Then start Claude Code from the project directory β /divi5-toolkit: should autocomplete.
Same JSON as Option 2, but write it to ~/.claude/settings.json instead of the per-project file. The plugin will be available in every Claude Code session on your machine.
The Divi5-ToolKit ships with .claude-plugin/marketplace.json (the marketplace manifest) alongside .claude-plugin/plugin.json (the plugin manifest). Claude Code looks for marketplace.json at exactly that path inside any directory you register via extraKnownMarketplaces.
The extraKnownMarketplaces entry in your settings tells Claude Code to treat the local directory as a marketplace; Claude reads .claude-plugin/marketplace.json from that directory to discover what plugins are available; enabledPlugins activates the plugin from that marketplace.
The marketplace name is divi5-local (declared inside .claude-plugin/marketplace.json). It must match the key you use in extraKnownMarketplaces and the part after the @ in enabledPlugins. The reference patterns in the JSON above use that name verbatim β change them in lockstep if you want a different name.
No publication, validation, or CLI registration step is needed.
divi5-toolkit/ # β repo root + marketplace root
βββ .claude-plugin/
β βββ marketplace.json # Marketplace manifest (lists plugins)
βββ plugins/
β βββ divi5-toolkit/ # β plugin lives in a subdirectory
β βββ .claude-plugin/
β β βββ plugin.json # Plugin manifest (name, version)
β βββ commands/ # Slash commands
β β βββ generate.md
β β βββ validate.md
β β βββ convert.md
β β βββ diagnose.md # NEW v2.2.0
β β βββ research.md
β β βββ scaffold.md
β β βββ audit.md
β β βββ responsive.md # NEW v2.3.0
β βββ agents/ # Autonomous agents
β β βββ divi5-validator.md
β β βββ divi5-error-learner.md
β β βββ divi5-researcher.md
β β βββ divi5-accessibility.md
β β βββ divi5-performance.md # NEW v2.2.0
β βββ skills/ # Auto-activating skills
β β βββ divi5-css-patterns/
β β β βββ SKILL.md
β β β βββ examples/
β β β β βββ button-variants.css
β β β β βββ design-tokens.css
β β β β βββ animations.css
β β β β βββ dark-mode.css
β β β β βββ woocommerce.css
β β β β βββ accessibility.css
β β β β βββ responsive-7-breakpoints.css
β β β β βββ loop-builder.css # NEW v2.2.0
β β β β βββ forms.css # NEW v2.2.0
β β β β βββ new-modules.css # NEW v2.2.0
β β β βββ references/
β β β βββ divi-selectors.md
β β β βββ responsive-breakpoints-2025.md
β β βββ divi5-compatibility/
β β β βββ SKILL.md
β β β βββ references/
β β β βββ unit-conversions.md
β β βββ divi5-performance/ # NEW v2.2.0
β β βββ SKILL.md
β β βββ examples/
β β β βββ critical-css.css
β β β βββ font-loading.css
β β βββ references/
β β βββ core-web-vitals.md
β βββ hooks/
β β βββ hooks.json # Event handlers
β β βββ css-validate.sh
β βββ templates/
β β βββ divi5-toolkit.local.md # Configuration template
β βββ .mcp.json
βββ docs/ # End-user documentation
β βββ usage.md # Detailed component reference
β βββ configuration.md # Config setting reference
β βββ workflows.md # Step-by-step scenarios
β βββ troubleshooting.md # FAQ + diagnostic steps
βββ CLAUDE.md # Developer guidance (working ON the plugin)
βββ STATE.md # Project state snapshot
βββ README.md
/divi5-toolkit:responsive command β verifies a page works across real device sizes instead of trusting that media queries exist.
et_pb_* elements named), broken column stacking, unusable navigation, touch targets below the 24px AA floor / 44px recommendation, illegible text, and fixed-header problems at short viewports. Spot-checks 1px either side of each active Divi breakpoint.max-width guards, 100vw scrollbar traps, 100vh mobile URL-bar issues (suggests svh/dvh), vw-only font sizes that ignore user zoom, absolute positioning with fixed offsets, missing table/code overflow handling, and more.active_breakpoints, divi_version, accessibility_level, css_prefix./diagnose routes size-specific symptoms ("broken on my phone") to it, /audit offers it when Category C scores poorly, /validate and /scaffold suggest it as the verification step. New walkthrough in docs/workflows.md; full reference in docs/usage.md./diagnose and divi5-performance as consumers of the keys they've read since v2.2.0.Bug-fix release: cross-platform hook reliability, knowledge-base contradictions, and command correctness.
hooks/css-validate.sh hard-required python3, which most Windows Git Bash setups don't have β under set -e the hook exited 127 on every Write/Edit. Windows backslash paths also broke the upward config-walk, so auto_validate never fired even where Python existed. Extraction now falls back jq β python3/python/py β sed, paths are normalized, the extension match is case-insensitive, and the script never exits non-zero. hooks.json now quotes ${CLAUDE_PLUGIN_ROOT} (paths with spaces). New .gitattributes pins *.sh to LF so core.autocrlf can't corrupt the hook on Windows checkouts.responsive-breakpoints-2025.md presented the 2025-recommended custom widths (479/767/1023/1279/1536/1920) as Divi 5's native breakpoints, contradicting the compatibility skill and selector reference (real defaults: Phone 767 / Phone Wide 860 / Tablet 980 / Tablet Wide 1024 / Widescreen 1280 / Ultra Wide 2560). The skill now leads with the defaults; the reference clearly labels its values as opt-in customizations and documents the defaultβrecommended mapping; the responsive-7-breakpoints.css header warns accordingly./scaffold's hero used min-height: clamp(60vh, 70vh, 90vh) β a no-op that always computes to 70vh (now clamp(480px, 70vh, 900px)). /diagnose listed "ToolUseContext" as a Divi error signal (leaked from this plugin's own v2.1.6 hook-bug history). /validate and the divi5-validator agent shipped negative-lookahead regexes the Grep tool can't execute (replaced with locate-then-inspect guidance). /convert's Conversions 8β9 were stranded after Step 7 (moved into Step 4). /audit's score formula (100 + sum) ignored its own category weights β scoring is now per-category budgets (40/20/15/10/15) matching the report breakdown./generate gained a "Read Project Config" step and now actually consumes default_format, css_prefix, divi_version, and active_breakpoints (the README config table had claimed this since v2.1.1); its variant example derives the class prefix instead of hard-coding .docs/usage, docs/configuration, docs/workflows) and the two refreshed SKILL.md files, but left some surfaces behind. v2.2.1 closes those gaps:
CLAUDE.md β "currently 5.2" β "currently 5.6"; architecture diagram's skills/ line now lists divi5-performance alongside the two existing skills.docs/troubleshooting.md β 5 new entries covering Loop Builder query/template scoping issues, 5.6 module styles not applying (Timeline, Breadcrumbs, SVG, TOC, Instagram Feed), Contact Form 7 Styler unstyled fields, and Core Web Vitals failures (routed to the divi5-performance agent).divi5-validator, divi5-researcher, divi5-accessibility agent descriptions now reference Divi 5.6, 5.3 pseudo-class editing, 5.5 Aspect Ratio/Framing. The accessibility agent's focus check notes 5.3's native focus design tabs make no-code focus styling the preferred path. The 6 older commands (audit, generate, validate, convert, research, scaffold) bump default divi_version to 5.6, expand their "Builder-Native Alternatives" sections to list Composable Settings (5.2+), pseudo-class editing (5.3+), and Aspect Ratio/Framing (5.5+), and reference /diagnose and the divi5-performance agent as escalation paths.skills/divi5-css-patterns/references/divi-selectors.md β added Contact Form 7 Styler row to the Forms & Utility table; new section for the 5.6 modules with selectors and a cross-reference to new-modules.css.skills/divi5-css-patterns/examples/woocommerce.css header cross-references loop-builder.css for product card grids.skills/divi5-css-patterns/examples/accessibility.css header notes 5.3 native focus pseudo-class editing as the preferred path over custom CSS focus ring overrides.claude plugin validate ..divi5-performance skill β Core Web Vitals (LCP, INP, CLS), Critical CSS strategy, Dynamic CSS pipeline, Inline Stylesheets, local font loading with size-adjust/ascent-override for CLS prevention, lazy-loading background images, cache plugin compatibility matrix. Includes examples/critical-css.css (hand-crafted critical CSS template), examples/font-loading.css (local @font-face pattern), and references/core-web-vitals.md (full LCP/INP/CLS reference with Divi-specific causes and fixes).divi5-performance agent β Performance auditor that triggers on Core Web Vitals mentions, slow page reports, render-blocking flags, or cache plugin conflicts. Reads Lighthouse / PSI output, project CSS, or Divi settings and returns prioritized fixes./divi5-toolkit:diagnose command β Diagnostic dispatcher. Paste a symptom, error, or "this isn't working" description; routes to the right specialist (error-learner, validator, performance, accessibility, compatibility) and returns root cause + fix with paste location.divi5-css-patterns/examples/:
loop-builder.css β Loop Builder CSS Grid layouts (cards, masonry, product overlay, horizontal list, pagination)forms.css β Divi 5.3 form module styling with :checked/:focus/:active pseudo-class equivalents, custom checkboxes/radios, Contact Form 7 Styler integrationnew-modules.css β Styling for the 5 new Divi 5.6 modules: Timeline (vertical + horizontal), Breadcrumbs, SVG (currentColor + stroke patterns), Table of Contents (sticky sidebar + smooth scroll), Instagram Feed (responsive grid + hover overlay)divi5-css-patterns, divi5-compatibility) now document:
:checked/:focus/:active), Contact Form 7 Styler module, Nested Option Presets, harmonized form field options. 69 bug fixes.PostToolUse Write/Edit hook was a prompt-type hook that asked an LLM to "stay silent for non-CSS edits." LLMs are unreliable at returning empty output β they kept narrating their decision (e.g. "This change is not CSS-related and does not trigger the validation condition"), which Claude Code surfaced as a blocking message and stopped continuation on every non-CSS Edit/Write across every project that had the plugin enabled. Replaced with a deterministic command-type hook (hooks/css-validate.sh) that filters by file extension in shell and only emits output when the edited file actually ends in .css/.scss/.sass/.less AND the project's .claude/divi5-toolkit.local.md sets auto_validate: true. No more false positives on HTML, PHP, Markdown, JSON, etc.<style> blocks and style="" attributes inside HTML/PHP files no longer trigger auto-validation. The previous prompt-based hook claimed to support this but couldn't do so reliably. Run /divi5-toolkit:validate manually if you want inline styles checked.claude plugin marketplace update divi5-local (or restart Claude Code) to pick up the fix.SessionStart entry from hooks/hooks.json. Claude Code's prompt-type hooks require a ToolUseContext, which doesn't exist before any tool has been called, so the hook was firing a ToolUseContext is required for prompt hooks. This is a bug. error every time a session started in a project with the plugin enabled. The hook only ever provided two nice-to-have notifications (stale last_research, outdated divi_version); both are still documented in docs/workflows.md and docs/configuration.md. The PostToolUse hook is unaffected β it has a tool context by design.divi_version and last_research are read by a SessionStart hook. They're now read only by divi5-researcher and the consuming commands.claude plugin marketplace update divi5-local (or restart Claude Code) to pick up the fix.--plugin-dir users): Restructured the repo so the plugin lives in plugins/divi5-toolkit/ instead of the repo root. Verified against the official Anthropic plugin marketplace docs: a directory-source plugin must live in a subdirectory of the marketplace root, not at the marketplace root itself. The source: "./" form attempted in v2.1.4 was rejected by Claude Code's loader even though the schema technically allowed it, because the plugin's .claude-plugin/plugin.json and the marketplace's .claude-plugin/marketplace.json cannot coexist in the same .claude-plugin/ directory.marketplace.json schema errors caught by claude plugin validate:
$schema field (not in the schema).description into metadata.description (description at root is not allowed).claude plugin validate . now passes for the marketplace.--plugin-dir now requires the subdirectory path:
# v2.1.4 and earlier (broken)
claude --plugin-dir "/path/to/Divi5-ToolKit"
# v2.1.5 and later
claude --plugin-dir "/path/to/Divi5-ToolKit/plugins/divi5-toolkit"
extraKnownMarketplaces is unchanged. Users still point at /path/to/Divi5-ToolKit (the marketplace root). Claude Code reads .claude-plugin/marketplace.json from there and follows the source: "./plugins/divi5-toolkit" reference automatically.--plugin-dir path.marketplace.json for persistent loading. Used source: "./" (plugin = marketplace root) and an incorrect top-level schema. Rejected by claude plugin validate and by Claude Code's loader. Superseded by 2.1.5.marketplace.json for persistent loading. File was placed at the wrong path and used the wrong schema. v2.1.4 supersedes this β do not use 2.1.3.--plugin-dir), per-project (extraKnownMarketplaces in .claude/settings.local.json), and global (same JSON in ~/.claude/settings.json). Includes the exact JSON schema and gitignore rule for keeping absolute paths out of git.docs/workflows.md First-Time Setup workflow now shows the marketplace approach as the recommended persistent setup.docs/troubleshooting.md "Slash commands don't autocomplete" entry now lists missing marketplace.json and missing extraKnownMarketplaces registration as causes.CLAUDE.md versioning checklist now requires keeping marketplace.json version in sync with .claude-plugin/plugin.json version on every release.docs/usage.md β comprehensive reference for every command (purpose, args, example, output, tools used), every agent (triggers, behavior, model, output), every skill (activation triggers, content), every hook, every CSS example, and every template.docs/configuration.md β every setting explained with rationale, plus 6 recommended config presets (solo developer, agency, government/healthcare, WooCommerce store, prototype, legacy 5.0/5.1 project).docs/workflows.md β 10 step-by-step scenarios: first-time setup, landing page from scratch, Divi 4 β 5 migration, inherited project audit, dark mode toggle, WooCommerce product grid, off-canvas menu, WCAG AA compliance, debugging "styles not applying", knowledge base refresh.docs/troubleshooting.md β FAQ + diagnostic steps covering plugin issues, Divi CSS issues, builder issues, plugin conflicts (WP Rocket, LiteSpeed, Autoptimize, Wordfence), migration issues, performance, and accessibility. Plus a 12-question general FAQ.docs/ directory.docs/, CLAUDE.md, and STATE.md.accessibility_level, flag_composable_alternatives, scaffold_style) were defined in the template but not actually consumed by any command or agent. Now wired into /validate, /audit, /convert, /scaffold, and the divi5-accessibility agent. Each consuming file reads .claude/divi5-toolkit.local.md in a "Read Project Config" step.accessibility_level: aaa adds stricter WCAG 2.1 AAA thresholds (7:1 contrast for normal text, β₯2px focus rings, hover-animation rules). accessibility_level: off skips accessibility checks entirely.CLAUDE.md β developer guide for working ON the plugin (architecture, conventions, versioning, naming).STATE.md β project state snapshot with component inventory.divi5-toolkit / Divi5 Toolkit / Divi 5)./generate, /scaffold, and divi5-accessibility β bounds when WebSearch/WebFetch should be used.description fields expanded with richer auto-activation triggers.divi-selectors.md, unit-conversions.md) now back-link to their parent skill.unit-conversions.md under css-patterns/references/. Removed./generate referenced "v5.1+" β corrected to "v5.2+"./scaffold command β generate complete page section templates (hero, pricing, FAQ, CTA, off-canvas menu, popup modal, WooCommerce grid, and 10 more)/audit command β whole-project CSS audit with scoring (A-F grade), category breakdown, and prioritized fix listdivi5-accessibility agent β WCAG 2.1 AA checker for focus indicators, color contrast, touch targets, reduced motion, semantic elementsprefers-reduced-motion)MIT
.claude-plugin/
marketplace.json
.gitattributes
.gitignore
CLAUDE.md
docs/
configuration.md
troubleshooting.md
usage.md
workflows.md
plugins/
divi5-toolkit/
.claude-plugin/
plugin.json
.mcp.json
agents/
divi5-accessibility.md
divi5-error-learner.md
divi5-performance.md
divi5-researcher.md
divi5-validator.md
commands/
audit.md
convert.md
diagnose.md
generate.md
research.md
responsive.md
scaffold.md
validate.md
hooks/
css-validate.sh
hooks.json
skills/
divi5-compatibility/
references/
unit-conversions.md
SKILL.md
divi5-css-patterns/
examples/
accessibility.css
animations.css
button-variants.css
dark-mode.css
design-tokens.css
forms.css
loop-builder.css
new-modules.css
responsive-7-breakpoints.css
woocommerce.css
references/
divi-selectors.md
responsive-breakpoints-2025.md
SKILL.md
divi5-performance/
examples/
critical-css.css
font-loading.css
references/
core-web-vitals.md
SKILL.md
templates/
divi5-toolkit.local.md
README.md
STATE.mdΒ© 2026 Flowy Β· Free and open source
Built for Claude Code Β· Not affiliated with Anthropic
my-docs/configuration.md/docs/workflows.md/docs/usage.md pointed at a root-level templates/ directory that hasn't existed since v2.1.5 (now plugins/divi5-toolkit/templates/). CLAUDE.md's test command still showed the pre-v2.1.5 --plugin-dir path. README's "researches weekly" claim corrected to on-demand. Agents' in-plugin file references now use ${CLAUDE_PLUGIN_ROOT} per convention.templates/divi5-toolkit.local.md default divi_version bumped to "5.6". last_research bumped to 2026-05-27.