dotfiles

Deploy and restow stow packages in this dotfiles repository. Use when editing files inside emacs/, git/, shell/, mail/, ssh/, utils/, agents/, claude/, or copilot/ packages, running make, checking package .stow-local-ignore files, or adding a new stow package — even if the user only says "install dotfiles" or "deploy config".

Creates and edits Agent Skills (SKILL.md files) according to the Agent Skills specification. Use when the user wants to create a new skill, scaffold a skill, write a SKILL.md, make an agent skill, define a reusable agent capability, or update an existing skill's instructions.

Creates Open Agent Format (OAF) compliant agent directories with AGENTS.md manifests, skills, MCP configs, and version history. Use when the user wants to create an OAF agent, scaffold an agent directory, generate an AGENTS.md file, set up Open Agent Format configuration, build a multi-agent package, or create a portable agent definition that works across Claude Code, Goose, Deep Agents, and Letta.

Teach agents how to write idiomatic Effect TypeScript code using Effect.gen generators, Effect.fn traced functions, pipe-based instrumentation, retry/timeout patterns, and Schema-tagged error handling. Use when writing effectful TypeScript with the Effect framework — Effect.gen, Effect.fn, Effect.pipe, Schedule, Effect.retry, Effect.timeout, Effect.catchTag, Effect.catch, TaggedErrorClass, Schema.Defect, or "defects" — even if the user only says "write an Effect program" or "handle errors in Effect".

Teach agents how to use Effect's ecosystem modules — typed HTTP clients with HttpClient and Schema, CLI applications with Command/Argument/Flag, OpenTelemetry observability with @effect/opentelemetry, and the use pattern for wrapping third-party Promise libraries. Use when making HTTP requests, building command-line tools, adding OpenTelemetry tracing, or integrating Promise-based libraries in Effect projects — even if the user only says "make an API call" or "build a CLI".

Teach agents how to model domain data with Effect Schema — records via Schema.Class, variants via Schema.TaggedClass + Schema.Union, branded primitives, exhaustive pattern matching with Match.value, and JSON serialization with Schema.fromJsonString. Use when defining data models, domain types, discriminated unions, branded types, or doing JSON parsing/validation in Effect projects — even if the user only says "define a schema" or "model this domain".

Teach agents how to structure Effect applications using Context.Service for dependency injection, Layer for implementations and resource lifecycle, service-driven development, and Config for type-safe configuration loading. Use when defining services, composing layers, providing dependencies, managing config, or structuring an Effect application's entry point — even if the user only says "set up services" or "wire up dependencies".

Teach agents how to test Effect TypeScript code using @effect/vitest — it.effect for native Effect tests, TestClock for deterministic time, Layer provisioning for dependency injection in tests, and the service-spy pattern for assertions. Use when writing tests for Effect code, setting up vitest for an Effect project, or mocking Effect services — even if the user only says "write tests" or "test this Effect code".

Edit modular Emacs configuration in emacs/.config/emacs/. Use when changing init-*.el modules, use-package setup, custom lisp packages, tree-sitter grammars, XDG path helpers, or Emacs appearance/editing/prog settings — even if the user only mentions "Emacs config" or "init.el".

Invoke GNU Stow to manage symlink farms — stow, restow, unstow, and simulate package deployment. Use when running stow commands, deploying dotfiles via symlinks, fixing stow conflicts, understanding -d/-t flags, restow after file changes, unstow with -D, dry-run with -n, or .stow-local-ignore rules — even if the user only says "symlink config" or "install package to home" without naming Stow.

Consult local Unix manual pages with man and info before guessing CLI flags. Use when configuring niche command-line tools, looking up man pages, Texinfo docs, apropos searches, verifying installed-version behavior, or when the user says "check the manual" — even for stow, mbsync, msmtp, notmuch, pass, or other poorly represented tools not named explicitly.

Configure GPTel, MCP servers, and AI tools in Emacs. Use when editing init-ai.el, init-ai-tools.el, gptel backends, mcp-hub-servers, prompts/ templates, or adding new agent tool definitions — even if the user only says "AI", "Claude", "MCP", or "gptel".