sales-breakdance
Provides development support and platform troubleshooting for the Breakdance WordPress builder.
Install
mkdir -p .claude/skills/sales-breakdance && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19384" && unzip -o skill.zip -d .claude/skills/sales-breakdance && rm skill.zipInstalls to .claude/skills/sales-breakdance
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Breakdance platform help — standalone visual website/page builder for WordPress (by Soflyy, the Oxygen makers): a front-end editor that replaces the theme, with a WooCommerce Builder, Form Builder + Popup Builder, Dynamic Data, Element Studio (custom-element IDE), Breakdance AI, and a real PHP developer API (Form Actions API, Dynamic Data Field API, Conditions API, hooks/filters). Use when a Breakdance form notification still emails you after a spam plugin blocked the entry, building a custom Form Action or Dynamic Data field, routing Breakdance AI to OpenRouter/Claude via the AI endpoint filters, migrating an Oxygen site, registering a custom element or display condition, building WooCommerce product templates, pages are slow despite the lean builder, or choosing Breakdance Free vs Pro (no lifetime plan). Do NOT use for cross-tool builder selection or funnel/CRO strategy (use /sales-funnel), A/B testing/heatmaps (use /sales-vwo), or checkout/cart across platforms (use /sales-checkout).Key capabilities
- →Build custom form actions and dynamic data fields
- →Configure WooCommerce product and cart templates
- →Troubleshoot builder performance issues
- →Route Breakdance AI to custom endpoints
- →Register custom elements and display conditions
How it works
The skill provides platform-specific guidance for the Breakdance visual builder, including developer API usage, form action configuration, and performance optimization techniques.
Inputs & outputs
When to use sales-breakdance
- →Build a custom Form Action
- →Create a dynamic data field
- →Troubleshoot Breakdance builder performance
About this skill
Breakdance Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Fix a broken state — form notifications still emailing after a spam plugin blocked the entry, form submissions not stored/not arriving, builder deactivated/blank after a migration, slow pages despite the lean builder, AI settings UI not reflecting a filter change
- B) Build with the UI — Elements, Templates/Design Library, the WooCommerce Builder (product/shop/cart/checkout templates), the Form Builder (multi-step, conditional fields), the Popup Builder, Dynamic Data (loops/repeaters/conditional display), global blocks, headers/footers
- C) Extend with code — a custom Form Action, a custom Dynamic Data field, an Element Display Condition, a custom element in Element Studio, reusable dependencies, or one of the
breakdance_*hooks/filters - D) Connect data or AI — POST a form to Zapier/Make via the Webhook action, route Breakdance AI to a different model/provider (OpenRouter, Claude) with the AI endpoint filters, or read/write page markup via the WordPress REST API
- E) Pick or compare a plan (Free vs Pro / +AI bundle), weigh Breakdance vs Bricks/Elementor/Oxygen, or plan an Oxygen→Breakdance migration
-
Free or paid? Breakdance Free (WordPress.org) ships ~80 elements + the core builder. Pro (~$199.99/yr, unlimited sites + unlimited domain activations) unlocks all ~145 elements, the full Design Library, the WooCommerce Builder, the Form Builder/Popup Builder, Global Blocks, and Client Mode. There is no lifetime plan (annual subscription with a price-lock guarantee). (Pricing best-effort — verify.)
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
Step 2 — Route or answer directly
| Problem domain | Route to |
|---|---|
| Funnel strategy, page structure, builder selection across tools (Bricks/Elementor/Oxygen/Beaver Builder/Gutenberg…) | /sales-funnel — Run: /sales-funnel {user's original question} |
| A/B testing methodology (Breakdance has no native split testing) | /sales-vwo — Run: /sales-vwo {user's original question} |
| Email sequences/automation after a form opt-in | /sales-email-marketing — Run: /sales-email-marketing {user's original question} |
| Growing the list, lead-magnet strategy | /sales-audience-growth — Run: /sales-audience-growth {user's original question} |
| WooCommerce store/checkout strategy across platforms | /sales-checkout — Run: /sales-checkout {user's original question} |
| WordPress/WooCommerce funnel + upsells around the pages | /sales-cartflows — Run: /sales-cartflows {user's original question} |
| On-page/technical SEO beyond clean markup | /sales-seo — Run: /sales-seo {user's original question} |
If the question is Breakdance-specific, continue to Step 3.
Step 3 — Breakdance platform reference
Read references/platform-guide.md for the full platform reference — modules, pricing/plan gates, data model, integration recipes, and the Oxygen relationship. For the developer APIs (Form Actions API, Dynamic Data Field API, Conditions API, the breakdance_* hooks/filters, AI endpoint filters, Menu/Animations JS APIs, and the WordPress REST surface), read references/breakdance-api-reference.md.
Answer the user's question using only the relevant section. Don't dump the full reference.
Step 4 — Actionable guidance
Focus on the user's specific situation.
- Breakdance is a standalone visual builder, not a Gutenberg block plugin. It builds pages in its own front-end editor and is themeless by default (it can replace the theme entirely) — closer to Elementor/Beaver Builder/Oxygen than to Spectra/Kadence/GenerateBlocks. Pages are Sections/Elements, not native blocks, so they live in Breakdance's own data, not as portable Gutenberg block markup.
- The form "spam still emails me" trap is real and the #1 gotcha. Breakdance runs form Actions After Submit in order, but it does not let plugins intercept the Email action — so a spam-filter plugin can block storage yet the Email notification still fires. Fix: order the spam-check action above Store Submission and Email, and for hard cases remove the Email action entirely and send notifications downstream (Make/Zapier) off the Webhook action. Enable the built-in honeypot (off by default) and reCAPTCHA v3 (the only version supported).
- Breakdance AI is model/provider-swappable via filters.
breakdance_ai_api_endpoint+breakdance_ai_modellet you point it at OpenRouter (and an Anthropic Claude model) or any OpenAI-compatible endpoint;breakdance_ai_enabledtoggles it. The WP-Admin AI Assistant settings UI won't reflect these filter changes — verify by watching the developer console and the provider's usage charts. The API key still goes in the "OpenAI API Key" field regardless of provider. - Register custom Form Actions / Dynamic Data fields / Conditions on
initand guard withfunction_exists()/class_exists()so the plugin fails gracefully when Breakdance is inactive — the docs explicitly call out file-loading race conditions otherwise. Custom elements are built in Element Studio, which also has a code escape hatch (PHP/HTML/CSS) and reusable dependencies (%%BREAKDANCE_REUSABLE_*%%, incl. predefined GSAP/ScrollTrigger). - Performance is the pitch, but it's not automatic. Breakdance markets a 45 KB blank page (vs Elementor's ~576 KB), conditional asset loading, and jQuery-independence. But slow real-world pages almost always come from misuse — bad layout structure, heavy Dynamic Data loops, unoptimized images, no caching — not the builder. Audit those (and the theme/host) before blaming Breakdance.
- The real automation surface is WordPress + the form Webhook action, not a hosted Breakdance API. There is no hosted REST API and no platform-level outbound webhook; the Form Builder's Webhook action POSTs submissions to Zapier/Make, and you read/write page content via the WordPress core REST API (Breakdance page data is in post meta, not portable block markup — see the reference). Migrating from Oxygen: Oxygen 6 runs on the Breakdance engine and Oxygen lifetime licenses now include it; for Oxygen Classic content, conversion is done with a third-party JSON converter (e.g. TransferForge), not a native importer.
If you discover a gotcha, workaround, or tip not covered in references/learnings.md, append it there.
Gotchas
Best-effort from research (2026-06) — review these, especially plan-gated features, pricing, and integration details that may be outdated.
- Spam plugins can't stop Breakdance's Email action. Even when a spam filter blocks a submission, the Email notification action can still send, because Breakdance doesn't expose an interception point for it. Order the spam-check action above Store/Email, or remove the Email action and notify via the Webhook action + Make/Zapier.
- Honeypot is off by default; reCAPTCHA is v3-only. Enable the honeypot field explicitly; Breakdance forms support reCAPTCHA v3 only (not v2 checkbox).
- No lifetime plan. Breakdance is annual-subscription only (~$199.99/yr unlimited sites) with a price-lock guarantee at renewal — unlike Bricks/Divi which sell lifetime. Don't promise a one-time license. (Pricing best-effort — verify.)
- The AI settings UI doesn't reflect endpoint/model filters. After applying
breakdance_ai_api_endpoint/breakdance_ai_model, the Breakdance → Settings → AI Assistant screen is unchanged; verify via the browser console and the provider's usage dashboard. The key always goes in the "OpenAI API Key" field. - Register extensions on
initwith guards. Form Actions, Dynamic Data fields, and Conditions must be registered inside a WordPress action (e.g.init) and wrapped infunction_exists()/class_exists()checks to avoid file-loading race conditions when Breakdance isn't active. - Oxygen migration is engine-shared but not one-click for Classic. Oxygen 6 is rebuilt on the Breakdance engine (and is included in the Oxygen lifetime license), but converting Oxygen Classic layouts uses a third-party JSON converter, not a built-in importer — test on staging and expect manual cleanup.
- Themeless by default = your theme's templates may not apply. Breakdance can replace the theme; if headers/footers/archives look wrong, confirm whether Breakdance Templates (not the theme) are controlling that area.
- No native A/B testing, heatmaps, analytics, or hosted REST API. It's a WordPress builder — measure with a separate tool (VWO, Microsoft Clarity) and automate via the WordPress REST API + the form Webhook action.
Related skills
/sales-funnel— Funnel strategy, page structure, and builder selection across tools (Bricks, Elementor, Oxygen, Beaver Builder, SeedProd, ClickFunnels, Leadpages)/sales-beaver-builder— Another standalone WordPress page builder (Rows/Columns/Modules + a PHP module API) — the closest "not-a-block-plugin" comparison to Breakdance/sales-seedprod— A WordPress page + Theme Builder plugin — compare theme-replacement, templates, and developer surface vs Breakdance/sales-spectra— A Gutenberg-native block plugin — the block-editor contrast to Breakdance's standalone editor and proprietary page data/sales-greenshift— A Gutenberg block plugin whose API Connector binds external/LLM APIs — compare data/AI integration vs Breakdance's AI endpoint filters + form Webhook action/sales-cartflows— WordPress/WooCommerce funnel + checkout/upsells around the pages Breakdance builds (CartFlows supports Breakdance for step design)/sales-vwo— A/B testing and heatmap methodology Breakdance lacks natively/sales-audience-growth— Growing an email list
Content truncated.
When not to use it
- →Cross-tool builder selection
- →Funnel or CRO strategy
- →A/B testing or heatmaps
Limitations
- →Does not allow plugins to intercept the Email action
- →AI Assistant UI does not reflect filter changes
How it compares
It provides specialized troubleshooting for Breakdance-specific behaviors, such as form action sequencing, which differs from standard WordPress block-based editing.
Compared to similar skills
sales-breakdance side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| sales-breakdance (this skill) | 0 | 28d | No flags | Intermediate |
| unity-developer | 142 | 3mo | No flags | Advanced |
| tauri | 76 | 17d | Review | Advanced |
| telegram-mini-app | 62 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by sales-skills
View all by sales-skills →You might also like
unity-developer
sickn33
Build Unity games with optimized C# scripts, efficient rendering, and proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and cross-platform deployment. Handles gameplay systems, UI implementation, and platform optimization. Use PROACTIVELY for Unity performance issues, game mechanics, or cross-platform builds.
tauri
EpicenterHQ
Tauri path handling, cross-platform file operations, and API usage. Use when working with file paths in Tauri frontend code, accessing filesystem APIs, or handling platform differences in desktop apps.
telegram-mini-app
davila7
Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and building viral mini apps that monetize. Use when: telegram mini app, TWA, telegram web app, TON app, mini app.
shopify-development
davila7
Build Shopify apps, extensions, themes using GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid. TRIGGER: "shopify", "shopify app", "checkout extension", "admin extension", "POS extension", "shopify theme", "liquid template", "polaris", "shopify graphql", "shopify webhook", "shopify billing", "app subscription", "metafields", "shopify functions"
nextjs-supabase-auth
davila7
Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.
nuxt
antfu
Nuxt full-stack Vue framework with SSR, auto-imports, and file-based routing. Use when working with Nuxt apps, server routes, useFetch, middleware, or hybrid rendering.