szinn

Jujutsu (jj) version control expert. Use when the project contains a `.jj/` directory, user asks about jj, jujutsu, stacking changes, bookmarks, rebasing, conflict resolution, or any VCS operations involving jj. Covers the full jj command surface including workspace concepts, operation log, revsets, and GitHub/Gerrit integration.

Set up isolated jj workspaces for parallel development in jj projects. ALWAYS use this skill — not git worktree skills — when the project contains a .jj/ directory. Use when starting feature work that needs isolation, before executing implementation plans, creating new workspaces, or any time physical directory isolation is needed in a jj repo.

Modern Dioxus 0.7 + Tailwind CSS development guide. Use when asking about Signals, Stores, ReadSignal props, async patterns, components, or Tailwind integration in Dioxus 0.7.

Expand a brief task description into a structured, context-rich prompt that maximizes first-attempt success. Research-only — does not make code changes.

Use when the user mentions issues, asks what to work on, references a backlog, asks about issue status or pipeline state, wants to find ready work, or references an issue slug (e.g. IB-42). Covers all IssueBoss MCP interactions including triage, artifact management, and pipeline advancement.

Orchestrate insights-locator and insights-analyzer to find and distill prior context from .insights/. Use when a topic may have prior research, at the start of brainstorming/spec/plan phases, or when the user says "check insights", "research insights", "look for prior context", or "what do we know about X".

Ad-hoc research skill — investigate any topic (no IssueBoss issue required) by dispatching research-topic-processor, presenting findings inline, and optionally saving a document to .insights/shared/research/.