Fresh Claude Onboarding: Happy Path Quick Start

[williamsharkey]

Problem

When a fresh Claude session starts with FunctionServer, it doesn't know about the Happy Path workflow. It will default to traditional patterns (read full files, write full files, no verification).

Proposed Solution

Create onboarding documentation and potentially a /happypath slash command that:

1. CLAUDE.md improvements - Add a "Quick Start for Fresh Sessions" section:

   ## Fresh Session Quick Start
   1. eye 'Lens.state()' - Check what's open
   2. eye 'Lens.open("~/file.js")' - Open in Studio
   3. eye 'Lens.code(1, 20)' - View with line numbers
   4. eye 'Lens.grep("pattern")' - Find without reading all
   5. eye 'Lens.setLine(N, "code")' - Surgical edit
   6. eye 'Lens.run()' - Execute and verify
   

2. System prompt injection - When Claude connects via MCP, inject the happy path pattern

3. Example workflows - Document common tasks:

   • "Fix a bug" workflow
   • "Add a feature" workflow
   • "Create new app" workflow

Acceptance Criteria

• Fresh Claude can discover happy path within first 2 messages
• Token usage reduced by >10x compared to naive approach
• Feedback loop is closed (write → run → see error → fix)

[williamsharkey]

Progress Update

Significant improvements made:

OS Core Additions

• setupHappyPath() now available globally (no launcher.js needed)
• setupHappyPath("project name") creates project + GitHub repo + opens in Studio
• ALGO.exec() for shell access without Studio
• ALGO.github.* for GitHub token access

Fresh Session Flow

// One command to start
setupHappyPath("my app")

// Or just load tools
setupHappyPath()  // Loads Studio, ready for Lens.help()

Lens.help() Available

Shows cheat sheet with all commands.

Still TODO

• Consider auto-showing Lens.help() on first use
• System prompt injection for even faster discovery
• Measure actual token usage in real workflows