Coding & Development

Diagnose a failing or flaky Vitest test or a failing CI check, find the root cause, and propose or apply the smallest correct fix. Use when a test fails locally or in CI.

Review the current branch's changes against main before opening a PR, using the code-reviewer subagent and this repo's checks. Use when asked to review local changes.

Add a new Next.js route handler under src/app/api with Zod validation, consistent errors and Vitest tests. Use when asked to add or extend an API endpoint.

Filter incoming Synoptic updates with keywords, include/exclude rules, regex, or AI filters, and organize feeds in dashboards, decks, collections, and terminal tabs. Use when configuring a monitoring workspace or reading its collection feed.

Read or edit a Synoptic profile, manage author follows and notification preferences, and review or mark notifications. Use for changes to the linked Synoptic account.

Configure supported Synoptic source monitors and custom scraper targets for social accounts, keywords, hashtags, cashtags, queries, follows or profile changes, Telegram channels, and GitHub repositories. Use when the user wants ongoing collection or a change to monitored sources.

Connect to a remote machine over SSH and work in a remote project using alias, key, or password authentication configured in ssh.md. Use when the user asks to ssh into a server, run commands on a remote machine, inspect or edit files on a remote project, or work on a remote project.

>- 当用户要求“让 Pi 做/看/审”、“用 Pi Agent”、“让另一家模型出第二意见或做对比”，或遇到批量文件处理、写代码、长篇调研和联网搜索、 长文初稿这类重活时使用：为节省 Bot 自身用量，这些默认交给 Bot 电脑上的 Pi Agent。通过原生 RPC 模式调用，按任务名保存会话以便连续修改。

Every skill in ~/.agents/skills and ~/.claude/skills (mine, pstack, Matt Pocock's) is a symlink into the git repo ~/Dev/agent-skills. Use before creating, editing, or removing any skill, including via /reflect, /automate-me, or skill-creator.

Audita um perfil de Instagram e reescreve a bio. Use quando a pessoa pedir análise de perfil, revisão de bio, "meu perfil não converte", "o que melhorar no meu Instagram", ou colar bio, nome, link, destaques ou posts (ou um print) pedindo opinião. Dá nota de 0 a 10 em sete critérios, reescreve a bio em 3 versões de até 150 caracteres e lista as 3 mudanças de maior impacto, em ordem.

Guides a Product Manager through building a structured gradual release plan based on the Idira Gradual Release Framework. Use when a PM says anything like "build a gradual rollout plan", "build me a rollout strategy", "create a release plan", "rollout strategy", "release strategy", "how should I roll this out", "canary plan", "feature rollout", or mentions NFI, release rings, LaunchDarkly flags, or customer exposure waves.

Prove a change with red → green evidence (screenshots, curl, failing-then-passing test, DB query, consumer outcome). Use standalone, as step 4 of autonomous-squad, or as QA verifying someone else's work.

Work an issue-tracker ticket (e.g. RND-123): bug → reproduce red, then minimal fix; feature → implement per PRD. Use standalone or as step 3 of autonomous-squad.

Ship a worked issue-tracker ticket (e.g. RND-123): PR → CI → independent review → evidence on the tkt → merge → cleanup, moving statuses. Use standalone or as step 5 of autonomous-squad.

Use when working on an issue-tracker ticket (Jira, Linear, GitHub Issues… e.g. RND-123) end to end — pick up, reproduce or implement, prove with evidence, move statuses. Bugs and features.

改写中文或英文论文、学术文本和技术文档，减少模板化、机械化表达，保留事实、术语、引文与结构。用户要求降 AIGC、去 AI 味、人性化改写或继续已有改写轮次时使用，支持文本、TXT、DOCX、分块高亮 HTML 对照，以及可用环境中的子代理分工；不用于查重检测或承诺检测分数。

在任意 Markdown 文件/文件夹上构建并迭代文件式个人知识库与知识图谱：给文档起草 frontmatter 元数据（日期/领域/状态/一句话结论），用 supersedes 演进、related 语义相关、[[双链]] 引用三类关系建图，脚本生成决策登记簿与图谱邻接表。当用户要求搭建个人知识库、建知识图谱、整理笔记或文档入库、更新已有知识库，或说"帮我回忆/复盘/找找之前关于某主题的分析和结论"、决策前想参考历史思路时使用。适用于任何支持 SKILL.md 的 Agent（ZCode、Claude Code 等）。

Code review rules for pull requests. Use when reviewing a PR or a diff, or re-reviewing a PR after new commits: what to flag, the severity bar, the comment format, and how to converge over review rounds instead of raising new minor issues every time.

Sets up or audits a repository's baseline files, including license, security policy, contributing guide, README, editor and Git hygiene, PR and issue templates, Dependabot, CI, and for Node.js/TypeScript projects the lint, format, test, hook, and publish tooling. Includes starter PR and issue templates. Use when bootstrapping a new repository, adding missing community or GitHub files to an existing one, or checking a repository against a new-repo checklist.

Upgrades, or migrates, an Android project to use Android Gradle Plugin (AGP) version 9. Do not use this skill for migrating Kotlin Multiplatform (KMP) projects.

Verify the enclosure in Fusion 360 with clash checks, clearance gaps, section views and screenshots. Use after every build, when checking fit or clearance, or when asked to show or screenshot the model.

Build or rebuild the enclosure in Fusion 360 from the repo's Python scripts via the Fusion MCP. Use when changing enclosure geometry or parameters, adding a feature, or when Fusion's model is missing or stale.

Runs a mock AI/ML engineer interview round and scores the answer against the 4-category rubric (0-5 each, total out of 20) with one improvement. Use when the user asks to "practise", "practice", "run a mock round", "mock interview", or "quiz me" on AI/ML interview prep.

글로만 설명하기 어려운 것을 실제로 띄워 찍은 화면과 저장된 값을 증거로 삼아, 하나의 질문에 답하는 HTML 보고서 한 장을 만든다. 휴대폰에서도 읽히고 브라우저 인쇄로 A4 PDF 가 그대로 나오며, 정할 것이 있으면 받는 사람이 문서 안에서 고르고 복사해 회신한다. 답할 질문에 따라 구조를 그때그때 짠다 - 무엇이 바뀌었나(개선 전후), 기획서대로 되었나(명세 대조), 우리 원칙대로 되어 있나(점검, 감사), 조건이 바뀌면 무엇이 달라지나(상태 대조), 지금 어떤 상태인가(현황), 무엇을 정해야 하나(의사결정). 화면에 드러나는 큰 기능을 구현하거나 고친 작업을 마쳤으면, 사용자가 따로 말하지 않아도 완료 보고를 이 보고서로 할지 먼저 떠올린다. "html 로 보여줘", "시각화해서 보여줘", "캡처해서 설명", "스크린샷 찍어서 설명", "실제 화면 찍어줘", "구현한 거 보여줘", "작업 끝났으면 정리해줘", "전후 비교", "before after", "뭐가 바뀌었는지 정리해줘", "기획서대로 됐는지 확인", "남은 게 뭔지", "점검 결과 정리", "결과보고서", "고객에게 보낼 자료", "기획자에게 보고", "의사결정문", "결정할 것 골라서 붙여넣게", "작업 내역 정리해서 공유"류 요청과, 점검, 코드 리뷰, 버그 조사의 결과가 화면에서 어떻게 보이는지가 논점일 때 발동합니다. 발견을 글머리표로 길게 늘어놓거나 코드 diff 를 붙여 설명하려 하기 전에 이것을 먼저 떠올린다 - 받는 사람은 코드를 읽지 않는다. (화면이 없는 순수 문서와 화면 사이 이동 흐름 지도는 이 스킬의 대상이 아니다.)