@jaypie/mcp 0.8.189 → 0.8.190

package/dist/assets.js

@@ -55,11 +55,11 @@ function getMcpAssetPaths() {
  */
 function getMcpBuildInfo() {
     return {
-        commit: "5569d996"
+        commit: "c95f849f"
             ,
-        version: "0.8.189"
+        version: "0.8.190"
             ,
-        versionString: "@jaypie/mcp@0.8.189#5569d996"
+        versionString: "@jaypie/mcp@0.8.190#c95f849f"
             ,
     };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jaypie/mcp",
-  "version": "0.8.189",
+  "version": "0.8.190",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/mcp/0.8.190.md

@@ -0,0 +1,11 @@
+---
+version: 0.8.190
+date: 2026-10-14
+summary: Skills agree on packages/cdk as the CDK package directory
+---
+
+## Changes
+
+- **Skills**: `monorepo`, `cdk`, `cicd-actions`, `cicd-deploy`, `dynamodb`, and `jaypie` name `packages/cdk` as the single location for the CDK package (#623)
+- **`monorepo`**: drops `stacks` as a workspace directory name; limits `workspaces/` to repositories whose `packages/` publish to npm; notes that the root `package.json` and vitest globs cover `packages/*` only
+- **`cicd-actions`**: `cdk-deploy` defaults `working-directory` to `packages/cdk`; `web-deploy` defaults to `packages/cdk/cdk-outputs.json` and `packages/web/dist`

package/skills/cdk.md

@@ -107,10 +107,10 @@ new JaypieSesIntake(this, "Intake", {
 
 ## Stack Structure
 
-Organize stacks in the `workspaces/` directory:
+The CDK package lives at `packages/cdk`, alongside every other workspace (see `skill("monorepo")`):
 
 ```
-workspaces/
+packages/
 ├── cdk/
 │   ├── src/
 │   │   ├── app.ts        # CDK app entry

package/skills/cicd-actions.md

@@ -194,7 +194,6 @@ runs:
         path: |
           node_modules
           packages/*/node_modules
-          workspaces/*/node_modules
         key: ${{ runner.os }}-node-${{ inputs.node-version }}-${{ hashFiles('**/package-lock.json') }}
         restore-keys: |
           ${{ runner.os }}-node-${{ inputs.node-version }}-
@@ -205,8 +204,7 @@ runs:
       with:
         path: |
           packages/*/dist
-          workspaces/*/dist
-          workspaces/*/.open-next
+          packages/*/.open-next
         key: ${{ runner.os }}-build-${{ github.sha }}
         restore-keys: |
           ${{ runner.os }}-build-
@@ -262,7 +260,7 @@ inputs:
   working-directory:
     description: 'Working directory for CDK commands'
     required: false
-    default: 'workspaces/cdk'
+    default: 'packages/cdk'
   require-approval:
     description: 'CDK approval mode (never, any-change, broadening)'
     required: false
@@ -310,7 +308,7 @@ inputs:
   outputs-file:
     description: 'Path to cdk-outputs.json produced by cdk deploy'
     required: false
-    default: 'workspaces/cdk/cdk-outputs.json'
+    default: 'packages/cdk/cdk-outputs.json'
   prefix:
     description: 'Output name prefix when exportOutputs({ prefix }) was used (e.g., "App")'
     required: false
@@ -318,7 +316,7 @@ inputs:
   source:
     description: 'Directory of built assets to sync'
     required: false
-    default: 'workspaces/web/dist'
+    default: 'packages/web/dist'
   region:
     description: 'AWS region'
     required: false

package/skills/cicd-deploy.md

@@ -261,7 +261,7 @@ jobs:
 
 CDK provisions a `JaypieWebDeploymentBucket`; it does not fill it. Jaypie avoids `s3deploy.BucketDeployment`, so shipping content is a workflow step:
 
-1. `cdk-deploy` deploys the bucket, distribution, and deploy role, and writes `workspaces/cdk/cdk-outputs.json`.
+1. `cdk-deploy` deploys the bucket, distribution, and deploy role, and writes `packages/cdk/cdk-outputs.json`.
 2. `web-deploy` reads `DestinationBucketName`, `DestinationBucketDeployRoleArn`, and `DistributionId` from that file.
 3. `web-deploy` assumes the deploy role, syncs the built assets, and invalidates the distribution.
 
@@ -278,7 +278,7 @@ See `skill("cicd-actions")` for the `web-deploy` action body and `skill("web")`
 `JaypieStack` names every stack `cdk-{PROJECT_SPONSOR}-{PROJECT_KEY}-{PROJECT_ENV}-{PROJECT_NONCE}[-{key}]` and resolves the account and region (see `skill("cdk")`). Do not compose stack names in `app.ts`:
 
 ```typescript
-// workspaces/cdk/src/app.ts
+// packages/cdk/src/app.ts
 import { App } from "aws-cdk-lib";
 import { JaypieAppStack } from "@jaypie/constructs";
 

package/skills/dynamodb.md

@@ -550,7 +550,7 @@ registerModel({ model: "session", indexes: [fabricIndex()], ttl: "30 days" });
 ```
 
 ```typescript
-// workspaces/cdk/lib/data-stack.ts
+// packages/cdk/lib/data-stack.ts
 import "@project/models"; // registers models
 import { JaypieDynamoDb } from "@jaypie/constructs";
 import { getAllRegisteredIndexes } from "@jaypie/fabric";

package/skills/jaypie.md

@@ -50,11 +50,10 @@ Jaypie projects use npm workspaces:
 
 ```
 project/
-├── packages/           # npm packages
+├── packages/           # npm workspaces
 │   ├── api/           # Express API
+│   ├── cdk/           # CDK app
 │   └── lib/           # Shared library
-├── workspaces/        # CDK infrastructure
-│   └── cdk/           # CDK app
 └── package.json       # Root workspace config
 ```
 

package/skills/monorepo.md

@@ -135,8 +135,12 @@ npm install --save-dev @jaypie/eslint @jaypie/repokit @jaypie/testkit eslint vit
 
 | Directory | Purpose |
 |-----------|---------|
-| `packages/` | npm packages (default workspace) |
-| `workspaces/` | CDK-deployed infrastructure and sites |
+| `packages/` | Default for every workspace: npm packages, the CDK package (`packages/cdk`), and sites (`packages/web`) |
+| `workspaces/` | Only in a repository whose `packages/` publish to npm: the unpublished workspaces that manage them (`workspaces/cdk`, `workspaces/documentation`) |
+
+Use `packages/cdk` unless the repository publishes its packages to npm. The Jaypie repository itself is the `workspaces/` case: `packages/` holds the published libraries and `workspaces/` holds the CDK app and documentation site that deploy around them.
+
+`packages/cdk` is the default the `cdk`, `cicd-actions`, and `cicd-deploy` skills assume. The root `package.json` scripts and the vitest `test.projects` glob cover `packages/*` only, so a repository that adds `workspaces/` must pass `workspaces/cdk` to the `cdk-deploy` and `web-deploy` inputs, and its workspaces fall out of `build`, `clean`, `format:package`, `test`, and `typecheck` until every one of those globs names it.
 
 ## Scripts Reference
 
@@ -164,10 +168,9 @@ npm install --save-dev @jaypie/eslint @jaypie/repokit @jaypie/testkit eslint vit
 - etc: configurations
 - lib: usually within a src directory, modules of encapsulated logic that could be refactored out later
 - LOCAL: human local scratch directory, include in gitignore
-- packages: default and preferred name for NPM workspaces; always use for packages publishing to NPM
-- stacks: allowed name for NPM workspaces that publish via CDK
+- packages: default directory for NPM workspaces, including the CDK package (`packages/cdk`); always use for packages publishing to NPM
 - templates: usually CloudFormation
-- workspaces: allowed name for NPM workspace that do not publish
+- workspaces: unpublished workspaces (CDK, sites) in a repository whose packages publish to NPM
 - var: agent and machine local scratch directory, include in gitignore
 
 ### Discouraged Folder Names