| name | freeplay-onboarding |
| description | Complete guided onboarding to Freeplay — analyzes codebase, migrates prompts, and integrates logging. Use whenever the user says 'onboard to Freeplay', 'set up Freeplay', 'get started with Freeplay', 'integrate Freeplay', or wants end-to-end setup. |
/freeplay-onboarding
Orchestrate the complete Freeplay onboarding flow with checkpoint-based progression.
This is the meta-skill that orchestrates:
/freeplay-plan - Analyze codebase/prompt-migration - Migrate prompts/record-to-freeplay - Integrate logging
Flow
Check state -> Display progress -> Execute phases (plan -> migrate -> log) with approval gate between each. Progress saved to .freeplay/ after each phase.
Workflow
Step 1: Check Existing State
Look for .freeplay/ directory and existing state files.
Reference _reference/ui-examples.md for UI formatting examples throughout onboarding. When interacting with Freeplay, prefer using the MCP server tools (mcp__freeplay-mcp-v1__*) first. For endpoints or operations not covered by MCP tools, see _shared/FREEPLAY_API_REFERENCE.md.
State detection:
.freeplay/environment-config.json exists -> Environment configured.freeplay/analysis.json exists -> Phase 1 complete.freeplay/migration-manifest.json exists -> Phase 2 complete.freeplay/integration-report.json exists -> Phase 3 complete
Step 1.5: Configure Environment
If .freeplay/environment-config.json doesn't exist, follow the configuration workflow in . This creates the config file with domain, API key, project ID, and URLs, and prompts the user to set environment variables.
