Menu
Deploy patterns and test with CLI
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Review a changeset for the Common Fabric repo — the local branch diff vs main, or a GitHub PR. Flags correctness and regression bugs loudly, checks that runtime-semantics changes stay coherent across docs/comments/examples, catches duplicated core machinery (hashing, serialization, cloning, identity) and code fighting the transformer/reactive model, and scrutinizes whether the tests guard the right principles. Report-first; offers to post a self-signed PR review. Use when asked to review code, review a PR, review the current branch or diff, or self-review before pushing. Invoke as /cf-review or /cf-review <PR#>.
Agent-specific interaction patterns for working with FUSE-mounted spaces. Use when deploying patterns via FUSE, working with Activity Logs, Annotations, or coordinating agent workflows that read/write pieces through the filesystem. Triggers include "deploy a pattern", "log an event", "create annotation", "agent workflow", or managing piece lifecycle via FUSE.
Critic agent that reviews pattern code for violations of documented rules, gotchas, and anti-patterns. Produces categorized checklist output with [PASS]/[FAIL]/[WARN] for each rule.
Guide for developing Common Fabric patterns (TypeScript modules that define reactive data transformations with UI). Use this skill when creating patterns, modifying existing patterns, or working with the pattern framework. Triggers include requests like "build a pattern", "fix this pattern error", "deploy this piece", or questions about handlers and reactive patterns.
Build Common Fabric patterns and sub-patterns
Guide for using the cf (Common Fabric) CLI to interact with pieces, patterns, and the Common Fabric. Use this skill when deploying patterns, managing pieces, linking data between pieces, or debugging pattern execution. Triggers include requests to "deploy this pattern", "call a handler", "link these pieces", "get data from piece", or "test this pattern locally".
| name | pattern-deploy |
| description | Deploy patterns and test with CLI |
| user-invocable | false |
Use the cf skill, or read skills/cf/SKILL.md, for comprehensive CLI
documentation. Use the command shapes from its Quick Command Reference rather
than guessing flags; this skill only covers the deploy workflow and exit
criteria.
skills/cf/SKILL.md — the Environment Setup section (CF_API_URL,
CF_IDENTITY, identity key creation) is the prerequisite for every command
belowdocs/development/LOCAL_DEV_SERVERS.md - Local dev setupdocs/common/workflows/development.md - Workflow commandsls -la ./cf.key 2>/dev/null || ls -la *.key 2>/dev/null || find . -name "*.key" -maxdepth 2 2>/dev/null
If no key exists, create one per the cf skill
(deno run -A packages/cli/mod.ts id new > cf.key for a unique key — note the
cf skill's warning: never redirect deno task cf output into a key file, the
wrapper pollutes it with ANSI preamble). Never overwrite an existing key file —
identity-scoped data (PerUser state, favorites) becomes invisible under a new
identity.
With CF_API_URL and CF_IDENTITY exported (see the cf skill), you can drop
--api-url/--identity; --space is always required.
Check syntax without deploying:
deno task cf check pattern.tsx --no-run
Deploy new pattern (first time only):
deno task cf piece new packages/patterns/[name]/main.tsx --identity cf.key --api-url $CF_API_URL --space <space>
# Output: Created piece bafyreia... <- SAVE this piece ID
Update deployed pattern (all subsequent iterations):
deno task cf piece setsrc packages/patterns/[name]/main.tsx --piece <ID> --identity cf.key --api-url $CF_API_URL --space <space>
--piece is required for setsrc — never "update" by re-running piece new,
which creates a duplicate piece.
Inspect piece state:
deno task cf piece inspect --piece <ID> --identity cf.key --api-url $CF_API_URL --space <space>
Test handler via CLI:
deno task cf piece call handlerName --piece PIECE_ID
deno task cf piece step --piece PIECE_ID # Required! Triggers recomputation
deno task cf piece inspect --piece PIECE_ID # Now shows updated state
Important: Always run piece step after piece call or piece set.
Without it, computed values remain stale and inspect/get return old data.
piece new or setsrc errors, re-run deno task cf check locally first.CF_API_URL is reachable (see the cf skill's troubleshooting table).new twice, remove the duplicate with
deno task cf piece rm --piece <ID> ... before continuing.new to "fix" a failed setsrc.deno task cf --help
deno task cf piece --help