@caddis/cli 0.4.34 → 0.4.36

package/bundles/antigravity-plugin-extras/skills/setup-project-ai/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: setup-project-ai
-description: "Install or refresh the agent-agnostic development harness in a project — an AGENTS.md-canonical rules hierarchy (root + per-folder) with a CLAUDE.md @import shim beside each, lean subagents, slash commands, settings.json, and the frontend/python test env. USE THIS SKILL when setting up AI resources on a new or existing project, bootstrapping the rules files (AGENTS.md/CLAUDE.md), adding subagents/commands, or when the user says 'set up the harness', 'setup-project-ai', 'generate CLAUDE.md', 'onboard this project to Claude Code / Codex / agy', or runs /setup-project-ai. Combines a deterministic generator (scripts/setup_project_ai.py) for the must-not-vary mechanics with an AI enrichment step that curates project-specific AGENTS.md content."
+description: "Install or refresh the agent-agnostic harness in a project: AGENTS.md rules with CLAUDE.md shims, subagents, commands and settings. Use when setting up AI resources on a project, or the user says 'set up the harness', 'setup-project-ai', 'generate CLAUDE.md', 'onboard this project to Claude Code / Codex / agy', or runs /setup-project-ai."
 ---
 
 # setup-project-ai

package/bundles/antigravity-plugin-extras/skills/shadcn-radix/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: shadcn-radix
-description: shadcn/ui component library, Radix UI primitives, theming with CSS variables, react-hook-form + zod forms, TanStack Table data tables, and cva variant composition. Use for shadcn setup, shadcn add, components.json, shadcn theming, Radix accessible components, shadcn form patterns, data tables, command palette, date picker, combobox, or drawer/sheet. References css-architecture for tokens and react-best-practices for structure.
+description: "shadcn/ui and Radix UI: setup (shadcn add, components.json), theming, react-hook-form + zod forms, TanStack Table data tables, cva variants, command palette, date picker, combobox, drawer/sheet."
 ---
 
 # shadcn/ui + Radix Primitives Skill

package/bundles/antigravity-plugin-extras/skills/sketch/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sketch
-description: Generate 2-3 interactive HTML design variants to explore UI directions side-by-side before committing to production code. Use for early-stage design exploration, comparing layout approaches, or when asked to "sketch this screen" or "show me variants".
+description: Generate 2-3 interactive HTML design variants to compare UI directions before production code. Use for early design exploration or when asked to "sketch this screen" or "show me variants".
 source: NousResearch/hermes-agent
 ---
 

package/bundles/antigravity-plugin-extras/skills/streamlit-dev/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: streamlit-dev
-description: Build production-ready Streamlit dashboards with best-practice patterns, caching, components, and theming. Use when implementing any Streamlit page, component, chart, or UI feature.
+description: "Build production Streamlit dashboards: caching, components, theming. Use for any Streamlit page, component, chart or UI feature."
 ---
 
 # Streamlit Development Skill

package/bundles/antigravity-plugin-extras/skills/theme-factory/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: theme-factory
-description: Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
+description: Style artifacts (slides, docs, reports, HTML pages) with one of 10 preset themes or a newly generated theme.
 license: Complete terms in LICENSE.txt
 ---
 

package/bundles/antigravity-plugin-extras/skills/ui-styling-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ui-styling-patterns
-description: Create accessible user interfaces with shadcn/ui components (Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use for responsive layouts, accessible components, theme customization, dark mode, and consistent styling patterns.
+description: "Accessible UIs with shadcn/ui, Radix and Tailwind CSS: responsive layouts, theming, dark mode and consistent styling."
 license: MIT
 ---
 

package/bundles/antigravity-plugin-extras/skills/ui-ux-intelligence/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ui-ux-intelligence
 context: fork
-description: "UI/UX design intelligence with CSV knowledge bases: 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types. Use when making design decisions that need data-backed palettes, font pairing lookups, or style-specific implementation guidance."
+description: "Data-backed UI/UX decisions from CSV knowledge bases: 50+ styles, 161 palettes, 57 font pairings, UX guidelines, chart types. Use to look up palettes, font pairs or style guidance."
 ---
 
 # UI/UX Pro Max - Design Intelligence

package/bundles/antigravity-plugin-extras/skills/understand-anything/SKILL.md

@@ -1,15 +1,11 @@
 ---
 name: understand-anything
 description: >
-  Analyze any codebase or knowledge base and produce a searchable interactive knowledge graph.
-  Use this skill whenever the user asks to understand a codebase, analyze project architecture,
-  map a repo, generate an architecture diagram, create onboarding docs, explain a specific file
-  or function, analyze the impact of a PR or diff, chat about code, or run any /understand command.
-  Also triggers on phrases like "how does this project work", "map out the codebase", "what changed
-  in this PR", "explain this file", "onboard me to this project", "what does X depend on",
-  "analyze this repo", "generate a knowledge graph", or "what is the architecture of this project".
-  Always use this skill for /understand, /understand-chat, /understand-dashboard, /understand-diff,
-  /understand-domain, /understand-explain, /understand-knowledge, and /understand-onboard commands.
+  Turn a codebase or knowledge base into a searchable interactive knowledge graph. Use for
+  /understand and /understand-chat, -dashboard, -diff, -domain, -explain, -knowledge, -onboard, or
+  phrases like "how does this project work", "map out the codebase", "what changed in this PR",
+  "explain this file", "onboard me to this project", "what does X depend on", "analyze this repo",
+  "generate a knowledge graph", or "what is the architecture of this project".
 ---
 
 # Understand Anything

package/bundles/antigravity-plugin-extras/skills/update-readme/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: update-readme
-description: Detect feature commits and update README sections (Features, API, Usage) with accurate repo-aware changes, then stage only README for a docs commit. Use when users add features/routes/components and want README maintained automatically.
+description: Detect feature commits and update README sections (Features, API, Usage) to match, then stage only the README. Use when features, routes or components were added.
 ---
 
 # Update README Skill

package/bundles/antigravity-plugin-extras/skills/word-cloud/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: word-cloud
-description: Generate beautiful word clouds — static or animated — from any input source. Handles text extraction from PDF, DOCX, XLSX, PPTX, HTML, CSV, TXT and produces production-ready components. Includes light/dark theming, sentiment/POS color coding, shape masking, and multiple animation modes.
+description: Generate static or animated word clouds from any text source (PDF, DOCX, XLSX, PPTX, HTML, CSV, TXT), with theming, sentiment coloring and shape masks.
 ---
 
 # Word Cloud Skill

package/bundles/codex/.codex/skills/coding/api-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: api-design
-description: REST and GraphQL API design patterns. Use when designing new API endpoints, defining resource schemas, planning versioning strategies, or reviewing API contracts. Covers naming conventions, pagination, filtering, error responses, and OpenAPI documentation.
+description: "REST and GraphQL API design: endpoints, resource schemas, versioning, pagination, error responses, OpenAPI. Use when designing or reviewing API contracts."
 ---
 
 # API Design Skill

package/bundles/codex/.codex/skills/coding/backend-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: backend-development
-description: Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.
+description: Backend API design, database schemas, microservices and TDD. Use for backend system architecture.
 source: wshobson/agents
 license: MIT
 ---

package/bundles/codex/.codex/skills/coding/code-review/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: code-review
 context: fork
-description: Automated code review for pull requests using specialized review patterns. Analyzes code for quality, security, performance, and best practices. Use when reviewing code changes, PRs, or doing code audits.
+description: Automated code review for quality, security, performance and best practices. Use when reviewing code changes, PRs, or doing code audits.
 source: anthropics/claude-code
 license: Apache-2.0
 ---

package/bundles/codex/.codex/skills/coding/codebase-audit/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: codebase-audit
 context: fork
-description: Systematic codebase audit methodology for unfamiliar codebases before architecture or implementation work. Use for new codebase, unfamiliar codebase, pre-implementation audit, codebase review, technical due diligence, or onboarding to an existing project. Produces AUDIT-FINDINGS.md and QUESTIONS.md. Routes to Architect, Planner, or Code Reviewer agents.
+description: 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.
 ---
 
 # Codebase Audit Skill

package/bundles/codex/.codex/skills/coding/dashboard-perf-sweep/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: dashboard-perf-sweep
 context: fork
-description: Re-measure an app's dashboard/API endpoints for load-time regressions and decide, with a documented checklist (not a black-box verdict), whether a slow one is a candidate for the rs-kit summary-table refresher pattern — or needs an index, keyset paging, gzip, or nothing at all. Use when the user says "sweep dashboard performance", "check if this app needs rs-kit", "re-measure the perf tracker", "is this endpoint a refresher candidate", or when a dashboard-performance-tracker.md is stale and needs re-validating. Read-only by default (dev servers only; prod requires an explicit opt-in and human confirmation) and human-invoked, never scheduled -- it surfaces candidates, it does not enroll them.
+description: Re-measure dashboard/API endpoints for load-time regressions and decide by checklist if a slow one needs the rs-kit refresher, an index, keyset paging, gzip, or nothing. Use when the user says "sweep dashboard performance", "check if this app needs rs-kit", "re-measure the perf tracker", "is this endpoint a refresher candidate", or dashboard-performance-tracker.md is stale. Read-only.
 ---
 
 # dashboard-perf-sweep — re-measure, then judge the shape, not just the time

package/bundles/codex/.codex/skills/coding/error-handling/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: error-handling
-description: Error handling patterns for Python and TypeScript applications. Use when designing error hierarchies, implementing retry logic, building error boundaries, or establishing logging strategies. Covers custom exceptions, result types, circuit breakers, and user-facing error messages.
+description: "Error handling for Python and TypeScript: error hierarchies, custom exceptions, result types, retries, circuit breakers, error boundaries, logging, user-facing messages."
 ---
 
 # Error Handling Skill

package/bundles/codex/.codex/skills/coding/python/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: python-development
-description: Modern Python development with Python 3.12+, Django, FastAPI, async patterns, and production best practices. Use for Python projects, APIs, data processing, or automation scripts.
+description: Modern Python 3.12+ (Django, FastAPI, async) with production best practices. Use for Python projects, APIs, data processing or scripts.
 source: wshobson/agents
 license: MIT
 ---

package/bundles/codex/.codex/skills/coding/sql/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sql
-description: Write high-quality, optimized SQL with best practices for performance, NULL handling, security, and readability. Database-agnostic patterns with dialect-specific notes.
+description: "Write optimized, secure, readable SQL: performance, NULL handling, dialect-specific notes."
 ---
 
 # SQL Expert Skill

package/bundles/codex/.codex/skills/data/database-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: database-design
-description: Database schema design, optimization, and migration patterns for PostgreSQL, MySQL, and NoSQL databases. Use for designing schemas, writing migrations, or optimizing queries.
+description: Database schema design, migrations and query optimization for PostgreSQL, MySQL and NoSQL.
 source: wshobson/agents
 license: MIT
 ---

package/bundles/codex/.codex/skills/data/db-diagram/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: db-diagram
 context: fork
-description: Turn a SQL artifact — a stored procedure, view, query, .sql file, or table name — into a diagram that explains it to a human. Use when the user says "diagram this query/proc/view/schema", "explain this SQL visually", "draw the ER diagram", "show me the data flow of this stored proc", "/mermaid-db", or "/excalidraw-db". Produces Mermaid (default, git-diffable) or Excalidraw (for design reviews). Read-only — never touches the database.
+description: Diagram a SQL artifact (stored proc, view, query, .sql file, table) as Mermaid or Excalidraw. Use when the user says "diagram this query/proc/view/schema", "explain this SQL visually", "draw the ER diagram", "show me the data flow of this stored proc", "/mermaid-db", or "/excalidraw-db". Read-only.
 ---
 
 # db-diagram — explain SQL as a diagram

package/bundles/codex/.codex/skills/devops/adopt-app/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: adopt-app
-description: Bring an app that was never scaffolded - a proof of concept that became real, a folder on a server, a checkout with no remote - up to the standard a generated app starts at. Inventories it without running it (local folder, network share, or a remote Windows box over WinRM), works out what stack each component is, measures it against an adoption standard with three verdicts (pass, gap, and question-only-a-person-can-answer), and writes an ordered plan whose steps cannot be done in the wrong order. Use when the user says "this app was never set up properly", "adopt this POC", "onboard this app", "it just runs from a folder on the server", "bring this up to standard", "what would it take to get this into CI", "nobody knows how this is deployed", or "it started as a prototype and now it is production".
+description: Bring an app that was never scaffolded (POC, server folder, checkout with no remote) up to standard — inventory without running it, pass/gap/question verdicts, ordered plan. Use when the user says "this app was never set up properly", "adopt this POC", "onboard this app", "it just runs from a folder on the server", "bring this up to standard", "what would it take to get this into CI", "nobody knows how this is deployed", or "it started as a prototype and now it is production".
 ---
 
 # adopt-app

package/bundles/codex/.codex/skills/devops/ci-cd-pipeline/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ci-cd-pipeline
 context: fork
-description: CI/CD pipeline design and implementation for GitHub Actions, Azure DevOps, and general pipeline architecture. Use when creating build pipelines, deployment workflows, quality gates, environment promotion strategies, or automating release processes.
+description: "CI/CD pipelines for GitHub Actions and Azure DevOps: build and deploy workflows, quality gates, environment promotion and release automation."
 ---
 
 # CI/CD Pipeline Skill

package/bundles/codex/.codex/skills/devops/port-to-github/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: port-to-github
-description: Move (port) an app or repository to GitHub from ANY source - a Gitea/GitLab/any git server URL, a local folder, a network (UNC) share, or a folder on a remote Windows box reached over WinRM - with or without existing git history. Keeps every branch and tag, verifies by SHA, translates Gitea/Forgejo Actions CI, enforces a source-only content policy (runtimes, binaries, data exports and dependencies stay out of the repo, over ALL history, with a runtime manifest and provisioning script so the environment is still reproducible), switches deploy checkouts to GitHub with automatic rollback, and retires the old host safely. Use when the user says "move this app to GitHub", "port X to GitHub", "migrate from Gitea", "put this folder on GitHub", "this app only exists on the server", "import the repo from the prod box", "keep binaries / MariaDB / PHP out of the repo", "check the repo only holds source", or "cut the deploy over to GitHub".
+description: Port an app or repo to GitHub from any source (git server, local folder, UNC share, Windows box over WinRM) — all branches and tags, SHA-verified, CI translated, history kept source-only, deploy cut over with rollback. Use when the user says "move this app to GitHub", "port X to GitHub", "migrate from Gitea", "put this folder on GitHub", "this app only exists on the server", "import the repo from the prod box", "keep binaries / MariaDB / PHP out of the repo", "check the repo only holds source", or "cut the deploy over to GitHub".
 ---
 
 # port-to-github

package/bundles/codex/.codex/skills/devops/safe-cleanup/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: safe-cleanup
-description: Use BEFORE deleting any directory tree, clearing a scratchpad, removing git worktrees, or "tidying up" generated folders - especially on Windows, where a recursive delete that meets a junction or symlink destroys the link's TARGET. Also use when verifying that a Python venv or node_modules survived a cleanup, because pip check and file counts both report healthy on a half-deleted environment.
+description: Use BEFORE deleting a directory tree, scratchpad or git worktree, or "tidying up" generated folders, especially on Windows, where deleting through a junction or symlink destroys its target; and to verify a venv or node_modules survived.
 ---
 
 # Safe Cleanup

package/bundles/codex/.codex/skills/devops/using-git-worktrees/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: using-git-worktrees
-description: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
+description: "Use when starting feature work that needs isolation from the current workspace, or before executing an implementation plan: creates an isolated git worktree safely."
 ---
 
 # Using Git Worktrees

package/bundles/codex/.codex/skills/devops/windows-deployment/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: windows-deployment
-description: "Deploy FastAPI + React/Vite apps to Windows Server with NSSM services, reverse proxy (IIS or nginx), and git-pull workflow. Use when deploying any web app to a Windows prod server, setting up NSSM services, configuring IIS or nginx reverse proxy, making code environment-aware for dev/prod, or troubleshooting prod deployment issues."
+description: "Deploy FastAPI + React/Vite apps to Windows Server with NSSM services, IIS or nginx reverse proxy and git-pull. Use for Windows prod deploys, NSSM, reverse proxy setup, dev/prod config, or prod troubleshooting."
 ---
 
 # Windows Server Deployment Skill

package/bundles/codex/.codex/skills/docs/code-documentation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: code-documentation
-description: Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
+description: "Write code documentation: API docs, README files, inline comments and developer guides."
 source: wshobson/agents
 license: MIT
 ---

package/bundles/codex/.codex/skills/docs/confluence-hla/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: confluence-hla
-description: Author enterprise High-Level Architecture (HLA) documents in Simplified Technical English and generate Confluence Storage Format XHTML with self-contained PlantUML diagrams, wrapped tables, and zero AI fingerprints. Use when creating high-level architecture designs, architecture documentation for Confluence, or converting markdown architecture to Confluence storage format.
+description: 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.
 ---
 
 # Confluence High-Level Architecture (HLA) Authoring Skill

package/bundles/codex/.codex/skills/docs/explainer-doc/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: explainer-doc
 context: fork
-description: Write a document that hands off work to a team who did NOT do the investigation — an external vendor, another team, a contractor — and who must be able to act on it alone. Use when the user says "write a spec for the X team", "document this for someone outside the team", "explainer doc", "implementation spec for a vendor", "hand this off to Y", or is about to write a design doc whose primary reader did not live through the debugging/design process. NOT for internal specs where the reader already has full context (use technical-writing or writing-plans instead) — this is specifically for the "stranger must follow it alone" case.
+description: Hand-off doc for a team that did NOT do the investigation (vendor, contractor, another team) — the "stranger must follow it alone" case. Use when the user says "write a spec for the X team", "document this for someone outside the team", "explainer doc", "implementation spec for a vendor", or "hand this off to Y". Not for readers with full context.
 ---
 
 # explainer-doc — write for the reader who has no other context

package/bundles/codex/.codex/skills/docs/tech-explainer/SKILL.md

@@ -2,18 +2,13 @@
 name: tech-explainer
 context: fork
 description: >-
-  Write a plain-language technical explainer for a smart reader who did NOT do the investigation — a
-  manager, an infra colleague, a stakeholder, the person whose recommendation you are answering.
-  Layered Mermaid diagrams that rank causes by SIZE OF EFFECT, a controlled-vocabulary table,
-  Simplified Technical English, published withdrawn results, and questions back to the reader. Use
-  this skill whenever the user says "explain this to X", "explainer", "write this up for someone
-  non-technical", "plain English", "simplified technical english", "STE", "explain our findings",
-  "write up the benchmark results", "answer my manager's recommendations", "why is it slow — document
-  it", "make a doc with diagrams explaining the stack", or is about to summarise an investigation, a
-  benchmark, a postmortem, an architecture, or a disagreement for a reader who will not read the raw
-  data. NOT for handing off work to be BUILT by a vendor or another team (use explainer-doc for that —
-  it produces an actionable spec); NOT for READMEs or API docs (use technical-writing). This one
-  produces UNDERSTANDING: the reader must finish able to argue with you on the merits.
+  Plain-language explainer, with ranked Mermaid diagrams and Simplified Technical English, for a
+  reader who did NOT do the investigation (manager, stakeholder). Use when the user says "explain
+  this to X", "explainer", "write this up for someone non-technical", "plain English", "simplified
+  technical english", "STE", "explain our findings", "write up the benchmark results", "answer my
+  manager's recommendations", "why is it slow — document it", "make a doc with diagrams explaining
+  the stack", or summarises an investigation for a reader who won't read the raw data. Not for build
+  hand-offs (explainer-doc) or READMEs.
 ---
 
 # tech-explainer — make a stranger understand, and able to push back

package/bundles/codex/.codex/skills/docs/technical-writing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: technical-writing
 context: fork
-description: Technical documentation best practices for READMEs, API docs, architecture docs, runbooks, and developer guides. Use when writing or reviewing documentation, creating onboarding guides, or establishing documentation standards.
+description: Documentation best practices for READMEs, API docs, architecture docs, runbooks and developer guides. Use when writing or reviewing docs or setting documentation standards.
 ---
 
 # Technical Writing Skill

package/bundles/codex/.codex/skills/frontend/css-architecture/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: css-architecture
-description: CSS architecture, design token strategy, Tailwind conventions, CSS Modules, container queries, dark mode, responsive patterns, and animation architecture. Use for design token naming, CSS custom properties, Tailwind config, container queries, dark mode implementation, fluid typography, or CSS animation decisions. Complements frontend-design (what to achieve) with how to implement it.
+description: "CSS architecture: design tokens, custom properties, Tailwind config, CSS Modules, container queries, dark mode, fluid typography, animation. Covers how to implement styling; frontend-design covers what to achieve."
 ---
 
 # CSS Architecture Skill

package/bundles/codex/.codex/skills/frontend/frontend-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: frontend-design
-description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics while strictly adhering to the user's technical standards.
+description: Create distinctive, production-grade frontend interfaces that avoid generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters or applications.
 ---
 
 # Frontend Design Skill

package/bundles/codex/.codex/skills/frontend/react-dev/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: react-dev
 version: 1.0.0
-description: This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing integration (TanStack Router, React Router).
+description: "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."
 ---
 
 # React TypeScript

package/bundles/codex/.codex/skills/frontend/ui-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ui-review
-description: Review UI implementations against design requirements, accessibility standards (WCAG 2.2 AA), and brand guidelines. Use when reviewing designs or validating UI before release.
+description: Review a UI against design requirements, WCAG 2.2 AA and brand guidelines. Use when validating UI before release.
 ---
 
 # UI Review Skill

package/bundles/codex/.codex/skills/frontend/warm-editorial-ui/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: warm-editorial-ui
-description: Apply the "Warm Editorial Refinement" design system — a sophisticated, executive-grade aesthetic with warm cream surfaces (light mode) and warm charcoal surfaces (dark mode), Bahnschrift + Plus Jakarta Sans typography, generous rounded corners, multi-layer shadows, and a warm neutral palette. Supports both light and dark themes via CSS custom properties and the `.dark` class. Use this skill whenever the user wants to build an app, dashboard, component, or web UI using the abc-project visual style. Trigger on phrases like "use our design system", "apply our template", "make it look like abc-project", "use the warm editorial style", "use our brand template", "add dark mode", or any request to build a new tool/app/dashboard for XYZ Brand or similar contexts. This is the canonical design template for all new frontend builds.
+description: Apply the "Warm Editorial Refinement" design system (warm cream/charcoal surfaces, Bahnschrift + Plus Jakarta Sans, layered shadows), the canonical template for new frontend builds. Use for apps, dashboards or UI in the abc-project style, or on "use our design system", "apply our template", "make it look like abc-project", "use the warm editorial style", "use our brand template", "add dark mode", or a new tool for XYZ Brand.
 ---
 
 # Warm Editorial Refinement — Design System

package/bundles/codex/.codex/skills/media/mermaid-diagrams/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: mermaid-diagrams
 context: fork
-description: Create software diagrams using Mermaid text-based syntax. Use for class diagrams (domain modeling, OOP design), sequence diagrams (API flows, interactions), flowcharts (processes, algorithms, user journeys), ERD (database schemas), C4 architecture diagrams, state diagrams, git graphs, gantt charts, and data visualization.
+description: "Software diagrams in Mermaid: class, sequence, flowchart, ERD, C4, state, git graph, gantt. Use for domain models, API flows, processes and database schemas."
 ---
 
 # Mermaid Diagramming

package/bundles/codex/.codex/skills/media/particle-art/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: particle-art
 version: 1.0.0
-description: Generate animated particle art React/Next.js components — zero dependencies, spring physics, CSS-variable theming, DPR-correct canvas, mouse interaction. Use when the user wants animated hero art, a living logo, a branded initial or monogram, a constellation background, or any "particles that form a shape". Triggers on "particle animation", "node network", "animated letter/logo/initials", "living letter", "morphing particles", "constellation", "neural net art", "dot field", "stipple portrait", "halftone animation", "ASCII art animation", "background art for my site", or "art that reacts to mouse". Covers — text/initials → spring-node letter; preset patterns (constellation, helix, spiral, DNA, hex-grid, wave, infinity); custom SVG paths; custom polygon points; Unicode halftone stipple; Gaussian dot field with sparks; SVG circuit traces; hybrid combos. Outputs a complete, self-contained, copy-paste-ready React component. Prefer this over p5.js (zero-dep, React-native, TypeScript), tsParticles (richer spring physics, CSS-var theming), Three.js (lightweight, no WebGL).
+description: Zero-dependency animated particle art as a React/Next.js component (spring physics, CSS-variable theming, mouse interaction). Use for animated hero art or a living logo, or on "particles that form a shape", "particle animation", "node network", "animated letter/logo/initials", "living letter", "morphing particles", "constellation", "neural net art", "dot field", "stipple portrait", "halftone animation", "ASCII art animation", "background art for my site", or "art that reacts to mouse".
 ---
 
 # Particle Art Generator

package/bundles/codex/.codex/skills/testing/playwright/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: playwright
 context: fork
-description: Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
+description: "Browser automation and testing with Playwright: auto-detects dev servers; tests pages, forms, logins, links, screenshots and responsive layouts. Use to test websites or automate any browser task."
 ---
 
 **IMPORTANT - Path Resolution:**

package/bundles/codex/.codex/skills/testing/test-strategy/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: test-strategy
 context: fork
-description: Test planning and strategy for projects of any size. Use when defining what to test, choosing test types, setting coverage goals, building test pyramids, or planning quality gates. Produces TEST-STRATEGY.md with prioritized test plan. Routes to Tester agent for execution.
+description: "Plan what to test: test types, coverage goals, test pyramid, quality gates. Produces a prioritized TEST-STRATEGY.md for the Tester agent."
 ---
 
 # Test Strategy Skill

package/bundles/codex/.codex/skills/testing/webapp-testing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: webapp-testing
 context: fork
-description: Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
+description: "Test local web apps with Playwright: verify frontend behavior, debug UI, capture screenshots and browser logs."
 license: Complete terms in LICENSE.txt
 ---
 

package/bundles/codex/.codex/skills/workflow/advisory-hub/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: advisory-hub
-description: Cross-session phase validation for multi-phase implementation plans — a long-lived "Hub" session RE-DERIVES each implementation phase's claims independently instead of trusting its self-assessment. Use when the user says "advisory hub", "validate this phase", "phase report", "hub verdict", "advisory context", "who checks the implementing session", "the plan turned out to be wrong", "hand off the hub", "re-derive don't trust", or when a long, multi-session plan with expensive-to-reverse decisions (a migration, a security change, anything touching production data correctness) needs an independent session that verifies every phase before the next one starts. NOT for a three-phase feature — it costs a full extra session's context per phase, and a skill that doesn't say so gets applied everywhere and resented. Every Hub artefact belongs in `.caddis/advisory-hub-reports/` — a succession prompt is `hub-NN.spawn.md` there, never a generic prompts folder, even when you write it by hand instead of running `/caddis:spawn-hub`.
+description: A long-lived "Hub" session re-derives each phase of a multi-session plan instead of trusting its self-report. Use when the user says "advisory hub", "validate this phase", "phase report", "hub verdict", "advisory context", "who checks the implementing session", "the plan turned out to be wrong", "hand off the hub", "re-derive don't trust", or a long plan with expensive-to-reverse work (a migration, a security change, production data correctness) needs independent checks; not for short features. Hub artefacts, including `hub-NN.spawn.md`, go in `.caddis/advisory-hub-reports/`.
 ---
 
 # Advisory Hub — cross-session phase validation

package/bundles/codex/.codex/skills/workflow/skill-creator/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: skill-creator
 context: fork
-description: Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
+description: Create, edit and improve skills, run evals and benchmarks, and optimize a skill's description for triggering accuracy.
 ---
 
 # Skill Creator

package/bundles/codex/AGENTS.md

@@ -47,11 +47,15 @@ Claude Code has subagents with their own context for exactly this; agents withou
 
 ### Resuming a session
 On a fresh session read in order: `.caddis/relay.md` (if present) → the active plan in
-`.caddis/plans/` → its tracker. The conversation is disposable; these files are the truth.
+`.caddis/plans/` → its tracker. Codex has no startup hook and must read `.caddis/relay.md`
+(the workstream index or active relay) on session start. The conversation is disposable;
+these files are the truth.
 
 ## Always-active conventions
 - **Commits**: Conventional Commits (`feat:`, `fix:`, `test:`, `chore:`). One logical change per commit.
 - **Terse**: lead with the answer; results/code over prose.
+- **Reuse**: Before writing new code, search for an existing function to reuse. Prefer the standard library or an installed package over new code or a new dependency.
+- **Shared points**: Before changing a function, find all its callers. Fix the shared point, unless the callers need different behaviour.
 - **Secrets**: never commit; keep env/config secrets git-ignored. Never print credentials.
 - **Document frontmatter**: Every descriptive Markdown deliverable you write (plan, PRD, ADR, design doc,
   runbook, analysis, handoff) must open with a YAML frontmatter block:

package/bundles/manifest.json

@@ -1,8 +1,8 @@
 {
-  "poolVersion": "1.3.121",
+  "poolVersion": "1.3.123",
   "bundles": {
-    "antigravity-plugin": "1.3.121",
-    "antigravity-plugin-extras": "1.3.39",
+    "antigravity-plugin": "1.3.123",
+    "antigravity-plugin-extras": "1.3.40",
     "codex": "unknown"
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@caddis/cli",
-  "version": "0.4.34",
+  "version": "0.4.36",
   "description": "Install, update and diagnose the caddis dev harness across every coding agent you use (Claude Code, agy/Antigravity, and more).",
   "keywords": [
     "caddis",