clanker-stuff

Read Confluence Server/DC wiki content via REST API. Use when the user pastes a Confluence URL, mentions Confluence, "the wiki", wiki pages or spaces, or asks to pull design docs, architecture notes, or meeting notes from Confluence.

Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues with the jira CLI, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

Weekly task refresh ritual for Task System v3. Use when the user asks for a "refresh", "weekly review", "task review", "rebuild my week", a "catch-up" after a gap, or is following up on a scheduled refresh nudge or morning deadline check. Also defines the content rules for those two scheduled nudges.

Manage personal finances tracked in an hledger plain-text journal. Use when the user asks about spending, account balances, net worth, equity, cash flow, income vs expenses, savings rate, investment value or ROI, budget status, wants to search past transactions, record a new transaction, import bank statements (CSV or PDF), update market prices, or set up finance tracking from scratch. Produces reports and appends validated transactions and prices; never edits or deletes existing entries.

Use when the user wants to manage their personal task list with Taskwarrior, e.g. "what should I work on next", "what's overdue", "add a task to ...", "mark task 12 done", "show my work tasks", "weekly review", or otherwise mentions tasks, todos, projects, or the `task` CLI. The user is the owner of the task list; the agent acts as a personal assistant for it, never as the task list's owner.

Structured workflow for large features and refactors. Use only when the user explicitly asks to use the big feature workflow.

Query Figma files via REST API. Use when the user pastes a figma.com URL or mentions Figma files, frames, nodes, components, variables, or design-system tokens (colors, spacing, typography).

Query and explore application logs using Loki and the logcli CLI. Use when searching logs, finding errors, tracing requests across services, tailing services live, or investigating production/staging issues.

Author architecture decision records (ADRs) that humans will actually read and agents can reliably act on. Use when the user asks to write, draft, propose, supersede, deprecate, or revise an ADR, or when another instruction routes an artifact to an ADR directory. This skill defines the template, the status lifecycle, the index conventions, and the writing rules. It does NOT decide where the ADR file lives - that belongs to the repo's own conventions.

Interview the user relentlessly about a plan or design or a feature until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design or feature, or mentions "grill me".