Roots Ecosystem

Overview

Use this skill to navigate Roots projects without loading the whole stack into context. Start from the smallest relevant reference, then load one task playbook only if the user is implementing or debugging real changes.

Quick Start

1. Identify the user's layer:
   • Bedrock project setup, .env, Composer, config/application.php, web/app/, mu-plugins -> read references/bedrock.md
   • Sage templates, Blade, components, composers, app/, resources/views/, Vite, editor assets -> read references/sage.md
   • Acorn booting, service providers, routes, WP-CLI, Blade rendering outside theme templates -> read references/acorn.md
   • Trellis provisioning, deploys, hooks, trellis CLI, Sage build steps during deploy -> read references/trellis.md
   • WordPress package distribution, WP Packages, roots/wordpress-full, roots/wordpress-packager, roots/wp-config, private plugin workflows, or Composer patches -> read references/packaging-and-distribution.md
   • Trellis CLI, roots/setup-trellis-cli, GitHub Actions deploys, or shared Roots support helpers -> read references/tooling-and-ci.md
   • Acorn extension packages such as mail, user roles, post types, prettify, FSE helper, llms.txt, or AI -> read references/acorn-extensions.md
   • Package-specific deep dive for a non-core Roots package -> start with the matching package index above, then load the linked package-*.md deep dive file
   • Cross-stack ownership or architecture -> read references/integration-patterns.md
   • Reusable provider/config/command/view patterns from Roots packages -> read references/acorn-package-patterns.md