Integrations

Authority-aware by design

Work with the WordPress stack you actually use.

Kitten detects active providers, delegates ownership, and labels what is core, optional, target-dependent, or planned.

Integration status

A clear boundary for every provider

Core / ready

Codex

Connected-agent workflow through the Kitten Studio contract.

Core / ready

Claude Code

Compatible MCP-client workflow using the same portable contracts.

Ready workflow

Figma workflow

Exact-node structured design input mapped into manifest v1.3; target validation remains required.

Core / ready

WordPress & Gutenberg

Pages, posts, media, navigation, blocks, templates, revisions, permissions, and publishing authority.

Optional provider

ACF

Optional editing adapter over portable REST-visible native metadata.

Ready vertical slice

Yoast / Rank Math

Portable SEO metadata with provider sync when the selected plugin is active.

Ready vertical slice

Polylang / WPML / TranslatePress

Delegated multilingual relationships with BCP 47, reciprocal URLs, and RTL foundations.

Optional provider

Form providers

Discovery, implementation planning, verified draft embed, and audit; provider creation and delivery remain authoritative.

Ready vertical slice

WooCommerce

Product and variation drafts plus store-readiness checks when WooCommerce is active.

Core / ready

Media Library

Raster provenance, pending review, responsive sizes, focal points, and reversible draft replacement.

Not claimed

Universal plugin support

Kitten does not claim compatibility with every plugin, host, payment, shipping, tax, or cache combination.

Planned / project-specific

Code Connect library

Project-specific maps can be added later; a universal complete library is not shipped.

This staging target

Current detected authorities

Validate your stack

Run preflight before you promise compatibility.