Skills Reference

Canonical creator workflow triggers, psychology-driven design skills, and installable support surfaces.

Creator Workflow

1. $brief - capture the request, goals, constraints, audience, genre, and outcome.
2. $blueprint - generate structured design and planning artifacts.
3. $forge - generate concrete creator-facing deliverables and system specs.
4. $crew - orchestrate multi-role creator workflows.
5. $autoforge - run an end-to-end creator workflow with minimal supervision.

Roblox Pre-Action Gate

• Before Roblox code generation, RCS must gather references, synthesize understanding, standardize terms, and design the modular file tree first.
• PRE_ACTION_COMPLETE must remain false until the pre-action artifact is complete.
• Use docs/reference/roblox-pre-action-protocol.md and templates/roblox/pre-action-plan.md as the required planning surfaces.

Psychology Design

• $brief:audience - identify target fantasy, habits, desire language, session length, and return motive.
• $brief:motivation - rank progression, status, FOMO, mastery, and community by genre fit and risk.
• $blueprint:psych - generate the player psychology blueprint from desire backward.
• $blueprint:loop - define trigger → action → reward → repeat across session, daily, weekly, and comeback loops.
• $blueprint:retention - define D1/D7/D30 assumptions, cadence, and comeback hooks.
• $blueprint:social - define how the experience becomes a social machine.
• $forge:reward-loop - generate trigger/action/reward/escalation/reset/fail-state specs.
• $forge:daily-loop - generate daily return motivators and bounded streak/event logic.
• $forge:event-loop - generate limited-time event structures with urgency and re-entry logic.
• $forge:progression - generate XP, level, multiplier, prestige, rebirth, and unlock ladders.
• $forge:status - generate prestige and flex systems with visible milestones.
• $forge:fomo - generate urgency mechanics with fairness notes and anti-frustration guardrails.
• $forge:mastery - generate learning, optimization, discovery, and skill-expression systems.
• $forge:community - generate systems that make playing with others sticky.

Canonical Framework

• Design from player desire backward.
• Use the five drivers: progression, status, FOMO, mastery, community.
• Map each driver through mechanic patterns, UI feedback, economy impact, retention impact, monetization fit, risk notes, and Roblox-fit notes.

Advanced Execution Surfaces

These are advanced operator surfaces. They are useful for diagnostics, parallel coordination, or focused verification, but they are not the primary creator workflow.

• $team - coordinated parallel execution when a creator plan needs durable staffing.
• $forge - persistent implementation and verification loop.
• $autopilot - autonomous execution runtime for advanced operator use.
• $ultrawork - max-parallel execution mode.
• $visual-verdict - structured visual QA loop for screenshot/reference matching
• $ecomode - token-efficient model routing
• $ultraqa - test/verify/fix loop

Planning & Clarification

• $brief - canonical briefing surface
• $blueprint - canonical planning surface
• $plan - supporting strategic planning when you are not using the canonical creator path
• $deep-interview - ambiguity-gated requirements clarification before implementation.

Agent Shortcuts

• $analyze
• $deepsearch
• $tdd
• $build-fix
• $code-review
• $security-review
• $visual-forge (advanced visual-delivery runtime)
• $visual-forge
• $git-master
• $review

Utilities

• $cancel, $doctor, $help, $note, $trace
• $skill
• $hud, $rcs-setup, $configure-notifications
• $forge-init (legacy helper)

Usage Examples

$brief "farming simulator for mobile-first Roblox sessions"
$brief:motivation "rank the retention drivers"
$blueprint:psych "design from player desire backward"
$blueprint:loop "define session, daily, weekly, and comeback loops"
$forge:progression "write the progression ladder"
$forge:community "write the social retention systems"
$code-review "review current branch"
$doctor

Visual Verdict Guidance

• Use for visual tasks with reference image(s) + generated screenshot.
• Pass threshold target: 90+.
• Use pixel diff / pixelmatch overlays only as secondary debugging support.