DanSnow

Implement or resume tasks from a Spectra change

Archive a completed change

Query openspec/documents and answer questions

Audit changed code for security sharp edges — dangerous defaults, type confusion, and silent failures

Commit files related to a specific Spectra change

Systematically debug a problem using a four-phase workflow

Have a focused discussion about a topic and reach a conclusion

Update an existing Spectra change from external context

Create well-structured commits following Conventional Commits spec. Use this skill whenever the user wants to commit, make a commit, stage changes, or write a commit message. Automatically detects jj vs git, groups changed files into logical commits, and formats messages as `type(scope): description`. Trigger on: "commit", "make a commit", "commit my changes", "stage and commit", "write a commit", "commit this", "conventional commit", "split into commits".

Audits a frontend codebase for design token and component extraction opportunities, then produces a structured proposal before touching any code. Use this skill whenever the user says things like "extract my design tokens", "set up a token system", "clean up my CSS variables", "create shared components", "reduce duplication in my UI", "set up a design system", "my components have too much copy-paste", "add a Button component", "standardize my buttons", "add shadcn", "use cva for variants", or asks to refactor repeated UI patterns (nav items, form fields, modals, page headers, buttons, inputs). Works with any frontend stack — React, Vue, Svelte, plain HTML/CSS, Tailwind, CSS Modules, vanilla CSS. Trigger even if the user only mentions one aspect (just tokens OR just components OR just buttons) — the skill handles all and will focus on whichever is relevant.

Jujutsu (jj) version control workflows and GitHub integration. Use when working with jj commands, creating commits with bookmarks, pushing to remote, creating PRs, or when the user mentions "jj", "jujutsu", "bookmark", or version control operations that involve jj instead of git. Also use when encountering jj-specific concepts like changes vs commits, bookmark tracking requirements, or when troubleshooting jj/GitHub integration issues.

Write a marimo notebook in a Python file in the right format.

Set up oxlint (linting) + oxfmt (formatting) for JavaScript/TypeScript projects. Use when user asks to "migrate to oxlint", "switch to oxc", "use oxfmt", "set up oxlint", or wants to adopt the oxc toolchain for linting and formatting — whether migrating from ESLint, Biome, Prettier, or starting fresh.

Search past Claude Code and Codex sessions. Triggers: /recall, "search old conversations", "find a past session", "recall a previous conversation", "search session history", "what did we discuss", "remember when we"

oRPC client-side patterns for TypeScript frontends using @orpc/contract, @orpc/client, @orpc/openapi-client, and @orpc/tanstack-query. Use when writing or modifying API client code that uses oRPC, adding new API endpoints to an oRPC contract, creating queries or mutations with oRPC + TanStack Query, or migrating from raw fetch to oRPC. Triggers: "add endpoint", "add API call", "oRPC", "contract", "queryOptions", "mutationOptions", "OpenAPILink".

Convert Markdown documentation to Atuin Runbook (.atrb) format with interactive terminals. Use when converting runbooks, migration docs, or step-by-step guides to executable runbook format. Triggers on "convert to runbook", "make runbook", "create .atrb", or when working with Atuin runbook files.

Implement or resume tasks from an OpenSpec change

Archive a completed change

Query openspec documents and answer questions based on spec content

Audit changed code for security sharp edges — dangerous defaults, type confusion, and silent failures

Systematically debug a problem using a four-phase workflow

Have a focused discussion about a topic and reach a conclusion

Update an existing OpenSpec change from external context

Create a change proposal with all required artifacts

Create a change proposal with all required artifacts

Implement or resume tasks from a Spectra change

Archive a completed change

Query openspec/ documents and answer questions

Systematically debug a problem using a four-phase workflow

Have a focused discussion about a topic and reach a conclusion

Update an existing Spectra change from external context

Process URLs queued in inbox.md, categorize them against lists/*.yaml, and add entries to the right category file. Use when the user asks to process the inbox, add URLs to the list, or triage new tool links into this repo's categories.

Interactive data exploration and visualization skill. Use when users ask to visualize data, analyze datasets, create charts, or explore data files (CSV, Excel, Parquet, JSON). This skill guides through data exploration, proposes visualization strategies based on data characteristics, creates interactive Plotly charts in marimo notebooks, and generates analytical conclusions.