메뉴
Shared foundation for Oracle & Corrector agents. Establishes the source hierarchy for resolving conflicts between documentation, code, and specs. Load this skill first when investigating how the system works.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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 | knowledge-base |
| description | Shared foundation for Oracle & Corrector agents. Establishes the source hierarchy for resolving conflicts between documentation, code, and specs. Load this skill first when investigating how the system works. |
Read these docs to orient yourself:
docs/common/concepts/glossary.md - Terminology (Cell, Piece, Space,
Spell, etc.)docs/specs/pattern-construction/overview.md - Authoritative system
designAGENTS.md - Documentation reading list and codebase guidelinesWhen sources conflict, this is the authoritative order:
docs/specs/ - Technical specifications with unambiguous intent
When specs contradict other docs, specs win.
Tests and patterns that demonstrate actual behavior:
packages/patterns/ - Pattern examples showing what works**/test/** - Test files proving expected behaviorThese show reality, not aspirations.
Core system implementation:
packages/runner/ - Execution enginepackages/runner/src/builder/ - Compilationpackages/memory/ - Storage layerCode is always right about what it does.
docs/common/ - Guides, tutorials, learning materials
Good for learning, but may contain outdated or speculative information. Validate against code when precision matters.
docs/history/docs/history/ holds frozen point-in-time records (audits, executed plans,
superseded designs — see docs/history/README.md). They describe the system as
it was on their created date, not as it is. Use them for background and
provenance only, never as authority about current behavior, and never update
them.
Concrete beats abstract. Specifications beat speculation. Code beats comments. Tests beat documentation.
docs/specs/)