Umbrella skill for all Convex development patterns. Routes to specific skills like convex-functions, convex-realtime, convex-agents, etc.

External API integration and webhook handling including HTTP endpoint routing, request/response handling, authentication, CORS configuration, and webhook signature validation

convert Voyager Screen to navigation 3

convert Voyager Screen to navigation 3

Prepares the codebase for a commit by formatting code and helping identify temporary comments.

Runs all necessary checks (lint, tests) and pushes to GitHub. Use this as the final safety gate.

Runs unit tests to quickly verify changes during the development loop.

This skill provides guidance for writing test factories in the Packmind codebase. It should be used when creating or updating factory functions in `**/test/*Factory.ts` files to ensure realistic test data with variety.

Generate local PR/branch review artifacts for the current branch vs its base - an in-repo canonical spec (if present) or an inferred review `spec.md`, plus `system-design-review.md`, `code-review.md`, and `walkthrough.md` (via `.agents/skills/drive-pr-walkthrough/SKILL.md`). Writes artifacts to disk (next to the in-repo spec when present, otherwise under `wip/`). Use when the user asks for a local PR/branch review, a code review, a system design review, to "review this branch", or to produce written review docs. Do not modify implementation code.

Bumps `biome` package versions (e.g. `@biomejs/biome`) using `pnpm`, aligns `biome.jsonc` files with the new version/s across the repository and runs biome-related checks. Use when required to update `biome` to a newer version - explicitly or implicitly (e.g. after running `pnpm up`, `pnpm update`, `pnpm upgrade` without specific package names).

Generate and iteratively refine engineering specs from a description, conversation summary, or blank template. Use when the user wants to create a spec, PRD, product requirements document, write up requirements, or spec out a feature. Also use when summarising a conversation into a spec.

Create a new transient project workspace under projects/<project>/ (folders + optional stub docs), then hand off to drive-create-spec / drive-generate-plan.

Migrates a monorepo package from `tsup` to `tsdown`. Use when asked to migrate a package to `tsdown` and the package has used `tsup` thus far.

Generate an execution plan from a spec, with milestones, tasks, and test coverage for all acceptance criteria. Use when the user wants to plan a project, break a spec into milestones, generate tasks from a spec, or create an execution plan. Optionally creates a Linear project.

Start here for all API mocking in tests. Covers auto-generation, fixtures, and when to use other skills. Required reading before creating, refactoring, or modifying any test involving API calls.

REQUIRED for editing any skill file. Ensures changes sync to Claude, Codex, and Cursor. Never edit .claude/skills/ files directly - always use this skill.

AI Manipulation Defense System implementation with Midstream, AgentDB, and lean-agentic

Insert or read behavior log rows in the local database (behavior_logs). Use when recording a good/bad behavior entry, attaching a Pavlok API response JSON, adding a coach comment, or fetching recent logs via scripts/behavior_log.py.

Send a Pavlok stimulus via the Pavlok API using scripts/pavlok.py. Use when you need to trigger vibe/beep/zap with a numeric value in this repo and print the API response.

Helps developers understand when to use @solana/kit vs @solana/web3.js (v1), provides migration guidance, API mappings, and handles edge cases for Solana JavaScript SDK transitions