@hailer/mcp 1.1.12 → 1.1.13

package/.claude/commands/learn.md

@@ -1,120 +0,0 @@
----
-description: Capture learning and apply fix to the right place
-argument-hint: <category> <description>
----
-# Learn & Apply
-
-Capture a learning, ask clarifying questions, then apply the fix to the right place.
-
-## Usage
-`/learn <category> <description>`
-
-## Categories
-- `agent/<name>` - Agent behavior issue (e.g., `agent/kenji`)
-- `skill/<name>` - Skill missing pattern (e.g., `skill/function-fields`)
-- `pattern` - General pattern to document
-- `bug` - Bug in code/config
-- `gotcha` - Common mistake to prevent
-
-## Examples
-```
-/learn agent/kenji should check enums.ts before API calls
-/learn skill/insights JOIN syntax was wrong for linked fields
-/learn pattern always verify push succeeded before continuing
-/learn gotcha phase IDs change when workflow is copied
-```
-
-## Instructions
-
-### Step 1: Parse & Understand
-
-Parse the input:
-- Category: first word (e.g., `agent/kenji`)
-- Description: rest of the text
-
-### Step 2: Ask Clarifying Questions
-
-Use AskUserQuestion to gather details:
-
-**For agent issues:**
-- "What was the symptom?" (wrong output, error, missed step)
-- "What should the agent do differently?"
-- "Should this be a rule, a skill addition, or both?"
-
-**For skill issues:**
-- "What was missing or wrong?"
-- "Can you give an example of correct vs incorrect?"
-
-**For patterns/gotchas:**
-- "What went wrong when this wasn't followed?"
-- "Where should this be documented?" (skill, agent, CLAUDE.md)
-
-### Step 3: Determine Target
-
-Based on category and answers, decide where the fix goes:
-
-| Category | Likely Target |
-|----------|---------------|
-| `agent/X` | `.claude/agents/agent-X.md` |
-| `skill/X` | `.claude/skills/X/SKILL.md` |
-| `pattern` | Relevant skill or CLAUDE.md |
-| `bug` | Code fix + possibly skill |
-| `gotcha` | Skill or agent rules section |
-
-### Step 4: Apply the Fix
-
-**Option A: Direct edit (if simple)**
-- Edit the target file directly
-- Add to appropriate section (rules, patterns, examples)
-
-**Option B: Delegate to Ada (if complex)**
-For complex changes, invoke Ada agent:
-```
-Task(subagent_type="agent-ada-skill-builder", prompt={
-  "task": "apply_learning",
-  "category": "<category>",
-  "learning": "<description>",
-  "details": "<clarification answers>",
-  "target": "<determined target>"
-})
-```
-
-### Step 5: Log & Confirm
-
-1. Log to `docs/learnings.md` for history:
-   ```markdown
-   - [<category>] <description> → Applied to <target> _(YYYY-MM-DD)_
-   ```
-
-2. Report what was done:
-   ```
-   Learning applied:
-   - Category: agent/kenji
-   - Fix: Added rule "Check enums.ts before making API calls"
-   - Location: .claude/agents/agent-kenji-data-reader.md
-   ```
-
-## File Template
-
-If creating `docs/learnings.md`:
-
-```markdown
-# Applied Learnings
-
-History of fixes applied from learnings.
-
----
-
-## Log
-
-- [agent/kenji] Check enums.ts first → Added to rules _(2026-01-31)_
-- [skill/insights] JOIN syntax example → Added to SKILL.md _(2026-01-31)_
-```
-
-## Notes
-
-- This command APPLIES fixes, not just logs them
-- Ask questions to understand the real issue
-- Small fixes: edit directly
-- Complex fixes: delegate to Ada
-- Always log what was done for history

package/.claude/commands/mcp-list.md

@@ -1,27 +0,0 @@
----
-description: List available and enabled MCP servers
----
-
-# List MCP Servers
-
-Show available MCP servers and their status.
-
-## Instructions
-
-1. Read `~/.mcp.json` (global servers) - look for `mcpServers` keys
-2. Read `./.mcp.json` (project servers) if it exists - look for `mcpServers` keys
-3. Read `.claude/settings.local.json` to find enabled servers (`enabledMcpjsonServers` array)
-4. Display a table showing all discovered servers:
-
-| Server | Source | Status |
-|--------|--------|--------|
-| chrome-devtools | global | enabled/disabled |
-| notebooklm | global | enabled/disabled |
-| hailer | project | enabled/disabled |
-
-A server is **enabled** if it's in `enabledMcpjsonServers` array.
-
-Also show:
-- `/mcp-enable <name>` to enable
-- `/mcp-disable <name>` to disable
-- Restart required after changes (`claude -c`)

package/.claude/commands/onboard-squad.md

@@ -1,140 +0,0 @@
----
-description: Bootstrap a new Hailer project end-to-end
-argument-hint: "project description or PRD path"
-allowed-tools: Task, Bash, Read
----
-# Onboard Squad
-
-Sequential pipeline: Create workspace infrastructure, scaffold the app, and verify everything is wired correctly.
-
-**Agents:**
-1. **Helga** - Workflow config (create workflows, fields, phases, teams, groups)
-2. **Alejandro** - Function fields and nameFunction
-3. **Giuseppe** - Scaffold first app with basic CRUD interface
-4. **Bjorn** - Audit config accuracy and field references
-
-**Goal:** $ARGUMENTS
-
-## Protocol
-
-### Step 1: Parse Requirements
-
-Parse `$ARGUMENTS` to determine input type:
-
-- **If it's a file path** (e.g., `docs/prd-onboarding.md`): Read it for requirements
-- **Otherwise:** Use it as a project description
-
-If `$ARGUMENTS` is a file path, read it first before proceeding to Helga.
-
-### Step 2: Helga (Workspace Config)
-
-Spawn Helga to create workspace infrastructure:
-
-```
-Task(subagent_type="agent-helga-workflow-config", prompt="Bootstrap a new Hailer project: $ARGUMENTS\n\nCreate: workflows (at least 1), fields for each workflow, phases, teams, and groups as needed.")
-```
-
-Wait for result. If Helga returns `"status": "ready_to_push"`:
-- Run the push commands she provides (e.g., `npm run fields-push:force`)
-- Then run `npm run pull` to refresh local workspace with new IDs
-- **Important:** Helga ALWAYS spawns Alejandro for nameFunction. Check if her result indicates Alejandro was spawned and created nameFunction. If yes, Alejandro's work is done - skip to Step 3.
-
-### Step 3: Alejandro (Function Fields) - Conditional
-
-Only spawn if Helga indicates additional function fields are needed beyond what was created by Helga+Alejandro auto-spawn.
-
-If needed, spawn Alejandro:
-
-```
-Task(subagent_type="agent-alejandro-function-fields", prompt="Create additional function fields for workflows created in: [INSERT HELGA'S GOAL].\n\nHelga created these workflows: [SUMMARIZE HELGA'S RESULT - workflow names, IDs, field counts].\n\nFunction fields already created by Helga: [FROM HELGA'S RESULT].")
-```
-
-Wait for result. If `"status": "ready_to_push"`:
-- Run the push commands
-- Run `npm run pull` to refresh workspace
-
-### Step 4: Giuseppe (App Scaffold)
-
-**Before spawning Giuseppe, enable builder mode:**
-```
-Bash: node .claude/hooks/app-edit-guard.cjs --agent-on
-```
-
-Spawn Giuseppe to build the first app using the new workspace:
-
-```
-Task(subagent_type="agent-giuseppe-app-builder", prompt="Scaffold the first Hailer app for this new project: $ARGUMENTS\n\nWorkspace created by Helga: [SUMMARIZE HELGA'S RESULT - workflow names, IDs, field counts]. Giuseppe: read workspace/ directly to discover exact field IDs, types, and team configurations. Do not guess IDs.\n\nBuild a basic CRUD interface using @hailer/app-sdk and Chakra UI. Start with the primary workflow. Use the Hailer Design System.\n\nNote: Assume Local Dev app exists (orchestrator checks this before spawning you). Build for local development at http://localhost:3000.")
-```
-
-**After Giuseppe completes, disable builder mode:**
-```
-Bash: node .claude/hooks/app-edit-guard.cjs --agent-off
-```
-
-Wait for result. If Giuseppe returns `"status": "ready_to_push"`:
-- Run the push commands
-
-### Step 5: Bjorn (Config Audit)
-
-Spawn Bjorn to verify everything is configured correctly:
-
-```
-Task(subagent_type="agent-bjorn-config-audit", prompt="Audit this new Hailer project setup:\n\n1. Verify CLAUDE.md accuracy (check that project type detection works)\n2. Verify workspace configuration: workflows, fields, phases, teams all match workspace/ files\n3. Verify field references in the new app match workspace/ field definitions\n4. Check for missing imports, incorrect IDs, or type mismatches\n5. Verify that nameFunction is set on the primary workflow\n\nProject goal: $ARGUMENTS\n\nReport any misconfigurations. If iteration <= 1, recommend fixes to the orchestrator.")
-```
-
-**Loop Control:**
-- If Bjorn finds no critical issues: proceed to Step 6 (report)
-- If Bjorn finds issues AND `iteration <= 1`:
-  - Increment `iteration`
-  - Determine which agent to fix it (usually Helga or Giuseppe)
-  - Run appropriate agent with the issues to fix
-  - Return to Step 5 (Bjorn re-audits)
-- If Bjorn finds issues AND `iteration > 1`: escalate to user in Step 6
-
-### Step 6: Report
-
-```markdown
-## Onboard Squad Complete
-
-**Project Goal:** $ARGUMENTS
-
-### Workspace Setup (Helga)
-- Workflows created: [list with IDs]
-- Fields created: [count]
-- Phases: [count]
-- Teams: [count]
-- Alejandro auto-spawn: [nameFunction created? Y/N]
-
-### Function Fields (Alejandro)
-- Additional function fields created: [list or "None needed"]
-- Skipped: [reason if skipped]
-
-### App Scaffold (Giuseppe)
-- App path: [path to new app]
-- Build status: Pass/Fail
-- Files created: [count/list]
-- Local dev setup: [check local dev app name]
-
-### Verification (Bjorn)
-- Critical issues found: [count] or "None"
-- Status: VERIFIED / NEEDS FIXES (if iteration > 1, see below)
-
-[If iteration > 1 - escalated:]
-### Remaining Issues
-[List issues Bjorn found that weren't resolved in 1 fix iteration]
-- Manual fixes recommended: [hints]
-
-### Next Steps
-1. Run `npm run dev` to test the app locally
-2. Ensure "Local Dev" app exists in Hailer workspace
-3. Test the app inside Hailer iframe at http://localhost:3000
-4. Run `npm run pull` to ensure workspace/ is fully up to date
-```
-
-## Notes
-
-- Each agent in the pipeline needs IDs from the previous step. Always `npm run pull` between Helga→Alejandro→Giuseppe to refresh local workspace.
-- Helga auto-spawns Alejandro for nameFunction. Check her result - only spawn Alejandro again in Step 3 if additional function fields are needed.
-- Giuseppe needs real workflow and field IDs from workspace/ - always read the files and paste actual IDs, never let him guess.
-- Bjorn's audit is the quality gate. If issues are found and you've iterated once, escalate remaining issues to the user rather than looping infinitely.
-- Set `iteration = 1` at the start. Increment after each Bjorn audit if fixes are attempted.