'naming' 검색 결과

Test naming conventions and best practices specialized skill. Used when naming test methods, improving test readability, and establishing naming standards. Covers three-part naming method, Chinese naming recommendations, test class naming, etc. Keywords: test naming, test naming, naming conventions, naming conventions, three-part naming, three-part naming, method_scenario_expected, method_scenario_expected, how to name tests, test readability, naming best practices, test report, test documentation

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

Apply consistent names to SGLang speculative decoding code, which verifies draft tokens to generate text. Distinguish tokens with or without the bonus token, counts, counters, and arrays when adding identifiers, renaming code, or reviewing changes.

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

• Naming variables in speculative decoding code
• Renaming identifiers to match their meaning
• Reviewing metric and counter names

Full brand naming workflow for founders, agencies, and businesses. Use this skill whenever the user says "help me name this brand", "brand naming", "I need a name for", "name ideas for", "what should I call my brand/company/product", "naming a startup", "brand name suggestions", "help with naming", or shares a brand brief and asks for name options. Also triggers when the user shares existing name options and asks for feedback, evaluation, ranking, or scoring of those names. Auto-detects whether to run the full generation workflow or the evaluation workflow based on what the user provides. Always use this skill for any brand or product naming task — even if the user just casually mentions needing a name.

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

Review Apache Pinot changes against naming and API conventions, including public names, method signatures, REST endpoints, JSON fields, and documentation. Use it when adding or renaming elements exposed to other code or users.

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

• Reviewing public class, method, or field names
• Checking new enum constants or DataType values
• Reviewing REST endpoints and JSON fields

Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.

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

Apply Swift API Design Guidelines to name, label, and document Swift APIs. Covers argument label rules (prepositional phrase rule, grammatical phrase rule, first-label omission), mutating/nonmutating pair naming (-ed/-ing participle pattern, form- prefix, sort/sorted, formUnion/union), side-effect naming (noun for pure, verb for mutating), documentation comment structure (summary by declaration kind, O(1) complexity rule), clarity at call site, role-based naming, protocol naming (-able/-ible/-ing), default arguments over method families, casing conventions, and terminology. Use when designing new Swift APIs, reviewing naming and argument labels, writing documentation comments, or refactoring for call site clarity.

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

リファクタリングを「更新されたチームの理解と、コードが表現する過去の理解の差分同期」と捉え、今回得た新知識（要求・ドメイン知識・制約）が naming と responsibility へ反映されているか、boundary が現在の understanding を表現しているか、diff の削除行やコメントに現れる過去の design history と constraint を失っていないかを diff-time で確認する。Knowledge Delta の signal は diff（追加/削除された hunk・コメント・ADR 参照）を一次情報とし、PR 本文が供給されるときは補助に用い、不確実なら question に留める。ドメイン用語の一貫性は ubiquitous-language-naming、集約/コンテキスト境界の設計判断は bounded-context-language、投機的抽象化・caller special-case は altitude-generalization、スコープ逸脱/前提破壊は fix-scope-integrity、振る舞い変更と構造変更の分離は behavior-structure-separation、完了主張の反証は refactor-claim-audit へ委譲する

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

Imperative guidance for the System.Text.Json APIs added in .NET 11: the built-in `JsonNamingPolicy.PascalCase` naming policy, and the strongly-typed generic `JsonSerializerOptions.GetTypeInfo` and `JsonSerializerOptions.TryGetTypeInfo` metadata accessors (generic overloads that return a typed `JsonTypeInfo`). USE ONLY when the user is targeting net11.0 or later and needs PascalCase JSON property or dictionary-key names without writing a custom naming policy, a strongly-typed generic `JsonTypeInfo` instead of the non-generic `JsonTypeInfo`, or a no-throw way to probe whether a type's serialization metadata is resolved. DO NOT USE when the target is earlier than net11.0, the requested behavior uses an established pre-net11 naming policy, or the user explicitly selected another JSON library.

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

Imperative guidance for the System.Text.Json APIs added in .NET 11: the built-in `JsonNamingPolicy.PascalCase` naming policy, and the strongly-typed generic `JsonSerializerOptions.GetTypeInfo` and `JsonSerializerOptions.TryGetTypeInfo` metadata accessors (generic overloads that return a typed `JsonTypeInfo`). USE ONLY when the user is targeting net11.0 or later and needs PascalCase JSON property or dictionary-key names without writing a custom naming policy, a strongly-typed generic `JsonTypeInfo` instead of the non-generic `JsonTypeInfo`, or a no-throw way to probe whether a type's serialization metadata is resolved. DO NOT USE when the target is earlier than net11.0, the requested behavior uses an established pre-net11 naming policy, or the user explicitly selected another JSON library.

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

What things get called. A file is named after its export in the project's case convention, a suffix is a resolution instruction rather than decoration, an index file only re-exports, and some symbol names are always wrong (utils, helpers, V2, Enhanced, New). Covers learning a tree's local vocabulary before adding to it, test and platform-variant naming, and the per-language conventions. Use when creating a file or directory, naming a test file, adding a platform variant, or when a name has to change. Triggers - "what should I call this file", "where does this file go", "naming convention", "kebab or camel", "name this test".

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

Next.js 16 이상에서 개발 서버 시작과 코드 변경 반영이 느린 원인을 살펴봅니다. Turbopack과 webpack의 선택, 캐시와 proxy.ts 명명도 확인합니다.

• 개발 서버 시작 지연을 조사할 때
• 코드 변경 반영이 느린 원인을 확인할 때
• Turbopack과 webpack을 선택할 때

Create project-specific rules for turning Figma designs into code. Bring design tokens, shared values such as colors and spacing, together with naming conventions and lint rules for automated checks in one reference.

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

• Defining rules for implementing Figma designs
• Documenting shared design values and naming conventions
• Consolidating automated checking rules in one reference

Audit CSS class names for inconsistency and ambiguity, then organize them using BEM, a convention that names components, their elements, and variations. Check the rendered interface across screen sizes and interaction states when reviewing changes.

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

• Auditing inconsistent CSS class names
• Renaming component classes using BEM
• Separating utility classes and JavaScript hooks

Design or improve what you sell by reviewing customer value, deliverables, bonuses, guarantees, deadlines, naming, and payment terms. Identify weak parts of a service, course, or coaching offer and draft specific changes to test.

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

• Package consulting services for sale
• Review course bonuses and guarantees
• Diagnose why an offer is not converting

Convert genomic positions between file conventions, standardize variant representations, and check reference genome or chromosome naming conflicts. The skill helps investigate one-base shifts and compare individual variants against a reference sequence before combining analysis files.

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

• Converting coordinates between BED and GFF/GTF
• Standardizing and comparing insertion or deletion records
• Checking reference genome and chromosome naming conflicts

Analyze an existing project's folders and produce a guide explaining directory purposes, naming conventions, and file placement. Choose a tree, list, or table, and optionally include templates for adding features consistently with the project's observed structure.

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

• Creating a folder guide for new team members
• Documenting naming and file placement conventions
• Preparing folder templates for new features

Generate five product name ideas based on brand values, target customers, and market positioning. Each suggestion includes its rationale, fit with the existing brand, memorability, and potential domain or trademark concerns.

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

• Name a new product or feature
• Explore names when rebranding
• Compare name options before launch

Audit game asset files for naming rules, size limits, formats, and broken references. Receive a report of measured violations and suggested fixes, with clear explanations of checks that lack data or cannot be assessed for the engine.

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

• Checking image and audio naming conventions
• Finding files that exceed asset size limits
• Investigating missing references and potentially unused assets

Apply Apache ShardingSphere’s written coding standards during implementation or review, covering naming, Java constructs, tests, and Maven dependencies. Also audit a specified scope without editing files, combining automated checks with manual inspection of applicable rules.

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

• Check changed code against written repository standards
• Review Java naming and declaration conventions
• Verify changed Maven dependency declarations

Design tools that agents can select and call correctly. Clarify descriptions, input rules, response formats, and recovery messages, then review overlapping tools and naming conventions using examples of successful and failed calls.

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

• Writing descriptions and input rules for new tools
• Investigating incorrect tool selection and calls
• Improving error messages with recovery steps

Use when the user asks to "codify our brand voice", "define naming rules for our products and tiers", or "write the tone-of-voice guide with banned phrases"; produces the brand-level voice canon (register, tone spectrum, banned-phrase list, few-shot examples drawn only from the brand's own published material) and the naming tax (product / feature / tier naming rules plus approved and banned terms) that seeds the narrative-registry canon and that every channel's voice adaptation points up to. Not for per-platform voice adaptation — use channel-registry's voice-dossier; not for finished copy or blog posts — use content-writer; not for the message hierarchy itself — use message-system-architect; not for claim adjudication — use offer-claims-registry. 品牌语气/词汇表/命名税/禁用词/品牌语言规范

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

Naming conventions, file structure, and coding standards for Angular projects. Use for Angular-specific naming and organization; defer language-only TypeScript naming questions.

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

The craft of creating and maintaining cohesive brand identity systems. Branding translates brand strategy into tangible visual and verbal identity—logos, color systems, typography, imagery, and voice guidelines that work together to make a brand recognizable and memorable. This skill covers logo design, visual identity systems, brand guidelines, naming, verbal identity, and brand application across touchpoints. Great branding is invisible when done right—it feels inevitable, as if the brand couldn't have looked any other way. Use when "logo, branding, brand identity, brand guidelines, visual identity, color palette, typography, brand book, naming, rebrand, brand refresh, brand system, branding, identity, logo, visual-design, guidelines, naming, typography, color" mentioned.

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

Use when refactoring code with poor names, when asked to improve naming, or when a user struggles to name a class/method/variable. Symptoms include -Manager/-Util suffixes, single-letter variables, process/handle/do verbs, primitive obsession, god methods with multiple responsibilities. Two modes — audit (broad scan, list opportunities) and improve (walk one specific identifier through the process).

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