'minimal' 검색 결과

File upload endpoints in ASP.NET minimal APIs (.NET 8+)

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

ASP.NET Core web framework conventions: Minimal API vs MVC controllers, Program.cs composition, DI lifetimes (Scoped/Singleton/Transient), Options pattern with IOptions<T>, middleware ordering (HTTPS redirect → routing → authentication → authorization), model binding and validation (FluentValidation / DataAnnotations), ProblemDetails error handling, structured logging with ILogger<T>, configuration layering (appsettings.json + environment variables + User Secrets), and health checks. Works alongside csharp-foundation:csharp-conventions and aspnet-core-plugin:efcore-patterns. Use this skill to: - Compose Program.cs correctly — register services, configure middleware in the right order, map endpoints. - Apply the Options pattern to avoid passing raw IConfiguration into services. - Write Minimal API endpoint groups with typed results and authorization. - Handle cross-cutting errors uniformly with ProblemDetails. - Configure structured logging and health checks for production readiness. Do NOT use this skill for: - EF Core entity configuration and migrations — see aspnet-core-plugin:efcore-patterns. - C# language idioms — see csharp-foundation:csharp-conventions. - Testing — see csharp-foundation:dotnet-testing.

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

Use when writing or restructuring code, before adding a helper, wrapper, config key, or dependency, or when the user asks for minimal or DRY code. Not for performance tuning: use optimize.

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

Replace sentence-by-sentence revised or paraphrased text back into an original paper or document while preserving the original formatting, typography, paragraph settings, citation layout, and document conventions as the source of truth. Use when the user provides revised text that maps back to original sentences, paragraphs, sections, or the whole document, but may also contain clear local sentence merges or splits, and asks to replace it back into the source, keep the original formatting, do sentence-by-sentence replacement, preserve original formatting, or only swap wording without rewriting the document. Only allow minimal edits to the rewritten text when fixing citation formatting, restoring protected original content, restoring the original person reference, or minimally splitting/merging text back into original sentence slots; otherwise do not improve grammar, style, logic, or wording.

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

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.

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

Use when designing or refining UIs that must be visually minimal, low-noise, and icon-forward while staying understandable for new users, especially when reducing text, consolidating controls, or streamlining dialogs, toolbars, search panels, or list results.

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

Review any business decision, plan, or strategy through the minimalist entrepreneur lens. Use to gut-check decisions, simplify approaches, or evaluate options using core principles.

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

Apply a refined Scandinavian visual system with a neutral black-and-white foundation, restrained sans-serif typography, purposeful product imagery, generous spacing, clear page chapters, and minimal decoration. Use when the user invokes /scandinavian-design or requests a Nordic, monochrome, calm, spacious, restrained, or minimalist interface.

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

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

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

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 editing an existing codebase and the goal is minimal, standard, and non-invasive changes — prioritizes simplest solution, standard libraries first, and surgical modification without unsolicited refactors

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

Reduce container attack surface by building application images on Google distroless base images that contain only the application runtime with no shell, package manager, or unnecessary OS utilities.

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

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has been paged at 3am for a factory class that wrapped one function: question whether the task needs to exist at all, reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full, ultra. The default is full. 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 such as general knowledge, prose, translation, summaries, recipes.

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

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

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

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.

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

Create ASP.NET Minimal API endpoints with proper OpenAPI documentation

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

Builds ASP.NET Core Minimal APIs -- route groups, filters, TypedResults, OpenAPI.

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

설계서나 요구사항에서 처음부터 끝까지 작동하는 작은 기능을 계획합니다. 초기 구조 생성, 생성과 평가 반복, 검토와 승인을 거쳐 최소 기능 제품을 만듭니다.

• 설계서에서 작동하는 MVP 구축
• 전체 흐름이 작동하는 작은 기능 계획
• 첫 기능의 초기 구조 생성

Python 앱을 Windows에 배포하도록 Nuitka 컴파일, 불필요한 파일과 DLL 용량 분석, Inno Setup을 통한 가벼운 설치 프로그램 제작을 지원합니다.

• Python 앱을 Windows용으로 배포하기
• 배포 용량이 큰 의존성 조사하기
• 새 Windows 환경의 실행 오류 조사하기

Write, review, and refactor C# and .NET code using practical conventions for asynchronous work, configuration, and dependency injection—passing services into classes. Includes examples for data access and APIs to support maintainable applications.

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

• Reviewing C# implementation conventions
• Improving asynchronous code and cancellation handling
• Organizing service dependencies and configuration

기존 PyTorch 학습 코드를 적은 수정으로 여러 GPU나 컴퓨터에 맞게 구성합니다. 혼합 정밀도, 메모리 절약 설정과 학습 실행 방법을 안내합니다.

• 단일 GPU 학습을 여러 GPU로 옮깁니다
• 혼합 정밀도 학습을 설정합니다
• DeepSpeed나 FSDP로 메모리를 절약합니다

과학 원리, 사물의 구조, 작업 흐름을 색상과 여백이 일관된 SVG 도표로 만듭니다. 밝은 화면과 어두운 화면을 지원하며 단일 HTML 파일로 출력합니다.

• 교재용 과학 원리 도해 제작
• 단면도와 층별 도표로 구조 설명
• 작업 공정과 데이터 흐름 시각화

실패하는 테스트를 먼저 작성하고 최소한의 코드로 통과시킨 뒤 정리하는 개발 절차를 적용합니다. 기능 추가와 버그 수정을 한 가지 동작씩 검증하며 진행합니다.

• 테스트를 먼저 작성하는 기능 추가
• 버그를 재현한 뒤 수정
• 테스트 통과를 유지하며 코드 정리

손으로 쓴 글자 사진을 컴퓨터에 설치할 수 있는 글꼴로 만듭니다. 문자 식별과 결과 확인, 획 굵기와 윤곽 조정, 웹 글꼴 내보내기를 지원합니다.

• 손으로 쓴 글자를 글꼴로 만들 때
• 획 굵기와 윤곽을 조정할 때
• 웹 글꼴을 내보낼 때