'conventions' 검색 결과

Use this skill when an agent needs to prepare a focused commit, follow repository commit-message conventions, write a clear commit message, and create the git commit cleanly.

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

Apply these opinionated .NET 8 architecture conventions whenever structuring or reviewing a backend service: clean architecture layering and which direction dependencies point, when CQRS with MediatR is worth it, cross-cutting concerns as pipeline behaviours, minimal APIs grouped by feature, keeping DbContext in Infrastructure, health checks and structured logging, WebApplicationFactory integration tests, and when AOT pays off.

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

Apply these opinionated TypeScript conventions whenever writing or reviewing TypeScript: branded types for domain modeling, discriminated unions for state, `satisfies` over `as`, const objects instead of enums, type-only imports, and the strict tsconfig baseline beyond `strict: true`. Also use for monorepo project references and incremental build setup.

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

Opinionated house conventions for NestJS backends — module boundaries and layering, provider wiring and injection scopes, guards/interceptors/pipes/filters, DTOs and validation, domain exceptions, config, and the Nest 11 / Express 5 behaviour that compiles cleanly and fails at runtime. Use whenever the code is NestJS (`@nestjs/*` in package.json, or `@Module`/`@Injectable`/`@Controller`/`@Cron` in the file), including when the question sounds like plain TypeScript, an OOP refactor, a code review, or an ops problem — the Nest-specific answer differs from the generic one. Typical asks: scaffolding a module, adding a controller, provider, or endpoint, wiring an enhancer, a boot-time DI or circular-import failure, a response leaking entity fields despite `@Exclude()`, a cron job firing on every replica, upgrading NestJS, or reviewing a Nest diff. Not for plain Express or Fastify, Angular, frontend, SQL, or CI.

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

Apply these opinionated Next.js conventions whenever writing or reviewing App Router code (14+): Server Components by default, where the 'use client' boundary belongs, the caching defaults that changed in Next 15, tag-based revalidation, treating Server Actions as public endpoints, the Metadata API, and next/image and next/font.

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

Apply these opinionated C# conventions whenever writing or reviewing C# 12 / .NET 8+ code: nullable enabled with warnings as errors, records and primary constructors, pattern matching over cast chains, the Result pattern for expected failures, async all the way with CancellationToken, IOptions config, IHttpClientFactory, and never returning EF entities from an API.

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

Apply these opinionated React conventions when writing React 18+ or 19 components: hooks patterns, Server Components, Suspense boundaries, state management, performance memoization, React 19 features (use, form actions).

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

Apply these opinionated JavaScript conventions whenever writing or reviewing JS or Node: ESM-first packaging, choosing between Promise combinators, error handling that doesn't swallow failures, AbortController for cancellation, keeping the event loop unblocked, and reaching for platform APIs before dependencies.

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

Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.

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

Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.

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

Idiomatic C# and .NET patterns, conventions, dependency injection, async/await, and best practices for building robust, maintainable .NET applications.

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

Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.

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

Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.

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

Audits project physical structure: file hygiene, ignore file quality, framework convention compliance, domain/layer organization, naming conventions. Stack-adaptive via auto-detection.

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

Write and update GitHub PR titles and PR bodies with repository templates and local conventions. Use when creating PRs with `gh pr create`, revising PR text, choosing a conventional title prefix (for example `feat(web):`), or ensuring ticket suffix rules.

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

Handle MindIE-SD documentation, governance, contributor workflow, commit or PR conventions, history cleanup, template changes, and version-policy updates with minimal context, fixed review steps, and deterministic output. Use this skill whenever the task touches docs/ 或文档站点内容与配置（Sphinx / Read the Docs / conf.py / index.md / 目录导航 / 首页）、中英文双语配套、治理文档、贡献流程说明、PR/MR 模板或标题正文规范、提交历史整理、版本策略与发布规则。即使用户只说「改个文档」「双语要同步」「commit message 怎么写」「PR 模板加一项」「把提交压一下」「rebase 冲突怎么理」而未提治理规范，也应触发。不负责通用工程实现与仓库默认工作流定义（后者以 AGENTS.md 为准）；Python 格式见 code-standards，Markdown 格式见 markdown-lint。

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

Write, refactor, or review Go code in the dygo framework or App SDK using dygo package boundaries and runtime conventions. Use for substantial Go implementation that is not primarily Cobra CLI work.

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

Review a dygo Business App for framework conventions, model quality, access control, SDK boundaries, observability, and safe lifecycle behavior. Use for App audits and pre-merge reviews, not ordinary implementation.

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

Suggest better variable, function, and class names based on context and conventions.

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

Cross-platform desktop development for macOS and Windows -- platform abstractions, UI convention differences, and multi-platform CI/CD. Activate on: cross-platform app, macOS and Windows, platform differences, DMG installer, MSI installer, NSIS installer, Cmd vs Ctrl, platform abstractions, menu bar differences, native conventions. NOT for: mobile apps, web-only apps, Tauri-specific internals (use rust-tauri-development).

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

Use when applying Cloudflare D1 migrations, fighting Supabase migration history vs SQL execution, choosing direct psql over CLI, designing idempotent migrations, debugging schema drift between local and remote, or recovering after a half-applied migration. Triggers: supabase migration repair instructions appearing, table missing after "applied" status, "Tenant or user not found" when running psql, --remote vs --local D1 confusion, NOT NULL on a populated column, foreign key constraint failures, drift between staging and prod schemas. NOT for Mongo/document migrations, ORM-managed migrations specifically (Prisma/Drizzle have their own conventions), or pure data backfills.

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

Generates shell completion scripts for CLI tools. Parses command structure from help output, commander/yargs configs, or manual specification. Produces completions for bash, zsh, and fish that follow each shell's conventions.

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

Design decisions for when and what sounds to use in web apps, mobile apps, and desktop native apps — plus how to create them with AI. Covers UI sound vocabulary (confirms, alerts, transitions, errors), platform conventions (iOS, macOS, Material), creating sounds with AI tools (ElevenLabs, AudioCraft, Stable Audio), Web Audio API for procedural sounds, haptic-audio pairing, and the psychology of satisfying vs. annoying UI sounds. Activate on 'app sounds', 'UI sounds', 'notification sound', 'sound design app', 'earcons', 'sonic branding', 'interaction sounds', 'feedback sounds', 'app audio', 'satisfying sounds'. NOT for professional audio engineering (use sound-engineer), Windows 3.1 retro sounds specifically (use win31-audio-design), music composition (use sound-engineer).

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

Review Replica pull requests using the same shared conventions and project guides as implementation agents. Use when reviewing changes to code, tests, workflows, or documentation in this repository.

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