4.6万 件 ・ 関連度順
概要と使いどころ
Blender Python API リファレンス。bpy / bmesh / mathutils / gpu / bpy_extras モジュール、 bpy.data / bpy.context / bpy.ops / bpy.types / bpy.props / bpy.msgbus / bpy.path コア API。 Mesh / Modifier / Geometry Nodes / Armature / Keyframe / Driver / Shape Key / NLA、 Cycles / EEVEE / Shader Nodes / Rigid Body / Cloth / Fluid / Compositor Nodes / AOV、 headless CLI レンダリング、add-on 開発、Extensions システム、MCP Server (Model Context Protocol)。
Biome (Rust 製フォーマッター・リンター) リファレンス。 JavaScript / TypeScript / JSX / CSS / JSON / GraphQL / HTML (Vue, Svelte, Astro) 対応。 biome.json, biome check / lint / format / ci / migrate / upgrade, linter ルール・preset・domains, GritQL プラグイン, assist (organizeImports), suppressions (biome-ignore), LSP / VS Code / Zed, ESLint / Prettier 移行, monorepo, CI。
App Store Connect API 4.5.1 (REST) アプリ配布リファレンス。JWT 認証、API キー作成・失効、 Apps, Builds, Bundle IDs, Bundle ID Capabilities, Certificates, Devices, Provisioning Profiles, Users, User Invitations, Merchant IDs, Pass Type IDs、TestFlight (Beta Groups / Testers)、 Sandbox Testers、App Review, Review Submissions, Customer Reviews, Custom Product Pages, Phased Release、In-App Purchases, Subscriptions, Subscription Groups, App Price Points, Promotional Offers, Win-back Offers, Sales Reports、App Asset Library (screenshots / app previews)、 Webhooks / Webhook Events / Deliveries、Xcode Cloud (Workflows, Build Runs, Artifacts)、 Alternative Distribution (EU マーケットプレイス / Web Distribution)、 Game Center (Achievements, Leaderboards, Challenges)、Analytics / 診断レポート。
Better Auth (TypeScript 認証フレームワーク) v1.7 リファレンス。 認証・認可、サインアップ・サインイン、セッション管理、OAuth、パスキー、二要素認証 (2FA / TOTP)、SSO / SAML、SCIM、 OAuth Provider (OAuth 2.1 / OIDC)、MCP 認可 (@better-auth/mcp)、Infrastructure (dash / sentinel)、 プラグイン (organization, admin, magic-link, anonymous 等)。betterAuth, createAuthClient, signUp, signIn, getSession。 Next.js, Nuxt, SvelteKit, Hono, Express, Expo, TanStack, Effect 統合。
Record PlayMode keyboard and mouse input to JSON. Use to capture gameplay, bug repro, or E2E input sequences for replay.
日本語の概要は準備中です。原文の説明を表示しています。
Use when Unity Editor is not running or needs a clean restart.
日本語の概要は準備中です。原文の説明を表示しています。
窓際族物語の動画を、チャプター毎のキーフレーム画像を作らずに「プロンプト＋キャラクターシート＋セリフ音声」だけでMiniMax H3（R2V）に生成させるワークフロー。ユーザーから「画像なしで動画を作って」「キーフレームなしで動画を作って」「シートだけで動画を作って」と指示されたときに必ず使用する。大まかな指示→チャプター分割案→チャプター毎の動きを人間に確認→全チャプター確定→プロンプト作成の順で進め、確定前にプロンプトを書かない。画風の注意文はチャプターに映るものだけを最小限で書き、モブキャラはラン専用のキャラクターシートを作って渡す。動画生成の実行先は/colab-video（Colab）または/local-videoステップ7（ローカルCUDA）。
窓際族物語の動画生成工程（/local-videoのステップ7）だけをGoogle Colab（CUDA GPU）で実行する派生ワークフロー。ローカルMacにCUDA GPUが無くMiniMax H3を実行できないとき、ユーザーから「Colabで動画を作って」「H3をColabで回して」「LTXで動画を作って」と指示されたときに必ず使用する。台本・音声・キーフレーム生成・画像検証（ステップ1〜6）と最終結合（ステップ8〜9）はローカルで行い、動画生成だけを同梱ノートブック（H3=h3_colab.ipynb / LTX-2.5=ltx25_colab.ipynb）でColabに切り出す。セリフ（wav駆動リップシンク）はH3、セリフなしI2VチャプターはLTX-2.5も選べる。無料T4は配管検証用、本番生成はL4/A100（Pay As You Go / Colab Pro）。
窓際族物語の動画をクラウドを使わずフルローカルで生成するワークフロー（MiniMax H3 + ComfyUI）。ユーザーから「ローカルで動画作成して」「ローカルLLMで動画を作って」と指示されたとき、MiniMax H3での動画生成・修正を頼まれたときに必ず使用する。台本→Irodori-TTS/VOICEVOX音声→draw-things-cliキーフレーム一括生成→Qwen3-VL（Ollama）による画像検証→チャプター毎のH3動画生成→ffmpeg結合まで全工程をローカルで完結させる。
Word文書（.docx）をMarkdownに変換し、参考文献を整理するスキル。「Wordをマークダウンに変換して」「docxをmdに変換して参考文献を整理して」「Word文書の参考文献を統合して」「レポートをMarkdownに変換して」などのリクエスト時に使用。pandoc（またはpython-docxフォールバック）による変換と、重複URL統合・番号再割当て・参考文献リスト生成・文書構造整形を行う。
Build kokoro-js-jp and run its real-browser e2e suite (Worker + WASM openjtalkjs g2p + ONNX kokoro-js synthesis, English and Japanese). Use when asked to verify this package actually works in a browser, to check whether a change broke synthesis, or to add browser-level regression coverage for a bug in the g2p/synthesis pipeline that vitest's pure-function tests can't catch. Not for typecheck/lint/unit-test requests — use npm run typecheck / npm test for those.
日本語の概要は準備中です。原文の説明を表示しています。
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
日本語の概要は準備中です。原文の説明を表示しています。
PJ ドキュメントの同期。PJ CLAUDE.md の更新依頼、ドキュメント整理依頼、コード変更後の CLAUDE.md・README・API 仕様への反映依頼（npm script・環境変数・API 追加等）の時に使用。user-level 設定との整合性確認も行う。境界: CLAUDE.md が未整備の新規 PJ は組み込みの /init。
現在の変更内容を確認し、適切なブランチ名を提案してブランチを作成するときに使う。ユーザーが「ブランチ作って」「作業用ブランチ切りたい」「変更に合わせてブランチ名を決めて」と言ったとき、または新規作業を始める前にブランチを作りたいときに適用する。git status / diff を確認し、プレフィックス規則（feat/fix/release/epic）に従ってブランチ名を提案し、ユーザー確認後に git checkout -b で作成する。
Draft or review an employer's Otameshi Tenshoku listing so a candidate can decide whether to apply: check item by item that the work, deliverable, out-of-scope tasks, required experience, support, hours, schedule, location, compensation, contract form and payment timing are stated, find open-ended, unpaid-company-work, guarantee, personal-attribute and unverifiable wording, and confirm that the hours, weekly availability, period, rate and budget hold together. Use when a hiring manager, recruiter or small-business owner wants a listing written from a plan, wants an existing draft or published listing reviewed before or after posting, or wants to know why applications are not coming; do not use to design the work itself (trial-work-design), to reply to applicants (applicant-reply), to state market rates, legal, tax or service conditions from memory, or to post or update the listing on the user's behalf.
日本語の概要は準備中です。原文の説明を表示しています。
Check, from the employer's side, what has been put in writing before a paid Otameshi Tenshoku assignment starts under gyomu-itaku: item by item whether the deliverable, delivery date, fee and how it is calculated, payment due date, who pays, out-of-scope work, revision limits, company support, rights, confidentiality and termination are stated in a contract, purchase order or email rather than in chat or by word of mouth, count the days from delivery to payment, and find pay tied to satisfaction or hiring, unpaid or unlimited revisions and one-sided termination. Use when a hiring manager, recruiter or small-business owner is about to offer terms to a candidate, has been asked by a candidate what is still unwritten, or needs the conditions written for a platform contract screen; do not use to judge whether the terms are lawful or the fee fair, to compute withholding or consumption tax, for employment contracts, or to sign, send or conclude the contract on the user's behalf.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a resignation and the move to a new employer: check the intended notice date, last working day, and start date against the notice period the employer's own rules require, count the weekdays left against remaining paid leave, and work through the checklist of handover, documents to receive, items to return, and the insurance, pension, and residual tax steps that a gap between jobs creates. Use when a user has accepted an offer and needs to work out when and how to resign, or wants to know what to confirm before giving notice; do not use to rule on whether they can legally leave, to judge a non-compete clause, to promise the departure will go smoothly, or to notify anyone.
日本語の概要は準備中です。原文の説明を表示しています。
Read a Japanese job posting closely and report what it actually states: base pay separated from fixed overtime allowance, the range converted to an hourly basis, required versus preferred requirements, and the terms left ambiguous. Use when a user wants a 求人票 or job description examined before applying, wants two postings compared on the same basis, or wants questions prepared about pay and working conditions; do not use to judge whether the user will be hired, to infer duties the posting does not state, or to evaluate the employer's reputation.
日本語の概要は準備中です。原文の説明を表示しています。
Sort incoming scout messages and agent-forwarded openings by what they actually disclose: whether the employer is named at all, which of pay, location, employment type, and duties are stated, whether the message refers to the applicant's own history or reads as a mass send, whether a stated salary is an offer or a "up to" figure, and whether the same employer has arrived through more than one route. Use when a user has a backlog of scout messages and wants to know which ones can be researched, what to ask before replying, and what to settle before handing over a resume; do not use to rate how promising an opening is, to judge an employer or an agent, or to reply on the user's behalf.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare a request to change the terms of a Japanese job offer before accepting it, sorting what the user wants changed (pay components, start date, work style, location, title, probation) by priority, tying each ask to a basis the user can show (the written offer, the job posting, what was said in interviews, their own records), working the timing back from the acceptance deadline, and drafting the message to the employer or recruiting agent. Use when a user has an offer and wants to ask for higher pay, a later start date, more remote days, or other changed terms, or wants to know how to raise it without losing the offer; do not use to predict whether the request will succeed, to set a target figure from market rates, to fabricate a competing offer, to decide whether to accept, or to send anything to the employer.
日本語の概要は準備中です。原文の説明を表示しています。
Check the working conditions of a Japanese job offer item by item against the conditions an employer states in writing, compare the offer letter or 労働条件通知書 with the job posting and what was said in interviews, and separate what is confirmed in writing from what is still only verbal. Use when a user has received an offer, a working-conditions notice, or an employment contract and wants to know what is missing, what conflicts with earlier statements, and what to confirm before the acceptance deadline; do not use to rule on whether the terms are lawful, to decide whether to accept or decline, or to contact the employer on the user's behalf.
日本語の概要は準備中です。原文の説明を表示しています。
Help a user talk through whether to change jobs, stay, or change something in their current work, starting from uncertainty, distress, a vague sense of stagnation, an offer in hand, a counter-offer from the current employer, or pressure from family or colleagues. Clarify what matters, separate deadlines that order the next steps from the decision itself, compare conditional options, and agree on a small next step and a time to revisit it. Use when someone asks whether they should quit, wonders whether leaving is just running away, has second thoughts after receiving an offer or being asked to stay, feels stuck because others say it would be a waste, wants to leave soon after joining, or wants advice before deciding to start a job search; do not make the final stay-or-leave decision, evaluate offer terms, plan the resignation, or predict hiring outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
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), 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.
日本語の概要は準備中です。原文の説明を表示しています。