dotfiles

Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

Turn the current conversation context into a Product Requirements Document (PRD) and submit it as a GitHub issue. Use when the user wants to create a PRD from the current context, or invokes `/create-prd`.

An extremely strict maintainability audit for abstraction quality, giant files, and spaghetti-condition growth. Use for a deep code quality review, code quality audit, or harsh maintainability review.

Write clean, modular bash scripts with proper error handling. Triggers on 'write a script', 'bash script', 'shell script', or 'automate with bash'.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Rigorous critique-fix loop using fresh-eyes reviewer subagents. Use when the user asks for an "adversarial review", says "review my changes rigorously", "critique this code" or invokes `/adversarial-review`. Expensive — don't trigger on casual review requests.

Guidelines for creating git commits. Use when making commits, staging changes for commit, or deciding how to split changes across commits.

Systematic questioning to clarify requirements, goals, and constraints. Use when there's ambiguity about what the user wants, hidden complexity needs uncovering, or you need to understand before proceeding. Triggers on unclear requirements, vague goals, or when the user says "interview me" or invokes `/interview`.

TypeScript type safety guidelines for writing maximally type-safe code. Apply these patterns when writing or reviewing any TypeScript: discriminated unions, type narrowing, type guards, exhaustiveness checks, avoiding `as` casts, preferring `unknown` over `any`, and making impossible states unrepresentable. Use this skill whenever writing TypeScript code, reviewing TypeScript for type safety issues, or when the user mentions type safety, type narrowing, discriminated unions, or asks to make types stricter/more explicit.

Audit the current plan against the original user request and produce a minimally patched revision.

Generate images using Gemini 3 Pro Image (Nano Banana Pro). Use this skill when the user asks to create, generate, or make an image, picture, illustration, artwork, mockup, or visual. Also use for image editing, transformation, or style transfer when a reference image is provided.