skilldrop-cli 0.16.17 → 0.16.19

package/packs/stakeholder-comms/skills/guide-builder/templates/api-reference.md

@@ -1,120 +0,0 @@
-# {API / event stream name} — Developer reference
-
-**Base URL:** `{https://api.example.com/v1}`
-**Auth:** {e.g. "Bearer token in `Authorization` header; obtain via …"}
-**Versioning:** {e.g. "URL-path `/v1`; breaking changes ship a new path. See Changelog."}
-**Content type:** `application/json` unless stated.
-
-## Conventions
-
-These apply to every endpoint/event below — read once, don't repeat per item.
-
-- **Errors** return this shape:
-  ```json
-  { "error": { "code": "string", "message": "human-readable", "details": {} } }
-  ```
-- **Pagination:** {e.g. "cursor-based: pass `?cursor=`; response includes `next_cursor` (null on last page)"}
-- **Idempotency:** {e.g. "mutating calls accept an `Idempotency-Key` header; replays within 24h return the original result"}
-- **Rate limits:** {e.g. "600 req/min/token; `429` with `Retry-After` when exceeded"}
-- **Timestamps:** ISO 8601 UTC (`2026-05-26T14:30:00Z`).
-
----
-
-## Endpoints
-
-### `{METHOD} /{path}` — {one-line purpose}
-
-{One sentence on when a consumer calls this.}
-
-**Auth:** {required scope/role, or "none"}
-
-**Path / query params**
-
-| Param | In | Type | Required | Description |
-|---|---|---|---|---|
-| `{id}` | path | string | yes | {…} |
-| `{limit}` | query | integer | no | {default, max} |
-
-**Request body**
-
-| Field | Type | Required | Description |
-|---|---|---|---|
-| `{field}` | string | yes | {…} |
-| `{field}` | integer | no | {default} |
-
-```json
-{ "field": "value", "field2": 42 }
-```
-
-**Response `200`**
-
-| Field | Type | Description |
-|---|---|---|
-| `{id}` | string | {…} |
-| `{status}` | enum(`a`,`b`) | {…} |
-
-```json
-{ "id": "abc_123", "status": "a", "created_at": "2026-05-26T14:30:00Z" }
-```
-
-**Errors**
-
-| Status | `error.code` | When |
-|---|---|---|
-| `400` | `invalid_request` | {…} |
-| `404` | `not_found` | {…} |
-| `409` | `conflict` | {…} |
-
-```json
-{ "error": { "code": "not_found", "message": "No resource with id abc_123" } }
-```
-
----
-
-## Events / messages
-
-For each event a consumer subscribes to.
-
-### `{event.name}` — {one-line: what happened}
-
-- **Emitted when:** {the trigger}
-- **Transport:** {e.g. "Kafka topic `orders.v1`" / "webhook POST to your callback URL" / "SNS topic ARN …"}
-- **Delivery:** {e.g. "at-least-once; consumers MUST be idempotent on `event_id`"}
-- **Ordering:** {e.g. "ordered per `partition_key = order_id`; no global order"}
-
-**Payload**
-
-| Field | Type | Required | Description |
-|---|---|---|---|
-| `event_id` | string (uuid) | yes | dedup key |
-| `occurred_at` | string (ISO 8601) | yes | when the fact happened (not when delivered) |
-| `data.{field}` | string | yes | {…} |
-
-```json
-{
-  "event_id": "evt_01HX...",
-  "type": "{event.name}",
-  "occurred_at": "2026-05-26T14:30:00Z",
-  "data": { "order_id": "ord_123", "amount_cents": 4999 }
-}
-```
-
-**Consumer notes:** {what a subscriber must handle — out-of-order arrival, schema evolution, poison messages}
-
----
-
-## Error code catalog
-
-| `error.code` | Meaning | Consumer action |
-|---|---|---|
-| `invalid_request` | malformed input | fix and retry; don't blind-retry |
-| `rate_limited` | over quota | back off per `Retry-After` |
-| `conflict` | idempotency or state clash | inspect existing resource |
-| {…} | … | … |
-
-## Changelog
-
-| Version / date | Change | Breaking? |
-|---|---|---|
-| `v1` — {YYYY-MM-DD} | initial | — |
-| {…} | … | yes/no |

package/packs/stakeholder-comms/skills/guide-builder/templates/design-walkthrough.md

@@ -1,72 +0,0 @@
-# {System / feature} — How it works
-
-**Who this is for:** {e.g. "an engineer joining the payments team" / "an adjacent team integrating with us"}
-**After reading, you'll be able to:** {concrete capability — "trace a checkout request end-to-end and know which service owns each step"}
-**Status:** describes the system as built on {YYYY-MM-DD}. For *why we chose this design*, see {link to ADRs / design-doc}.
-
-## The mental model
-
-{One paragraph or one diagram. The single idea a reader must hold to understand everything below — e.g. "Every write goes through the command bus; reads come straight from a denormalized view. Nothing reads the write tables directly."}
-
-```
-{Optional ASCII or Mermaid sketch — or link to an architecture-diagrams output. Keep it to the load-bearing boxes and arrows, not every box.}
-```
-
-## Components
-
-What each piece does and why it exists — not how to deploy it.
-
-| Component | Responsibility | Why it's separate |
-|---|---|---|
-| {name} | {one line — what it owns} | {what would break if it were merged into its neighbour} |
-| {…} | … | … |
-
-## How a {request / event / job} flows through
-
-Trace one representative path step by step. This is the heart of the walkthrough.
-
-1. **{Entry point}** — {what happens, which component, what data} → `{file or module:fn}`
-2. **{Next hop}** — {…} → `{file:fn}`
-3. **{…}** — {…}
-4. **{Result}** — {what the caller gets back / what side effect lands}
-
-> Trace it yourself: {how to watch this flow live — a log query, a trace ID, a debug endpoint}.
-
-## Key design decisions (and why)
-
-The non-obvious choices a reader will otherwise undo by accident.
-
-- **{Decision}** — {why; what was rejected}. {Link to the ADR if one exists.}
-- **{Decision}** — {…}
-
-## Data & state
-
-- **Source of truth:** {where the canonical data lives}
-- **Derived / cached:** {what's a projection of it, and how it's kept in sync}
-- **What's NOT persisted:** {e.g. "session state is in memory; a restart drops it — by design"}
-
-## Where the code lives
-
-| Concern | Path | Notes |
-|---|---|---|
-| {entry points / routes} | `{path}` | {…} |
-| {core logic} | `{path}` | start here when reading |
-| {data layer} | `{path}` | … |
-| {tests worth reading first} | `{path}` | the integration tests document the contract |
-
-## Making common changes
-
-How to do the things a new contributor will need in week one.
-
-- **Add a {new endpoint / event / field}:** {the 2–4 places to touch, in order}
-- **Change {common thing}:** {…}
-
-## Gotchas / sharp edges
-
-- ⚠️ {Non-obvious constraint that will bite — "the queue is at-least-once; handlers must be idempotent"}
-- ⚠️ {…}
-
-## Glossary
-
-- **{Term}** — {definition in this system's context, not the generic one}
-- **{Term}** — {…}

package/packs/stakeholder-comms/skills/guide-builder/templates/setup-guide.md

@@ -1,109 +0,0 @@
-# {Project / component} — Setup guide
-
-**Goal:** {one sentence — the end state, e.g. "Run the API locally with a seeded database and answer a request on `localhost:3000`."}
-**Time:** ~{N} minutes
-**You'll have at the end:** {concrete artifact — "a running server, a seeded DB, and a passing health check"}
-
-## Placeholders used in this guide
-
-Replace these everywhere they appear. Nothing else is a placeholder.
-
-| Placeholder | What to put | Where to get it |
-|---|---|---|
-| `<YOUR_API_KEY>` | {what it is} | {where to obtain it} |
-| `<DB_PASSWORD>` | {what it is} | {…} |
-
-## Prerequisites
-
-Check each before starting — a failed setup is almost always a missing prerequisite.
-
-| Need | Version | Check it | If missing |
-|---|---|---|---|
-| {Node / Python / Docker / …} | `>= {x.y}` | `node --version` | {install link / command} |
-| {…} | … | `…` | … |
-
-## Steps
-
-### 1. {Imperative — e.g. "Clone the repo and enter it"}
-
-```bash
-git clone {repo-url} && cd {repo-dir}
-```
-
-**You should see:** {what success looks like — e.g. "a `package.json` in the directory: `ls package.json`"}
-
-### 2. {Imperative — e.g. "Install dependencies"}
-
-```bash
-{exact command — e.g. `npm ci`}
-```
-
-**You should see:** {e.g. "`added 412 packages` with no errors"}
-
-### 3. {Imperative — e.g. "Configure environment"}
-
-```bash
-cp .env.example .env
-# then set:
-#   API_KEY=<YOUR_API_KEY>
-#   DB_PASSWORD=<DB_PASSWORD>
-```
-
-**You should see:** {e.g. "`.env` exists and has no remaining `<…>` placeholders: `grep '<' .env` returns nothing"}
-
-### 4. {Imperative — e.g. "Start dependencies"}
-
-```bash
-{e.g. `docker compose up -d postgres`}
-```
-
-**You should see:** {e.g. "`docker compose ps` shows postgres as `healthy`"}
-
-### 5. {Imperative — e.g. "Run migrations and seed"}
-
-```bash
-{e.g. `npm run db:migrate && npm run db:seed`}
-```
-
-**You should see:** {e.g. "`Migrations complete (3 applied)` and `Seeded 12 rows`"}
-
-### 6. {Imperative — e.g. "Start the service"}
-
-```bash
-{e.g. `npm run dev`}
-```
-
-**You should see:** {e.g. "`Listening on http://localhost:3000`"}
-
-## Verify it works
-
-One end-to-end check that proves the whole setup, not just the last step.
-
-```bash
-{e.g. `curl -s localhost:3000/health`}
-```
-
-**Expected:** {e.g. `{"status":"ok","db":"connected"}`}
-
-If you get this, you're done.
-
-## Troubleshooting
-
-| Symptom | Likely cause | Fix |
-|---|---|---|
-| {exact error text} | {what's actually wrong} | {command or step to fix} |
-| `ECONNREFUSED ...:5432` | Postgres not up yet | Re-run step 4; wait for `healthy` |
-| {…} | … | … |
-
-## Teardown
-
-```bash
-{e.g. `docker compose down -v`}
-```
-
-Removes {what — "containers and the local volume; your `.env` is left intact"}.
-
-## Next steps
-
-- {Where to go now — "Run the test suite: `npm test`"}
-- {Link to the design walkthrough or API reference for this project, if one exists}