@caddis/cli 0.4.93 → 0.4.95
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bundles/antigravity-plugin/guard_agy.py +6 -2
- package/bundles/antigravity-plugin/plugin.json +1 -1
- package/bundles/antigravity-plugin/repo_freshness.py +71 -6
- package/bundles/antigravity-plugin/repo_hygiene.py +516 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_exit.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_file_lock.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_frontmatter.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_redact.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_roadmap.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_rows.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_status.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_tidy.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_todo.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_workstreams.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/__pycache__/caddis_worktree_safety.cpython-311.pyc +0 -0
- package/bundles/antigravity-plugin/scripts/caddis_finished.py +537 -0
- package/bundles/antigravity-plugin/scripts/caddis_guide.json +9 -8
- package/bundles/antigravity-plugin/scripts/caddis_own_cleanup.py +23 -248
- package/bundles/antigravity-plugin/scripts/caddis_prepush_config.py +222 -0
- package/bundles/antigravity-plugin/scripts/caddis_repo_tidy.py +240 -0
- package/bundles/antigravity-plugin/scripts/caddis_tidy.py +12 -0
- package/bundles/antigravity-plugin/scripts/caddis_worktree_root.py +111 -2
- package/bundles/antigravity-plugin/scripts/setup_project_ai.py +703 -174
- package/bundles/antigravity-plugin/skills/_registry.md +4 -4
- package/bundles/antigravity-plugin/skills/adopt-app/SKILL.md +2 -5
- package/bundles/antigravity-plugin/skills/cloud-phases/SKILL.md +1 -1
- package/bundles/antigravity-plugin/skills/dashboard-perf-sweep/SKILL.md +1 -1
- package/bundles/antigravity-plugin/skills/db-diagram/SKILL.md +1 -1
- package/bundles/antigravity-plugin/skills/explainer-doc/SKILL.md +1 -1
- package/bundles/antigravity-plugin/skills/implement/SKILL.md +4 -0
- package/bundles/antigravity-plugin/skills/port-to-github/SKILL.md +2 -5
- package/bundles/antigravity-plugin/skills/pr-merge/SKILL.md +1 -1
- package/bundles/antigravity-plugin/skills/ship-merge/SKILL.md +1 -1
- package/bundles/antigravity-plugin/skills/ship-pr/SKILL.md +1 -1
- package/bundles/antigravity-plugin/skills/tech-explainer/SKILL.md +2 -6
- package/bundles/antigravity-plugin/skills/using-git-worktrees/SKILL.md +19 -2
- package/bundles/antigravity-plugin/skills/warm-editorial-ui/SKILL.md +1 -1
- package/bundles/antigravity-plugin-extras/plugin.json +1 -1
- package/bundles/antigravity-plugin-extras/skills/_registry.md +2 -2
- package/bundles/antigravity-plugin-extras/skills/building-ai-agent-on-cloudflare/SKILL.md +1 -2
- package/bundles/antigravity-plugin-extras/skills/building-mcp-server-on-cloudflare/SKILL.md +1 -2
- package/bundles/antigravity-plugin-extras/skills/data-contract-pipeline/SKILL.md +1 -1
- package/bundles/antigravity-plugin-extras/skills/responsive-mobile-native/SKILL.md +2 -4
- package/bundles/antigravity-plugin-extras/skills/runner-move/SKILL.md +2 -4
- package/bundles/antigravity-plugin-extras/skills/setup-project-ai/SKILL.md +1 -1
- package/bundles/antigravity-plugin-extras/skills/understand-anything/SKILL.md +2 -5
- package/bundles/codex/.codex/skills/coding/dashboard-perf-sweep/SKILL.md +1 -1
- package/bundles/codex/.codex/skills/data/db-diagram/SKILL.md +1 -1
- package/bundles/codex/.codex/skills/devops/adopt-app/SKILL.md +2 -5
- package/bundles/codex/.codex/skills/devops/port-to-github/SKILL.md +2 -5
- package/bundles/codex/.codex/skills/devops/using-git-worktrees/SKILL.md +19 -2
- package/bundles/codex/.codex/skills/docs/explainer-doc/SKILL.md +1 -1
- package/bundles/codex/.codex/skills/docs/tech-explainer/SKILL.md +2 -6
- package/bundles/codex/.codex/skills/frontend/warm-editorial-ui/SKILL.md +1 -1
- package/bundles/manifest.json +3 -3
- package/package.json +1 -1
|
@@ -16,7 +16,7 @@
|
|
|
16
16
|
| Code Review | `code-review/` | Automated code review for quality, security, performance and best practices. Use when reviewing code changes, PRs, or doing code audits. |
|
|
17
17
|
| Codebase Audit | `codebase-audit/` | Audit an unfamiliar codebase before architecture or implementation work. Use for a new codebase, pre-implementation audit, codebase review, technical due diligence or onboarding. Produces AUDIT-FINDINGS.md and QUESTIONS.md. |
|
|
18
18
|
| Cross Review | `cross-review/` | Cross-vendor code review of the current diff — a second-vendor model (agy Argon by default; DeepSeek, GLM or any OpenAI-compatible endpoint) reviews your changes to catch bugs a same-vendor reviewer misses |
|
|
19
|
-
| Dashboard Perf Sweep | `dashboard-perf-sweep/` | Re-measure dashboard/API endpoints for load-time regressions
|
|
19
|
+
| Dashboard Perf Sweep | `dashboard-perf-sweep/` | Re-measure dashboard/API endpoints for load-time regressions. Use when the user says "sweep dashboard performance", "check if this app needs rs-kit", or "re-measure the perf tracker". |
|
|
20
20
|
| Error Handling | `error-handling/` | Error handling for Python and TypeScript: error hierarchies, custom exceptions, result types, retries, circuit breakers, error boundaries, logging, user-facing messages. |
|
|
21
21
|
| Fastapi Dev | `fastapi-dev/` | Build FastAPI backends with standard patterns, error handling, and testing |
|
|
22
22
|
| Javascript Typescript | `javascript-typescript/` | JavaScript and TypeScript development with ES6+, Node.js, React, and modern web frameworks. Use for frontend, backend, or full-stack JavaScript/TypeScript projects. |
|
|
@@ -30,7 +30,7 @@
|
|
|
30
30
|
| Skill | Path | When to Use |
|
|
31
31
|
|-------|------|-------------|
|
|
32
32
|
| Database Design | `database-design/` | Database schema design, migrations and query optimization for PostgreSQL, MySQL and NoSQL. |
|
|
33
|
-
| Db Diagram | `db-diagram/` | Diagram
|
|
33
|
+
| Db Diagram | `db-diagram/` | Diagram SQL artifacts (procs, views, queries, tables) as Mermaid or Excalidraw. Use when the user says "diagram this SQL", "draw the ER diagram", "/mermaid-db", or "/excalidraw-db". |
|
|
34
34
|
|
|
35
35
|
### Devops
|
|
36
36
|
|
|
@@ -53,7 +53,7 @@
|
|
|
53
53
|
| Code Documentation | `code-documentation/` | Write code documentation: API docs, README files, inline comments and developer guides. |
|
|
54
54
|
| Confluence Hla | `confluence-hla/` | High-Level Architecture (HLA) documents in Simplified Technical English as Confluence Storage Format XHTML with PlantUML. Use for Confluence architecture docs or converting markdown architecture. |
|
|
55
55
|
| Data Lineage | `data-lineage/` | Generate End-to-End Data Lineage and Telemetry Specification Markdown and Confluence XHTML for fleet observability. |
|
|
56
|
-
| Explainer Doc | `explainer-doc/` |
|
|
56
|
+
| Explainer Doc | `explainer-doc/` | Write a self-contained hand-off spec for an external team or vendor. Use when the user says "write a spec for the X team", "explainer doc", "spec for a vendor", or "hand this off to Y". |
|
|
57
57
|
| Hld | `hld/` | Generate High-Level Design (HLD) Markdown documentation and Confluence XHTML with native PlantUML diagrams. |
|
|
58
58
|
| Lld | `lld/` | Generate Lower-Level Design (LLD) Markdown documentation and Confluence XHTML with native PlantUML diagrams. |
|
|
59
59
|
| Office Documents Official | `office-documents-official/` | Hint for Office and PDF file work. Use when the user asks to create, edit, read or convert a Word .docx, PDF, PowerPoint .pptx or Excel .xlsx file. caddis does not ship these skills; points to Anthropic's official document-skills plugin. |
|
|
@@ -72,7 +72,7 @@
|
|
|
72
72
|
| React Best Practices | `react-best-practices/` | Modern React development guidelines covering hooks, component patterns, state management, performance optimization, and TypeScript integration. |
|
|
73
73
|
| React Dev | `react-dev/` | Type-safe React 18-19 with TypeScript: components, generic components, hooks, events, Server Components, TanStack Router and React Router. Use when React TypeScript or React 19 is involved. |
|
|
74
74
|
| Ui Review | `ui-review/` | Review a UI against design requirements, WCAG 2.2 AA and brand guidelines. Use when validating UI before release. |
|
|
75
|
-
| Warm Editorial Ui | `warm-editorial-ui/` | Apply the
|
|
75
|
+
| Warm Editorial Ui | `warm-editorial-ui/` | Apply the Warm Editorial Refinement design system. Use when the user says "use our design system", "warm editorial style", "apply our template", or "make it look like abc-project". |
|
|
76
76
|
|
|
77
77
|
### General
|
|
78
78
|
|
|
@@ -1,11 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: adopt-app
|
|
3
3
|
description: >-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
app was never set up properly", "adopt this POC", "onboard this app", "it just runs from a folder on
|
|
7
|
-
the server", "what would it take to get this into CI", "nobody knows how this is deployed", or "it
|
|
8
|
-
started as a prototype and now it is production".
|
|
4
|
+
Inventory an unscaffolded app or POC read-only and produce an adoption plan. Use when the user
|
|
5
|
+
says "adopt this POC", "onboard this app", "never set up properly", or "get this into CI".
|
|
9
6
|
---
|
|
10
7
|
|
|
11
8
|
# adopt-app
|
|
@@ -41,7 +41,7 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
|
|
|
41
41
|
`git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
|
|
42
42
|
- **Pull a branch to test it:** `git fetch origin`, then
|
|
43
43
|
`git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
|
|
44
|
-
`origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
|
|
44
|
+
`origin/<default>`), and run the gates there. Install dependencies fresh with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" --bootstrap` (run in the worktree); never link `node_modules` or a venv.
|
|
45
45
|
- **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
|
|
46
46
|
`git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
|
|
47
47
|
checkout has the default branch out; then leave it and report it. Delete the local feature branch only when no
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: dashboard-perf-sweep
|
|
3
3
|
context: fork
|
|
4
|
-
description: Re-measure dashboard/API endpoints for load-time regressions
|
|
4
|
+
description: Re-measure dashboard/API endpoints for load-time regressions. Use when the user says "sweep dashboard performance", "check if this app needs rs-kit", or "re-measure the perf tracker".
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# dashboard-perf-sweep — re-measure, then judge the shape, not just the time
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: db-diagram
|
|
3
3
|
context: fork
|
|
4
|
-
description: Diagram
|
|
4
|
+
description: Diagram SQL artifacts (procs, views, queries, tables) as Mermaid or Excalidraw. Use when the user says "diagram this SQL", "draw the ER diagram", "/mermaid-db", or "/excalidraw-db".
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# db-diagram — explain SQL as a diagram
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: explainer-doc
|
|
3
3
|
context: fork
|
|
4
|
-
description:
|
|
4
|
+
description: Write a self-contained hand-off spec for an external team or vendor. Use when the user says "write a spec for the X team", "explainer doc", "spec for a vendor", or "hand this off to Y".
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# explainer-doc — write for the reader who has no other context
|
|
@@ -91,6 +91,10 @@ and 95-154 turns per session were started by background events. Each turn re-rea
|
|
|
91
91
|
`python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_spend.py" run --caller lane-pN -- agy ...`.
|
|
92
92
|
- **Fewer wake-ups.** Run one `ci-watch` per PR head. When it times out on a queued run, watch that run once
|
|
93
93
|
with `ci-watch --run <id>`; do not start a new PR watch. Write no "still waiting" turns.
|
|
94
|
+
- **Silent agents.** For a subagent in its own worktree, start the shell watcher in the background (a script, not a
|
|
95
|
+
model): `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_silence_watch.py" --worktree <path> --silent-min 20`. Exit 3
|
|
96
|
+
and a `SILENT:` line mean no commit, file change or output for 20 minutes. Then look at the agent, and stop or
|
|
97
|
+
resume it. Add `--extra-file <the agent's output file>` so a long quiet build does not count as silence.
|
|
94
98
|
|
|
95
99
|
## Waves
|
|
96
100
|
|
|
@@ -1,11 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: port-to-github
|
|
3
3
|
description: >-
|
|
4
|
-
Port an app or repo to GitHub
|
|
5
|
-
|
|
6
|
-
with rollback. Use when the user says "move this app to GitHub", "port X to GitHub", "migrate from
|
|
7
|
-
Gitea", "this app only exists on the server", "import the repo from the prod box", "keep binaries
|
|
8
|
-
out of the repo", or "cut the deploy over to GitHub".
|
|
4
|
+
Port an app or repo to GitHub with verified history, CI translation, and deploy cutover. Use when
|
|
5
|
+
the user says "move this app to GitHub", "port X to GitHub", or "migrate from Gitea".
|
|
9
6
|
---
|
|
10
7
|
|
|
11
8
|
# port-to-github
|
|
@@ -47,7 +47,7 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
|
|
|
47
47
|
`git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
|
|
48
48
|
- **Pull a branch to test it:** `git fetch origin`, then
|
|
49
49
|
`git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
|
|
50
|
-
`origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
|
|
50
|
+
`origin/<default>`), and run the gates there. Install dependencies fresh with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" --bootstrap` (run in the worktree); never link `node_modules` or a venv.
|
|
51
51
|
- **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
|
|
52
52
|
`git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
|
|
53
53
|
checkout has the default branch out; then leave it and report it. Delete the local feature branch only when no
|
|
@@ -46,7 +46,7 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
|
|
|
46
46
|
`git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
|
|
47
47
|
- **Pull a branch to test it:** `git fetch origin`, then
|
|
48
48
|
`git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
|
|
49
|
-
`origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
|
|
49
|
+
`origin/<default>`), and run the gates there. Install dependencies fresh with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" --bootstrap` (run in the worktree); never link `node_modules` or a venv.
|
|
50
50
|
- **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
|
|
51
51
|
`git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
|
|
52
52
|
checkout has the default branch out; then leave it and report it. Delete the local feature branch only when no
|
|
@@ -45,7 +45,7 @@ It prints `SHARED: yes <reason>` or `SHARED: no` and exits 0. It says yes when t
|
|
|
45
45
|
`git -C <worktree> rebase origin/<default>` and `git -C <worktree> push --force-with-lease origin HEAD:<branch>`.
|
|
46
46
|
- **Pull a branch to test it:** `git fetch origin`, then
|
|
47
47
|
`git worktree add --detach "$(python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" test-<name> --record --purpose "test <name>")" origin/<branch>` (for the default branch,
|
|
48
|
-
`origin/<default>`), and run the gates there. Install dependencies fresh; never link `node_modules` or a venv.
|
|
48
|
+
`origin/<default>`), and run the gates there. Install dependencies fresh with `python "${CLAUDE_PLUGIN_ROOT}/scripts/caddis_worktree_root.py" --bootstrap` (run in the worktree); never link `node_modules` or a venv.
|
|
49
49
|
- **Clean up after a merge:** do not switch or pull. Run `git fetch --prune`, then
|
|
50
50
|
`git fetch origin <default>:<default>`: it fast-forwards the default branch with no checkout. Git refuses when a
|
|
51
51
|
checkout has the default branch out; then leave it and report it. Delete the local feature branch only when no
|
|
@@ -2,12 +2,8 @@
|
|
|
2
2
|
name: tech-explainer
|
|
3
3
|
context: fork
|
|
4
4
|
description: >-
|
|
5
|
-
Plain-language explainer
|
|
6
|
-
|
|
7
|
-
to X", "explainer", "write this up for someone non-technical", "plain English", "STE", "explain our
|
|
8
|
-
findings", "write up the benchmark results", "why is it slow — document it", or summarises an
|
|
9
|
-
investigation for a reader who won't read the raw data. Not for build hand-offs (explainer-doc) or
|
|
10
|
-
READMEs.
|
|
5
|
+
Plain-language explainer with Mermaid diagrams and STE for stakeholders. Use when the user says
|
|
6
|
+
"explain this to X", "plain English", "STE", or "explain our findings".
|
|
11
7
|
---
|
|
12
8
|
|
|
13
9
|
# tech-explainer — make a stranger understand, and able to push back
|
|
@@ -55,8 +55,25 @@ git worktree add -b <branch> $wt origin/<default>
|
|
|
55
55
|
|
|
56
56
|
## Install dependencies fresh
|
|
57
57
|
|
|
58
|
-
|
|
59
|
-
|
|
58
|
+
Run one command, inside the new worktree:
|
|
59
|
+
|
|
60
|
+
```powershell
|
|
61
|
+
python "<caddis scripts>\caddis_worktree_root.py" --bootstrap
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
It installs this worktree's own dependencies:
|
|
65
|
+
|
|
66
|
+
- `uv sync --frozen --all-extras` when `uv.lock` exists. Without `uv.lock`: `python -m venv .venv`, then `pip install`
|
|
67
|
+
of what the repo declares (`-e ".[dev]"` or `-e .`, then `requirements.txt` and `requirements-dev.txt`).
|
|
68
|
+
- `npm ci` in the root and in `frontend/`, for each folder that has a `package-lock.json`.
|
|
69
|
+
|
|
70
|
+
It refuses to run in a main checkout (exit 2) and stops at the first failing step (exit 1).
|
|
71
|
+
|
|
72
|
+
The pre-push gate needs this. In a worktree the gate uses only the worktree's own `.venv`. It never uses the main
|
|
73
|
+
checkout's venv (stale, and it belongs to a running dev service) and never the system Python. A worktree with no
|
|
74
|
+
`.venv` fails the gate with this command in the message. Do not push with `--no-verify` to get round it.
|
|
75
|
+
|
|
76
|
+
For a stack the script does not cover, use the project's own command (`cargo build`, `go mod download`). Call the
|
|
60
77
|
venv's own `python`; a bare `pip` can install into the global Python.
|
|
61
78
|
|
|
62
79
|
Never link `node_modules` or a venv from another folder. Tools that follow the link then change the
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: warm-editorial-ui
|
|
3
|
-
description: Apply the
|
|
3
|
+
description: Apply the Warm Editorial Refinement design system. Use when the user says "use our design system", "warm editorial style", "apply our template", or "make it look like abc-project".
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Warm Editorial Refinement — Design System
|
|
@@ -131,12 +131,12 @@
|
|
|
131
131
|
| Agent Md Refactor | `agent-md-refactor/` | Refactor bloated agent instruction files (AGENTS.md, .cursorrules, .github/ files) into linked, progressively disclosed docs. |
|
|
132
132
|
| Agent Orchestration | `agent-orchestration/` | Blueprint for orchestrating the agent pipeline from spec to planning, implementation, testing and debugging, plus when a second model is worth it, the intent→model map and cost guardrails. |
|
|
133
133
|
| Ask Questions If Underspecified | `asking-questions/` | Clarify requirements before implementing. Do not use automatically, only when invoked explicitly. |
|
|
134
|
-
| Data Contract Pipeline | `data-contract-pipeline/` | Build, audit and validate
|
|
134
|
+
| Data Contract Pipeline | `data-contract-pipeline/` | Build, audit, and validate DB-to-UI data contracts. Use when the user mentions data mapping, UI lineage, DisplayDTOs, source-to-screen mapping, or asks if a UI is backed by real data. |
|
|
135
135
|
| Developer Growth Analysis | `developer-growth-analysis/` | Analyze recent Claude Code chat history for coding patterns and gaps, find learning resources on HackerNews, and send a growth report to Slack DMs. |
|
|
136
136
|
| File Organizer | `file-organizer/` | Organize files and folders by context: find duplicates, suggest better structures, automate cleanup. |
|
|
137
137
|
| Game Changing Features | `game-changing-features/` | Find 10x product opportunities and high-leverage features. Use when the user mentions '10x', says 'what would make this 10x better', 'product strategy', or 'what should we build next'. |
|
|
138
138
|
| Golden Nuggets | `golden-nuggets/` | Extract durable tribal knowledge ('gold nuggets') from a codebase or changed files and route each to an instruction file, runbook, hub or CI review inbox. Use after a feature, fix, sprint, incident or release. |
|
|
139
139
|
| Intent Writer | `intent-writer/` | Structure freetext ideas, backlog items, or vague requirements into a formal Intent Document that preserves user intent across the entire agent pipeline chain. |
|
|
140
140
|
| Receiving Code Review | `receiving-code-review/` | Use when receiving code review feedback, before implementing it, especially if it seems unclear or wrong: verify with technical rigor, no performative agreement or blind implementation. |
|
|
141
|
-
| Setup Project Ai | `setup-project-ai/` | Install or refresh the
|
|
141
|
+
| Setup Project Ai | `setup-project-ai/` | Install or refresh the project AI harness: AGENTS.md, CLAUDE.md shims, agents, settings. Use when the user says 'set up the harness', 'generate CLAUDE.md', or runs /setup-project-ai. |
|
|
142
142
|
| Verification Loop | `verification-loop/` | Systematic code change verification — lint, test, type-check, review |
|
|
@@ -3,8 +3,7 @@ name: building-ai-agent-on-cloudflare
|
|
|
3
3
|
context: fork
|
|
4
4
|
description: |
|
|
5
5
|
Builds stateful AI agents on Cloudflare Workers with the Agents SDK. Use when the user wants to
|
|
6
|
-
"build an agent", "
|
|
7
|
-
AI", "WebSocket AI", or asks about agent "state management", "scheduled tasks" or "tool calling".
|
|
6
|
+
"build an agent", "stateful agent", "WebSocket AI", or mentions "Agents SDK".
|
|
8
7
|
---
|
|
9
8
|
|
|
10
9
|
# Building Cloudflare Agents
|
|
@@ -3,8 +3,7 @@ name: building-mcp-server-on-cloudflare
|
|
|
3
3
|
context: fork
|
|
4
4
|
description: |
|
|
5
5
|
Builds and deploys remote MCP servers on Cloudflare Workers with tools and OAuth. Use when the
|
|
6
|
-
user wants to "build MCP server", "
|
|
7
|
-
MCP", or mentions "MCP authentication", "MCP deployment" or Model Context Protocol on Cloudflare.
|
|
6
|
+
user wants to "build MCP server", "remote MCP", "deploy MCP", or add "OAuth to MCP".
|
|
8
7
|
---
|
|
9
8
|
|
|
10
9
|
# Building MCP Servers on Cloudflare
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: data-contract-pipeline
|
|
3
3
|
context: fork
|
|
4
|
-
description: "Build, audit and validate
|
|
4
|
+
description: "Build, audit, and validate DB-to-UI data contracts. Use when the user mentions data mapping, UI lineage, DisplayDTOs, source-to-screen mapping, or asks if a UI is backed by real data."
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# Data Contract Pipeline
|
|
@@ -1,10 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: responsive-mobile-native
|
|
3
3
|
description: >
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
"bottom nav", "touch gestures", "works on iPhone/Android", "responsive design", or any web UI
|
|
7
|
-
missing mobile support.
|
|
4
|
+
Adapt desktop-first web apps into responsive, mobile-native PWAs from one codebase. Use when the
|
|
5
|
+
user says "make this PWA", "mobile-friendly", "tablet layout", or "responsive design".
|
|
8
6
|
---
|
|
9
7
|
|
|
10
8
|
# Responsive Mobile-Native Skill
|
|
@@ -1,10 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: runner-move
|
|
3
3
|
description: >-
|
|
4
|
-
Move GitHub Actions jobs from self-hosted
|
|
5
|
-
|
|
6
|
-
"stop using self-hosted runners", "runner migration", "move jobs off the runner box", or "run
|
|
7
|
-
CI on windows-latest or ubuntu-latest".
|
|
4
|
+
Move GitHub Actions jobs from self-hosted to GitHub-hosted runners. Use when the user says
|
|
5
|
+
"move CI to GitHub-hosted runners", "stop using self-hosted runners", or "runner migration".
|
|
8
6
|
---
|
|
9
7
|
|
|
10
8
|
# runner-move
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: setup-project-ai
|
|
3
|
-
description: "Install or refresh the
|
|
3
|
+
description: "Install or refresh the project AI harness: AGENTS.md, CLAUDE.md shims, agents, settings. Use when the user says 'set up the harness', 'generate CLAUDE.md', or runs /setup-project-ai."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# setup-project-ai
|
|
@@ -1,11 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: understand-anything
|
|
3
3
|
description: >
|
|
4
|
-
Turn a codebase
|
|
5
|
-
|
|
6
|
-
phrases like "how does this project work", "map out the codebase", "what changed in this PR",
|
|
7
|
-
"explain this file", "onboard me to this project", "what does X depend on", "analyze this repo",
|
|
8
|
-
"generate a knowledge graph", or "what is the architecture of this project".
|
|
4
|
+
Turn a codebase into an interactive knowledge graph. Use for /understand* commands, or when the
|
|
5
|
+
user says "map out the codebase", "how does this project work", or "knowledge graph".
|
|
9
6
|
---
|
|
10
7
|
|
|
11
8
|
# Understand Anything
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: dashboard-perf-sweep
|
|
3
3
|
context: fork
|
|
4
|
-
description: Re-measure dashboard/API endpoints for load-time regressions
|
|
4
|
+
description: Re-measure dashboard/API endpoints for load-time regressions. Use when the user says "sweep dashboard performance", "check if this app needs rs-kit", or "re-measure the perf tracker".
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# dashboard-perf-sweep — re-measure, then judge the shape, not just the time
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: db-diagram
|
|
3
3
|
context: fork
|
|
4
|
-
description: Diagram
|
|
4
|
+
description: Diagram SQL artifacts (procs, views, queries, tables) as Mermaid or Excalidraw. Use when the user says "diagram this SQL", "draw the ER diagram", "/mermaid-db", or "/excalidraw-db".
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# db-diagram — explain SQL as a diagram
|
|
@@ -1,11 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: adopt-app
|
|
3
3
|
description: >-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
app was never set up properly", "adopt this POC", "onboard this app", "it just runs from a folder on
|
|
7
|
-
the server", "what would it take to get this into CI", "nobody knows how this is deployed", or "it
|
|
8
|
-
started as a prototype and now it is production".
|
|
4
|
+
Inventory an unscaffolded app or POC read-only and produce an adoption plan. Use when the user
|
|
5
|
+
says "adopt this POC", "onboard this app", "never set up properly", or "get this into CI".
|
|
9
6
|
---
|
|
10
7
|
|
|
11
8
|
# adopt-app
|
|
@@ -1,11 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: port-to-github
|
|
3
3
|
description: >-
|
|
4
|
-
Port an app or repo to GitHub
|
|
5
|
-
|
|
6
|
-
with rollback. Use when the user says "move this app to GitHub", "port X to GitHub", "migrate from
|
|
7
|
-
Gitea", "this app only exists on the server", "import the repo from the prod box", "keep binaries
|
|
8
|
-
out of the repo", or "cut the deploy over to GitHub".
|
|
4
|
+
Port an app or repo to GitHub with verified history, CI translation, and deploy cutover. Use when
|
|
5
|
+
the user says "move this app to GitHub", "port X to GitHub", or "migrate from Gitea".
|
|
9
6
|
---
|
|
10
7
|
|
|
11
8
|
# port-to-github
|
|
@@ -55,8 +55,25 @@ git worktree add -b <branch> $wt origin/<default>
|
|
|
55
55
|
|
|
56
56
|
## Install dependencies fresh
|
|
57
57
|
|
|
58
|
-
|
|
59
|
-
|
|
58
|
+
Run one command, inside the new worktree:
|
|
59
|
+
|
|
60
|
+
```powershell
|
|
61
|
+
python "<caddis scripts>\caddis_worktree_root.py" --bootstrap
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
It installs this worktree's own dependencies:
|
|
65
|
+
|
|
66
|
+
- `uv sync --frozen --all-extras` when `uv.lock` exists. Without `uv.lock`: `python -m venv .venv`, then `pip install`
|
|
67
|
+
of what the repo declares (`-e ".[dev]"` or `-e .`, then `requirements.txt` and `requirements-dev.txt`).
|
|
68
|
+
- `npm ci` in the root and in `frontend/`, for each folder that has a `package-lock.json`.
|
|
69
|
+
|
|
70
|
+
It refuses to run in a main checkout (exit 2) and stops at the first failing step (exit 1).
|
|
71
|
+
|
|
72
|
+
The pre-push gate needs this. In a worktree the gate uses only the worktree's own `.venv`. It never uses the main
|
|
73
|
+
checkout's venv (stale, and it belongs to a running dev service) and never the system Python. A worktree with no
|
|
74
|
+
`.venv` fails the gate with this command in the message. Do not push with `--no-verify` to get round it.
|
|
75
|
+
|
|
76
|
+
For a stack the script does not cover, use the project's own command (`cargo build`, `go mod download`). Call the
|
|
60
77
|
venv's own `python`; a bare `pip` can install into the global Python.
|
|
61
78
|
|
|
62
79
|
Never link `node_modules` or a venv from another folder. Tools that follow the link then change the
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: explainer-doc
|
|
3
3
|
context: fork
|
|
4
|
-
description:
|
|
4
|
+
description: Write a self-contained hand-off spec for an external team or vendor. Use when the user says "write a spec for the X team", "explainer doc", "spec for a vendor", or "hand this off to Y".
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# explainer-doc — write for the reader who has no other context
|
|
@@ -2,12 +2,8 @@
|
|
|
2
2
|
name: tech-explainer
|
|
3
3
|
context: fork
|
|
4
4
|
description: >-
|
|
5
|
-
Plain-language explainer
|
|
6
|
-
|
|
7
|
-
to X", "explainer", "write this up for someone non-technical", "plain English", "STE", "explain our
|
|
8
|
-
findings", "write up the benchmark results", "why is it slow — document it", or summarises an
|
|
9
|
-
investigation for a reader who won't read the raw data. Not for build hand-offs (explainer-doc) or
|
|
10
|
-
READMEs.
|
|
5
|
+
Plain-language explainer with Mermaid diagrams and STE for stakeholders. Use when the user says
|
|
6
|
+
"explain this to X", "plain English", "STE", or "explain our findings".
|
|
11
7
|
---
|
|
12
8
|
|
|
13
9
|
# tech-explainer — make a stranger understand, and able to push back
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: warm-editorial-ui
|
|
3
|
-
description: Apply the
|
|
3
|
+
description: Apply the Warm Editorial Refinement design system. Use when the user says "use our design system", "warm editorial style", "apply our template", or "make it look like abc-project".
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Warm Editorial Refinement — Design System
|
package/bundles/manifest.json
CHANGED
package/package.json
CHANGED