---
name: arranque-de-proyecto
description: Bricks project kickoff — what to ask, in what order, from a blank site through design system, header, templates, and first pages.
domain: bricks
type: system
version: 1.1.0
min_lolacore_version: 2.7.0
triggers:
  keywords:
    - project kickoff
    - new bricks site
    - design system setup
    - brand palette
    - arranque
    - empezar proyecto
    - paleta de marca
    - convención de nombres
    - nueva web
    - cabecera
    - header footer
---

## Purpose

Blank-site kickoff. The designer already has brand and copy. You establish the system, then build header, templates, and pages on top of it. Existing-site orientation is the same reads without creating tokens — use playbook `bricks-anatomy` + skill `lolacore-bricks-system-architect`.

## Key concepts

Two entry modes, same apparatus.

- **Blank site:** convention → tokens → header/footer → templates → first pages → components/clone if asked.
- **Inherited site:** overview + index + reads first. Do not impose a new convention on existing classes unless asked.

Question budget: **maximum 4 questions** before the first write proposal. Combine palette + typography when they already sent a PDF or hex list. Never re-ask something in memory bootstrap facts or a saved convention.

## Rules

1. Orient — `getBricksOverview` + `getBricksOperatingGuide` (`project_bootstrap`). If coverage is incomplete, `rebuildDesignIndex` until finished.
2. Read what exists — `getGlobalVariables`, `getGlobalClasses`, `getThemeStyles`, `getTemplates`.
3. Convention — if overview has no `design_convention`: offer `detected_framework` from dry-run `setDesignConvention`. Ask naming pattern, variable policy, protected prefixes in plain language. Save and show compliance percent. Do not rename existing classes to match.
4. Brand — palette as one `setGlobalVariable` batch. Typography as `updateThemeStyle`, not duplicate variables. Spacing tokens only if they will be reused.
5. Chrome — header and footer via `createTemplate` + `setTemplateContent`. Preview `updateTemplateConditions` (entire site vs selected types) before saving.
6. First pages — paste copy → `addSection` / heading / text / image / button using site classes. `getPageStructure` if the page already has a tree.
7. Reuse — a repeated block becomes a component (`createComponentFromElement`). Twenty similar pages → `cloneStructure` with per-page substitutions, not twenty manual copies.
8. Shop — only if WooCommerce is active: `getWooBricksSurface`, then product/archive/cart templates as asked.
9. Verify — summarize what was created. Remind to refresh the front (variables and theme styles self-heal; class CSS regenerated).
10. Stop before it feels like a form. The designer decides brand; you execute.
