dotfiles

Generate clean, minimal technical SVG diagrams in a consistent Cloudflare-inspired style. Use when creating architecture diagrams, flow diagrams, or component diagrams for blog posts and documentation.

Guides creation and improvement of best-practice agent skills following the open format specification. Covers frontmatter, directory structure, progressive disclosure, reference files, rules folders, degrees of freedom, content patterns, executable scripts, MCP tool references, evaluations, cross-model testing, and a ten-dimension audit protocol for existing skills. Use when creating a new skill, authoring SKILL.md, setting up a rules-based audit skill, structuring a skill bundle, writing scripts inside a skill, evaluating a skill, improving or rewriting an existing skill, or asking "how to write a skill", "improve this skill", "audit my skill", or "review this SKILL.md".

Diagnoses Erivault application behavior across product docs, repo code, Cloudflare, Neon Postgres, queues, Durable Objects, R2 assets, AI Gateway, media workflows, browser, and mobile capture state. Use when investigating Erivault bugs, asking "what happened", checking logs, verifying deploys, debugging capture evidence, or designing testable diagnostics.

Design a new product module's full screen set in the Erivault `erivault-web` Paper file, reusing the established design system (tokens, shell, components) and grounded in the module's ADR + implementation plan. Covers researching the existing system, extracting authoritative tokens, planning the state×role×platform matrix, building screens via duplicate-and-adapt, and tying into existing surfaces. Use when designing a new module or surface (tenancies, inspections, renewals, capture, packs...) in Paper, extending the erivault-web design file, building all states/roles for a feature on web and mobile, or when the user says "design the X module", "design a new flow", "design X in the Paper board", "add the screens for X", or "make it consistent with our design system".

View and edit cmux settings in ~/.config/cmux/cmux.json. Use when the user wants to change cmux preferences (appearance, sidebar, notifications, automation, browser, shortcuts), set a value by JSON path, validate the file, open it in an editor, or look up which keys cmux recognizes. Triggers on '/cmux-settings', 'change cmux setting', 'set <something> in cmux', 'cmux config', 'cmux.json', or 'rebind a cmux shortcut'.

Perform exhaustive code reviews using multi-agent analysis and dynamic skill discovery

Execute work plans efficiently while maintaining quality and finishing features

Reviews stop-gate requests scoped to the immediately previous assistant turn. Use when the user asks for a stop-gate review, allow/block decision, or previous-turn-only review, especially when non-editing turns should return ALLOW immediately.

Add Agentation visual feedback toolbar to a Next.js project

Render Mermaid diagrams as SVG and PNG using the Beautiful Mermaid library. Use when the user asks to render a Mermaid diagram.

Find design smells in a breadboard and fix them. Use after breadboarding to validate affordance boundaries, naming, and wiring correctness.

Expert guidance for creating, writing, and refining shared agent skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices across Claude, Codex, and OpenCode.

Remove AI-generated code slop from current branch

Design engineering principles and patterns for building polished, accessible web interfaces. Use this skill when building UI components, reviewing frontend code, implementing forms, handling touch interactions, optimizing performance, or creating marketing pages. Triggers on: design engineering, UI polish, input fields, form validation, button states, touch devices, mobile UX, accessibility, a11y, keyboard navigation, aria labels, font rendering, typography, layout shift, z-index, animations, transitions, easing, hover effects, tap targets, iOS Safari, prefers-reduced-motion, marketing pages, landing pages, dark mode, theme switching, scrollbars, gradients, shadows, virtualization, preloading.

Create Excalidraw diagram JSON files that make visual arguments. Use when the user wants to visualize workflows, architectures, or concepts.

This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.

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 (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

Fix incorrect SKILL.md files when a skill has wrong instructions or outdated API references

Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. This skill should be used when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.

This skill provides workflows for managing Jira tickets using Atlassian's official CLI (acli). It should be used when creating, viewing, searching, or managing Jira work items from the command line. Triggers on "create jira ticket", "search jira", "view issue", "jira cli", "jira workitem".

Pre-brainstorm product diagnostic — challenge whether something is worth building before shaping begins. Two modes: Startup (hard questions about demand, users, wedge) and Builder (enthusiastic design partner for side projects, hackathons, learning). Produces a design document, never code. This skill should be used when someone says "I have an idea", "is this worth building", "help me think through this", "office hours", or before /workflows-brainstorm.

qmd - Search local markdown notes, documentation, and Claude session history. Use when user says "qmd", "search notes", "find docs", "search sessions", "local search", "knowledge base search", or needs to retrieve markdown files.

Resolve all PR comments using parallel processing, then extract reusable conventions

Resolve all pending CLI todos using parallel processing

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

Use this methodology when collaboratively shaping a solution with the user - iterating on problem definition (requirements) and solution options (shapes).

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Triage and categorize findings for the CLI todo system

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

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.

Apply professional typographic principles when creating web pages, components, stylesheets, or any HTML/CSS output. Use this skill whenever generating or reviewing CSS that involves text styling, layout of reading content, font sizing, spacing, or any UI where readable prose matters. Triggers include: requests for "good typography", "readable text", "type scale", styling body copy, blog layouts, article pages, documentation sites, landing pages with prose, email templates, or any review of typographic quality in existing CSS/HTML.

Shape a feature through collaborative R/S/fit-check dialogue before planning implementation

Enhance a plan with dynamic skill/agent discovery and targeted research

Ship-readiness pass: review, fix, and validate working copy or PR changes. This skill should be used when asked to finalize, harden, do a final pass, or make code shippable. Runs as a forked subagent.

Founder-mode plan review — stress-test a plan before implementation begins. Four modes: EXPAND (dream big), SELECTIVE (hold scope + cherry-pick expansions), HOLD (maximum rigor), REDUCE (strip to essentials). Reviews architecture, errors, security, data flow, tests, performance, observability, deployment, long-term trajectory. Produces error/rescue maps, failure mode registries, mandatory diagrams. This skill should be used after /workflows-plan produces spec.md and prd.json, before /workflows-work begins implementation. Triggers on "review the plan", "is this plan good enough", "plan review", "CEO review", "think bigger", "expand scope", "rethink this", "is this ambitious enough".

Transform feature descriptions into well-structured specs and executable PRDs