Abilities for Fluent registers every operation across the Fluent suite — CRM, forms, community, cart, support, booking, boards, affiliate — as a callable ability behind the Trinity gate. The plugins you already chose. The workflows you already built. Now reachable from a chat with your AI client.
A reading of this plugin before any feature list. Same shape as every product in the Trinity — value first, spec second.
Each plugin in the suite gets its own ability set, registered only if that plugin is active on the site. You don't pay an attention tax for capabilities you're not running.
Two scenes from the alpha. Real sequences the AI can run today, on a site running the Trinity and Fluent together. The shape of the operator's day after.
Not a marketing claim. A statement of completeness. The Trinity makes WordPress AI-operable. Abilities for Fluent extends that to the suite of plugins you already pay for. WordPress core gives you the rest. There is nothing else needed in the middle.
For the operator who already runs on Fluent, the deep confirmation is this: every plugin you chose, every workflow you built, is now part of the AI-operable layer. You didn't bet on the wrong stack. You bet early.
For the operator who hasn't picked yet: this is the suite that pairs cleanly with the Trinity. One vendor on the suite side. One open-source ecosystem on the operating side. Zero SaaS layers between you and your data.
Other plugin suites can be supported the same way. Fluent is where the alpha launches because Fluent is what we run.
The Trinity is three: Abilities MCP, MCP Adapter, Abilities for AI. Abilities for Fluent is what becomes possible the moment all three are in place — the same operating layer, extended into the plugin suite that runs your business.