Creytix
Sign in
Creytix Design LabsLive

Design Labs core workflows

Three recipes: check a token, get a component approved, and run a growth playbook.

Overview

Design Labs' job is governance around a shared system — tokens, components, and the growth playbook library that runs under the same review. Most day-to-day work is one of three things.

Steps

  1. •

    Workflow 1 — check what a token actually controls

    Open the tokens view in Design Labs and review the current color, type, and spacing tokens your routes read from before assuming a value is hardcoded somewhere.

  2. •

    Workflow 2 — get a shared component approved for reuse

    Check the component gallery for review status before building with a shared component; if it's missing or not yet reviewed, request it through Design Labs rather than forking a one-off version on your page.

  3. •

    Workflow 3 — run a growth or AEO playbook

    Open Growth & AEO playbooks, pick one for your goal (organic ranking, answer-engine visibility, or both), run it against your live workspace manifest, and check llms.txt / cornerstone sync status afterward.

Capabilities

  • Single source of truth for tokens — every shipped route reads from the same set, not a per-page copy.
  • Governance-gated component reuse — nothing fleet-wide ships without a Design Labs pass.
  • Workspace-aware growth playbooks that act on your actual manifest.

Limits & honest scope

  • Changing a tenant's palette today is a token-source change reviewed through Design Labs, not yet a self-serve in-studio toggle — see Tokens & brand switcher.
  • The component gallery's browsable index is still filling in; discovering a component sometimes still means asking the team directly.
  • No growth playbook can promise a ranking or an AI-answer placement — treat the library as structured guidance and automation, not a guarantee.

Related