Overview/Agent hub

Agent hub

The repo-native interface for generating Cloaked screens, prototypes, and product artifacts from registry-backed design tokens, optional data inputs, synthetic examples, and reusable briefs.

Workflow

How agents should build

  1. Read the registry Use registry/ as the source of truth and generated/agent/manifest.json as the generated repo map.
  2. Treat data as optional context Use approved or user-provided data when it exists. If it does not, state assumptions and use examples/data/ only as synthetic scaffolding.
  3. Start from a kit Use the matching HTML kit in site-source/kits/ before inventing a new pattern.
  4. Use tokens Implement with generated/site/colors_and_type.css, generated from registry/tokens.css.
Contracts

Machine-readable entry points

Source of truth

Canonical files that generate repeated site, doc, agent, and token outputs.

  • registry/design-system.json
  • registry/agent.json
  • registry/tokens.css
  • registry/token-map.json
  • registry/pages.json
  • registry/components.json
  • registry/content-rules.json
  • registry/data.json

Agent outputs

Generated files consumed by AI agents and coding tools.

  • AGENTS.md
  • generated/agent/manifest.json
  • generated/agent/playbooks/build-screen.md

Interactive architecture

A clickable map of how Figma, registry sources, generated outputs, audits, Cloudflare deploys, Workers, and MCP fit together.

MCP tester

A design-site page for calling the production design MCP with manually entered Cloudflare Access credentials.

  • content/site-pages/mcp-tester.html
  • generated/site/mcp-tester.html
  • https://design.cloaked.team/mcp
  • Open MCP tester

Optional approved data

Approved personas, mock product states, and scenarios are optional context for future agent workflows. The current design-system contract must work without them; use data/ only when approved inputs exist or are explicitly supplied.

  • generated/indexes/approved-data.json
  • data/personas/index.json
  • data/README.md

Synthetic examples

Synthetic seed personas, mock datasets, and scenarios used to demonstrate the agent workflow. These are not Cloaked-approved customer or product data.

  • generated/indexes/synthetic-data.json
  • examples/data/personas/index.json
  • examples/data/mock/day30-user.json
  • examples/data/mock/exposure-monitor.day30.json
Command

Validate the hub

The repo includes checks for JSON parseability and local site links. 

npm run check