@hatchway/cli 0.50.55 → 0.50.57

package/dist/instrument.js

@@ -20,6 +20,7 @@ Sentry.init({
     // eslint-disable-next-line @typescript-eslint/no-explicit-any
     integrations: integrations,
     tracesSampleRate: 1.0,
+    enableLogs: true,
     debug: false,
     sendDefaultPii: false,
     // Configure trace propagation (Runner → Broker communication)

package/dist/instrument.js.map

@@ -1 +1 @@
-{"version":3,"file":"instrument.js","sources":["../src/instrument.ts"],"sourcesContent":["import * as Sentry from \"@sentry/node\";\n\n// Debug logging for instrumentation (enabled via DEBUG_SENTRY=1)\nconst debugSentry = process.env.DEBUG_SENTRY === '1';\nconst log = (msg: string) => debugSentry && console.log(`[sentry-instrument] ${msg}`);\n\n// Build integrations array\nconst integrations: unknown[] = [];\n\n// Add http integration for request tracing\nif (typeof Sentry.httpIntegration === \"function\") {\n  integrations.push(Sentry.httpIntegration());\n  log('Added httpIntegration');\n}\n\nlog(`Total integrations configured: ${integrations.length}`);\n\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n  // eslint-disable-next-line @typescript-eslint/no-explicit-any\n  integrations: integrations as any[],\n  tracesSampleRate: 1.0,\n  debug: false,\n  sendDefaultPii: false,\n  // Configure trace propagation (Runner → Broker communication)\n  tracePropagationTargets: [\n    // Local development\n    \"localhost\",\n    \"localhost:3000\",\n    \"localhost:4000\",\n    /^https?:\\/\\/localhost:\\d+$/,\n\n    // Production domains\n    \"hatchway.sh\",\n    \"hatchway.app\",\n    \"hatchway.up.railway.app\",\n    \"broker.hatchway.sh\",\n    \"broker.hatchway.app\",\n    \"broker.up.railway.app\",\n\n    // Wildcard patterns for Railway\n    /^https?:\\/\\/.*\\.railway\\.app/, // Railway deployments\n    /^https?:\\/\\/.*\\.up\\.railway\\.app/, // Railway preview deployments\n    /^https?:\\/\\/.*\\.hatchway\\.app/, // Custom domain subdomains\n  ],\n});\n"],"names":[],"mappings":";;;;;;AAEA;AACA,MAAM,WAAW,GAAG,OAAO,CAAC,GAAG,CAAC,YAAY,KAAK,GAAG;AACpD,MAAM,GAAG,GAAG,CAAC,GAAW,KAAK,WAAW,IAAI,OAAO,CAAC,GAAG,CAAC,uBAAuB,GAAG,CAAA,CAAE,CAAC;AAErF;AACA,MAAM,YAAY,GAAc,EAAE;AAElC;AACA,IAAI,OAAO,MAAM,CAAC,eAAe,KAAK,UAAU,EAAE;IAChD,YAAY,CAAC,IAAI,CAAC,MAAM,CAAC,eAAe,EAAE,CAAC;IAC3C,GAAG,CAAC,uBAAuB,CAAC;AAC9B;AAEA,GAAG,CAAC,CAAA,+BAAA,EAAkC,YAAY,CAAC,MAAM,CAAA,CAAE,CAAC;AAE5D,MAAM,CAAC,IAAI,CAAC;AACV,IAAA,GAAG,EAAE,OAAO,CAAC,GAAG,CAAC,UAAU;;AAE3B,IAAA,YAAY,EAAE,YAAqB;AACnC,IAAA,gBAAgB,EAAE,GAAG;AACrB,IAAA,KAAK,EAAE,KAAK;AACZ,IAAA,cAAc,EAAE,KAAK;;AAErB,IAAA,uBAAuB,EAAE;;QAEvB,WAAW;QACX,gBAAgB;QAChB,gBAAgB;QAChB,4BAA4B;;QAG5B,aAAa;QACb,cAAc;QACd,yBAAyB;QACzB,oBAAoB;QACpB,qBAAqB;QACrB,uBAAuB;;AAGvB,QAAA,8BAA8B;AAC9B,QAAA,kCAAkC;AAClC,QAAA,+BAA+B;AAChC,KAAA;AACF,CAAA,CAAC"}
+{"version":3,"file":"instrument.js","sources":["../src/instrument.ts"],"sourcesContent":["import * as Sentry from \"@sentry/node\";\n\n// Debug logging for instrumentation (enabled via DEBUG_SENTRY=1)\nconst debugSentry = process.env.DEBUG_SENTRY === '1';\nconst log = (msg: string) => debugSentry && console.log(`[sentry-instrument] ${msg}`);\n\n// Build integrations array\nconst integrations: unknown[] = [];\n\n// Add http integration for request tracing\nif (typeof Sentry.httpIntegration === \"function\") {\n  integrations.push(Sentry.httpIntegration());\n  log('Added httpIntegration');\n}\n\nlog(`Total integrations configured: ${integrations.length}`);\n\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n  // eslint-disable-next-line @typescript-eslint/no-explicit-any\n  integrations: integrations as any[],\n  tracesSampleRate: 1.0,\n  enableLogs: true,\n  debug: false,\n  sendDefaultPii: false,\n  // Configure trace propagation (Runner → Broker communication)\n  tracePropagationTargets: [\n    // Local development\n    \"localhost\",\n    \"localhost:3000\",\n    \"localhost:4000\",\n    /^https?:\\/\\/localhost:\\d+$/,\n\n    // Production domains\n    \"hatchway.sh\",\n    \"hatchway.app\",\n    \"hatchway.up.railway.app\",\n    \"broker.hatchway.sh\",\n    \"broker.hatchway.app\",\n    \"broker.up.railway.app\",\n\n    // Wildcard patterns for Railway\n    /^https?:\\/\\/.*\\.railway\\.app/, // Railway deployments\n    /^https?:\\/\\/.*\\.up\\.railway\\.app/, // Railway preview deployments\n    /^https?:\\/\\/.*\\.hatchway\\.app/, // Custom domain subdomains\n  ],\n});\n"],"names":[],"mappings":";;;;;;AAEA;AACA,MAAM,WAAW,GAAG,OAAO,CAAC,GAAG,CAAC,YAAY,KAAK,GAAG;AACpD,MAAM,GAAG,GAAG,CAAC,GAAW,KAAK,WAAW,IAAI,OAAO,CAAC,GAAG,CAAC,uBAAuB,GAAG,CAAA,CAAE,CAAC;AAErF;AACA,MAAM,YAAY,GAAc,EAAE;AAElC;AACA,IAAI,OAAO,MAAM,CAAC,eAAe,KAAK,UAAU,EAAE;IAChD,YAAY,CAAC,IAAI,CAAC,MAAM,CAAC,eAAe,EAAE,CAAC;IAC3C,GAAG,CAAC,uBAAuB,CAAC;AAC9B;AAEA,GAAG,CAAC,CAAA,+BAAA,EAAkC,YAAY,CAAC,MAAM,CAAA,CAAE,CAAC;AAE5D,MAAM,CAAC,IAAI,CAAC;AACV,IAAA,GAAG,EAAE,OAAO,CAAC,GAAG,CAAC,UAAU;;AAE3B,IAAA,YAAY,EAAE,YAAqB;AACnC,IAAA,gBAAgB,EAAE,GAAG;AACrB,IAAA,UAAU,EAAE,IAAI;AAChB,IAAA,KAAK,EAAE,KAAK;AACZ,IAAA,cAAc,EAAE,KAAK;;AAErB,IAAA,uBAAuB,EAAE;;QAEvB,WAAW;QACX,gBAAgB;QAChB,gBAAgB;QAChB,4BAA4B;;QAG5B,aAAa;QACb,cAAc;QACd,yBAAyB;QACzB,oBAAoB;QACpB,qBAAqB;QACrB,uBAAuB;;AAGvB,QAAA,8BAA8B;AAC9B,QAAA,kCAAkC;AAClC,QAAA,+BAA+B;AAChC,KAAA;AACF,CAAA,CAAC"}

package/dist/lib/skills/platform-plugin/.claude-plugin/plugin.json

@@ -0,0 +1,5 @@
+{
+  "name": "hatchway-platform",
+  "version": "2.0.0",
+  "description": "Hatchway platform skills for building production-ready applications. Provides procedural knowledge for task tracking, communication style, dependency management, design excellence, build verification, context awareness, and architectural thinking."
+}

package/dist/lib/skills/platform-plugin/skills/architectural-thinking/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: architectural-thinking
+description: "Pre-planning procedure for new tasks. Visualize end state, identify structure, and anticipate problems before coding. Use when starting a new feature, scaffolding a project, or planning a multi-file change."
+user-invocable: false
+---
+
+# Architectural Thinking
+
+Spend 30 seconds thinking before writing code. Plan the shape of the solution first.
+
+## Before Creating Your Todo List
+
+1. **Visualize the end state** -- What files will exist? What's the component hierarchy? How does data flow?
+2. **Anticipate problems** -- What could break? (types, imports, circular dependencies) Are there conflicting patterns in the codebase?
+3. **Design the experience** -- What's the visual identity? What makes this feel polished rather than generic?
+4. **Order the work** -- Create todos in dependency order. Group related changes. Put configuration and setup first.
+
+## Example
+
+Task: "Build a product catalog with filtering"
+
+Think first:
+```
+Files needed: ProductCard, ProductGrid, FilterSidebar, useProducts hook, types.ts
+Data flow: useProducts fetches → FilterSidebar updates query → ProductGrid re-renders
+Risk: Filter state and URL sync could cause re-render loops
+Order: types → hook → ProductCard → ProductGrid → FilterSidebar → integration
+```
+
+Then create the todo list and execute confidently.
+
+## Avoid
+
+- Jumping straight into coding without understanding the full scope
+- Creating files in random order, discovering missing dependencies mid-build
+- Designing components in isolation without thinking about how they compose

package/dist/lib/skills/platform-plugin/skills/build-verification/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: build-verification
+description: "Fix-verify iteration loop for dependency, build, and runtime errors. Use when installing packages, running dev servers, fixing build errors, or verifying that code compiles and runs."
+user-invocable: false
+---
+
+# Build Verification
+
+Every code change must be verified. Never declare success without seeing clean output.
+
+## The Loop
+
+```
+1. Make a fix
+2. Run the build or dev server
+3. Read the output
+4. If errors remain → go to 1
+5. If clean → move on
+```
+
+## Dependency Failures
+
+Read the full error. Fix package.json (version conflicts, missing peers). Re-run install. Verify before writing any source code.
+
+## Build / TypeScript Errors
+
+Fix errors top-to-bottom (earlier errors often cause later ones). Re-run after each fix. Target zero warnings.
+
+## Dev Server Verification
+
+Start the dev server once at the end for final verification. Check for:
+- "compiled successfully" or "ready in X ms"
+- No red error text or stack traces
+- Correct port binding
+
+Stop the server after verification -- do not leave it running.
+
+## Example
+
+```
+$ npm run build
+Error: Cannot find module './utils/helpers'
+
+→ Read imports, discover file was moved to lib/helpers.ts
+→ Update import path
+→ Re-run npm run build
+→ "compiled successfully" ✓
+```
+
+## Never
+
+- Declare "fixed" without running verification
+- Skip re-running after a change
+- Leave a failing dev server and move on

package/dist/lib/skills/platform-plugin/skills/communication-style/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: communication-style
+description: "Concise output formatting for the Hatchway platform UI. Use when generating any response during task execution."
+user-invocable: false
+---
+
+# Communication Style
+
+Keep output minimal so the Hatchway UI stays clean and scannable.
+
+## During Execution
+
+- Work silently -- no narration of what you're about to do
+- After completing each task, write ONE short summary sentence
+
+## On Completion
+
+- Provide a 2-3 sentence summary of everything that was done
+- Format all responses in Markdown
+
+## Example
+
+Bad (verbose):
+> I'm going to start by reading the package.json to understand the dependencies.
+> Now I'll install the missing packages. Let me check if tailwind is configured...
+
+Good (concise):
+> Added Tailwind CSS with the brand color palette and updated all components to use utility classes.

package/dist/lib/skills/platform-plugin/skills/context-awareness/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: context-awareness
+description: "Read-before-write discipline. Search for patterns and understand existing code before modifying files. Use when editing existing files, adding features to an existing codebase, or creating new components."
+user-invocable: false
+---
+
+# Context Awareness
+
+Understand the codebase before changing it. Read first, write second.
+
+## Before Modifying Any File
+
+1. **Search** -- Use Grep to find similar patterns (naming conventions, import style, component structure)
+2. **Read** -- Open related files to understand data flow and dependencies
+3. **Assess** -- Will this change break imports elsewhere? Is there an existing utility to reuse?
+4. **Change** -- Make targeted edits that match existing code style
+
+## Example
+
+Task: "Add a user avatar component"
+
+Before creating `UserAvatar.tsx`:
+```
+Grep: "Avatar" → find existing avatar usage
+Grep: "component" in src/components/ → see naming pattern (PascalCase folders? flat files?)
+Read: src/components/Button.tsx → see how components are structured (props interface, export style)
+Read: src/lib/utils.ts → check for existing image/URL helpers
+```
+
+Then create `UserAvatar.tsx` matching the patterns found.
+
+## Never
+
+- Blindly modify files without reading surrounding context
+- Create a new utility when one already exists in the codebase
+- Ignore the project's established patterns in favor of your own preferences

package/dist/lib/skills/platform-plugin/skills/dependency-management/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: dependency-management
+description: "Install all project dependencies upfront in a single operation. Use when starting a new feature, scaffolding a project, or when any npm/pnpm package installation is needed."
+user-invocable: false
+---
+
+# Dependency Management
+
+Identify every package the feature needs before writing source code. Install once, then build.
+
+## Workflow
+
+1. Read the requirements and identify ALL needed packages
+2. Add them all to package.json in one edit
+3. Run install once (`pnpm install` or `npm install`)
+4. Begin writing source code
+
+## Example
+
+Task: "Add a chart dashboard with date filtering"
+
+Identify upfront: recharts, date-fns, @types/recharts
+
+```json
+// One package.json edit with all three
+"dependencies": {
+  "recharts": "^2.12.0",
+  "date-fns": "^3.6.0"
+},
+"devDependencies": {
+  "@types/recharts": "^2.0.0"
+}
+```
+
+Then one `npm install`, then start coding.
+
+## Avoid
+
+- Writing code, discovering a missing import, installing, repeat
+- Running multiple install commands throughout the build
+- Installing packages one at a time as you discover them

package/dist/lib/skills/platform-plugin/skills/design-excellence/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: design-excellence
+description: "Visual design thinking for production-ready UI. Use when building new pages, components, or styling any user-facing interface."
+user-invocable: false
+---
+
+# Design Excellence
+
+Before writing CSS or choosing colors, decide on a clear aesthetic direction and commit to it.
+
+## Design Thinking
+
+- **Purpose**: What problem does this interface solve? Who uses it?
+- **Tone**: Pick a direction -- minimal, bold, editorial, playful, luxury, brutalist, organic. Commit fully.
+- **Differentiation**: What makes this memorable? What's the one thing a user will notice?
+
+## Principles
+
+- **Color discipline**: Pick a small, intentional palette (primary + neutrals + accent). Define as CSS custom properties. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+- **Typography hierarchy**: Pair a distinctive heading font with a readable body font. Use weight and size to create clear visual hierarchy.
+- **Spatial composition**: Use an 8pt spacing system. Be generous with whitespace. Consider asymmetry and grid-breaking elements where appropriate.
+- **Motion**: Focus on high-impact moments (page load reveals, hover states) rather than scattered micro-interactions. Keep transitions 200-300ms.
+- **Accessibility**: Semantic HTML, 4.5:1 contrast ratio, keyboard navigation, 44px touch targets.
+
+## Mobile First
+
+Design for 375px, then enhance for 768px and 1440px. Use CSS Grid/Flexbox for fluid layouts. Cap content width at 1200-1440px.
+
+## Avoid
+
+- Generic AI aesthetics (purple gradients on white, Inter/Roboto defaults, cookie-cutter card layouts)
+- Decorative filler with no purpose (random gradient circles, blurry blobs, geometric noise)
+- Copying the template's visual identity -- create something original
+
+Every interface should feel intentionally designed for its specific context.

package/dist/lib/skills/platform-plugin/skills/template-originality/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: template-originality
+description: "Replace template scaffolding with original design. Use ONLY when building a new project from a template scaffold, not when editing existing projects."
+user-invocable: false
+---
+
+# Template Originality
+
+The template is a scaffold -- it provides structure, build tooling, and routing. Its visual design is disposable.
+
+## What to Replace
+
+- Delete or completely rewrite template example components (hero sections, sample cards, "Welcome to X" pages)
+- Replace the template's color scheme and typography with choices specific to this app
+- Design layouts that serve this app's actual content, not the template's demo content
+
+## How to Think About It
+
+- What is this app's personality? (playful, serious, minimal, bold)
+- What colors represent this specific brand or purpose?
+- What layout structure serves these specific features?
+
+## Example
+
+Template ships with: purple gradient hero, 3-column feature cards, "About" and "Features" pages.
+
+For a recipe app: Warm earth-tone palette, editorial food photography layout, ingredient-focused navigation, full-bleed recipe cards. Nothing from the template survives visually.
+
+## Avoid
+
+- Keeping template hero sections with just the text swapped
+- Reusing the template's default color scheme (especially purple/indigo)
+- Copying template navigation structure when the app needs something different
+- Leaving template example pages like "About" or "Features" with placeholder content

package/dist/lib/skills/platform-plugin/skills/todo-workflow/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: todo-workflow
+description: "Step-by-step task tracking using the TodoWrite tool. Use when executing any multi-step task, follow-up request, or build workflow."
+user-invocable: false
+---
+
+# Todo Workflow
+
+The Hatchway UI tracks progress via TodoWrite. Without it, users see nothing happening.
+
+## Workflow
+
+For each todo:
+
+1. Mark it `in_progress` via TodoWrite
+2. Do the work
+3. Mark it `completed` via TodoWrite
+4. Write one sentence about what you did
+5. Move to the next todo
+
+Update after every single todo -- never batch multiple completions into one call.
+
+## Follow-ups
+
+Even simple follow-up requests get at least one todo. Create it, mark in_progress, do the work, mark completed.
+
+## Example
+
+Task: "Add a dark mode toggle"
+
+```
+TodoWrite → [{content: "Add theme context provider", status: "in_progress"}, ...]
+  → Create ThemeContext.tsx
+TodoWrite → [{content: "Add theme context provider", status: "completed"}, ...]
+  Added ThemeProvider with light/dark state and localStorage persistence.
+TodoWrite → [{content: "Add toggle component to header", status: "in_progress"}, ...]
+  → Create DarkModeToggle.tsx, add to Header
+TodoWrite → [{content: "Add toggle component to header", status: "completed"}, ...]
+  Added moon/sun icon toggle to the header nav bar.
+```
+
+## Autonomous Execution
+
+Keep working until 100% complete. Do not pause to ask "Should I continue?" unless you need information only the user can provide or encounter an unrecoverable error.

package/dist/lib/skills/platform-plugin/skills/todo-workflow-codex/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: todo-workflow-codex
+description: "Task tracking via inline JSON code blocks for the Codex agent. Use when executing any multi-step task or build workflow."
+user-invocable: false
+---
+
+# Task Tracking via JSON Code Blocks
+
+Track progress by including JSON code blocks in your responses. The system extracts them automatically.
+
+## Format
+
+```json
+{"todos":[
+  {"content":"Task description","status":"completed","activeForm":"Past tense"},
+  {"content":"Current task","status":"in_progress","activeForm":"Present continuous"},
+  {"content":"Future task","status":"pending","activeForm":"Will do"}
+]}
+```
+
+## When to Include
+
+- At the start: initial task breakdown
+- After each major step: updated statuses
+- At the end: all tasks completed
+
+## Example
+
+Task: "Add a contact form"
+
+Response 1:
+```json
+{"todos":[
+  {"content":"Create form component with validation","status":"in_progress","activeForm":"Creating form component"},
+  {"content":"Add API route for form submission","status":"pending","activeForm":"Will add API route"},
+  {"content":"Style form with project design system","status":"pending","activeForm":"Will style form"}
+]}
+```
+
+Response 2 (after completing form):
+```json
+{"todos":[
+  {"content":"Create form component with validation","status":"completed","activeForm":"Created form component"},
+  {"content":"Add API route for form submission","status":"in_progress","activeForm":"Adding API route"},
+  {"content":"Style form with project design system","status":"pending","activeForm":"Will style form"}
+]}
+```
+
+This is NOT a tool call -- simply include the JSON block in your message text.
+
+## Autonomous Execution
+
+Keep working until 100% complete. Do not pause to ask "Should I continue?" unless you need information only the user can provide or encounter an unrecoverable error.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hatchway/cli",
-  "version": "0.50.55",
+  "version": "0.50.57",
   "description": "Hatchway CLI - Build AI-powered apps with Claude. Just run: npx @hatchway/cli runner",
   "private": false,
   "type": "module",
@@ -41,15 +41,15 @@
   "homepage": "https://github.com/codyde/hatchway#readme",
   "preferGlobal": true,
   "scripts": {
-    "dev": "RUNNER_WS_URL=ws://localhost:3000/ws/runner tsx --import ./src/instrument.ts src/index.ts",
+    "dev": "RUNNER_WS_URL=ws://localhost:3000/ws/runner RUNNER_SHARED_SECRET=${RUNNER_SHARED_SECRET:-dev-secret} tsx --import ./src/instrument.ts src/index.ts",
     "dev:cli": "tsx --import ./src/instrument.ts src/cli/index.ts",
-    "build": "rollup -c && cp templates.json dist/",
+    "build": "rollup -c && cp templates.json dist/ && rm -rf dist/lib/skills/platform-plugin && mkdir -p dist/lib/skills && cp -R src/lib/skills/platform-plugin dist/lib/skills/platform-plugin",
     "build:tsc": "tsc -p tsconfig.json",
-    "start": "RUNNER_WS_URL=ws://localhost:3000/ws/runner node --import ./dist/instrument.js dist/index.js",
+    "start": "RUNNER_WS_URL=ws://localhost:3000/ws/runner RUNNER_SHARED_SECRET=${RUNNER_SHARED_SECRET:-dev-secret} node --import ./dist/instrument.js dist/index.js",
     "cli": "node --import ./dist/instrument.js dist/cli/index.js"
   },
   "dependencies": {
-    "@anthropic-ai/claude-agent-sdk": "^0.2.29",
+    "@anthropic-ai/claude-agent-sdk": "^0.2.45",
     "@hatchway/droid-sdk": "^1.0.0",
     "@clack/prompts": "^0.11.0",
     "@openai/codex-sdk": "^0.93.0",