Claude Skills by vindm

Teaching material for Claude Code. When you bootstrap a `.claude/` directory, this doc teaches you HOW to author the design-system reference skill — the always-on entry-point that EVERY UI agent loads to learn the project's tokens, chrome primitives, surface hierarchy, motion presets, status colors, library gotchas, and i18n conventions. It's the skill that prevents agents from re-deriving "what does this project's design system contain" on every dispatch.

Set up LLM workflow discipline for projects that use AI / LLM calls in production or eval suites. Authors an eval-cost-watcher agent that projects token cost BEFORE regression evals run, plus an AI-workflow-discipline rule covering mock-mode placement, fixture freshness, and multi-stage cost accumulation. Optionally a small eval-regression skill stub. Invoke /dotclaude:ai-workflow only when the project actually has AI workflows.

Full hierarchical bootstrap of a project's AI dev infrastructure — walks 7 layers from identity to maintenance, authoring CLAUDE.md + docs/ knowledge graph + .claude/ system in one guided session. Reads the project first, interviews per-layer, stages everything for review, then commits. The headline v2 command. Invoke /dotclaude:bootstrap in any project root.

Set up coding hygiene + voice discipline for a project. Authors a tailored kit of code-review agent, decomposition skill, file-size + voice rules, and edit-time hooks — derived from the project's stack, its actual file-size distribution, the bug classes visible in git history, and any project-specific voice. Invoke /dotclaude:coding in any project root with source code.

Set up database / persistent-state discipline for a project with a DB. Authors a data-auditor agent (5 categories of integrity check), a migration-create skill, query-discipline rule (CLI > MCP DB tool for reads), and edit-time regen hook — all derived from the project's actual schema, migration framework, and access-control model. Optionally an RLS-security-reviewer if Postgres + row-level security is in use. Invoke /dotclaude:data in any project with persistent state.

Set up design / IA / UX / a11y / visual-quality discipline for a project. Authors a tailored kit of design audit agents, IA skills, and design-token rules — derived from the project's actual UI surfaces, the user's named design benchmarks, and past design failure modes. Invoke /dotclaude:design in any project root that has a human-facing surface.

Lighter alternative to /dotclaude:bootstrap when you want Layer 6 domain kits only, skipping upstream layers. Orchestrates the relevant subset of domain skills (design / coding / planning / testing / data / ai-workflow) based on project shape — no identity / architecture / process / quality-bar / knowledge-graph / maintenance authoring. Use /dotclaude:init for incremental Layer 6 setup on partial-brownfield projects, or when the user already has CLAUDE.md authored by hand.

Set up pre-implementation discipline + audit routing for a project with regular multi-module changes. Authors a pre-flight agent that maps integration points, parallel paths, and cross-boundary surfaces — plus an audit-routing rule that orders which agent fires for which question. Invoke /dotclaude:planning in any project where "we shipped feature X and broke unrelated thing Y" has happened more than once.

Set up test architecture + coverage discipline for a project. Authors a tests-architect agent (4 modes — audit / design / implement / maintain) tuned to the project's stack, test framework, risk model, and existing patterns. Plus a small "test discipline" rule when helpful. Invoke /dotclaude:testing in any project where tests exist OR should exist.