1,180 件 ・ 関連度順
概要と使いどころ
Use when implementing GPT chat, streaming, function calling, embeddings for RAG, images, audio or batch jobs, or troubleshooting 429 rate limits and API or TypeScript errors. Stateless OpenAI patterns that prevent 16 documented errors.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill before answering, planning, or editing any MSTest 3.x-to-4.x upgrade or post-upgrade failure. Triggers include "MSTest v4 breaking changes"; CS0507/CS0103/CS1061/CS1615; ExecuteAsync, CallerInfo, DisplayName, or custom TestMethodAttribute; ClassCleanupBehavior; ContainsKey; ThrowsExactly or ExpectedException; IsInstanceOfType out parameters; TestTimeout.Infinite; ManagedType; net6/net7 compatibility; TestCase.Id history; TestName in ClassInitialize; TreatDiscoveryWarningsAsErrors; discovery errors after a clean build; and MSTest.Sdk/MTP or vstest.console discovery changes. Do not use for v1/v2-to-v3 leftovers, framework conversion, runner-only migration, or a general .NET upgrade.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses and fixes .NET MAUI development environment issues. Validates .NET SDK, workloads, Java JDK, Android SDK, Xcode, and Windows SDK. All version requirements discovered dynamically from NuGet WorkloadDependencies.json — never hardcoded. Use when: setting up MAUI development, build errors mentioning SDK/workload/JDK/Android, "Android SDK not found", "Java version" errors, "Xcode not found", environment verification after updates, or any MAUI toolchain issues. Do not use for: non-MAUI .NET projects, Xamarin.Forms apps, runtime app crashes unrelated to environment setup, or app store publishing issues. Works on macOS, Windows, and Linux.
日本語の概要は準備中です。原文の説明を表示しています。
Set up Tailwind v4 with shadcn/ui using @theme inline pattern and CSS variable architecture. Four-step pattern: CSS variables, Tailwind mapping, base styles, automatic dark mode. Prevents 8 documented errors. Use when initializing React projects with Tailwind v4, or fixing colors not working, tw-animate-css errors, @theme inline dark mode conflicts, @apply breaking, v3 migration issues.
日本語の概要は準備中です。原文の説明を表示しています。
Fix JSON parse errors when fetching archived API responses from Wayback Machine. Use when: (1) Getting "Expecting value: line 1 column 1 (char 0)" JSON decode errors from archived URLs, (2) Wayback returns HTML instead of expected JSON/raw content, (3) Crawling archived REST APIs or JSON endpoints from web.archive.org. The `id_` modifier returns raw content without the Wayback toolbar wrapper.
日本語の概要は準備中です。原文の説明を表示しています。
Fix Node.js pg-pool not reconnecting after CloudSQL connection reset (ECONNRESET). Use when: (1) Retries fail with same ECONNRESET error despite retry logic, (2) "Connection terminated" or "connection already closed" errors persist across retries, (3) "remaining connection slots are reserved" errors in CloudSQL, (4) High-concurrency Node.js app with pg-pool and CloudSQL/managed PostgreSQL. The pool caches dead connections - you must recreate the pool, not just retry.
日本語の概要は準備中です。原文の説明を表示しています。
Fix PostgreSQL deadlock errors caused by concurrent schema initialization in worker processes. Use when: (1) psycopg2.errors.DeadlockDetected during CREATE INDEX/TABLE IF NOT EXISTS, (2) Multiple Cloud Run jobs, Kubernetes pods, or worker processes start simultaneously, (3) Error shows "Process X waits for RowExclusiveLock... blocked by process Y", (4) init_schema() or migration code runs at worker startup. The key insight: "IF NOT EXISTS" is NOT truly concurrent-safe - PostgreSQL still acquires locks that can deadlock.
日本語の概要は準備中です。原文の説明を表示しています。
Fix "Requested backend named 'X' does not exist" or TLS alert errors in Fastly Compute@Edge. Use when: (1) Backend works locally but fails in production with "backend does not exist", (2) TLS alert received (alert_id=0) errors when calling external APIs from Fastly, (3) Backends defined in fastly.toml aren't available after deployment. The fastly.toml [[backends]] section only applies during initial service creation - existing services require backends to be added via CLI or API with proper SSL/SNI configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Set up Cloud Run Jobs with CloudSQL connection. Use when: (1) Deploying long-running batch jobs that need database access, (2) Errors like "Cloud SQL Proxy not found" in container, (3) "password authentication failed" despite correct credentials, (4) Job creation fails with permission errors. Covers socket path configuration, IAM permissions, and common gotchas.
日本語の概要は準備中です。原文の説明を表示しています。
Fix flaky Flutter/Dart tests that fail in CI but pass locally due to unhandled Future rejections. Use when: (1) Test passes locally but fails in CI with cryptic errors, (2) Test creates Futures that will throw errors (e.g., network calls to fake URLs), (3) Even with .catchError() at the end, test still fails, (4) Error message shows test name but truncated error like "ROR]" or "[ERROR]". Solution: Avoid creating Futures that will reject; test state machine behavior with synchronous operations instead.
日本語の概要は準備中です。原文の説明を表示しています。
Add custom metadata headers (x-amz-meta-*) to AWS v4 signed requests for GCS S3-compatible API. Use when: (1) Adding custom metadata to GCS uploads via S3 API, (2) Getting signature mismatch errors after adding new headers, (3) x-amz-meta-* headers being ignored or causing 403 errors. Custom headers MUST be included in canonical headers and signed headers list.
日本語の概要は準備中です。原文の説明を表示しています。
Fix Fastly Compute Rust crate `cargo test` failures with "ld: symbol(s) not found" errors for Fastly SDK symbols like `_version_set`, `_body_new`, `_req_send` on native host builds. Use when: (1) `cargo test` on a Fastly Compute crate fails at link time with errors mentioning libfastly and symbols with names like `fastly::http::response::handle::...`, (2) You added a `#[cfg(test)]` module to a file in a Fastly Compute binary crate and the tests never seem to run or fail to link, (3) Existing `#[cfg(test)]` modules in src/main.rs or its sibling modules appear dead despite being present in the source tree, (4) `cargo test --lib` works but `cargo test` fails.
日本語の概要は準備中です。原文の説明を表示しています。
Detect semantic-level bugs by analyzing whether code behavior matches its intended purpose inferred from function/variable names, comments, docstrings, and documentation. Use when users need to: (1) Find logic errors where implementation contradicts stated intent, (2) Identify off-by-one errors and boundary mismatches, (3) Detect inverted logic or wrong operators, (4) Catch missing edge case handling, (5) Verify code matches its documentation. Highlights mismatches between intent and implementation across multiple programming languages.
日本語の概要は準備中です。原文の説明を表示しています。
Performs abstract interpretation over source code to infer possible program states, variable ranges, and data properties without executing the program. Reports potential runtime errors including out-of-bounds accesses, null dereferences, type inconsistencies, division by zero, and integer overflows. Use when analyzing code for potential runtime errors, performing static analysis, checking safety properties, or verifying program behavior without execution.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically repair buggy code and generate comprehensive tests for Python, Java, and C++ programs. Use when users need to fix logic errors or runtime errors in functions, modules, or repositories. Accepts specifications via natural language descriptions, existing test cases, or input/output examples. Generates corrected code, creates or updates tests to verify correctness and prevent regressions, and produces a detailed report explaining the bug, fix, and testing strategy. Triggers on requests like "fix this bug", "repair this code", "debug this function", or "this code is broken".
日本語の概要は準備中です。原文の説明を表示しています。
Use when seeing errors about better-sqlite3 native module, NODE_MODULE_VERSION mismatch, "was compiled against a different Node.js version", or similar native binding errors.
日本語の概要は準備中です。原文の説明を表示しています。
Validate any Lattice SKILL.md against all tier conventions — atoms, molecules, and refiners. Catches structural errors, broken cross-references, and convention violations before they reach the repo. If you just wrote or modified a Lattice skill file and haven't run this yet, run it now — manual review consistently misses the same categories of errors this skill is specifically designed to catch. Use when the user says 'validate this skill', 'check this skill', 'does this follow conventions', 'review this skill file', 'check my SKILL.md', or 'skill validate'. Reports PASS/FAIL with specific file-and-section findings and actionable fixes. Standalone — does not call other skills.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when authoring reusable, idempotent MATLAB scripts that build System Composer architecture models via the architecture-modeling API — `systemcomposer.createModel`, `addComponent`, `addPort`, `setInterface`, `connect(srcPort, dstPort)`, interface dictionaries (.sldd) with `addInterface`/`addElement`, profiles/stereotypes with `Profile.createProfile` and `addStereotype`, or `systemcomposer.allocation.createAllocationSet`. Also trigger when debugging these APIs (connections that don't appear, interfaces that don't resolve, profile save errors, `createAllocationSet` signature-mismatch errors). Do NOT trigger for ad-hoc structural edits to an already-built model (adding one SubSystem, rewiring a port) — use `building-simulink-models` with `model_edit` for that.
日本語の概要は準備中です。原文の説明を表示しています。
Compile the TMDb package AND all test targets (without running the tests) to catch test-code compile errors. Use after changing tests or shared code to check everything still builds — delegates to the tooling-runner agent (Haiku) and returns a concise pass/fail + errors-as-file:line summary. Differs from /build, which compiles only the library; to run the tests, use /test.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze application error logs and monitoring platform exports (Sentry, Datadog, Rollbar) to identify error patterns, duplicates, and severity. Use when someone asks to "audit errors", "analyze exceptions", "find noisy alerts", "deduplicate error groups", or "triage production errors". Parses JSON/CSV error exports and produces categorized reports with root cause analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Build robust TypeScript applications with Effect — type-safe error handling, concurrency, dependency injection, and streaming. Use when someone asks to "handle errors without try-catch", "type-safe error handling in TypeScript", "dependency injection without classes", "concurrent TypeScript", "Effect library", "replace try-catch with typed errors", or "functional programming in TypeScript". Covers Effect, Layer, Schedule, Stream, and Schema.
日本語の概要は準備中です。原文の説明を表示しています。
亚马逊管理之道 (亚马逊管理之道 (The Amazon Way — Amazon 自身的领导力与运营操作系统) — 这个 master skill 蒸馏的不是『在亚马逊平台上开店卖货』(那是跨境电商运营,已由 cross-border-ecommerce 另蒸),也不是 AWS 云技术架构;而是亚马逊这家公司『怎么运营自己、怎么做决策、怎么招人、怎么创新、怎么规划』的一整套可迁移的管理机制(mechanisms)与心智操作系统。面向想在自己团队/公司引入亚马逊式机制的创始人/CEO/高管/运营负责人(COO)、产品经理与技术产品经理(PM/PMT)、组织与流程设计者(chief of staff / ops)、以及在亚马逊工作或准备面试亚马逊(著名的 LP 行为面试 + Bar Raiser)的人。覆盖: (a) 第一性张力 — 亚马逊 OS 的核心世界观分歧: **机制 > 良好意图(Good intentions don't work, mechanisms do:问题不能靠『下次更努力』修复,要装一个带检查闭环的自我强化流程) ⇄ 可控输入指标 vs 滞后输出指标(管你能控制的 input 如选品/价格/在库/配送速度,而非 revenue/股价这类滞后又不可控的 output) ⇄ 长期主义 vs 季度业绩(Day 1、willing to be misunderstood、用现金流+飞轮长期投入,宁可牺牲短期利润) ⇄ 客户执念 vs 竞争对手执念(working backwards 从客户倒推,而非从竞品或『我们能造什么』正推) ⇄ 叙事备忘录 vs PPT(6-pager + 开会前静默阅读、动手前先写 PR/FAQ;写作逼出清晰思考,禁 PowerPoint) ⇄ 单线程负责人/两个披萨团队 vs 协调税(separable、autonomous、one owner per initiative,砍掉跨团队依赖) ⇄ 高标准可学习可传递 vs 与生俱来(insist on the highest standards + Bar Raiser 招聘门,标准是 domain-specific 且能教的) ⇄ 节俭催生创造力 vs 血汗文化(frugality/约束驱动发明 —— 但 frugality + 高压 bar + URA 强制淘汰 = 文化阴暗面批判) ⇄ 两类决策(Type 1 不可逆/单向门 慎重 vs Type 2 可逆/双向门 高判断力个人快速决策,别用重流程拖慢))**; (b) 核心机制(mechanisms,本行的『工具栈』其实是一套运营机制而非软件) — Leadership Principles(14 条→2021 增至 16 条,是一套运营语言和决策仲裁器)、Working Backwards(从客户倒推:动手前先写新闻稿+常见问答 PR/FAQ)、叙事备忘录(6-pager narrative / 1-pager + silent reading 静默阅读、禁 PPT)、Weekly Business Review(WBR + metrics deck 指标看板)、input/output metrics(可控输入指标体系、DMAIC 式指标选择)、年度规划(OP1/OP2 + S-Team goals)、Bar Raiser(招聘机制,独立于用人经理的抬杠者拥有一票否决)、Two-Pizza Team / Single-Threaded Leader STL / separable teams、Correction of Errors(COE 事故复盘 + 5 Whys 五问法)、Andon Cord(安灯绳,借自丰田,一线可拉停)、Flywheel(飞轮:低价→更多客户→更多卖家→更多选品→更低成本结构→更低价)、Type 1/Type 2(单向门/双向门决策分级)、Regret Minimization Framework(遗憾最小化,贝索斯创业决策法); (c) 心智模型层 — customer obsession(客户执念是所有 LP 之首)、long-term thinking / Day 1(第二天就是停滞衰亡)、invent and simplify、ownership(主人翁,不说 that's not my job)、bias for action(可逆决策就快,speed matters)、disagree and commit(充分反对后即便不同意也全力执行)、frugality、dive deep(深入细节、不靠代理指标脱离一线)、think big、are right a lot(用强判断力和证伪自己的能力多做对的判断)、earn trust、deliver results; (d) 工作流/SOP — 用亚马逊方式发起一个新产品/业务(先写 PR/FAQ→评审→倒推着造)、如何跑一场 WBR、如何写和评审一份 6-pager(叙事流程 + 静默阅读)、Bar Raiser 招聘 loop、年度规划(OP1/OP2→S-Team goals→输入指标追踪)、事故后的 Correction of Errors; (e) 知识正典(en-primary,极其丰富且可取一手) — 贝索斯致股东信 1997-2021(1997 首封是奠基文本,每年附在信末;Day 1、遗憾最小化、long term)、《Working Backwards》Colin Bryar & Bill Carr(2021,运营机制圣经)、《The Everything Store》Brad Stone(2013,公司史)、《Amazon Unbound》Brad Stone(2021,权力与阴暗面续作)、《Invent and Wander》贝索斯文集(2020)、《The Amazon Way》/《Think Like Amazon》John Rossman(前亚马逊高管)、Amazon 官方 Leadership Principles 页(amazon.jobs,一手)、HBR『The Institutional Yes』(2007 贝索斯访谈); (f) 行业大佬/figures — Jeff Bezos(创始人,源头教义)、Andy Jassy(现任 CEO,OS 超越创始人的证据 + AWS 缔造者)、Colin Bryar(前贝索斯影子/TPM,《Working Backwards》作者)、Bill Carr(前数字媒体 VP,《Working Backwards》作者)、Jeff Wilke(前全球消费者 CEO,运营架构师)、John Rossman(前亚马逊、机制布道者/顾问)、Brad Stone(记者/编年史作者,批判性外部视角); (g) 争议/批判(必须保留,不能洗白) — 文化阴暗面(NYT 2015『Inside Amazon: Wrestling Big Ideas in a Bruising Workplace』揭露高压职场)、仓储与一线劳工争议、URA(unregretted attrition 强制淘汰)与 stack-ranking 的残酷、frugality + 高 bar = 燃尽(burnout);机制能否迁出亚马逊(cargo-culting:在初创或非科技公司照搬 PR/FAQ/输入指标/Bar Raiser 常失败);是贝索斯个人天才(personality)还是制度化机制(institution)—— OS 在贝索斯卸任后于 Jassy 治下延续,是机制派的证据; (h) 流派/思想谱系 — **信徒/机制布道派(Bryar & Carr《Working Backwards》+ 前亚马逊 operator 顾问圈,信 mechanisms 可移植、任何公司可安装)** vs **批判派(Brad Stone《Amazon Unbound》+ NYT + 劳工视角,认为 OS 与高淘汰的残酷机器不可分割,不该被浪漫化)** vs **情境/规模怀疑派(机制之所以有效是因为亚马逊特定的规模/现金流/创始人权力,照搬到小公司=cargo cult)** vs **创始人中心 vs 制度中心之争(是贝索斯个人 vs 可传承的机制)**。不含: 在亚马逊开店卖货/选品/PPC/FBA 的卖家运营(=cross-border-ecommerce)、AWS 云技术架构与运维、通用 MBA 管理理论泛泛而谈、把普通商业常识包装成『亚马逊独家秘诀』。) Master OS — automated mastery of 亚马逊管理之道 (The Amazon Way — Amazon 自身的领导力与运营操作系统) — 这个 master skill 蒸馏的不是『在亚马逊平台上开店卖货』(那是跨境电商运营,已由 cross-border-ecommerce 另蒸),也不是 AWS 云技术架构;而是亚马逊这家公司『怎么运营自己、怎么做决策、怎么招人、怎么创新、怎么规划』的一整套可迁移的管理机制(mechanisms)与心智操作系统。面向想在自己团队/公司引入亚马逊式机制的创始人/CEO/高管/运营负责人(COO)、产品经理与技术产品经理(PM/PMT)、组织与流程设计者(chief of staff / ops)、以及在亚马逊工作或准备面试亚马逊(著名的 LP 行为面试 + Bar Raiser)的人。覆盖: (a) 第一性张力 — 亚马逊 OS 的核心世界观分歧: **机制 >
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive status reports for git repositories. Analyzes commits, codebase structure, type errors, branch health, dependency status, GitHub PRs/issues/CI, working tree changes, and optionally integrates with `td` (task management CLI) if a `.todos` folder is present. **TRIGGERS - Use this skill when:** - User asks for the status of a git project or repo - User asks "what's going on in [project]" or "give me an overview of [repo]" - User wants a project summary, progress report, or codebase overview - User asks about recent commits, code structure, or project health - User says "check my project" or "project status" **Output:** A rich, structured text report covering overview, branches, commit history, codebase breakdown, GitHub activity, dependency health, issues/errors, working tree changes, task management, and summary.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and fix mini-program failures through reproducible, evidence-driven root-cause analysis across source, state, asynchronous timing, caches, mock data, build versions, platform behavior, devices, cloud calls, and external services. Use when users report white screens, crashes, stale or jumping values, missing data, intermittent behavior, permission failures, performance stalls, device-only defects, API or cloud-function errors, source-versus-build mismatches, or regressions whose cause is not yet established. Freezes the observation environment, ranks competing hypotheses, runs discriminating checks, creates a failing regression test before repair, covers analogous states, and never hides a known failure with longer waits, swallowed errors, forced success, or cosmetic patches.
日本語の概要は準備中です。原文の説明を表示しています。