@hailer/mcp 2.0.0-beta.5 → 2.0.0-beta.8

package/.claude/skills/create-and-publish-app/SKILL.md

@@ -30,10 +30,12 @@ Apps are scaffolded and published exclusively through the scripts: `npx @hailer/
 npx @hailer/create-app <project-name> --template react-ts
 ```
 
-- Run from a parent directory (`mkdir -p apps` first if needed)
-- NEVER copy an existing app — scaffold fresh
-- The CLI is interactive-only via `npm create` — always pass name + template as arguments
-- Then `cd apps/<project-name> && npm install`
+**This exact form is non-interactive — it runs with zero prompts. Do NOT deviate:**
+- **`<project-name>` is a POSITIONAL argument, not a flag.** `--name <x>` is silently ignored and the CLI drops to an interactive "Project name:" prompt that hangs an agent. Put the name first, bare.
+- **`--template` must be a real template name:** `react-ts` (recommended), `react`, `react-swc-ts`, `vanilla-ts`, `vanilla`, `preact-ts`, `preact`, `svelte-ts`, `svelte`. NOT `minimal` (invalid → drops to a "Select a framework" prompt that hangs).
+- **Use a fresh, lowercase, kebab-case name** in an empty target dir — that skips the overwrite prompt AND the package-name prompt. e.g. `injured-players-cost`.
+- Never run `npx @hailer/create-app` bare and never pipe input to it (`echo …|`, `printf`, `expect`) — the one-line form above already needs no input.
+- Run from a parent directory (`mkdir -p apps` first if needed), NEVER copy an existing app, then `cd <project-name> && npm install`.
 </scaffold>
 
 <build>

package/.claude/skills/hailer-app-builder/SKILL.md

@@ -12,10 +12,28 @@ triggers:
 
 Patterns and templates for building Hailer apps with @hailer/app-sdk.
 
+<build-philosophy>
+## How to Build Fast: Correct Data First, Theme Does the Looks
+
+The goal of the first version is **showing the correct data the user asked for** — not a custom-designed UI. Get the data right; the user iterates on looks afterward. Two rules make apps both fast and good:
+
+1. **Spend your effort on the data layer, because that's what's easy to get wrong.** Read the real field/phase/workflow IDs from `workspace/enums.ts` + `fields.ts` (never guess, never use labels as keys), fetch with the SDK, and read field values by ID. A dashboard that shows the *wrong* numbers beautifully is a failure; correct numbers in plain components is a success.
+
+2. **Do NOT hand-design UI or build a component library — the scaffold already installed the Hailer theme.** `main.tsx` wires `<ChakraProvider theme={hailerTheme}>`, so **every stock Chakra component is already on Hailer brand** (Nunito Sans, the full Hailer palette, light/dark via system) and there are **214 ready icons** in `src/hailer/theme/icons/`. Compose the UI from plain Chakra primitives — they look right for free:
+   - Layout: `Box`, `Flex`, `Grid`, `SimpleGrid`, `Stack`, `Container`
+   - Data: `Stat`/`StatLabel`/`StatNumber`/`StatHelpText` (stat cards), `Table`/`Thead`/`Tbody`/`Tr`/`Td`, `Card`/`CardHeader`/`CardBody`
+   - Text/state: `Heading`, `Text`, `Badge`, `Tag`, `Spinner`, `Skeleton`, `Alert`
+   - Import icons like `import { HailerSearch } from './hailer/theme/icons/HailerSearch'`
+
+   Don't write custom CSS, custom color values, or bespoke styled components on the first pass. Reach for a Chakra component; it's already themed. The user refines the look later — your job is correct data in a clean themed shell.
+
+3. **Always handle the three states** — loading (`Spinner`/`Skeleton`), empty (a `Text`, never a crash), and outside-Hailer (the app must render standalone — never block on `inside`). Real data is async; assume it's missing first.
+</build-philosophy>
+
 <critical-rules>
 ## CRITICAL: Scaffolding and Data Sources
 
-**Scaffold new apps with `npx @hailer/create-app` — scaffold fresh, never copy an existing app.** Never manually create the project structure. (Apps are script-only — no MCP scaffold tool exists.)
+**Scaffold with the exact non-interactive form: `npx @hailer/create-app <name> --template react-ts`.** The name is POSITIONAL (not `--name`), the template must be valid (`react-ts`/`react`/`vanilla-ts`/`svelte-ts`/…, NOT `minimal`), and the dir must be fresh — that combination runs with zero prompts. A bare `npx @hailer/create-app`, a wrong `--name` flag, an invalid template, or piping input all drop into an interactive prompt that hangs the agent. Scaffold fresh, never copy an existing app, never hand-create the structure. (Apps are script-only — no MCP scaffold tool exists.)
 
 **For project data structure (workflows, fields, phases):**
 - READ workspace/ TypeScript files directly (fields.ts, phases.ts, enums.ts)

package/CLAUDE.md

@@ -25,7 +25,7 @@ Before any MCP call, ask: "Is this answerable from `workspace/` files or a CLI?"
 | Create / modify insights config | Edit `insights.ts` → `npm run insights-push:force` | — (runtime `run_insight` is fine) |
 | Create / modify document templates | Edit `templates/` → `npm run templates-sync:force` | — |
 | Test function field code | vitest locally | `test_function_field` |
-| Scaffold an app | `npx @hailer/create-app` (fresh — never copy an existing app) | — (script-only; no MCP tool exists) |
+| Scaffold an app | `npx @hailer/create-app <name> --template react-ts` (name is POSITIONAL, not `--name`; bare command PROMPTS and hangs agents) | — (script-only; no MCP tool exists) |
 | Publish an app | `cd app && npm run publish-production -- --force` (add `--market` for marketplace versions) | — (script-only; no MCP tool exists) |
 | Create / modify apps registry | Edit `workspace/apps.ts` → `npx hailer-sdk ws-config apps push --force` | `manage_app` |
 | Create / update activities | MCP `create_activity`, `update_activity` | — |
@@ -99,7 +99,7 @@ Always use `:force` — the non-force variants prompt interactively.
 
 | Step | How |
 |------|-----|
-| Scaffold | `npx @hailer/create-app` — scaffold fresh, never copy an existing app |
+| Scaffold | `npx @hailer/create-app <name> --template react-ts` (name POSITIONAL; bare = interactive prompt that hangs agents) — scaffold fresh, never copy an existing app |
 | Local dev | `cd app && npm run dev` |
 | Publish | `cd app && npm run publish-production -- --force` (add `--market` for marketplace; `--force` skips the overwrite prompt that hangs agents); then share via `manage_app` add_member |
 | Register / share | Edit `workspace/apps.ts` → `npx hailer-sdk ws-config apps push --force` |
@@ -142,4 +142,6 @@ Load in sub-agents via the Skill tool. Never in main context.
 
 **Essential:** `/save`, `/handoff`, `/prd`, `/autoplan`, `/ws-pull`
 
-**Squads** (drive the native Workflow tool): `/app-squad "<desc>"`, `/review-squad [target]`, `/debug-squad "<bug>"`
+**Squads** (drive the native Workflow tool): `/review-squad [target]`, `/debug-squad "<bug>"`
+
+Build apps with a single agent + the `hailer-app-builder` / `create-and-publish-app` skills — faster than fanning out a squad (no shared-contract prep, no cross-agent integration fixups).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hailer/mcp",
-  "version": "2.0.0-beta.5",
+  "version": "2.0.0-beta.8",
   "config": {
     "docker": {
       "registry": "registry.gitlab.com/hailer-repos/hailer-mcp"

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

@@ -1,37 +0,0 @@
----
-description: Build a Hailer app with hyper-parallel component teams
-argument-hint: "app description"
-allowed-tools: Workflow, Bash, Read, Skill, Agent
----
-# App Squad
-
-Hyper-parallel app build: the orchestrator does ALL prep, then a Workflow fans out one agent per component with everything pre-loaded. Component agents do ZERO discovery — they just write code.
-
-**Goal:** $ARGUMENTS
-
-## Step 1: Prep (you, before the Workflow)
-
-- **Schema**: read `workspace/enums.ts` + relevant `workspace/<Name>_<id>/fields.ts`/`phases.ts` via a fast sub-agent (never in main context). Only if there's no `workspace/` dir, fall back to MCP `describe_workflows` (+ `include: ["schema","phases"]`).
-- **Scaffold**: `npx @hailer/create-app` — NEVER copy an existing app. (Apps are script-only — no MCP scaffold tool exists.)
-- **Read the scaffold SDK**: `src/hailer/use-app.ts` (store API), `src/main.tsx` (providers), `ls src/hailer/theme/icons/`. Read one working app from `apps/` for live SDK patterns.
-- **Skills**: load `hailer-app-builder` + `hailer-design-system` once; their content goes into the contract.
-
-## Step 2: Shared contract
-
-One document every agent receives verbatim: all workflow/field/phase IDs; the actual use-app.ts store shape and fetch patterns; helper functions; the component manifest (name, file path, props, renders what); exact import paths incl. icons; the working-app SDK patterns (**apps must render outside Hailer — never block on `inside`**); both skills' content.
-
-## Step 3: Workflow fan-out
-
-Author a Workflow script (this command is your opt-in to call the Workflow tool): `parallel()` over the component manifest — Shell (App.tsx: nav, state, fetching), Overview (dashboard), List (table: filters, sorting), Detail (modal), plus one per extra workflow. Each agent gets the full contract + its mission and returns ONLY complete TypeScript/React code as its final text.
-
-## Step 4: Assemble + verify (you)
-
-Write each component to its file, delete scaffold demo components, fix import/prop mismatches, then `npx tsc --noEmit` and `npx vite build`. Under ~5 errors: fix directly; structural failures: re-spawn that one agent with the error and contract.
-
-Report: path, component count, build/TS status, next steps (`cd apps/<name> && npm run dev`, test in the Hailer iframe).
-
-## Rules
-
-- NEVER copy existing apps — scaffold fresh
-- Agents never load skills or read files — you pre-load and paste
-- Include ACTUAL SDK code in the contract, not summaries