site-spinup

Create a brand site directory with tokens.css and config.json in a 2-tier multi-site framework.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/aramark-destinations/aramark-mb --skill site-spinup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-spinup
Source: https://github.com/aramark-destinations/aramark-mb/tree/main/.agents/skills/eds/site-spinup
Command: npx skills add https://github.com/aramark-destinations/aramark-mb --skill site-spinup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rapidly scaffold a new brand site using a 2-tier multi-site framework, enabling teams to spin up property sites quickly without duplicating core infrastructure.

Core Features & Use Cases

  • Tier 1: Brand-specific blocks under brands/{brand}/blocks and Tier 2: shared blocks under /blocks for rapid variation.
  • Design tokens centralize branding via brands/{brand}/tokens.css and optional brand overrides in config.json for analytics and integrations.
  • Use Case: Launching a new property site or seasonal brand variant with consistent design and predictable deployment.

Quick Start

Create a new brands/{brand} directory, add tokens.css for design tokens, and optionally configure blocks and a config.json to tailor the brand.

Frequently Asked Questions about site-spinup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new brand site using a multi-site framework?

You can rapidly launch a new brand site by creating a brands/{brand} directory, adding a tokens.css file for centralized design tokens, and optionally configuring a config.json for analytics and integrations within the multi-site framework.

How does a 2-tier multi-site framework organize shared and brand-specific blocks?

A 2-tier multi-site framework organizes blocks by placing brand-specific variations under brands/{brand}/blocks while keeping shared root blocks under /blocks, enabling rapid site creation without duplicating core infrastructure.

What is the best way to manage design tokens for multiple brand sites?

The best way to manage design tokens for multiple brand sites is by centralizing branding variables in a brands/{brand}/tokens.css file, allowing each property site to apply distinct styling while maintaining predictable deployment.

Can I use config.json to add analytics and integrations to a brand site?

Yes, you can use an optional config.json file to apply brand overrides for analytics and integrations when launching a new property site or seasonal brand variant.

Does launching a new property site require duplicating core infrastructure?

No, launching a new property site does not require duplicating core infrastructure because the multi-site framework leverages shared root blocks alongside brand-specific blocks and tokens to streamline deployment.