# Agent Composer Pro Starter Sites Integrations

Starter Sites can hand its configuration package to Agent Composer as an inactive working Config Set and request provider-owned components from Gatey, Flow, and AI-Kit after the base structure is reviewed. Static Publisher remains a separate production release option.

Active providers are detected through their public runtime markers, not an assumed plugin directory path. Each provider owns its block definition, visible strings, validation, and business logic. Starter Sites changes only an unchanged Composer-owned import draft.

Site-specific content models follow the same ownership boundary. A reviewed provider plugin must register each custom post type, attach each taxonomy, expose REST-visible fields, define relation storage, and declare ownership before Starter Sites captures the destination. Agent Composer records and checks that capability evidence and may import an inactive contract that refers to it, but Starter Sites does not implement duplicate relation or taxonomy abilities. Composer supplies the generic relation lookup/field write and policy-gated taxonomy search/create/assignment workflows after the Config Set is separately validated and activated.

Shared WP Suite Theme CSS is stored by WordPress under the `smartcloud-wpsuiteio-theme` Custom CSS stylesheet key. Marker-delimited owner fragments let Starter Sites replace or remove its own CSS without modifying operator CSS or another integration's fragment.