@crossdelta/platform-sdk 0.25.6 → 0.26.0

package/bin/docs/generators/README.md

@@ -10,47 +10,19 @@ generators/
 ├── service.md          # Main service generator instructions
 ├── code-style.md       # Code style, formatting, naming conventions
 ├── testing.md          # Testing rules and patterns
+├── natural-language.md # Natural-language prompt pipeline
 ├── hono-bun.md         # Hono with Bun runtime specifics
 ├── hono-node.md        # Hono with Node.js runtime specifics
 └── nest.md             # NestJS framework specifics
 ```
 
-## How Instructions Are Loaded
-
-Instructions are configured in `package.json` under `generatorConfig.docs`:
-
-```json
-{
-  "generatorConfig": {
-    "docs": {
-      "base": ["service.md", "code-style.md", "testing.md"],
-      "frameworks": {
-        "hono": { "bun": "hono-bun.md", "node": "hono-node.md" },
-        "nest": "nest.md"
-      }
-    }
-  }
-}
-```
+## How Instructions Are Served
 
-**Load Order:**
-1. **Base docs** - Always loaded (service.md, code-style.md, testing.md)
-2. **Framework-specific** - Based on `serviceType` and `packageManager`
-3. **Workspace instructions** - every one of `CLAUDE.md`, `AGENTS.md`, `.github/copilot-instructions.md`, `docs/ai-guidelines.md` that the workspace carries. Missing files are skipped; the token budget is split across the ones found.
+The pf MCP server lists the `.md` files in this directory as the resource `docs://generators` and serves each one as `docs://generators/<name>` (`packages/pf-mcp/src/resources/generator-docs.ts`; the directory is read by `listGeneratorDocs` in `cli/src/core/facade/index.ts`). The build copies the directory to `bin/docs/generators` (`build:copy` in `package.json`). An agent reads the file it needs; nothing is merged or loaded in a fixed order.
 
 ## Adding New Generators
 
 To add instructions for a new framework:
 
 1. Create `<framework>.md` in this directory
-2. Add to `generatorConfig.docs.frameworks` in `package.json`
-3. Follow the existing format from `hono-bun.md` or `nest.md`
-
-## Template Variables
-
-The following variables are replaced at runtime:
-
-| Variable | Description |
-|----------|-------------|
-| `{{scope}}` | Package scope (e.g., `@orderboss`) |
-| `{{AVAILABLE_CONTRACTS}}` | Auto-generated list of existing contracts |
+2. Follow the existing format from `hono-bun.md` or `nest.md`

package/bin/templates/workspace/.claude/rules/cloudevents.md

@@ -53,7 +53,7 @@ Rules for working with the CloudEvents package and event handlers.
 
 ## NATS Migrations
 
-See [Infrastructure](infrastructure.md) for migration conventions (`infra/migrations/`).
+Stream migrations live in `infra/migrations/`.
 
 ## Publishing Checklist
 
@@ -61,7 +61,6 @@ See [Infrastructure](infrastructure.md) for migration conventions (`infra/migrat
 2. Update `CHANGELOG.md`
 3. **Push to remote before publishing** — npm publish reads from the repo
 4. Trigger workflow: `gh workflow run publish-packages.yml -f package=cloudevents`
-5. After publishing: the `sync-templates` pre-commit hook auto-updates downstream `package.json` references
 
 ## Distributed Tracing
 

package/bin/templates/workspace/CLAUDE.md

@@ -25,7 +25,7 @@ You are assisting in TypeScript-first monorepos using modern TypeScript tooling
 
 - **Test consumers**: When changing a shared package (`packages/*`), run tests in **all consuming services**, not just the package itself. Changes to shared code have blast radius.
 - **Push before publish**: Always push commits to remote before triggering npm publish workflows. The CI reads from the repo, not your local machine.
-- **Pre-commit hooks exist**: The repo has a `sync-templates` hook that auto-updates downstream `package.json` refs after version bumps. Never bypass with `--no-verify`.
+- **Pre-commit hooks**: Never bypass them with `--no-verify`.
 - **Capture lessons**: When a convention or pitfall emerges, propose updating a scoped `.claude/rules/` file. Ask before creating new files. Keep `CLAUDE.md` project-agnostic; domain-specific rules go in scoped files with `paths:`.
 
 ## Monorepo Awareness
@@ -52,6 +52,10 @@ regardless of which file is open, because that cost is paid on every turn.
 Code style and testing conventions are not rules here: the `pf` generators carry their own, and they
 load whenever the generator writes code.
 
+## Agent Kit
+
+Skills, agents and general rules under `.claude/` come from `@crossdelta/agent-kit` and are listed in `.claude/agent-kit.lock.json`. Project values (languages, plan directory, models, checks) live in `.claude/agent-kit.json`. Update with `pf agents sync`; a conflicting local edit lands as `<file>.kit-new`. Put project knowledge into `.claude/project/<skill>.md` or a rule beside `.claude/rules/kit/`, so the kit files stay updatable. `pf plans` shows the plan progress of the current sprint.
+
 ## Key Packages
 
 Installed from npm, not vendored into this repo. Read their APIs in `node_modules/`, not from memory.

package/bin/templates/workspace/package.json.hbs

@@ -17,6 +17,14 @@
     "commands": {
       "pulumi": {
         "cwd": "infra"
+      },
+      "agents": {
+        "command": "bunx @crossdelta/agent-kit",
+        "description": "Agent kit: init, sync, check, plans"
+      },
+      "plans": {
+        "command": "bunx @crossdelta/agent-kit plans",
+        "description": "Live view of the sprint's lanes and their plan progress"
       }
     },
     "paths": {
@@ -43,6 +51,7 @@
   },
   "devDependencies": {
     "@biomejs/biome": "2.3.7",
+    "@crossdelta/agent-kit": "latest",
     "@crossdelta/platform-sdk": "latest",
     "dotenv-cli": "^8.0.0",
     "turbo": "^2.5.6"

package/bin/templates/workspace/packages/contracts/README.md.hbs

@@ -89,7 +89,7 @@ Contracts are **auto-generated** when you create event handlers:
 
 ```bash
 # 1. Create service with event handler
-pf new hono-micro notifications --ai -d "Sends emails on order.created events"
+pf new hono-micro notifications
 
 # 2. Add event (creates contract, mock, handler)
 pf cloudevents add order.created --service services/notifications

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crossdelta/platform-sdk",
-  "version": "0.25.6",
+  "version": "0.26.0",
   "description": "Platform toolkit for event-driven microservices — keeping code and infrastructure in lockstep.",
   "keywords": [
     "cli",
@@ -65,42 +65,6 @@
     "name": "Marcelle Hövelmanns",
     "email": "mail@hoevelmanns.io"
   },
-  "generatorConfig": {
-    "docs": {
-      "base": [
-        "service.md",
-        "code-style.md",
-        "testing.md"
-      ],
-      "frameworks": {
-        "hono": {
-          "bun": "hono-bun.md",
-          "node": "hono-node.md"
-        },
-        "nest": "nest.md"
-      }
-    },
-    "serviceTypes": {
-      "hono": {
-        "commandType": "hono-micro",
-        "entryPoint": "src/index.ts",
-        "skipFiles": [
-          "package.json",
-          "tsconfig.json",
-          "Dockerfile"
-        ]
-      },
-      "nest": {
-        "commandType": "nest-micro",
-        "entryPoint": "src/main.ts",
-        "skipFiles": [
-          "package.json",
-          "tsconfig.json",
-          "Dockerfile"
-        ]
-      }
-    }
-  },
   "scripts": {
     "dev": "tsup --watch",
     "build:copy": "cp cli/integration.collection.json bin/integration.collection.json && rm -rf bin/templates && mkdir -p bin/templates && cp -r cli/src/commands/create/workspace/templates bin/templates/workspace && cp -r cli/src/commands/create/hono-microservice/templates bin/templates/hono-microservice && cp -r cli/src/commands/create/nest-microservice/templates bin/templates/nest-microservice && mkdir -p bin/docs/generators && cp -r docs/generators/* bin/docs/generators/",
@@ -115,15 +79,11 @@
   },
   "schematics": "./dist/schematics/collection.json",
   "dependencies": {
-    "@ai-sdk/anthropic": "^2.0.53",
-    "@ai-sdk/openai": "^2.0.79",
     "@angular-devkit/core": "^21.0.0",
     "@crossdelta/cloudevents": "^0.10.0",
     "@crossdelta/flowcore": "^0.1.2",
     "@faker-js/faker": "^9.8.0",
-    "@inquirer/prompts": "^7.5.0",
     "@listr2/prompt-adapter-enquirer": "^2.0.15",
-    "ai": "^5.0.108",
     "chalk": "^5.4.1",
     "chokidar": "^5.0.0",
     "cli-table3": "^0.6.5",
@@ -136,11 +96,9 @@
     "handlebars": "^4.7.8",
     "jiti": "^2.6.1",
     "listr2": "^8.3.2",
-    "ora": "^8.2.0",
     "package-up": "^5.0.0",
     "rimraf": "^6.1.2",
     "terminal-link": "^4.0.0",
-    "ts-morph": "^27.0.0",
     "zod": "^4.0.0",
     "@crossdelta/infrastructure": "^0.16.0"
   },

package/schemas/service-types.schema.json

@@ -1,33 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "Service Types Configuration",
-  "description": "Configuration for different microservice types in the Platform SDK",
-  "type": "object",
-  "properties": {
-    "serviceTypes": {
-      "type": "object",
-      "additionalProperties": {
-        "type": "object",
-        "required": ["commandType", "entryPoint", "skipFiles"],
-        "properties": {
-          "commandType": {
-            "type": "string",
-            "description": "CLI command type for scaffolding (e.g., 'hono-micro', 'nest-micro')"
-          },
-          "entryPoint": {
-            "type": "string",
-            "description": "Relative path to the service entry point file"
-          },
-          "skipFiles": {
-            "type": "array",
-            "description": "Files that should not be overwritten by AI generation",
-            "items": {
-              "type": "string"
-            }
-          }
-        }
-      }
-    }
-  },
-  "required": ["serviceTypes"]
-}