onboarding

Configuring Cursor routines for a new workspace involves running a guided six-phase onboarding process that collects workspace details and automatically generates a working config.yaml, state.md, and the Cursor rule.

Generating config.yaml for Cursor setup is best handled by an interactive onboarding wizard that gathers your product identity, data, and tool details, then auto-generates the file while propagating placeholders across skills.

Yes, the Cursor onboarding wizard works for fresh clones. It applies to new workspaces or fresh clones needing complete setup, validating across all skill files and offering optional local installation for auto-discovery.

State tracking during Cursor workspace setup works by creating an initial state.md file. This file is generated during the onboarding workflow to establish a baseline and ensure a clean initial run for your routines.

Yes, you can re-run the onboarding configuration as needed. The process provides batch-ready summaries and next steps, allowing you to easily update your config.yaml and workspace setup if your details change.

The limitations of automated Cursor routine setup are that it requires completing a structured six-phase questionnaire to collect necessary workspace details, and it primarily targets new workspaces or fresh clones rather than modifying existing configurations.