chancegraff
UserHooks, rules, skills, and instructions for use with Claude Code
Categories
Indexed Skills (19)
attentive-brand-artifacts
Use when creating or editing Attentive-branded artifacts, React components, HTML pages, Sandpack themes, decks, docs, charts, dashboards, product mockups, images, social posts, or customer-facing copy that needs Attentive colors, logo handling, typography, data visualization, visual style, or brand voice.
docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of Microsoft Word Documents, such as 'Word doc', 'word document', '.docx', '.dotx', 'microsoft doc'. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a deliverable as a Word or .docx file (to download, email or print), use this skill. However, if they ask for a document, page, report, memo, or notes WITHOUT naming a file format and the session offers Claude's own dedicated document or page skill or connector, use that instead, even if they will email or print it. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
pptx
Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations as PowerPoint (.pptx) files; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email, summary, or creating a different type of slide deck); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user asks for a PowerPoint or .pptx file, or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. However, when the user asks for a deck, slides, a slide deck, or a presentation without naming a file format, default to using a dedicated slide-deck artifact type or a separate slides skill if this session offers one; otherwise, use this skill.
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
stop-slop
Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.
archify
Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid.
pr-review-response
End-to-end workflow for responding to PR review feedback. Reads all review comments and requested changes on the current branch's pull request, plans and implements fixes via specialist agents, runs verification, and responds to every review thread on GitHub like a thoughtful engineer. Use this skill when the user wants to address PR feedback, respond to review comments, handle requested changes, or update their branch after a code review. Also applies when the user says things like "address the PR comments", "fix the review feedback", "respond to the reviewers", "handle the PR reviews", or "update the PR based on feedback".
work-the-branch
Workflow for advancing in-progress work on the current branch, at any stage, through to review-ready. Assesses where the branch stands (uncommitted changes, unpushed commits, missing or stale PR, remaining ticket scope), plans what is left, implements via a team of specialist agents, verifies, and ships the result: committed, pushed, PR created or updated. Use when the user invokes /work-the-branch.
jira-ticket-workflow
End-to-end Jira ticket workflow that manages a cross-functional team of agents to plan, implement, review, and ship work defined by a Jira ticket. Use this skill whenever the user provides a Jira ticket number (e.g., USP-2313, AID-21, CRM-450) and wants the work completed, or when they mention working on a Jira ticket, implementing a ticket, picking up a ticket, or completing a task from Jira. Also use this when the user says things like "do this ticket", "work on this issue", "implement this", or references a JIRA-style identifier followed by a request to build/fix/change something. Even if the user just pastes a ticket number with no other context, this skill applies.
attentive-pixel-perfect-slides
Use when creating, converting, editing, or QAing Attentive PowerPoint decks with the canonical 2026 template, including new presentations, rebranding existing decks, and checking brand or layout fidelity.
import-memory
Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.
morning
Render the user's morning brief as a styled HTML artifact, or set it up as a recurring weekday task. Use only when the user explicitly asks to run, see, or set up their morning brief, or if they invoke /morning by name. A question about their day, schedule, or calendar is not by itself a request for the brief; answer it directly instead.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
epic-orchestrator
Orchestrate parallel execution of a Jira Epic's tickets by dispatching headless Claude Code workers in isolated git worktrees. Analyzes tickets for dependencies, plans execution waves, spawns one worker per ticket with a skill file loaded as its system prompt, coordinates with workers via append-only markdown files, and manages the full lifecycle through to PRs and review response. Invoke manually via /epic-orchestrator.
session-debrief
An end-of-session candor ritual. Answers two questions about the work just completed: what you're least confident about right now, and the biggest thing the user probably doesn't realize about the situation. Use this skill when the user invokes it directly (e.g. /session-debrief) to close out a working session. It is a forcing function for honesty: surface the doubts and blind spots that normal task-completion mode tends to paper over, before the user walks away believing the work is more finished or more certain than it is.
team-dev-workflow
General-purpose team development workflow for making and shipping code changes. Coordinates a team of specialist agents to plan, implement, review, verify, and ship code. Gathers context from Jira tickets, Figma designs, PR reviews, and the codebase. Scales from small bug fixes to large features. Use when the user invokes /team-dev-workflow.
plan-convergence
Class-audit review procedure for plan convergence. Review rounds run until the surviving findings are nitpick-only, meaning wording taste, phrasing, or cosmetic rewrap, with no falsified claim, no contradiction, and no ownership or commitment change. Invoke when starting or continuing review rounds on any plan.
plan-drafting
Template and drafting rules for every implementation plan. Invoke before drafting a new plan or rewriting a major plan section.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.