ticket-format
The ticket-format skill provides a standardized three-section template for creating Linear or Superset tickets in the superset-sh/superset repository. Use it when drafting or grooming tickets to ensure consistent structure: a context section explaining the problem or feature request, an optional references section tracking the ticket's origin, and implementation notes with optional subsections for files, approach, related code patterns, and known constraints. This enforces outcome-focused communication and enables progressive detail as codebase context becomes available.
git clone --depth 1 https://github.com/superset-sh/superset /tmp/ticket-format && cp -r /tmp/ticket-format/.agents/skills/ticket-format ~/.claude/skills/ticket-formatSKILL.md
# Ticket Format ## Context 2–4 sentences. What's broken or wanted, and why. Outcome-focused, not solution-focused. ## References Where the ticket came from. Omit section if none. | Source | Who | Link | Date | |--------|-----|------|------| | Slack #feedback | @alice | [thread](…) | 2026-05-10 | ## Implementation notes Agent-groomed. Leave empty if you don't have codebase context; a later grooming pass will fill it in. When you do fill it in, use these sub-headings and skip what doesn't apply: - `### Files`: `path:line` + why relevant - `### Approach`: one paragraph - `### Related code`: similar patterns in the repo - `### Gotchas`: constraints, prior incidents
Validates project structure against co-location and architecture patterns defined in AGENTS.md
Create workspaces, spawn agents, schedule automations, and manage Superset projects/tasks/hosts via the `superset` CLI. Use to orchestrate coding agents across devices from the terminal.
Verify UI behavior end-to-end by driving the running desktop app over the Chrome DevTools Protocol. Use when asked to verify, reproduce, or confirm a UI change, bug, or regression in the real app rather than in tests.
Create a database migration with Drizzle on a fresh Neon branch. Use when changing the packages/db schema or generating migrations.
Walk the user through design or implementation decisions one at a time, or review completed code one change at a time. Use when the user says "walk me through each decision", "let's decide together", "help me work through these choices", "walk me through what you did", or "QA step by step". Present concise context, mutually exclusive options, log each answer, and finish with a summary.
Critique and improve the visual design of an existing UI component with concrete implementation guidance. Use when the user asks to redesign, restyle, reimagine, polish, or improve a component, screen, or interface, especially in React and Tailwind codebases.
Read and update the Superset desktop app's user settings (theme, fonts, terminal, git, notifications, behavior) via the superset CLI, including creating and installing custom themes from JSON. Use when asked to change app settings, switch or create a theme, adjust fonts, or configure desktop preferences without opening the settings UI.
Personalized audit that teaches the advanced Superset features the user isn't using yet (automations, parallel agents, tasks, multi-host, terminal remote control, custom commands, MCP) and sets them up live. Use when the user wants to get more out of Superset, asks "what else can Superset do", "how do I 10x my workflow", "what am I missing", or wants to learn a specific Superset feature.