.dotfiles

Universal commenting and documentation conventions across all languages. Load when writing or reviewing substantial comments, docstrings, file headers, or migration documentation. Project-specific commenting standards in `docs/commenting-standard.md` (when present) extend or override this baseline.

Exhaustive post-work audit for any codebase. Run after finishing a feature, sprint, bug fix, or refactoring pass to find overlooked edge cases, discarded response data, missing cross-field validations, misleading success signals, untested failure paths, and implicit assumptions. Invoke with /deep-audit or /deep-audit followed by context. Use this skill whenever the user says audit, review my changes, check my work, what did I miss, post-mortem, sanity check, edge cases, or asks to verify completeness of recent code changes.

Use when modifying the agentic coding environment, including dotfiles, skills/rules wiring, AGENTS.md/CLAUDE.md loading, Stow symlinks, Claude/Codex/OpenCode/Pi config, plugins, MCP, hooks, or harness compatibility. Loads the runbook to avoid breaking cross-harness setup. Defer to skill-creator-global for skill authoring craft, description quality, and progressive disclosure.

Retrieves up-to-date documentation, API references, and code examples for any developer technology via the ctx7 (Context7) CLI. Use this skill whenever the user mentions "ctx7" or "context7", or asks about a specific library, framework, SDK, CLI tool, or cloud service -- even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer -- do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.

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.

Create, revise, or review Agent Skills for authoring quality. Use when writing SKILL.md content, improving skill descriptions and trigger words, deciding what belongs in SKILL.md versus references/scripts, or diagnosing why a skill over-triggers or under-triggers. Defer to agentic-coding-harnesses for dotfiles, Stow, symlinks, harness visibility, AGENTS.md, plugins, MCP, or environment wiring.

Search, scrape, and interact with the web via the Firecrawl CLI. Use this skill whenever the user wants to search the web, find articles, research a topic, look something up online, scrape a webpage, grab content from a URL, get data from a website, crawl documentation, download a site, or interact with pages that need clicks or logins. Also use when they say "fetch this page", "pull the content from", "get the page at https://", or reference external websites. This provides real-time web search with full page content and interact capabilities — beyond what Claude can do natively with built-in tools. Do NOT trigger for local file operations, git commands, deployments, or code editing tasks.

Automate browser interactions, test web pages and work with Playwright tests.

Restore context after /clear or new session. Shows current branch, uncommitted changes, open PRs, recent commits, issue tracker state, and what to do next. Use whenever starting a new session, resuming work, or after clearing context. Triggers on catchup, where was I, what was I doing, restore context, resume, status.

Investigate a problem thoroughly and ship a well-tested fix. Accepts a GitHub issue number, issue URL, PR URL, discussion URL, security alert URL, Linear issue identifier or URL, or plain text description. Enters plan mode for investigation before writing any code.

Commit, rebase, and merge the current branch.

Rebase the current branch with smart conflict resolution.

Adversarial code review of the current branch. Launches a thorough review checking correctness, security, performance, architecture, type safety, and test coverage. Verifies findings against current library documentation via ctx7 and web sources to avoid flagging correct modern patterns as errors. Use after completing a feature, before merging any agent-generated code, when running gate checks between waves, or whenever you suspect code quality issues. Also use when asked to "review," "audit," "check," or "look over" code changes, even if the user doesn't say "adversarial."

Stage, commit, push, create PR, wait for CI, merge, and clean up. Fully automatic end-to-end shipping workflow that detects current state and picks up from wherever the process left off. Use when shipping changes, merging, creating a PR, pushing code, or when the user says ship it, merge it, send it, land it, push this, create a PR, open a PR.

Reference for the workmux CLI that manages git worktrees and tmux windows as isolated development environments. Use when the user mentions workmux, worktrees, or parallel agent workflows.

Launch one or more tasks in new git worktrees using workmux.

Python conventions for this user. Loads only when reading or editing .py / .pyi files. Reflects Python 3.14 (PEP 749 lazy annotations, PEP 750 t-strings, PEP 779 free-threading), 3.13 floor, modern tooling (uv, ruff, pyright/mypy, pytest 9 + pytest-asyncio 1.3), Pydantic v2, FastAPI Annotated dependency style.

Production scalability rules for backend code. Apply when writing or editing database queries, API endpoints, background jobs, caching layers, or server-side code that will run under load. Prevents the scaling cliff (works for 10 users, breaks at 1000) by enforcing N+1 avoidance, cursor pagination, request coalescing, async queues, connection pooling, timeouts, rate limits, and observability standards. Triggers on database, query, API, endpoint, route, handler, controller, service, cache, queue, background job, worker, migration, schema, ORM, performance, scale, or production hardening tasks.

Security conventions for code that handles secrets, authentication, user input, external calls, cryptography, dependencies, or LLM/AI integrations. Load when working with auth flows, API endpoints, webhooks, file uploads, queue consumers, prompts to LLMs, or anything that touches untrusted data.

TypeScript and Next.js conventions for this user. Loads only when reading or editing .ts/.tsx files. Reflects TypeScript 6 (strict-by-default), Next.js 16 (async APIs, proxy.ts, Cache Components), React 19.2.