# Agent Composer Theme Integration

Composer is theme-aware but theme-independent. It discovers the active theme's templates, registered patterns, Gutenberg blocks, `theme.json` settings, and optional presentational manifest. A Config Set can require only capabilities that exist on the current site.

SmartCloud Agent Canvas is the reference presentation layer. Canvas provides core-block templates, patterns, styles, tokens, and a read-only semantic manifest. Composer continues to own Site Contracts and Blueprints. A Canvas manifest must not contain credentials, provider runtime configuration, prompts, or executable callbacks.

Composer also works with compatible third-party block themes. Start with Universal Gutenberg or use Detected Theme Starter when Composer finds a safe single-root core-block pattern in the active theme. The generated starter excludes hidden utility, query, navigation, template, shortcode, and Custom HTML patterns, records its source and theme fingerprint, and remains inactive until explicit validation and activation. Validate and preview it before adding more page types. Partial support is expected: a theme may support standard pages and posts without supporting a specialized product or architecture layout.

Avoid duplicate page titles. If an approved pattern supplies the single H1, select a theme template that does not render another post-title H1. Required sequences should contain only patterns that every valid draft needs, and every nested block used by a pattern must be in the Blueprint allowlist.

After a theme switch or upgrade, rescan the site, clone the active Config Set, update references in the clone, validate every affected Blueprint, and preview representative drafts. Activate the clone only after review. The theme change itself never rewrites or activates Composer configuration.

Provider plugins may add blocks and provider-owned WordPress Abilities. Composer discovers and delegates to these providers but does not republish their business operations as Composer-owned tools. Review each provider's external-service and privacy documentation before using provider-backed components.