'minimal' 검색 결과

Build ASP.NET Minimal API endpoints with explicit request and response types, input validation, and standard error responses. Organize related endpoints and add OpenAPI documentation, a structured description of API operations, parameters, and schemas.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building Minimal API endpoints with explicit types
• Adding operation and parameter descriptions to OpenAPI
• Organizing related endpoints with MapGroup()

Generate ASP.NET Core pages, components, or API endpoints for creating, reading, updating, and deleting database records. Follow the project's existing styling and code conventions, with database migrations and verification of the generated functionality.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add database-backed record management pages
• Generate Minimal API endpoints for a model
• Create Blazor forms that match existing styling

Build .NET 8 APIs and backend services using C# 12, with clear separation of application responsibilities. The skill covers database access, authentication, API documentation, compilation checks, and integration tests that verify components working together.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building endpoints with minimal APIs
• Adding database access with Entity Framework Core
• Separating application responsibilities with MediatR

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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

따뜻한 무채색과 글자 대비, 넉넉한 여백으로 잡지처럼 정보를 정리하는 미니멀 웹 화면을 설계합니다. 카드 그리드와 은은한 강조색을 활용합니다.

• 미니멀 제품 화면의 프로토타입 제작
• 기능 소개 카드의 비대칭 그리드 배치
• 서체와 여백, 색상 통일

Turn incomplete or intermittent bug reports into a minimal reproduction backed by recorded evidence. Capture the environment, expected and actual results, commands, and remaining unknowns in a brief before diagnosis or repair.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying an incomplete bug report
• Recording how often an intermittent failure occurs
• Documenting an environment-specific failure

Set up or repair the OMC status display in Claude Code, then choose how much information it shows. Configure presets and individual elements to monitor task progress, context usage, and running agents during a session.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up or repairing the status display
• Switching to a minimal status line
• Viewing running agents and their tasks

Create Marp presentation slides, written in Markdown, using seven themes for business, technical, academic, and creative content. The skill organizes headings, bullet points, whitespace, and images into a consistent presentation saved as a Markdown file.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create slides for lectures and seminars
• Prepare proposals and business reports
• Build slides for technical presentations

Keep coding tasks small by checking whether new code is needed, reusing existing helpers, and preferring standard libraries or built-in platform features. Apply the same approach to feature development, bug fixes, refactoring, and reviews.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding a feature with minimal code
• Reviewing unnecessary dependencies
• Simplifying an overcomplicated implementation

Build C# applications with .NET 8+, including ASP.NET Core APIs and Blazor interfaces. Get models, endpoints, services, and configuration, with guidance on database access, asynchronous operations, cancellation, authentication, performance tuning, and tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a REST API with ASP.NET Core
• Implement database access with Entity Framework Core
• Create Blazor components and manage application state

Create sparse vertical posters from themes, articles, or photos, using paper textures, generous empty space, experimental typography, and one accent color. It also analyzes visual references and produces reusable style rules and image generation prompts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn an article into a poster with one visual metaphor
• Create a poster that preserves a photo's recognizable subject
• Extract reusable style rules from reference images

Design minimal agency websites around a precise column grid, oversized headlines, generous whitespace, and restrained imagery. Establish a consistent visual direction for service listings, labels, buttons, and subtle motion across architecture, design, or strategy agency pages.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Website design for architecture and design agencies
• Establishing a consistent visual system across pages
• Structuring service listings with a clear column grid

Build or update ASP.NET Core API endpoints with defined request and response types, appropriate HTTP status codes, OpenAPI documentation, and centralized error handling. Also creates .http request files for manually checking endpoint behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add API endpoints following existing project conventions
• Document API inputs and responses with OpenAPI
• Standardize error responses and exception handling

Create a restrained animated HTML title scene around a brand or theme word. Thin letters appear in sequence, while generous whitespace, warm gold lines, corner marks, and softly pulsing indicators frame the message.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Introducing a brand word
• Creating a restrained title card
• Presenting a theme with generous whitespace

Configure a terminal status display for Diverga research projects. Show the project name, research stage, checkpoint progress, and memory health, choose among four display presets, and set up or repair the Claude Code integration.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Monitor research progress in the terminal
• Show detailed checkpoint completion status
• Focus the display on memory and context health

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates ASP.NET Minimal API endpoints with correct request/response types and complete OpenAPI (Swagger) documentation. Use when adding or reviewing Minimal API endpoints in .NET, or when generated OpenAPI output is missing schemas, status codes, or descriptions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

저장소에서 외부 요청이나 사용자 입력으로 악용할 수 있는 취약점을 찾습니다. 입력 경로와 재현 절차, 영향을 확인해 버그 바운티 보고서 작성을 지원합니다.

• 외부 요청으로 도달 가능한 취약점 조사
• 정적 분석 결과 검토
• 최소 재현 절차와 영향 정리