threa

Keep the Threa Pi remote-control extension in `extensions/pi-remote/` aligned with the current Pi extension API and Threa bot-runtime public API. Use when asked to update, verify, sync, or troubleshoot the Pi remote plugin, `/remote-control`, or `threa-remote.ts`.

Create a well-structured pull request with proper description, design decisions, and file changes. Use when asked to create a PR, open a PR, or submit changes for review.

Call Threa's public REST API (send/list/search/update/delete messages, list streams/users/members, search memos/attachments) with curl or a Bun script. Use when asked to post messages to a stream, seed a stream with test data, drive the API from automation, dedupe by metadata, inspect a production workspace (streams, messages, members) for troubleshooting, or otherwise hit https://staging.threa.io / https://app.threa.io endpoints with an API key. Reads from production should use the read-only prod key.

Rewrite user-facing copy (marketing pages, docs, headings, UI microcopy, READMEs, PR descriptions) to strip AI-slop and salesy tone, leaving plain, understated, factual prose. Use when asked to "deslopify", "deslop", "remove the AI slop", "make this less salesy/less AI-sounding", "make the copy plainer", or when reviewing copy for slop tells.

Run multi-perspective code review on a PR or the local branch

Write a session handover doc for the next agent picking up this line of work. Use when asked to "write a handover", "hand over", "handoff doc", or at the end of a session whose work continues in a future session.

Find or deduce the implementation plan for the current feature branch

Embed or refresh the implementation plan inside the PR description as a collapsible details block. Use before/after creating a PR so CodeRabbit and reviewers have accurate plan context without committing plan files to the repo.

Update a pull request description. Use when asked to update PR description, edit PR body, or refresh PR details.

Write ONE feature doc from docs/features/INVENTORY.md, verified against the code, and open a small PR for it. Use when asked to "document <feature>", "fill in the feature doc for X", "do the next feature doc", "backfill feature docs", or when a remote agent is started with a feature name to document.

Systematically triage and respond to PR review comments. Use when asked to check PR comments, address review feedback, respond to reviewers, or fix issues raised in code reviews.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

Rebase the current feature branch onto the latest origin/main for our squash-merge workflow, then force-push. Use when asked to "rebase on main", "rebase on origin main", "update my branch with main", "rebase because we squash merge", or to clean up a branch stacked on a squash-merged PR.

Query the production Postgres database read-only. Use when investigating a production data inconsistency, verifying what's actually in a workspace's rows (vs. what the API/UI shows), confirming row counts after a backfill, diagnosing outbox/queue backlogs, or any other read-only forensic dig into the prod database. Two access paths: psql with $POSTGRESQL_PROD_READ_ONLY_CONN_STRING from a terminal, or HTTPS via the apps/db-read-proxy service when running in a Claude Code web session. Not for writes — every layer is read-only.

Operate Railway infrastructure: create projects, provision services and databases, deploy code, configure environments and variables, manage domains, troubleshoot failures, check status and metrics, and query Railway docs. Use this skill whenever the user mentions Railway, deployments, services, environments, build failures, or infrastructure operations, even if they don't say "Railway" explicitly.

Update the vendored `frontend-design` skill in `.agents/skills/frontend-design/` from upstream `anthropics/skills` on GitHub. Use when the user asks to "sync frontend-design", "update the frontend-design skill", or "pull the latest frontend-design from GitHub".

Create a git commit with proper message formatting. Use when asked to commit changes, handles sandbox heredoc limitations.

Navigate the GitHub API using curl when gh CLI is unavailable (Claude Code web sessions). Use when gh commands fail with "command not found" and you need to interact with GitHub PRs, issues, or repos. ALSO USE THIS when you need to troubleshoot CI failures, fetch GitHub Actions job logs, or debug workflow runs. When a check run fails, ALWAYS fetch the logs using this skill before speculating about the cause.

Create a new database migration with timestamp-based naming. Use when adding schema changes.

Run TypeScript type checking across the entire monorepo

Find configuration sprawl - duplicated constants, types, and values that should be centralized

Search OpenRouter API for AI models and get pricing/capability details for model-reference.md