@jstn-sdk/rcs 0.1.7 → 0.1.8

package/plugins/roblox-ai-os-creator-skills/skills/skill/SKILL.md

@@ -11,6 +11,7 @@ artifact-type: "skill"
 # Skill Management CLI
 
 Meta-skill for managing Roblox Creator Skills workflow skills via CLI-like commands.
+Default examples should stay grounded in Roblox creator workflows rather than generic software helpers.
 
 ## Subcommands
 
@@ -28,13 +29,13 @@ Show all local skills organized by scope.
 USER SKILLS (~/.codex/skills/):
 | Name              | Triggers           | Quality | Usage | Scope |
 |-------------------|--------------------|---------|-------|-------|
-| error-handler     | fix, error         | 95%     | 42    | user  |
-| remote-audit      | remote, payload    | 88%     | 23    | user  |
+| remote-audit      | remote, payload    | 95%     | 42    | user  |
+| gui-state-check   | gui, hud, state    | 88%     | 23    | user  |
 
 PROJECT SKILLS (.codex/skills/):
 | Name              | Triggers           | Quality | Usage | Scope   |
 |-------------------|--------------------|---------|-------|---------|
-| test-runner       | test, run          | 92%     | 15    | project |
+| datastore-guard   | datastore, profile | 92%     | 15    | project |
 ```
 
 **Fallback:** If quality/usage stats not available, show "N/A"
@@ -101,16 +102,16 @@ argument-hint: "<args>"
 
 **Example:**
 ```
-User: /skill add custom-logger
-Assistant: Creating new skill 'custom-logger'...
+User: /skill add remote-audit-helper
+Assistant: Creating new skill 'remote-audit-helper'...
 
-Description: Enhanced logging with structured output
-Triggers (comma-separated): log, logger, logging
-Argument hint (optional): <level> [message]
+Description: Audit RemoteEvent payload validation and server authority checks
+Triggers (comma-separated): remote, payload, validation
+Argument hint (optional): <remote-name> [surface]
 Scope (user/project): user
 
-✓ Created skill at ~/.codex/skills/custom-logger/SKILL.md
-→ Edit with: /skill edit custom-logger
+✓ Created skill at ~/.codex/skills/remote-audit-helper/SKILL.md
+→ Edit with: /skill edit remote-audit-helper
 ```
 
 ---
@@ -136,15 +137,15 @@ Remove a skill by name.
 
 **Example:**
 ```
-User: /skill remove old-logger
-Assistant: Found skill 'old-logger' in user scope:
-  Description: Legacy logging utility
+User: /skill remove old-trade-audit
+Assistant: Found skill 'old-trade-audit' in user scope:
+  Description: Legacy trading remote audit helper
   Scope: user (~/.codex/skills/)
 
-Delete 'old-logger' skill? (yes/no)
+Delete 'old-trade-audit' skill? (yes/no)
 
 User: yes
-Assistant: ✓ Removed skill 'old-logger' from user scope
+Assistant: ✓ Removed skill 'old-trade-audit' from user scope
 ```
 
 ---
@@ -158,10 +159,10 @@ Edit an existing skill interactively.
 2. **Read current content** via Read tool
 3. **Display current values:**
    ```
-   Current skill 'custom-logger':
-   - Description: Enhanced logging with structured output
-   - Triggers: log, logger, logging
-   - Argument hint: <level> [message]
+   Current skill 'remote-audit-helper':
+   - Description: Audit RemoteEvent payload validation and server authority checks
+   - Triggers: remote, payload, validation
+   - Argument hint: <remote-name> [surface]
    - Scope: user
    ```
 4. **Ask what to change:**
@@ -180,19 +181,19 @@ Edit an existing skill interactively.
 
 **Example:**
 ```
-User: /skill edit custom-logger
-Assistant: Current skill 'custom-logger':
-  - Description: Enhanced logging with structured output
-  - Triggers: log, logger, logging
-  - Argument hint: <level> [message]
+User: /skill edit remote-audit-helper
+Assistant: Current skill 'remote-audit-helper':
+  - Description: Audit RemoteEvent payload validation and server authority checks
+  - Triggers: remote, payload, validation
+  - Argument hint: <remote-name> [surface]
 
 What would you like to edit? (description/triggers/argument-hint/content/rename/cancel)
 
 User: triggers
-Assistant: Current triggers: log, logger, logging
-New triggers (comma-separated): log, logger, logging, trace
+Assistant: Current triggers: remote, payload, validation
+New triggers (comma-separated): remote, payload, validation, server-authority
 
-✓ Updated triggers for 'custom-logger'
+✓ Updated triggers for 'remote-audit-helper'
 ```
 
 ---
@@ -211,19 +212,19 @@ Search skills by content, triggers, name, or description.
 3. **Display matches** with context:
 
 ```
-Found 3 skills matching "typescript error":
+Found 3 skills matching "remote payload":
 
-1. typescript-fixer (user)
-   Description: Fix common TypeScript errors
-   Match: "typescript error handling patterns"
+1. remote-audit (user)
+   Description: Review RemoteEvent / RemoteFunction payload contracts
+   Match: "remote payload validation"
 
-2. error-handler (user)
-   Description: Generic error handling utilities
-   Match: "Supports TypeScript and JavaScript errors"
+2. trade-safety (user)
+   Description: Trading safety checks for inventory mutation
+   Match: "payload ownership and duplicate-request validation"
 
-3. lint-fix (project)
-   Description: Auto-fix linting errors
-   Match: "TypeScript ESLint error resolution"
+3. datastore-guard (project)
+   Description: Profile and save-path safety helpers
+   Match: "remote requests that mutate persistent state"
 ```
 
 **Ranking:** Prioritize matches in name/triggers over content matches
@@ -837,6 +838,3 @@ What would you like to do?
 - `/skill stats` - Show usage statistics across all skills
 - `/skill validate` - Check all skills for format errors
 - `/skill template <type>` - Create from predefined templates
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/plugins/roblox-ai-os-creator-skills/skills/team/SKILL.md

@@ -511,6 +511,3 @@ Two cleanup paths exist and must not be confused:
 **Good:** The user changes only the output shape or downstream delivery step (for example `make a PR`). Preserve earlier non-conflicting workflow constraints and apply the update locally.
 
 **Bad:** The user says `continue`, and the workflow restarts discovery or stops before the missing verification/evidence is gathered.
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/plugins/roblox-ai-os-creator-skills/skills/trace/SKILL.md

@@ -35,6 +35,3 @@ Present the timeline first, then the summary. Highlight:
 - **Mode transitions** (how execution modes changed)
 - **Bottlenecks** (slow tools or agents)
 - **Flow patterns** (keyword -> skill -> agent chains)
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/plugins/roblox-ai-os-creator-skills/skills/ultraqa/SKILL.md

@@ -9,9 +9,9 @@ artifact-type: "skill"
 
 # UltraQA Skill
 
-[ULTRAQA ACTIVATED - AUTONOMOUS QA CYCLING]
+Use `$ultraqa` when you need a strict QA loop for Roblox Studio, Luau, creator-runtime, or plugin changes and the first verification pass is not enough.
 
-## Overview
+This skill is strongest when the work needs repeatable test -> diagnose -> fix -> retest cycling until the changed behavior is actually proven.
 
 ## GPT-5.5 Guidance Alignment
 
@@ -30,7 +30,7 @@ Parse the goal from arguments. Supported formats:
 | `/ultraqa --tests` | tests | All test suites pass |
 | `/ultraqa --build` | build | Build succeeds with exit 0 |
 | `/ultraqa --lint` | lint | No lint errors |
-| `/ultraqa --typecheck` | typecheck | No TypeScript errors |
+| `/ultraqa --typecheck` | typecheck | No TypeScript errors in the RCS runtime/tooling layer |
 | `/ultraqa --custom "pattern"` | custom | Custom success pattern in output |
 
 If no structured goal provided, interpret the argument as a custom goal.
@@ -49,7 +49,7 @@ If no structured goal provided, interpret the argument as a custom goal.
      ```
      delegate(role="test-engineer", tier="STANDARD", task="TEST:
      Goal: [describe what to verify]
-     Service: [how to start]
+     Surface: [Roblox Studio, Luau module, plugin widget, or RCS runtime]
      Test cases: [specific scenarios to verify]")
      ```
 
@@ -89,11 +89,11 @@ If no structured goal provided, interpret the argument as a custom goal.
 Output progress each cycle:
 ```
 [ULTRAQA Cycle 1/5] Running tests...
-[ULTRAQA Cycle 1/5] FAILED - 3 tests failing
+[ULTRAQA Cycle 1/5] FAILED - 3 checks failing
 [ULTRAQA Cycle 1/5] Architect diagnosing...
-[ULTRAQA Cycle 1/5] Fixing: auth.test.ts - missing mock
+[ULTRAQA Cycle 1/5] Fixing: TradeRequest.server.luau validation path or matching runtime harness
 [ULTRAQA Cycle 2/5] Running tests...
-[ULTRAQA Cycle 2/5] PASSED - All 47 tests pass
+[ULTRAQA Cycle 2/5] PASSED - verification target is green
 [ULTRAQA COMPLETE] Goal met after 2 cycles
 ```
 
@@ -145,6 +145,3 @@ Use MCP state cleanup rather than deleting files directly.
 ---
 
 Begin ULTRAQA cycling now. Parse the goal and start cycle 1.
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/plugins/roblox-ai-os-creator-skills/skills/ultrawork/SKILL.md

@@ -177,6 +177,3 @@ ecomode (token efficiency)
 
 Ultrawork is the parallelism and execution-discipline layer. Forge adds persistence, architect verification, deslop, and retry-until-done behavior. Autoforge adds the broader autonomous lifecycle pipeline. Ecomode adjusts ultrawork's model routing to favor cheaper models.
 </Advanced>
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/plugins/roblox-ai-os-creator-skills/skills/visual-forge/SKILL.md

@@ -9,7 +9,7 @@ artifact-type: "skill"
 
 # Visual Forge Skill
 
-Legacy compatibility surface. Public creator language should prefer **Visual Forge** concepts and `$forge` as the persistent implementation owner.
+Visual Forge is the visual-delivery lane for Roblox creator UI, HUD, and plugin work. `$forge` remains the persistent implementation owner when the work turns into a code-bearing completion loop.
 
 Use this skill when the user wants Codex to build or restyle Roblox creator UI through a compatibility visual-delivery loop: an approved generated reference, static reference, or captured inspiration baseline becomes the target, Forge implements, and Visual Verdict drives measured iteration rather than subjective description alone.
 
@@ -157,6 +157,3 @@ Do not make major design pivots unless explicitly requested."
 ```
 
 Task: {{ARGUMENTS}}
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/plugins/roblox-ai-os-creator-skills/skills/visual-verdict/SKILL.md

@@ -78,6 +78,3 @@ When mismatch diagnosis is hard:
 }
 ```
 </Example>
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/plugins/roblox-ai-os-creator-skills/skills/wiki/SKILL.md

@@ -59,6 +59,3 @@ At session end, discoveries can be captured as `session-log-*` pages. Configure
 ## Hard Constraints
 - No vector embeddings — query uses keyword + tag matching only
 - Wiki files remain local project state under `.rcs/wiki/`
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/plugins/roblox-ai-os-creator-skills/skills/worker/SKILL.md

@@ -9,7 +9,7 @@ artifact-type: "skill"
 
 # Worker Skill
 
-> Legacy compatibility surface. Public creator language should prefer `crew` / coordinated execution terminology. This file remains the internal worker-runtime protocol surface for tmux-managed crew panes.
+> Internal worker-runtime surface. Active creator language should prefer `crew` / coordinated execution terminology. This file exists so tmux-managed crew panes follow one strict protocol.
 
 This skill is for a Codex session that was started as a coordinated crew worker pane under `rcs team` / `$team`.
 
@@ -110,6 +110,3 @@ Crew worker sessions should treat team state + CLI interop as the source of trut
 ## Shutdown
 
 If the crew lead sends a shutdown request, follow the shutdown inbox instructions exactly, write your shutdown ack file, then exit the Codex session.
-surface-class: "internal"
-domain: "creator-runtime"
-audience: "internal"

package/skills/ai-slop-cleaner/SKILL.md

@@ -141,6 +141,3 @@ Remaining Risks:
 **Bad:** Keep a `fallback if it fails` branch that silently defaults after a swallowed error instead of fixing the root cause or making failure explicit.
 
 **Good:** A version-specific compatibility shim is narrow, documented, preserves error evidence, has primary and fallback regression tests, and is reported as a grounded compatibility/fail-safe fallback.
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/analyze/SKILL.md

@@ -9,7 +9,7 @@ artifact-type: "skill"
 
 # Analyze — Read-Only Deep Analysis
 
-Use this skill to answer the user’s question through **read-only repository analysis**. The goal is to explain what the codebase most likely says about the question, not to drift into implementation, debugging theater, or generic fix planning.
+Use this skill to answer the user’s question through **read-only repository analysis**. In this repo, that usually means Roblox Studio, Luau, plugin, creator-runtime, or workflow evidence, not generic software diagnosis detached from the actual creator surface.
 
 ## Use `$analyze` when
 
@@ -20,11 +20,11 @@ Use this skill to answer the user’s question through **read-only repository an
 - the user wants to understand architecture, behavior, causality, impact, or tradeoffs before changing anything
 
 Examples:
-- why a workflow behaves a certain way
-- how a feature is wired across modules
-- what likely explains a failure, regression, or mismatch
-- what would be impacted by changing a dependency or contract
-- which interpretation of the current codebase is best supported
+- why a remote validation path behaves a certain way
+- how a creator HUD or plugin surface is wired across modules
+- what likely explains a trade, datastore, or workflow regression
+- what would be impacted by changing a provider contract, remote schema, or creator-runtime boundary
+- which interpretation of the current Roblox-facing codebase is best supported
 
 ## Do not use `$analyze` when
 
@@ -150,6 +150,3 @@ A good analyze response is:
 - concise for simple cases, broader only when the question truly needs it
 
 Task: {{ARGUMENTS}}
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/ask-claude/SKILL.md

@@ -63,6 +63,3 @@ Minimum artifact sections:
 5. Action items / next steps
 
 Task: {{ARGUMENTS}}
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/ask-gemini/SKILL.md

@@ -63,6 +63,3 @@ Minimum artifact sections:
 5. Action items / next steps
 
 Task: {{ARGUMENTS}}
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/autoforge/SKILL.md

@@ -20,6 +20,3 @@ For Roblox implementation tasks, `$autoforge` must still obey the mandatory gate
 5. only then begin execution
 
 `PRE_ACTION_COMPLETE` must become `true` before any Roblox code generation.
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/autopilot/SKILL.md

@@ -165,6 +165,3 @@ Autopilot invents independent "Expansion", "QA", and "Validation" phases and tre
 Why bad: this bypasses the strict `$blueprint -> $forge -> $code-review` contract.
 </Bad>
 </Examples>
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/autoresearch/SKILL.md

@@ -70,6 +70,3 @@ The completion artifact must include both an architect approval verdict and an o
 - No direct CLI launch.
 - No tmux split-pane launch.
 - No noop-count completion gate.
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/blueprint/SKILL.md

@@ -235,6 +235,3 @@ Need:
 - anti-duplication rules for queue join/leave
 - verification path for queue sync and teleport readiness"
 ```
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/blueprint-loop/SKILL.md

@@ -21,6 +21,3 @@ Return a filled **Dopamine Loop Map** using `templates/psychology/dopamine-loop-
 - daily loop
 - weekly loop
 - comeback loop
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/blueprint-psych/SKILL.md

@@ -23,6 +23,3 @@ Return:
 - fairness risks.
 
 Use `docs/reference/player-psychology-framework.md` as the framework source.
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/blueprint-retention/SKILL.md

@@ -17,6 +17,3 @@ Return:
 - a filled **Retention Design Sheet** from `templates/psychology/retention-design-sheet.md`
 - a compact **Weekly LiveOps Plan**
 - comeback hooks and burnout guardrails
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/blueprint-social/SKILL.md

@@ -17,6 +17,3 @@ Return a **Social Retention Spec** using `templates/psychology/social-mechanic-s
 - parties / guilds / trading / co-op / invites / presence systems as appropriate
 - why solo-only design would underperform
 - anti-spam guardrails
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/brief/SKILL.md

@@ -29,6 +29,3 @@ Use the protocol in:
 Follow with:
 - `$brief:audience`
 - `$brief:motivation`
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/brief-audience/SKILL.md

@@ -21,6 +21,3 @@ Return a filled **Player Motivation Profile** using `templates/psychology/player
 - Name the primary fantasy before talking about features.
 - Call out likely session length and why the player comes back.
 - End with 3 audience risks or mismatches.
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/brief-motivation/SKILL.md

@@ -24,6 +24,3 @@ Return a **Motivation Matrix** with:
 - Explain the dominant driver in one sentence.
 - Separate “good urgency” from manipulative pressure.
 - Prefer community when social play is naturally supported.
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/build-fix/SKILL.md

@@ -10,6 +10,7 @@ artifact-type: "skill"
 # Build Fix Skill
 
 Fix build and compilation errors quickly with minimal code changes. Get the build green without refactoring.
+For this repo, that usually means TypeScript/Rust/toolchain fixes around the RCS runtime or Roblox workspace scaffolding, not generic product rewrites.
 
 ## When to Use
 
@@ -144,9 +145,6 @@ Keeps trying until build passes, even if it takes multiple iterations.
 
 **With Team:**
 ```
-/team "debug build failures and fix type errors"
+/team "debug build failures and fix Roblox workspace or RCS runtime type errors"
 ```
 Uses: explore → build-fixer → verifier workflow.
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/cancel/SKILL.md

@@ -401,6 +401,3 @@ rm -rf .rcs/state/team/                  # All team state
 # Kill all rcs-team-* tmux sessions
 tmux list-sessions -F '#{session_name}' 2>/dev/null | grep '^rcs-team-' | while read s; do tmux kill-session -t "$s" 2>/dev/null; done
 ```
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/code-review/SKILL.md

@@ -9,7 +9,7 @@ artifact-type: "skill"
 
 # Code Review Skill
 
-Conduct a thorough code review for quality, security, and maintainability with severity-rated feedback.
+Conduct a thorough code review for Roblox Studio, Luau, creator-runtime, plugin, and workflow changes with severity-rated feedback.
 
 ## When to Use
 
@@ -38,11 +38,11 @@ Delegates to the `code-reviewer` and `architect` agents in parallel for a two-la
    - Both lanes run in parallel and produce distinct outputs before final synthesis
 
 3. **Review Categories**
-   - **Security** - Hardcoded secrets, injection risks, XSS, CSRF
-   - **Code Quality** - Function size, complexity, nesting depth
-   - **Performance** - Algorithm efficiency, N+1 queries, caching
-   - **Best Practices** - Naming, documentation, error handling
-   - **Maintainability** - Duplication, coupling, testability
+   - **Roblox Security** - server authority, remote validation, replicated secrets/data exposure, DataStore/economy safety
+   - **Code Quality** - function size, complexity, nesting depth, cross-module clarity
+   - **Performance** - replication churn, avoidable UI rebuilds, hot-path inefficiency, heavy runtime loops
+   - **Best Practices** - naming, documentation, error handling, service placement
+   - **Maintainability** - duplication, coupling, testability, workflow boundary clarity
 
 4. **Severity Rating**
    - **CRITICAL** - Security vulnerability (must fix before merge)
@@ -291,6 +291,3 @@ Parallel code review across multiple files.
 - **Address CRITICAL/HIGH first** - Fix security and bugs immediately
 - **Consider context** - Some "issues" may be intentional trade-offs
 - **Learn from reviews** - Use feedback to improve coding practices
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/configure-notifications/SKILL.md

@@ -289,6 +289,3 @@ Show:
 - Whether explicit `notifications.openclaw` exists (and therefore overrides aliases)
 - Verbosity + idle cooldown + reply listener state
 - Config path (`~/.codex/.rcs-config.json`)
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/crew/SKILL.md

@@ -12,6 +12,3 @@ artifact-type: "skill"
 Use `$crew` when the work needs coordinated creator lanes such as systems design, economy review, social design, and implementation planning in parallel.
 
 For Roblox tasks, the crew should not fan out implementation until the shared pre-action artifact exists and `PRE_ACTION_COMPLETE` is `true`.
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/deep-interview/SKILL.md

@@ -470,6 +470,3 @@ deep-interview -> blueprint -> autopilot
 </Advanced>
 
 Task: {{ARGUMENTS}}
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/deepsearch/SKILL.md

@@ -40,6 +40,3 @@ Perform thorough search of the codebase for the specified query, pattern, or con
 - **Key Insights** (patterns, conventions, gotchas)
 
 Focus on being comprehensive but concise. Cite file paths and line numbers.
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/doctor/SKILL.md

@@ -241,6 +241,3 @@ rm -rf ~/.agents/skills
 
 After applying fixes, inform user:
 > Fixes applied. **Restart Codex CLI** for changes to take effect.
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/ecomode/SKILL.md

@@ -116,6 +116,3 @@ Use `rcs_state` MCP tools for ecomode lifecycle state.
   `state_write({mode: "ecomode", active: false})`
 - **On cancellation/cleanup**:
   run `$cancel` (which should call `state_clear(mode="ecomode")`)
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/forge/SKILL.md

@@ -188,6 +188,3 @@ $forge "Implement the approved trading system:
 - StarterGui trade UI only mirrors server-confirmed state
 - verify duplicate acceptance cannot double-grant items"
 ```
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/forge-community/SKILL.md

@@ -18,6 +18,3 @@ Generate a **Community Stickiness Spec**.
 - group progression or co-op loops
 - social presence surfaces
 - anti-spam and anti-abuse guardrails
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/forge-daily-loop/SKILL.md

@@ -17,6 +17,3 @@ Generate a **Daily Return Loop Spec** for short-return Roblox play.
 - rotating goals or offers
 - event hooks
 - fairness and anti-burnout guardrails
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/forge-event-loop/SKILL.md

@@ -17,6 +17,3 @@ Generate an **Event / FOMO Plan** using `templates/psychology/event-fomo-design-
 - include re-entry logic
 - include rerun policy
 - call out frustration risks
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/forge-fomo/SKILL.md

@@ -18,6 +18,3 @@ Generate a **Fair Urgency Review** for limited-time mechanics.
 - fairness guardrails
 - comeback or rerun path
 - anti-frustration notes
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/forge-init/SKILL.md

@@ -48,6 +48,3 @@ After creating the PRD, start execution with:
 ```
 
 Forge will iterate until all acceptance criteria in the PRD are met and architect-verified.
-surface-class: "historical"
-domain: "creator-runtime"
-audience: "internal"

package/skills/forge-mastery/SKILL.md

@@ -18,6 +18,3 @@ Generate a **Mastery Depth Spec**.
 - discovery moments
 - skill-expression rewards
 - feedback surfaces that make mastery legible
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/forge-progression/SKILL.md

@@ -18,6 +18,3 @@ Generate a **Progression Ladder**.
 - unlock cadence
 - multiplier / prestige / rebirth logic where fit
 - clarity notes for first-session payoff
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/forge-reward-loop/SKILL.md

@@ -21,6 +21,3 @@ Generate a concrete **Reward Loop Spec**.
 - fail state
 - recovery path
 - Roblox-fit note
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/forge-status/SKILL.md

@@ -19,6 +19,3 @@ Generate a **Prestige / Status Spec**.
 - visible milestones
 - pets, profile badges, or showcases where fit
 - visibility and fairness risks
-surface-class: "canonical"
-domain: "creator-runtime"
-audience: "creator"

package/skills/git-master/SKILL.md

@@ -31,6 +31,3 @@ delegate(role="git-master", tier="STANDARD", task="{{ARGUMENTS}}")
 - Style detection from repo history
 
 Task: {{ARGUMENTS}}
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"

package/skills/help/SKILL.md

@@ -77,6 +77,3 @@ Use:
 - `docs/reference/roblox-pre-action-protocol.md`
 - `templates/psychology/`
 - `templates/roblox/`
-surface-class: "operator"
-domain: "creator-runtime"
-audience: "operator"