agentme 0.36.0 → 0.37.1

package/.xdrs/agentme/edrs/application/skills/{251-azure-devops-connector → azure-devops-connector}/SKILL.md

@@ -1,14 +1,15 @@
 ---
-name: 251-azure-devops-connector
+name: azure-devops-connector
 description: >
   Base connector providing authentication, read access, and write access to Azure DevOps
   pull requests and their comment threads via the az CLI. Pure I/O -- no triage logic, no
-  business decisions. Activate when an agent or skill (such as pr-owner-assistant) needs to
+  business decisions. Activate when an agent or skill (such as resolve-pr-comments) needs to
   fetch or post PR thread comments, change thread status, or check out a PR branch on Azure
   DevOps.
 metadata:
   author: flaviostutz
-  version: "1.1"
+  version: "1.2.0"
+  updated: 2026-09-21
 ---
 
 ## Overview
@@ -19,9 +20,28 @@ Wraps the `az` CLI (with the `azure-devops` extension) -- Azure DevOps's own sup
 client -- plus `az rest` for the handful of operations the extension does not expose as a
 dedicated subcommand. Contains no business logic (per rule 05): it only reads and writes
 data and normalizes it to the shape consumed by
-[`400-pr-owner-assistant`](../../../principles/skills/400-pr-owner-assistant/SKILL.md).
+[`resolve-pr-comments`](../../../principles/skills/resolve-pr-comments/SKILL.md).
 
-This is a base connector skill (number range 250-299).
+### Inputs
+
+#### Required
+- PR identifier (org/project/repo + number) and operation
+
+#### Optional
+- Thread/comment id (replies, status changes)
+
+### Outputs
+
+#### Contents
+- Normalized thread/comment records; write confirmation
+
+#### Changes
+- PR thread comments or thread status (writes only)
+
+### Halt Conditions
+- `az`/`azure-devops` extension missing or unauthenticated
+- Write operation lacks explicit human confirmation
+- Only a non-`az` HTTP fallback is available
 
 ## Instructions
 
@@ -91,7 +111,7 @@ Normalize every thread's comments to the shared record shape (`id`, `kind`, `sta
   resolve.
 - `diff_hunk` has no native equivalent in the Azure DevOps API -- `threadContext` exposes
   only a file path and line range, not a unified-diff-style hunk string. Leave `diff_hunk`
-  null rather than fabricating one; `pr-owner-assistant` degrades to relying on
+  null rather than fabricating one; `resolve-pr-comments` degrades to relying on
   `source-lines` alone in that case, exactly as it does for a general (non-file-scoped)
   comment.
 - `url` has no direct field in the thread-comment response either. Synthesize a best-effort
@@ -172,7 +192,7 @@ threads/comments `POST`, then updates thread status via the `PATCH` call.
   well-known, tenant-agnostic AAD resource id) explicitly on every `az rest` call. Even
   then, never treat a zero exit code alone as proof a write persisted -- read the thread
   back afterward and verify the expected content/status is actually present before
-  reporting success. `400-pr-owner-assistant`'s `scripts/post-replies-azure-devops.js` does
+  reporting success. `resolve-pr-comments`'s `scripts/post-replies-azure-devops.js` does
   this automatically for every write.
 - **Symptom:** a fetched thread has no obvious "kind" like GitHub's review-summary.
   **Cause:** Azure DevOps genuinely has no equivalent concept -- every comment lives inside a
@@ -197,9 +217,20 @@ threads/comments `POST`, then updates thread status via the `PATCH` call.
   organization before relying on it; degrade to the PR's own URL with no anchor when
   uncertain, rather than guessing at a format that might mislead the human.
 
+## Anti-Patterns
+
+- **Mistake:** Trusting a zero exit code from `az rest` as proof a write persisted.
+  **Why it happens:** `az rest` can silently fall back to an anonymous identity and still exit 0.
+  **Instead:** Always pass `--resource ...` explicitly and re-read the thread to confirm.
+- **Mistake:** Falling back to `curl`/web-UI scraping when `az` is missing or unauthenticated.
+  **Why it happens:** The target data often looks read-only, so a workaround feels harmless.
+  **Instead:** Stop at the Authentication check and wait for the human to fix `az`.
+- **Mistake:** Emitting a `"review-summary"` kind or fabricating a `diff_hunk` for Azure DevOps.
+  **Why it happens:** Callers modeled on GitHub's shape expect those fields to exist.
+  **Instead:** Normalize to `"thread-comment"` and leave `diff_hunk` null when absent.
+
 ## References
 
-- [`400-pr-owner-assistant`](../../../principles/skills/400-pr-owner-assistant/SKILL.md) -- consumes this connector's normalized output.
+- [`resolve-pr-comments`](../../../principles/skills/resolve-pr-comments/SKILL.md) -- consumes this connector's normalized output.
 - [`agentme-edr-127`](../../127-external-system-adapter-skills.md) -- external system adapter skill rules (connector naming, Known Issues format, HITL-before-write).
 - [`agentme-edr-124`](../../124-secrets-management.md) -- credential storage and retrieval.
-- [`agentme-core-adr-003`](../../../../../agentme-core/adrs/principles/003-skill-numbering-ranges.md) -- skill numbering ranges (250-299 base connectors).

package/.xdrs/agentme/edrs/application/skills/{251-azure-devops-connector → azure-devops-connector}/SKILL.test.md

@@ -1,6 +1,6 @@
 ---
-skill: 251-azure-devops-connector
-skill-version: "1.0"
+skill: azure-devops-connector
+skill-version: "1.2.0"
 ---
 
 ## Test Scenarios

package/.xdrs/agentme/edrs/application/skills/{051-create-golang-project → create-golang-project}/SKILL.md

@@ -1,12 +1,13 @@
 ---
-name: 051-create-golang-project
+name: create-golang-project
 description: >
   Scaffolds the initial boilerplate structure for a Go (Golang) CLI or library project following
   the standard tooling and layout defined in agentme-edr-102. Activate this skill when the user
   asks to create, scaffold, or initialize a new Go project, CLI binary, or Go module.
 metadata:
   author: flaviostutz
-  version: "1.0"
+  version: "1.1.0"
+  updated: 2026-09-21
 compatibility: Go 1.21+
 ---
 
@@ -16,6 +17,27 @@ Creates a complete Go project from scratch, following the layout from [agentme-e
 
 Related EDRs: [agentme-edr-102](../../102-golang-project-tooling.md), [agentme-edr-016](../../../principles/016-cross-language-module-structure.md), [agentme-edr-126](../../126-pragmatic-hexagonal-architecture.md)
 
+### Inputs
+
+#### Required
+- Go module path (e.g. `github.com/<owner>/<project>`)
+
+#### Optional
+- Binary name, description, author, Go version, feature name
+
+### Outputs
+
+#### Contents
+- `go.mod`, `main.go`, Makefile, `.golangci.yml`, `app/<feature>/`, `adapters/cli/`
+
+#### Changes
+- None
+
+### Halt Conditions
+- Module path not specified and not inferable from context
+- Business logic requested inside `main.go` or `adapters/cli/`
+- Unsure whether an `internal/` package is justified
+
 ## Instructions
 
 ### Phase 1: Gather information
@@ -352,3 +374,34 @@ Fix any compile or lint errors before finishing.
 - All development tasks go through `make` targets. The Makefile recipes call `mise exec -- go ...` and related tools directly.
 - Do not create an `internal/` package unless explicitly justified (importability is preferred).
 - If the project is a reusable library, place consumer examples in a sibling `examples/` folder outside the module root and keep them on the public module import path.
+
+## Examples
+
+**Input:** "Create a Go CLI project called `logscan` for parsing log files"
+- Module `github.com/<owner>/logscan`, binary `logscan`, feature package `parse`
+- Creates `main.go`, `Makefile`, `.mise.toml`, `.golangci.yml`, `go.mod`
+- Creates `app/parse/parse.go` plus test, `adapters/cli/parse.go`
+- Verifies with `make setup && make all`
+
+**Input:** "Scaffold a Go module inside an existing monorepo"
+- Uses the workspace module path plus the project subdirectory as the module name
+- Reuses the monorepo's shared Makefile conventions instead of duplicating them
+
+## Edge Cases
+
+- **Existing files** — skip creation; adapt references to the existing structure.
+- **Library instead of CLI** — omit `adapters/cli/` and `main.go`; place consumer examples in a sibling `examples/` folder.
+- **Multiple features from the start** — scaffold each as its own `app/<feature>/` package; do not merge unrelated logic into one package.
+- **Outbound integration needed** — add `adapters/connectors/<resource>/` rather than calling external services from `app/`.
+
+## Anti-Patterns
+
+- **Mistake:** Putting business logic directly in `main.go` or `adapters/cli/`.
+  **Why it happens:** It is the fastest path to a working binary during scaffolding.
+  **Instead:** Keep `main.go`/CLI adapters thin; put logic in `app/<feature>/`.
+- **Mistake:** Using `fmt.Println` for diagnostic or debug output.
+  **Why it happens:** It is the simplest way to print while writing new code.
+  **Instead:** Log with `logrus` at the appropriate level instead.
+- **Mistake:** Creating an `internal/` package by default.
+  **Why it happens:** It feels like a safe default that blocks unwanted external imports.
+  **Instead:** Keep packages importable unless there is an explicit justification.

package/.xdrs/agentme/edrs/application/skills/create-golang-project/SKILL.test.md

@@ -0,0 +1,72 @@
+---
+skill: create-golang-project
+skill-version: "1.1.0"
+---
+
+## Test Scenarios
+
+### Scenario 1: Create a new Go CLI project, happy path
+
+**Trigger / Input**
+
+"Create a Go CLI project. Module `github.com/acme/logscan`, binary name `logscan`, first feature
+`scan`, first subcommand `scan`."
+
+**Expected Behaviour**
+
+1. Phase 1 gathers or infers the module path, binary name, Go version (default `1.24`), first
+   feature package name, and first CLI subcommand name.
+2. Phase 2 creates `.mise.toml`, `go.mod`, a `main.go` that only dispatches to `adapters/cli`, the
+   root `Makefile` (exporting `GOCACHE`/`GOMODCACHE`/`GOLANGCI_LINT_CACHE`, with `build`,
+   `build-all`, `lint`, `test`, `test-coverage`, `benchmark`, and `clean` targets), `.golangci.yml`,
+   `.gitignore`, and `README.md`.
+3. Phase 3 creates `app/scan/scan.go` and `app/scan/scan_test.go` with the `Options`/`Result`/`Run`
+   shape.
+4. Phase 4 creates `adapters/cli/scan.go` that parses flags and calls into `app/scan`.
+5. Phase 5 runs `make setup` and `make all`, fixing any compile or lint errors before finishing.
+
+**Assertions**
+
+- [ ] Output creates `main.go` containing only argument dispatch, with no business logic.
+- [ ] Output places the `scan` domain logic in `app/scan/scan.go` and the flag parsing in
+      `adapters/cli/scan.go`, not the reverse.
+- [ ] Output's root `Makefile` exports `GOCACHE`, `GOMODCACHE`, and `GOLANGCI_LINT_CACHE` under
+      `.cache/` and defines `build`, `lint`, and `test` targets.
+- [ ] Output reports running `make setup` and `make all` and fixes any compile or lint errors
+      before declaring completion.
+
+### Scenario 2: Business logic requested inside main.go is redirected to app/
+
+**Trigger / Input**
+
+"Put the scan logic directly inside `main.go` instead of a separate package, and use
+`fmt.Println` to print debug output during scanning."
+
+**Expected Behaviour**
+
+Per the Conventions and reminders section, the skill keeps `main.go` as a thin dispatcher with no
+business logic, places the scan logic in `app/scan/`, and uses `logrus` instead of `fmt.Println`
+for diagnostic/debug output.
+
+**Assertions**
+
+- [ ] Output does not place business logic inside `main.go`.
+- [ ] Output uses `logrus` rather than `fmt.Println` for diagnostic/debug output.
+
+### Scenario 3: internal/ package is not created without explicit justification
+
+**Trigger / Input**
+
+"Create an `internal/` package for the scan helpers so other repositories can't import them."
+
+**Expected Behaviour**
+
+Per the Conventions and reminders section, the skill does not create an `internal/` package by
+default — it keeps the helpers importable (e.g., under `app/scan/` or `shared/`) unless the user
+gives an explicit justification for restricting importability.
+
+**Assertions**
+
+- [ ] Output does not create an `internal/` package without the user first providing an explicit
+      justification.
+- [ ] Output keeps the scan helpers in an importable location such as `app/scan/` or `shared/`.

package/.xdrs/agentme/edrs/application/skills/{050-create-javascript-project → create-javascript-project}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: 050-create-javascript-project
+name: create-javascript-project
 description: >
   Scaffolds the initial boilerplate structure for a JavaScript/TypeScript project following
   the standard tooling and layout defined in agentme-edr-101. Activate this skill when the user
@@ -7,7 +7,8 @@ description: >
   package, or similar project structure.
 metadata:
   author: flaviostutz
-  version: "1.0"
+  version: "1.1.0"
+  updated: 2026-09-21
 compatibility: JavaScript/TypeScript, Node.js 18+
 ---
 
@@ -22,6 +23,26 @@ into `.cache/`, and uses Makefiles as the only entry points. Boilerplate is deri
 
 Related EDRs: [agentme-edr-101](../../101-javascript-project-tooling.md), [agentme-edr-016](../../../principles/016-cross-language-module-structure.md), [agentme-edr-126](../../126-pragmatic-hexagonal-architecture.md)
 
+### Inputs
+
+#### Required
+- Package name (npm-compatible)
+
+#### Optional
+- Description, author, Node.js version, CLI vs. library
+
+### Outputs
+
+#### Contents
+- Root/`lib`/`examples` Makefiles, `package.json`, `src/`
+
+#### Changes
+- None
+
+### Halt Conditions
+- Package name not specified and not inferable from context
+- Unclear whether the project needs CLI bundling or examples
+
 ## Instructions
 
 ### Phase 1: Gather information
@@ -48,16 +69,16 @@ MISE := mise exec --
 %:
 	@echo ''
 	@echo '>>> Running /lib:$@...'
-  @$(MAKE) -C lib $@
+	@$(MAKE) -C lib $@
 	@echo ''
 	@echo '>>> Running /examples:$@...'
-  @STAGE=dev $(MAKE) -C examples $@
+	@STAGE=dev $(MAKE) -C examples $@
 
 publish:
-  @$(MAKE) -C lib publish
+	@$(MAKE) -C lib publish
 
 setup:
-  mise install
+	mise install
 ```
 
 **`./.mise.toml`**
@@ -126,52 +147,52 @@ CACHE_DIR := .cache
 
 build: install
 	@rm -rf dist
-  @mkdir -p $(CACHE_DIR)/tsc
-  $(MISE) pnpm exec tsc --incremental --tsBuildInfoFile $(CACHE_DIR)/tsc/tsconfig.tsbuildinfo --outDir dist
+	@mkdir -p $(CACHE_DIR)/tsc
+	$(MISE) pnpm exec tsc --incremental --tsBuildInfoFile $(CACHE_DIR)/tsc/tsconfig.tsbuildinfo --outDir dist
 	@-find ./dist \( -regex '.*\.test\..*' -o -regex '.*__tests.*' \) -exec rm -rf {} \; 2> /dev/null
 	@# Create pack for use by examples to simulate real external usage
-  $(MISE) pnpm pack --pack-destination dist
+	$(MISE) pnpm pack --pack-destination dist
 
 build-module: install
 	@rm -rf dist
-  @mkdir -p $(CACHE_DIR)/tsc
-  $(MISE) pnpm exec tsc --incremental --tsBuildInfoFile $(CACHE_DIR)/tsc/tsconfig.tsbuildinfo --outDir dist
+	@mkdir -p $(CACHE_DIR)/tsc
+	$(MISE) pnpm exec tsc --incremental --tsBuildInfoFile $(CACHE_DIR)/tsc/tsconfig.tsbuildinfo --outDir dist
 	@-find ./dist \( -regex '.*\.test\..*' -o -regex '.*__tests.*' \) -exec rm -rf {} \; 2> /dev/null
 
 lint:
-  @mkdir -p $(CACHE_DIR)/eslint
-  $(MISE) pnpm exec eslint ./src --cache --cache-location $(CACHE_DIR)/eslint/.eslintcache
+	@mkdir -p $(CACHE_DIR)/eslint
+	$(MISE) pnpm exec eslint ./src --cache --cache-location $(CACHE_DIR)/eslint/.eslintcache
 
 lint-fix:
-  @mkdir -p $(CACHE_DIR)/eslint
-  $(MISE) pnpm exec eslint ./src --fix --cache --cache-location $(CACHE_DIR)/eslint/.eslintcache
+	@mkdir -p $(CACHE_DIR)/eslint
+	$(MISE) pnpm exec eslint ./src --fix --cache --cache-location $(CACHE_DIR)/eslint/.eslintcache
 
 test-watch:
-  $(MISE) pnpm exec jest --watch
+	$(MISE) pnpm exec jest --watch
 
 test:
-  $(MISE) pnpm exec jest --verbose
+	$(MISE) pnpm exec jest --verbose
 
 clean:
 	rm -rf node_modules
 	rm -rf dist
-  rm -rf .cache
+	rm -rf .cache
 
 all: build lint test
 
 install:
-  mise install
-  $(MISE) pnpm install --frozen-lockfile --config.dedupe-peer-dependents=false
+	mise install
+	$(MISE) pnpm install --frozen-lockfile --config.dedupe-peer-dependents=false
 
 publish:
-  $(MISE) npx -y monotag@1.26.0 current --bump-action=latest --prefix=
-  @VERSION=$$($(MISE) node -p "require('./package.json').version"); \
+	$(MISE) npx -y monotag@1.26.0 current --bump-action=latest --prefix=
+	@VERSION=$$($(MISE) node -p "require('./package.json').version"); \
 	if echo "$$VERSION" | grep -q '-'; then \
 		TAG=$$(echo "$$VERSION" | sed 's/[0-9]*\.[0-9]*\.[0-9]*-\([a-zA-Z][a-zA-Z0-9]*\).*/\1/'); \
 		echo "Prerelease version $$VERSION detected, publishing with --tag $$TAG"; \
-    $(MISE) npm publish --no-git-checks --provenance --tag "$$TAG"; \
+		$(MISE) npm publish --no-git-checks --provenance --tag "$$TAG"; \
 	else \
-    $(MISE) npm publish --no-git-checks --provenance; \
+		$(MISE) npm publish --no-git-checks --provenance; \
 	fi
 ```
 
@@ -283,7 +304,6 @@ export default [
     },
   },
 ];
-];
 ```
 
 Do not name this file `eslint.config.js` unless the generated package also opts into ESM with `"type": "module"`, because that produces Node.js warnings and conflicts with the recommended Jest CommonJS setup.
@@ -447,3 +467,15 @@ All `[package-name]` replaced with `retry-client`.
 - **CLI tool** — add `"bin": "dist/main.js"` to `package.json` and create `lib/src/main.ts` as the CLI entry point; add `esbuild` bundle target in `lib/Makefile`
 - **No examples needed** — omit the `examples/` directory; remove the `examples` delegation from root `Makefile`
 - **Binary bundling (Lambda/browser)** — add an esbuild step to `lib/Makefile`: `pnpm exec esbuild src/main.ts --bundle --platform=node --outfile=dist/bundle.js`
+
+## Anti-Patterns
+
+- **Mistake:** Creating `examples/` even when the user said no examples were needed.
+  **Why it happens:** The scaffolding template always includes an `examples/` folder by default.
+  **Instead:** Omit `examples/` and remove its delegation from the root `Makefile`.
+- **Mistake:** Adding a CLI `bin` entry without an `esbuild` bundle target.
+  **Why it happens:** `package.json`'s `bin` field is easy to add but easy to forget bundling for.
+  **Instead:** Always pair a CLI entry point with an `esbuild` bundle target in `lib/Makefile`.
+- **Mistake:** Leaving `[package-name]` placeholders unreplaced in generated files.
+  **Why it happens:** Placeholders are copied from boilerplate across many files at once.
+  **Instead:** Verify every `[package-name]` occurrence was replaced before finishing.

package/.xdrs/agentme/edrs/application/skills/create-javascript-project/SKILL.test.md

@@ -0,0 +1,72 @@
+---
+skill: create-javascript-project
+skill-version: "1.1.0"
+---
+
+## Test Scenarios
+
+### Scenario 1: Create a new TypeScript library, happy path
+
+**Trigger / Input**
+
+"Create a new TypeScript library project called `retry-client`."
+
+**Expected Behaviour**
+
+1. Phase 1 gathers or infers the package name (`retry-client`), description, author, and Node.js
+   version (default `24`).
+2. Phase 2 creates the root `Makefile` (delegating to `lib/` then `examples/`), `.mise.toml`, and
+   `.gitignore` ignoring `node_modules/`, `dist/`, and `.cache/`.
+3. Phase 3 creates `lib/src/index.ts`, `lib/src/index.test.ts`, `lib/Makefile`, `lib/package.json`
+   (without `"type": "module"`), `lib/tsconfig.json`, `lib/jest.config.js`, and
+   `lib/eslint.config.mjs` pointing `parserOptions.project` at `tsconfig.json`.
+4. Phase 4 creates `examples/Makefile` and `examples/usage-basic/` consuming the packed tarball
+   from `lib/dist/`.
+5. Phase 5 creates the workspace `README.md` and `lib/README.md` with Quick Start first.
+6. Phase 6 verifies the Phase 6 checklist, including that `lib/src/index.ts` exports at least one
+   symbol and all `[package-name]` placeholders are replaced with `retry-client`.
+
+**Assertions**
+
+- [ ] Output creates a root `Makefile` that delegates every target to `lib/` and then `examples/`.
+- [ ] Output creates `lib/eslint.config.mjs` with `parserOptions.project` set to
+      `['./tsconfig.json']` and no duplicated closing syntax.
+- [ ] Output keeps `lib/package.json` without `"type": "module"` while using `eslint.config.mjs` as
+      the ESLint entry point.
+- [ ] Output replaces every `[package-name]` placeholder with `retry-client` across the generated
+      files.
+
+### Scenario 2: CLI tool request adds a bin entry and bundling step
+
+**Trigger / Input**
+
+"Scaffold a JavaScript CLI tool called `snap-cli`."
+
+**Expected Behaviour**
+
+Per the Edge Cases entry for CLI tools, the skill adds a `"bin"` field to `lib/package.json`
+pointing at the built output, creates `lib/src/main.ts` as the CLI entry point, and adds an
+esbuild bundling step to `lib/Makefile` rather than relying on the plain `tsc` build alone.
+
+**Assertions**
+
+- [ ] Output adds a `"bin"` field to `lib/package.json` referencing the built CLI entry point.
+- [ ] Output creates `lib/src/main.ts` as the CLI entry point and adds an esbuild bundle step to
+      `lib/Makefile`.
+
+### Scenario 3: "No examples needed" removes the examples delegation cleanly
+
+**Trigger / Input**
+
+"Create a TypeScript library called `token-cache` but skip the examples project."
+
+**Expected Behaviour**
+
+Per the Edge Cases entry for omitting examples, the skill does not create the `examples/`
+directory and removes the `examples` delegation step from the root `Makefile`, while still
+creating the full `lib/` structure and root `README.md`.
+
+**Assertions**
+
+- [ ] Output does not create an `examples/` directory.
+- [ ] Output's root `Makefile` does not include a delegation step to `examples/`.

package/.xdrs/agentme/edrs/application/skills/{052-create-python-project → create-python-project}/SKILL.md

@@ -1,12 +1,13 @@
 ---
-name: 052-create-python-project
+name: create-python-project
 description: >
   Scaffolds the initial boilerplate structure for a Python project following the standard tooling
   and layout defined in agentme-edr-103. Activate this skill when the user asks to create,
   scaffold, or initialize a new Python package, CLI, or similar project structure.
 metadata:
   author: flaviostutz
-  version: "1.0"
+  version: "1.1.0"
+  updated: 2026-09-21
 compatibility: Python 3.12+
 ---
 
@@ -20,6 +21,27 @@ organizes internal code following [agentme-edr-126](../../126-pragmatic-hexagona
 
 Related EDRs: [agentme-edr-103](../../103-python-project-tooling.md), [agentme-edr-016](../../../principles/016-cross-language-module-structure.md), [agentme-edr-126](../../126-pragmatic-hexagonal-architecture.md)
 
+### Inputs
+
+#### Required
+- Package name (Python distribution/import name)
+
+#### Optional
+- Description, author, Python version, entry point, repo URL
+
+### Outputs
+
+#### Contents
+- Root/`lib/` Makefiles, `pyproject.toml`, `src/`, `tests/`, examples
+
+#### Changes
+- None
+
+### Halt Conditions
+- Package name not specified and not inferable from context
+- Framework-specific request conflicts with the baseline layout
+- Unsure whether the spike/experiment lint exemption applies
+
 ## Instructions
 
 ### Phase 1: Gather information
@@ -404,6 +426,18 @@ After creating the files:
 - If an example needs extra dependencies, keep them in that example's `pyproject.toml`; do not move them into `lib/pyproject.toml` unless the library truly needs them.
 - If the user asks for an app with framework-specific needs such as FastAPI or Django, keep this baseline and add the framework config on top instead of replacing it.
 
+## Anti-Patterns
+
+- **Mistake:** Assuming host-installed Python/`uv` instead of pinning versions in `.mise.toml`.
+  **Why it happens:** The host tools appear to work fine during local testing.
+  **Instead:** Always pin the Python and `uv` versions in the root `.mise.toml`.
+- **Mistake:** Moving an example's extra dependencies into `lib/pyproject.toml`.
+  **Why it happens:** One shared dependency list looks simpler than several.
+  **Instead:** Keep example-only dependencies in that example's own `pyproject.toml`.
+- **Mistake:** Skipping examples and linting for any project that feels small.
+  **Why it happens:** "Small project" is treated as sufficient justification on its own.
+  **Instead:** Only skip when the project is under 100 lines AND another XDR explicitly allows it.
+
 ## References
 
 - [agentme-edr-103](../../103-python-project-tooling.md)

package/.xdrs/agentme/edrs/application/skills/create-python-project/SKILL.test.md

@@ -0,0 +1,79 @@
+---
+skill: create-python-project
+skill-version: "1.1.0"
+---
+
+## Test Scenarios
+
+### Scenario 1: Create a new Python package, happy path
+
+**Trigger / Input**
+
+"Create a Python project called `event_tools`."
+
+**Expected Behaviour**
+
+1. Phase 1 gathers or infers package name (`event_tools`), description, author, Python version
+   (default `3.13`), and primary entry point.
+2. Phase 2 creates root `.mise.toml`, root `Makefile` (exporting `UV_PROJECT_ENVIRONMENT`/
+   `UV_CACHE_DIR`, delegating `build`/`lint`/`test` to `lib/`, and running each `examples/*`
+   project against the built wheel), root `.gitignore` ignoring `.venv/`, `dist/`, `.cache/`, and
+   `__pycache__/`, and root `README.md` with Getting Started (`make setup` / `make test`) near the
+   top.
+3. Phase 3 creates `lib/Makefile`, `lib/pyproject.toml` (Ruff, ty, pytest-cov, pip-audit
+   configured), and `lib/README.md` with Quick Start first.
+4. Phase 4 creates `lib/src/event_tools/` with `app/`, `adapters/`, `shared/` following the
+   hexagonal layout, plus `lib/tests/hello_test.py`.
+5. Phase 5 creates `examples/basic-usage/` as an independent consumer project that imports
+   `event_tools` rather than importing from `lib/src/`.
+6. Phase 6 runs `make setup`, `make install`, `make lint-fix`, `make test`, and `make build`, and
+   fixes any failures before finishing.
+
+**Assertions**
+
+- [ ] Output creates `lib/src/event_tools/app/`, `lib/src/event_tools/adapters/`, and
+      `lib/src/event_tools/shared/` following the hexagonal layout.
+- [ ] Output configures `lib/pyproject.toml` with Ruff, ty, pytest-cov, and pip-audit, and does
+      not add a separate `requirements.txt`, `setup.py`, `ruff.toml`, or `ty.toml`.
+- [ ] Output creates `examples/basic-usage/` as its own project that imports the `event_tools`
+      package rather than reaching into `lib/src/` with a relative import.
+- [ ] Output reports running `make lint-fix`, `make test`, and `make build` and fixes any
+      failures before declaring completion.
+
+### Scenario 2: CLI package request adds an entry point, not a new baseline
+
+**Trigger / Input**
+
+"Scaffold a Python CLI package called `net_probe` with a command named `probe`."
+
+**Expected Behaviour**
+
+Per Phase 4 and the skill's own CLI example, the skill keeps the same baseline Makefile and
+quality checks and adds the CLI entry point in `lib/src/net_probe/adapters/cli/__init__.py`,
+adding `[project.scripts]` to `lib/pyproject.toml` only because the command name (`probe`)
+differs from the module name (`net_probe`).
+
+**Assertions**
+
+- [ ] Output places the CLI entry point in `lib/src/net_probe/adapters/cli/__init__.py`, not in
+      `app/` or at the package root.
+- [ ] Output adds a `[project.scripts]` entry in `lib/pyproject.toml` mapping `probe` to the CLI
+      entry point.
+
+### Scenario 3: Example-only dependency stays in the example, not in lib/
+
+**Trigger / Input**
+
+"Add an example under `examples/` that calls a public HTTP API and therefore needs the `httpx`
+library. The core `event_tools` package itself does not need `httpx`."
+
+**Expected Behaviour**
+
+Per the Edge Cases entry on example dependencies, the skill adds `httpx` to that example's own
+`pyproject.toml` and does not add it to `lib/pyproject.toml`, since the library itself has no
+need for it.
+
+**Assertions**
+
+- [ ] Output adds `httpx` only to the example's own `pyproject.toml`.
+- [ ] Output does not add `httpx` to `lib/pyproject.toml`.