skills

Interact with Atlassian Jira and Confluence from the terminal. Search, create, and update Jira tickets; read, search, create, and update Confluence pages. Use when the user mentions Jira tickets, issues, work items, sprints, Confluence pages, documentation, or Atlassian in general.

Write BDD scenarios grounded in existing UI/UX implementation. Researches pages, components, types, and mock data before writing any scenario. Use when generating .feature files for a product that already has a working app or prototype.

Onboard a new Claude Code user — set up their ~/.claude/CLAUDE.md, install relevant skills, and start a structured learning program covering best practices. Use when setting up Claude Code for the first time, onboarding someone to Claude Code, or continuing a learning session.

Generate poster images. Use when the user asks to create a poster, flyer, print material, social media graphic, or any visual marketing asset

Track ticket sales for a live event (concert, festival, conference, workshop) with daily snapshots, generate a burndown chart comparing actual sales to ideal-linear targets and tier-cumulative milestones, and report whether the event is on pace. Use when the user asks how sales are going, wants to know if their event will sell out, asks for a daily sales report, wants to set up sales tracking for an upcoming event, or asks about ticket pace / velocity / projection. Trigger generously: phrases like 'how is concert sales going', 'burndown for my event', 'are we going to sell out', 'sales velocity', 'daily ticket chart', 'how many tickets do we need to sell', or any case where the user has a ticketed event with a fixed sales window and wants visibility on pacing.

AI content and SEO agent that audits sites, fixes indexing issues, writes blog posts aligned with OKRs, generates YouTube metadata, and produces monthly analytics reports. Use when asked to run SEO audit, write a blog post, create content calendar, fix indexing, generate YouTube descriptions, or produce an analytics report.

Use when a software project under ~/Projects should become a separate organization under ~/Orgs, or when governance files are mixed into a code repo and need to be split into a dedicated org workspace.

Transform requirements into structured user stories with acceptance criteria using INVEST principles. Use when the user asks to write a user story, create a ticket, define acceptance criteria, or convert requirements into dev-ready stories.