What this prompt does
This prompt casts the model as a WordPress multisite architect planning and configuring a network for a [organization_type] running [site_count] sites. It moves through six stages: architecture planning, the wp-config and rewrite setup, theme and plugin strategy, user management, shared resources, and performance plus maintenance.
The first decision it forces — subdirectory versus subdomain — shapes everything downstream, so the prompt ties that choice to the [organization_type] rather than picking arbitrarily. It then sets the multisite constants, wires domain mapping through [domain_mapping_plugin], network-activates [network_plugins], defines [role_count] roles, and caps each site at [storage_limit]. Shared media via [media_solution] and an object cache on [object_cache] are the operational details that keep a [site_count]-site network from sprawling.
The prompt's strength is that it treats the network as an ongoing system, not a one-time install. The role hierarchy spans super admin down to single-site editor, with single sign-on via [sso_method] so users move between sites without re-authenticating. A plugin whitelist stops site admins from installing unapproved code, content syndication pushes shared pages out from the main site, and a health dashboard surfaces per-site storage, plugin update status, and performance across the whole network. These are the controls that decide whether [site_count] sites stay maintainable or become a liability.
When to use it
- An organization needs many related sites under one WordPress install.
- You must decide between subdirectory and subdomain structure for
[site_count]sites. - Different site groups need different branding from one parent theme.
- You want centralized roles and single sign-on across the network via
[sso_method]. - Assets uploaded on one site must be reachable network-wide.
- You need per-site storage caps and network-wide health monitoring.
Example output
Expect an architecture write-up plus configuration steps: a topology recommendation (subdirectory vs subdomain) for [web_server], the wp-config constants and rewrite rules, a theme plan using [theme_framework] with [child_theme_count] child themes, a network-plugin list, a [role_count]-role hierarchy with SSO via [sso_method], a shared-media setup using [media_solution], and a maintenance dashboard tracking per-site storage against [storage_limit], plugin updates, and caching through [object_cache].
Pro tips
- Pick subdirectory vs subdomain based on
[organization_type]and DNS needs; switching later is painful. - Keep
[network_plugins]to genuinely network-wide tools and leave the rest for per-site activation. - Set
[storage_limit]per site early so one heavy site does not starve the others. - Use a plugin whitelist so site admins cannot install unapproved code across
[site_count]sites. - Configure
[object_cache]with site-aware keys so caches do not collide across the network. - Test
[domain_mapping_plugin]and sunrise.php on staging before pointing live domains at the network. - Keep
[child_theme_count]child themes lean; each one is another surface to maintain when the[theme_framework]parent updates. - Confirm
[web_server]rewrite rules early, since subdomain and subdirectory setups need different configuration to route correctly.
