dotfiles

Render a document, a diagram, or a report as HTML for human visualisation.

Use when writing prose meant to read by humans: PR descriptions, docs, blog drafts, emails, design memos

Guidelines on creating issues on GitHub

Run a premortem on any plan, launch, product, hire, strategy, or decision. Assumes it already failed 6 months from now and works backward to find every reason why. Produces a revised plan with blind spots exposed. MANDATORY TRIGGERS: 'premortem this', 'premortem my', 'run a premortem', 'what could kill this', 'future-proof this', 'stress test this plan', 'what am i missing here', 'find the blind spots'. STRONG TRIGGERS: 'what could go wrong', 'am i missing anything', 'poke holes in this', 'where will this break', 'devil's advocate this'. Do NOT trigger on simple feedback requests, or factual questions. DO trigger when someone has a plan or commitment where the cost of being wrong is high.

Schedule a prompt to fire back at yourself at a future time or on a recurring cron pattern. Use when the user says "remind me", "every N minutes/hours/days", "at HH:MM tomorrow", "check X periodically", or otherwise asks for any time-based action. Triggered by the `schedule` tool plus the `/schedule` command for listing and deletion.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get roasted on their design, or mentions "brainstorm".

Pick one open task and implement it end-to-end as a unit of work. Use when the user asks to pick a task.

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

Use when the user asks to look for projects, repos, or tools they've starred or curated on GitHub — especially their own GitHub Stars lists. Triggers on phrases like "find projects on GitHub", "from my starred repos", "in my AI starred repos list".

Run a deep research session and save it to Obsidian.

Audit GitHub Actions workflows for supply-chain and CI/CD security vulnerabilities — script injection, expression injection, token exfiltration, unpinned actions, cache poisoning, and Shai-Hulud-class self-replicating worms. Use when the user asks to audit, review, or check the security of GitHub Actions, workflows, CI/CD pipelines, or asks about supply-chain risk, npm publish security, or Shai-Hulud.

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

Guide for creating custom OpenCode agents using markdown files with YAML frontmatter

ImageMagick 7+ image manipulation commands and best practices

Evaluate test suite quality by introducing code mutations and verifying tests catch them. Use for mutation testing, test quality, mutant detection, and test effectiveness analysis.

Fast JavaScript/TypeScript formatter compatible with Prettier. Use when formatting JS/TS files, setting up code formatting, or migrating from Prettier.

High-performance linter for JavaScript/TypeScript built on Oxc. 50-100x faster than ESLint with built-in React, TypeScript, Next.js, and accessibility rules. Use when setting up linting, migrating from ESLint, or configuring lint rules.

Fast, disk space efficient package manager for Node.js with strict dependency resolution and monorepo support

tsdown is a fast and elegant TypeScript library bundler powered by Rolldown and Oxc

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

A blazing fast unit testing framework powered by Vite

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

Create a PRD through user interview, codebase exploration, and module design. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

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.

Use when the user asks to send, transfer, or taildrop files to a device. Triggers on phrases like "send to hex", "transfer to m4x", "taildrop this".

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.

Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.

Create a minimal reproduction for a bug. Use when the user asks to create a repro.

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".