821 件 ・ 関連度順
概要と使いどころ
This skill should be used when the user asks to "fix a bug with minimal changes", "analyze change scope for a bugfix", "find the minimal set of files to change", "do a focused bugfix", or "scope a minimal repair".
日本語の概要は準備中です。原文の説明を表示しています。
Generate or analyze poetic paper-texture minimal zine posters with large negative space, a small editorial collage or focal element, experimental typography, and one clear color accent. Use when the user gives a theme, sentence, article, mood, object, photo, content brief, reference images, or an image folder and wants a final poster image, a production-ready image prompt, reusable style rules, or varied layouts that stay in one visual family.
日本語の概要は準備中です。原文の説明を表示しています。
Luxury-minimal whitespace hero — single word reveals letter by letter, warm-gold hairline, breathing indicators.
日本語の概要は準備中です。原文の説明を表示しています。
Design and implement Minimal APIs in ASP.NET Core using handler-first endpoints, route groups, filters, and lightweight composition suited to modern .NET services. USE FOR: building new HTTP APIs in ASP.NET Core; creating lightweight microservices; choosing between Minimal APIs and controllers. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
日本語の概要は準備中です。原文の説明を表示しています。
Minimal / clean / Linear / Notion / Vercel / whitespace-heavy UIs. Locked knobs: CRAFT=8, MOTION=3, DENSITY=2. Monochrome + one accent, Inter/Geist, hairline borders over shadows. Trigger on: minimal, clean, Linear-like, Notion-like, Vercel-like, whitespace-heavy.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a vague bug report into a VERIFIED minimal reproduction and then a failing regression test, agent-driven end to end. Covers extracting the implicit repro from a thin report (env, build, steps, data), the reproduce-minimize-isolate-capture loop, git bisect to find the introducing commit, building a deterministic minimal repro (fixed seeds, frozen time, stubbed network), writing the failing regression test BEFORE the fix (red) and confirming the fix flips it green, and writing repro evidence back into the ticket. Distinguishes flaky-not-reproducible from environment-specific. Use when: "reproduce this bug," "minimal reproduction," "repro steps," "find the commit that broke it," "git bisect," "make the repro deterministic," "write a failing test for this bug," "regression test for a defect," "can't reproduce this bug." Not for: Classifying/deduplicating/severity-routing existing failures without reproducing them — that is ai-bug-triage. Generating tests from specs rather than from a defect — that is ai-test-generation. Related: ai-bug-triage, ai-test-generation, test-reliability, systematic-debugging, qa-project-context.
日本語の概要は準備中です。原文の説明を表示しています。
侍酒师与葡萄酒 (侍酒师 / 葡萄酒 (Sommelier & Wine) — 葡萄酒鉴赏 + 侍酒服务的职业认知操作系统，从业者/侍酒师/学习者视角。覆盖: (a) 两大认证体系张力 — WSET (Wine & Spirit Education Trust, 英国, 知识+SAT 系统化品鉴方法, Diploma/L4 笔试导向) vs Court of Master Sommeliers (CMS, 美/英, 服务+盲品演绎法+理论三位一体, MS 头衔), 外加 Institute of Masters of Wine (MW, 学术研究+论文) 与 UC Davis 葡萄酒学/葡萄栽培学学院派; (b) 盲品 = 纯 tacit 校准技能 — 演绎品鉴网格 (deductive tasting: 看色/闻香/品味 → 结构线索 calculated structure → 推断品种/产区/年份/酒龄), WSET SAT vs CMS deductive grid 两套方法论; (c) 第一性张力 — codifiable 理论层 (产区/品种/酒法/风土/酿造/葡萄栽培) ⇄ tacit 校准层 (品鉴味觉记忆/盲品/侍酒服务), 这行的核心矛盾是「可背诵的知识」与「不可言传的味觉」之间; (d) 旧世界 vs 新世界框架 — 旧世界以风土/法定产区为组织原则 (AOC/DOCG/QbA 分级法), 新世界以品种为标签; 风土 (terroir) 是核心组织概念; (e) 侍酒服务/酒店层 — 餐厅 floor 的配餐 (food pairing)、醒酒/侍酒温度、酒单与酒窖管理、by-the-glass 与饮品项目经济学、盲品 service exam; (f) 葡萄酒商业层 — 三级分销体系 (美国 three-tier)、定价/配额 (allocation)、期酒 (en primeur)、投资酒 (Liv-ex) 与拍卖; (g) 智识/品味演进 — 帕克百分制 (Robert Parker / Wine Advocate 100-point) vs Jancis Robinson 20 分制散文派; 经典派 vs 现代派酿造; 自然酒/低干预 (natural/minimal-intervention) vs 传统技术派. 学派分歧: WSET 知识体系派 vs CMS 服务盲品派、旧世界风土派 vs 新世界品种/技术派、自然酒派 vs 传统派、百分制点评派 vs 散文叙述派、经典平衡派 vs 浓郁现代派. 不含: 家庭自酿 DIY 套件、纯调酒/鸡尾酒/烈酒、葡萄园重型农机工程、酒精成瘾/公共卫生政策、酒类电商运营纯营销。) Master OS — automated mastery of 侍酒师 / 葡萄酒 (Sommelier & Wine) — 葡萄酒鉴赏 + 侍酒服务的职业认知操作系统，从业者/侍酒师/学习者视角。覆盖: (a) 两大认证体系张力 — WSET (Wine & Spirit Education Trust, 英国, 知识+SAT 系统化品鉴方法, Diploma/L4 笔试导向) vs Court of Master Sommeliers (CMS, 美/英, 服务+盲品演绎法+理论三位一体, MS 头衔), 外加 Institute of Masters of Wine (MW, 学术研究+论文) 与 UC Davis 葡萄酒学/葡萄栽培学学院派; (b) 盲品 = 纯 tacit 校准技能 — 演绎品鉴网格 (deductive tasting: 看色/闻香/品味 → 结构线索 calculated structure → 推断品种/产区/年份/酒龄), WSET SAT vs CMS deductive grid 两套方法论; (c) 第一性张力 — codifiable 理论层 (产区/品种/酒法/风土/酿造/葡萄栽培) ⇄ tacit 校准层 (品鉴味觉记忆/盲品/侍酒服务), 这行的核心矛盾是「可背诵的知识」与「不可言传的味觉」之间; (d) 旧世界 vs 新世界框架 — 旧世界以风土/法定产区为组织原则 (AOC/DOCG/QbA 分级法), 新世界以品种为标签; 风土 (terroir) 是核心组织概念; (e) 侍酒服务/酒店层 — 餐厅 floor 的配餐 (food pairing)、醒酒/侍酒温度、酒单与酒窖管理、by-the-glass 与饮品项目经济学、盲品 service exam; (f) 葡萄酒商业层 — 三级分销体系 (美国 three-tier)、定价/配额 (allocation)、期酒 (en primeur)、投资酒 (Liv-ex) 与拍卖; (g) 智识/品味演进 — 帕克百分制 (Robert Parker / Wine Advocate 100-point) vs Jancis Robinson 20 分制散文派; 经典派 vs 现代派酿造; 自然酒/低干预 (natural/minimal-intervention) vs 传统技术派. 学派分歧: WSET 知识体系派 vs CMS 服务盲品派、旧世界风土派 vs 新世界品种/技术派、自然酒派 vs 传统派、百分制点评派 vs 散文叙述派、经典平衡派 vs 浓郁现代派. 不含: 家庭自酿 DIY 套件、纯调酒/鸡尾酒/烈酒、葡萄园重型农机工程、酒精成瘾/公共卫生政策、酒类电商运营纯营销。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 侍酒师 / 葡萄酒 (Sommelier & Wine) — 葡萄酒鉴赏 + 侍酒服务的职业认知操作系统，从业者/侍酒师/学习者视角。覆盖: (a) 两大认证体系张力 — WSET (Wine & Spirit Education Trust, 英国, 知识+SAT 系统化品鉴方法, Diploma/L4 笔试导向) vs Court of Master Sommeliers (CMS, 美/英, 服务+盲品演绎法+理论三位一体, MS 头衔), 外加 Institute of Masters of Wine (MW, 学术研究+论文) 与 UC Davis 葡萄酒学/葡萄栽培学学院派; (b) 盲品 = 纯 tacit 校准技能 — 演绎品鉴网格 (deductive tasting: 看色/闻香/品味 → 结构线索 calculated structure → 推断品种/产区/年份/酒龄), WSET SAT vs CMS deductive grid 两套方法论; (c) 第一性张力 — codifiable 理论层 (产区/品种/酒法/风土/酿造/葡萄栽培) ⇄ tacit 校准层 (品鉴味觉记忆/盲品/侍酒服务), 这行的核心矛盾是「可背诵的知识」与「不可言传的味觉」之间; (d) 旧世界 vs 新世界框架 — 旧世界以风土/法定产区为组织原则 (AOC/DOCG/QbA 分级法), 新世界以品种为标签; 风土 (terroir) 是核心组织概念; (e) 侍酒服务/酒店层 — 餐厅 floor 的配餐 (food pairing)、醒酒/侍酒温度、酒单与酒窖管理、by-the-glass 与饮品项目经济学、盲品 service exam; (f) 葡萄酒商业层 — 三级分销体系 (美国 three-tier)、定价/配额 (allocation)、期酒 (en primeur)、投资酒 (Liv-ex) 与拍卖; (g) 智识/品味演进 — 帕克百分制 (Robert Parker / Wine Advocate 100-point) vs Jancis Robinson 20 分制散文派; 经典派 vs 现代派酿造; 自然酒/低干预 (natural/minimal-intervention) vs 传统技术派. 学派分歧: WSET 知识体系派 vs CMS 服务盲品派、旧世界风土派 vs 新世界品种/技术派、自然酒派 vs 传统派、百分制点评派 vs 散文叙述派、经典平衡派 vs 浓郁现代派. 不含: 家庭自酿 DIY 套件、纯调酒/鸡尾酒/烈酒、葡萄园重型农机工程、酒精成瘾/公共卫生政策、酒类电商运营纯营销。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「侍酒师」「sommelier」「葡萄酒」「wine」「盲品」
日本語の概要は準備中です。原文の説明を表示しています。
Generates Minimal API endpoints following Microsoft's recommended approach. Creates fast, testable HTTP APIs with minimal code using MapGet/MapPost/MapPut/MapDelete. Preferred over controller-based APIs for new projects.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when architecting new Claude Code agents following Anthropic best practices. Guides through YAML frontmatter creation, agent structure definition, role boundaries, and validation. Critical for creating minimal agent files (~150 lines) with proper skill invocations. Examples: <example>Context: User wants to create a new agent for security auditing user: "Create a security-auditor agent" assistant: "I'll use the agent-creator skill to build this agent following Anthropic best practices" <commentary>New agent creation requires the agent-creator skill to ensure proper structure and YAML frontmatter.</commentary></example> <example>Context: Existing agent file is too verbose and needs refactoring user: "The architect agent is 2000 lines, refactor it to minimal structure" assistant: "I'll use the agent-creator skill to refactor this into a minimal ~150 line agent with a separate skill file" <commentary>Agent refactoring requires the agent-creator skill to separate identity from technical procedures.</commentary></example>
日本語の概要は準備中です。原文の説明を表示しています。
Revise an already accepted article, essay, paper, statement, or manuscript under strict minimal-change constraints while still satisfying reviewer comments, supervisor feedback, or requested edits. Use when the user asks for minimal edits, smallest necessary changes, preserve the current voice, keep the existing style, avoid broad rewriting, or implement requested revisions without unnecessary polishing.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "最小再現環境を作って", "再現環境を構築して", "問題を切り分けたい", "パッケージの不具合か確認したい", "create a minimal reproduction", "isolate the issue", "build a repro environment", "reproduce this bug", "narrow down the cause", "is this a package bug or my code", "このPRの問題を再現して", "this commit broke something", or wants to determine whether a bug is caused by a package, the environment, or application code. Accepts PR URLs, commit hashes, or branch names as input.
リポジトリから外部経由で悪用できる脆弱性を探し、入力から危険な処理までの経路、再現手順、影響を確認して報奨金制度向けの報告を支援するスキル。
ECCの導入・更新・再設定を、利用中のエージェント環境に合わせて進めます。導入状況の確認から変更内容のプレビュー、適用、検証までを対話形式で案内します。
Editorial-minimalist web prototype. Warm monochrome canvas, serif display + grotesque body, 1px hairline borders, muted pastel chips, generous macro-whitespace, ambient micro-motion. Distilled from Leonxlnx/taste-skill `minimalist-skill`.
日本語の概要は準備中です。原文の説明を表示しています。
16:9 HTML deck in editorial-minimalist taste. Warm cream slides, serif display + grotesque body, hairline rules, monospace meta, generous macro-whitespace, one accent. Distilled from Leonxlnx/taste-skill `minimalist-skill`.
日本語の概要は準備中です。原文の説明を表示しています。
Create ASP.NET Minimal API endpoints with proper OpenAPI documentation
日本語の概要は準備中です。原文の説明を表示しています。
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
日本語の概要は準備中です。原文の説明を表示しています。
Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Builds REST APIs using minimal or controller-based routing, configures database access with Entity Framework Core, implements async patterns and cancellation, structures applications with CQRS via MediatR, and scaffolds Blazor components with state management. Invoke for C#, .NET, ASP.NET Core, Blazor, Entity Framework, EF Core, Minimal API, MAUI, SignalR.
日本語の概要は準備中です。原文の説明を表示しています。
Editorial-minimalist: 暖色单色 canvas + serif display + grotesque body
日本語の概要は準備中です。原文の説明を表示しています。
Create a clean minimal beige light-mode design system with warm neutral shells, quiet process grids, restrained accent color, and elegant low-contrast structure.
日本語の概要は準備中です。原文の説明を表示しています。
Create a minimal agency design system with a disciplined editorial grid, oversized typography, quiet uppercase utility labels, restrained image blocks, and subtle structural detail.
日本語の概要は準備中です。原文の説明を表示しています。
Fast path for a minimal CloudBase Web + database demo (最小前后端 / 最小可用 fullstack / Lovable-like BaaS). Defaults to @cloudbase/js-sdk client CRUD (NoSQL app.database / PG app.rdb), MCP-only schema, preview-first, and forbids cloud functions unless secrets, cron/background jobs, or logic that security rules/RLS cannot express. Use for 搭一套 demo、留言板、Todo、Notes、Kanban, or when users say 带云函数+云数据库 but only need CRUD. NOT for production multi-service backends, CloudRun, WeChat Mini Programs, or tasks that truly need server secrets.
日本語の概要は準備中です。原文の説明を表示しています。
Generate luxury and premium aesthetic video prompts for Seedance 2.0 on Higgsfield. Use for luxury brand content, premium product showcases, high-end lifestyle, minimalist aesthetic, elegant brand videos, or any content requiring sophisticated visual treatment. Triggers on luxury, premium, high-end, elegant, minimalist, sophisticated, exclusive, refined, designer, couture, bespoke.
日本語の概要は準備中です。原文の説明を表示しています。
Guide minimal code via a decision ladder with full safety, edge, and negative-case coverage. Use when adding code, choosing a dependency, or auditing a diff.
日本語の概要は準備中です。原文の説明を表示しています。