dev-kit

Audit your Claude Code static config for token waste and bloat. Use when the user says "audit my context", "context audit", "check my settings", "why is Claude so slow", "token optimization", or runs /context-audit. Reads the user's /context output to weight findings by actual token cost, then audits MCP servers, CLAUDE.md files, skills, settings.json, and permissions. Returns a health score with prioritized fixes. Scope: STATIC config only — settings, instruction files, MCP overhead, permission rules. Does NOT audit conversation-level bloat (oversized Bash outputs, repeat file reads, accumulating tool results) — that's a separate concern surfaced as a callout when relevant signals appear.

Record and maintain a project's follow-ups and to-dos in Jason's central Obsidian "closet" so loose threads survive across sessions and can be pulled from one list. Use proactively whenever work leaves a deferred, blocked, descoped, or noticed-but-not-fixed item; when the user says "add a to-do/follow-up", "log this for later", "the closet", "things to follow up on", "remind me to"; and at the end of a wave, session, or orchestration. Orchestrators and workers both log here — for each completed-with-leftovers or blocked dispatch.

Ephemeral, forkable Postgres databases via ghost.build — the agent-native database service. Use this skill when the user needs: a throwaway Postgres for testing, a safe fork of an existing database to experiment against without polluting state, an isolated DB per agent task, or any work that benefits from "create-fork-discard freely" semantics. Triggers: user says "ghost create", "fork the database", "spin up a Postgres", "I need a test DB", "give me a database for this agent", "ghost.build", or describes a scenario that would otherwise require a Docker postgres container + manual setup + manual teardown. The CLI lives at `~/.local/bin/ghost`. MCP tools are also available (install via `ghost mcp install`) and are the preferred surface for in-conversation database operations.

Node.js / Bun / TypeScript house style for your projects — runtime choice, imports, naming, errors, async patterns, testing. Load this skill whenever a worker is touching `.ts`, `.tsx`, `.js`, or `.mjs` files in a your project. Use it instead of guessing the conventions from the surrounding code (the surrounding code may itself be drift). Defaults documented here are the operator's preferences as expressed across the house conventions.

Maintain your Obsidian vault at <OBSIDIAN_VAULT_PATH>/. Every project gets the same standardized folder layout, lives under <Project Name>/, and stays current as work progresses. Trigger when the user says "Obsidian vault", "the vault", "update the vault", or asks for project status updates after work landed. Skill encodes the layout, the maintenance contract, the housekeeping rubric, and the human-AND-AI-readable format conventions.

Hard rules for working with a production database. Triggers when the user says "production database", "prod database", "prod DB", "live database", or when any database-modifying command (`prisma db push`, `prisma migrate`, `ALTER`, `DROP`, `UPDATE`, `DELETE`, `CREATE INDEX`, etc.) is being considered against a `DATABASE_URL` that resolves to production. Encodes the hard lesson that a stale-branch `prisma db push --accept-data-loss` can silently drop a column with live data. This skill prevents that pattern from recurring by mandating surgical, single-statement, idempotent SQL with explicit per-operation confirmation for anything destructive.

Python house style for general engineering work — tooling (uv, ruff, pytest), imports, types, errors, async patterns, packaging. Load this skill whenever a worker is touching `.py` files in a your project. Most your projects are Bun-first, but supporting utilities, ML code, and external integrations may be Python. These are the defaults to apply when the project's local CLAUDE.md doesn't override.

Rust house style for general engineering work — cargo, clippy, rustfmt, error handling with `thiserror` / `anyhow`, async patterns with tokio, testing. Load this skill whenever a worker is touching `.rs` files. Some projects have a Rust component (the policy bash-gate kernel) and several adjacent projects use Rust for performance-sensitive paths. These are the defaults to apply when the project's local CLAUDE.md doesn't override.

Workflow for executing against a written specification — read the spec, ask clarifying questions ONLY for real ambiguity, implement, test, ship. Honors "Done when" criteria, scope boundaries, and constraint adherence. Use this skill whenever a worker is dispatched with a defined GOAL, DELIVERABLE, DONE WHEN, and CONSTRAINTS — i.e. anything spawned through team templates or orchestrator-mode dispatch. Also use when reading an ADR / roadmap / RESUME.md and converting it to executable work. The skill enforces: spec is the contract, not a suggestion. Don't gold-plate. Don't ask permission for things the spec already decided. Don't leave the spec half-done.