dotfiles

Use when asked to find first customers, early adopters, design partners, beta users, or leads for a startup or product idea, to research who might buy, to define an ideal customer profile (ICP), or to validate early demand from public signals — given a product URL, repository, or description.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Feedback-loop-first diagnosis for hard bugs and performance regressions — build a tight red-capable repro loop before hypothesising.

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

Compact the current conversation into a handoff document for another agent to pick up.

Feedback-loop-first diagnosis for hard bugs and performance regressions — build a tight red-capable repro loop before hypothesising.

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

Behavior-driven front-end testing with DOM Testing Library and user-event. Use when writing or reviewing UI tests for React, Vue, Svelte, browser DOM code, forms, accessibility behavior, async rendering, loading states, error states, or user interactions.

Practical functional programming patterns for immutable data, pure transformations, composable logic, and readable business rules. Use when writing data transformations, reducers, state updates, collection processing, or side-effect-light application logic.

Neovim Lua configuration and plugin development guidance. Use when editing Neovim config, lazy.nvim plugin specs, Lua modules under nvim/, keymaps, autocmds, highlights, LSP setup, diagnostics, Treesitter integration, colorschemes, or Neovim plugin code.

Strict TypeScript patterns for safe, maintainable code. Use when writing or reviewing TypeScript, including .ts or .tsx files, schema validation, dependency injection, public API types, async control flow, and type-safety fixes.

TypeScript strict mode patterns. Use when writing any TypeScript code.