写作与创作技能

Inspects PostHog Visual Review (VR) runs that gate PR merges with screenshot regression checks. Use when the user mentions "visual review", "VR", "snapshot diff", "screenshot test", "storybook regression", "playwright snapshot", asks why a PR is blocked or what changed visually, wants to triage the VR backlog, decide whether a snapshot diff is real vs flaky, or check whether a story has been changing across runs. Also invoke when a PR has a failing `visual-review` status check, when a PR comment mentions "Visual review", or when the user is on a branch with an open VR run.

中文简介正在准备中。当前显示原文说明。

Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want to fix v5 without bumping the version", or anything involving the version history. Calls out today's limitations honestly: there is no pointer flip; "rollback" means forking the old query into a new top version.

中文简介正在准备中。当前显示原文说明。

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.

中文简介正在准备中。当前显示原文说明。

Senior software engineer for story execution and code implementation. Use when the user asks to talk to Elliot or requests the developer agent.

中文简介正在准备中。当前显示原文说明。

Map the competitive landscape for a Stellar project idea. Use when a user says "who are my competitors on Stellar", "competitive analysis Stellar", "what already exists in this space on Stellar", "show me similar Stellar projects", "is anyone else building this on Stellar", or "map the Stellar landscape for X". Queries the 728-project LumenLoop ecosystem database and Electric Capital developer activity to rank competitors by SCF funding history and repo activity.

中文简介正在准备中。当前显示原文说明。

Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"

中文简介正在准备中。当前显示原文说明。

When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.

中文简介正在准备中。当前显示原文说明。

Manage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.

中文简介正在准备中。当前显示原文说明。

Generate a vertical story image for TikTok or Instagram book promotion with cover art, hook text, and author branding.

中文简介正在准备中。当前显示原文说明。

Extract applicant details, employment history, income, and references from a rental application form into structured JSON for tenant screening.

中文简介正在准备中。当前显示原文说明。

Storybook (UI カタログ) リファレンス。story, CSF (Component Story Format), CSF Next (CSF Factories), args, argTypes, decorators, play function, interaction tests, autodocs, main.ts / preview.ts, アドオン (a11y, controls, viewport, themes), Vitest addon, test-runner, Storybook MCP server, components manifest, アドオン作成, upgrade / migration。

中文简介正在准备中。当前显示原文说明。

nuqs (Type-safe URL search params 状態管理, React / Next.js) リファレンス。 useQueryState, useQueryStates, parseAsString / parseAsInteger / parseAsArrayOf 等 parsers、 NuqsAdapter (Next.js / React Router / TanStack Router / Remix)、createSerializer、 createStandardSchemaV1, inferParserType、shallow routing、history 制御、SSR、 URL 長さ制限 (limits)、Zod / Effect / Sury 連携。

中文简介正在准备中。当前显示原文说明。

CadQuery (Python 製 3D CAD スクリプティングライブラリ) リファレンス。 Workplane API (lineTo / extrude / revolve / sweep / loft / fillet / chamfer / shell)、 Sketch API、Assemblies (Constraint solver)、Free Function API (hollow / prism / draft / offset2D, History)、 Selectors、Shape / Vertex / Edge / Wire / Face / Shell / Solid、 Import / Export (STEP / DXF / STL / glTF / SVG)、Visualization (VTK, cadquery.fig 非ブロッキング, Jupyter)、CQGI。

中文简介正在准备中。当前显示原文说明。

Madogiwa StudioのRemote Web MCPを使い、窓際族物語のギャラリー、記事、エピソード、生成バージョン、使用モデル、登場メンバー、Seedanceプロンプト、入力画像・参照音声・資料、YouTube動画IDと公開状態を登録・確認する。ユーザーがMadogiwa Studioへの登録、公式サイトコンテンツ編集、動画アップロード、プロンプト同期、入力素材管理、Studio ID確認、MCP接続や同僚環境への導入を頼んだときに使用する。

中文简介正在准备中。当前显示原文说明。

窓際族物語のストーリー（あらすじ）からSeedance用の台本・動画生成プロンプト・セリフ音声（VOICEVOX/Irodori-TTSボイスクローン）・Codex参考画像を作成するワークフロー。ユーザーからストーリーを渡されたとき、台本やSeedanceプロンプトの作成・修正を頼まれたとき、キャラのセリフ音声の生成を頼まれたとき、クリップの参考画像（キーフレーム）生成を頼まれたときに必ず使用する。

中文简介正在准备中。当前显示原文说明。

GameDay シナリオを AWS FIS 実験テンプレート (CDK) として実装する。「シナリオを FIS にして」「実験テンプレートを作って」「障害注入を実装して」「fault-injection を書いて/直して」など、FIS 実験の実装・修正・レビューの全てで必ず使う。FIS アクションの選定、停止条件 (CloudWatch アラーム)、実験ロールの最小権限 IAM、爆発半径の制御 (selectionMode)、実験レポート設定、ECS タスクアクションの SSM サイドカー前提条件など、検証済みの判断基準とコード例を提供する。lib/constructs/fault-injection.ts を編集するときは内容にかかわらず該当する。

中文简介正在准备中。当前显示原文说明。

新しい GameDay シナリオを追加する。「シナリオを追加して」「新しい障害を考えて」「次の GameDay のネタが欲しい」「scenario-03 を作って」など、シナリオの新規作成・追補・改訂の全てで必ず使う。立案 (gameday-scenario エージェント) → 観測可能性チェック → scenarios/NN-<slug>.md への保存 → fis-experiment スキルへの引き継ぎまでの手順を提供する。特に「観測窓より速い障害は見えない」「読み取りプローブでは書き込み断が見えない」などリハーサル実測に基づく設計チェックを保存前の関門にする。

中文简介正在准备中。当前显示原文说明。

AI が生成した日本語テキストから「AI っぽさ」を取り除き、人間が書いた文章に書き換える。 日本語の文章を編集・推敲・レビューするときに使う。Wikipedia の "Signs of AI writing" を 基にした blader/humanizer の日本語版。英語固有のルールは日本語の等価パターンへ置き換え、 日本語特有のパターン（「することができます」の冗長形、敬語の均一化、主語の過剰明示、 カタカナ語の氾濫、定型評価語、体温のない結論、体言止めの乱発）を追加している。

中文简介正在准备中。当前显示原文说明。

日本語と英語の文章を ukwhatn 本人の文体で書く・下書きする・推敲する。PR 概要欄、レビュー指摘・返信、Slack・Discord のメッセージ、チーム内ドキュメント、対外ビジネスメール、コミュニティのフォーラム告知とその合意形成の投稿、記事・レポート・議事録・提案書等の長文を日本語で書く時、本人の代わりに文章を書く時、国際的なコミュニティの運営間チャットに英語で投稿する時に使用。AI 特有の冗長さ・難語・翻訳調を排し、相手と媒体に応じて敬体/常体と敬語の重さを切り替える。雑談・times の投稿は対象外。境界: 実装修正を伴う PR コメント対応は pr-comment（本スキルは文章作成のみ）、コミットメッセージは commit、画面の文言は writing-ui-text、コードコメントは writing-code。

中文简介正在准备中。当前显示原文说明。

AIが生成した日本語を推敲するスキル。利用者が yomiyasu の名前を出して頼んだとき（「/yomiyasu」、「$yomiyasu:yomiyasu」、「yomiyasu で推敲して」など）と、スキルを使った日本語の推敲をはっきり頼んだときだけ使う。CLAUDE.md、AGENTS.md、カスタム指示などで yomiyasu を使うよう求められているときも、名前を出して頼まれたものとして扱う。名前を出さずに日本語の文章を書かせる依頼や、コード、設定、ドキュメントの更新では使わない。意味と条件を保ち、不自然な比喩、曖昧な主述関係、不要な装飾やコピー調を整える。

中文简介正在准备中。当前显示原文说明。

Prepare for a Japanese job interview by working from the documents already submitted: find where an interviewer will dig in (claims the applicant cannot back up, work described in the first person plural, outcomes with no measure, gaps or overlaps in the employment history, must-have requirements the documents never answer), and turn them into questions to prepare evidence for. Use when a user has an interview scheduled and wants to know what will be asked and what to have ready, or wants to prepare reverse questions from earlier company research; do not use to predict whether they will pass, to write answers containing experience they did not report, or to schedule or contact anyone.

中文简介正在准备中。当前显示原文说明。

Assemble a Japanese shokumu-keirekisho (career history document) from an experience inventory, choosing between reverse-chronological, chronological, and skills-based layouts, mapping the target posting's requirements to the experiences that can support them, and drafting the summary, work history, skills, and self-PR so that each sentence stays within what its evidence supports and confidential details are abstracted. Use when a user wants to write or rebuild a whole shokumu-keirekisho for a specific posting or as a general version, or wants to decide which experiences to include and in what order; do not use to invent experience, numbers, titles, or qualifications, to predict whether it will pass screening, to fill in a rirekisho form, or to submit it anywhere.

中文简介正在准备中。当前显示原文说明。

Inventory a person's work history as facts before any document is written, listing each period of employment and what they actually did, splitting every experience into situation, their own actions, outcome, and stated role, and recording what each claim rests on (public record, their own records, someone who was there, or memory alone). Use when a user is starting a job search, needs material for a rirekisho, shokumu-keirekisho, or entry sheet, or wants to find which periods of their history they have never written down; do not use to judge their strengths, aptitude, or market value, to name a job they are suited for, or to write finished application copy.

中文简介正在准备中。当前显示原文说明。

Triage a GitHub issue that already has the cc-issue-created label and is assumed ready to start. Inspect the comment history first to decide whether human confirmation is needed (cc-need-human-check, highest priority — reserved for issue-level deadlock, or for confirmation items answer-issue-questions already investigated and explicitly marked unanswerable); otherwise close the issue as not needed, delegate unanswered confirmation items in the last comment or the description to answer-issue-questions (cc-answer-issue-questions), refresh a description stale relative to settled comment-history content (cc-update-issue), turn the issue into an Epic and split it into sub-issues when its work should ship as separate PRs (cc-epic-issue), or move to execution (cc-exec-issue). Any UI-changing issue is routed to the design-first flow (cc-create-ui-design) before execution; the exceptions are an issue whose description already names the .pen design to implement against, and a minor UI change that introduces no new visual decision (no new screen/section, no layout change, no new reusable component, no visual expression outside existing design tokens/components). Design files are never edited in the implementation PR. Dependency checks are out of scope.

中文简介正在准备中。当前显示原文说明。