Resources
A resource is a non-executable asset RBA has standardized — a project skeleton, a contract template, a reference architecture, a runbook, a checklist. Resources sit one level out from skills: they aren't code or prompts, but they're the artifacts work produces (or starts from).
What lives here
- Project skeletons — Starter repos for common shapes (CMS migration, headless commerce, new microsite).
- Templates — Statement-of-work templates, technical-design-doc templates, decision-record templates.
- Reference architectures — Diagrams and documentation for canonical setups RBA has battle-tested.
- Runbooks and checklists — Operational guides for incident response, go-live, knowledge transfer.
How resources differ from skills
A skill guides you through producing something. A resource is the thing — either as a starting point you adapt, or a reference you compare against.
Many RBA skills reference resources: the Generate Project Brief skill, for example, points to a Brief Template resource that captures the standard sections. The skill provides the methodology; the resource provides the artifact format.
Bundled with plugins
Resources ship inside plugin bundles so they install alongside the skills and agents that use them. A sitecore-toolkit plugin might bundle three skills, two agents, and a reference architecture resource — the whole "Sitecore expert" package, installed in one step.