setup

/setup - DEPRECATED

This skill is deprecated as of 2026-02-02.

All setup functionality (permissions, configuration) has been moved into the quick-start onboarding skill (Step 9).

If you manually triggered this

The quick-start onboarding flow now includes:

• Step 0: Welcome & Language
• Steps 1-8: Goals, workspace, first build planning
• Step 9: Permissions Setup ← (previously in this skill)
• Step 10: Start fresh

Say "hi" to start the quick-start onboarding flow.

For developers

This skill should no longer auto-trigger. The SessionStart hook should inject quick-start directly when onboarding is needed.

---

Execution Workflow

Step 1: Welcome

Display:

Welcome to Nexus!

One quick question before we start.

Step 2: Permission Settings (ASK USER)

Use AskUserQuestion with clear explanation:

Question: "How should I handle permissions?"

Header: "Permissions"

Options:
1. Label: "Automatic (Recommended)"
   Description: "I can read, write, and run commands without asking each time.
                 This is how Nexus works best - smooth and uninterrupted.
                 You can change this anytime in .claude/settings.local.json"

2. Label: "Ask each time"
   Description: "I'll ask permission before every file edit or command.
                 More control, but many interruptions during workflows."

If "Automatic": Create .claude/settings.local.json:

{
  "permissions": {
    "allow": ["Bash(*)", "Edit", "Write", "Read", "Glob", "Grep", "WebFetch", "WebSearch"]
  }
}

If "Ask each time": Skip file creation, user will be prompted for each tool.

Step 3: VS Code Settings (AUTOMATIC)

Automatically create/update .vscode/settings.json:

If user chose "Automatic" in Step 2:

{
  "markdown.preview.breaks": true,
  "markdown.preview.typographer": true,
  "files.associations": {
    "*.md": "markdown"
  },
  "claudeCode.allowDangerouslySkipPermissions": true,
  "claudeCode.initialPermissionMode": "bypassPermissions"
}