figura-cli 0.7.0 → 0.8.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "figura-cli",
-  "version": "0.7.0",
+  "version": "0.8.1",
   "description": "Command-line client for the Figura visualization SaaS",
   "license": "MIT",
   "type": "module",

package/skills/figura-fig/SKILL.md

@@ -74,7 +74,8 @@ keeping the brand tokens and overall structure stable.
 bunx figura-cli brand --json
 ```
 
-This returns `{ name, appDescription, tokensBlock, isCustom }`.
+This returns `{ name, appDescription, tokensBlock, forbidden, surfaces, isCustom }`
+(`forbidden` is a string, `surfaces` is a string[]).
 
 - If **`isCustom: true`** — use the returned `tokensBlock` as the ground-truth design
   system (palette, type, spacing, icon language) and render for `name` / `appDescription`.
@@ -83,6 +84,17 @@ This returns `{ name, appDescription, tokensBlock, isCustom }`.
   `reference/brand-tokens.md` (next to this file). It is a clean, brand-neutral baseline —
   understated and professional, NOT any specific company's look.
 
+**Honor the team's guardrails and surfaces** (they complete the brand the same way the
+engine's own generator does):
+
+- **`forbidden`** (when non-empty) — treat it as **HARD BRAND GUARDRAILS — never do these**.
+  Whatever it lists, never violate it in the generated HTML. These override any default
+  styling instinct; if a guardrail conflicts with the request, keep the guardrail.
+- **`surfaces`** (when non-empty) — the product's known surface/IA list (e.g.
+  `feed, settings, onboarding`). Use it to ground the fig in the product's real structure
+  instead of inventing an unrelated information architecture; prefer the surface that matches
+  the requested screen/area.
+
 **Pick the platform** from the request:
 
 - **`mobile`** (default) — an iPhone-framed app screen.