'naming' 검색 결과

アプリ名・サービス名の命名を、5つの専門エージェントチームで多角的に評価・決定するスキル。 ブランディング、商標/法的リスク、デジタルプレゼンス(SEO/ASO/SNS)、国際展開(多言語/発音)の 4観点から候補を提案・調査・議論し、コンテキストファイルと議事録で次回セッションへ引き継ぐ。 Use when: アプリ名を決めたい、サービス名を変更したい、プロダクト名を検討したい、 ネーミングブレスト、名前の商標チェック、アプリ名のリネーム。 Triggers: "アプリ名", "サービス名", "プロダクト名", "ネーミング", "名前を決め", "リネーム", "rename", "app name", "naming", "ブランド名", "商標チェック"

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

Use this skill to configure and manage NPSP Household Accounts: household naming rules, formal/informal greeting formats, primary contact designation, household merges, and household splits. Trigger keywords: NPSP household naming, household account not updating, merge duplicate households NPSP, household greeting customization, primary affiliation NPSP. NOT for FSC (Financial Services Cloud) households — use admin/household-model-configuration. NOT for bulk-loading constituents and households into NPSP — use data/constituent-data-migration.

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

Refactor code by renaming variables, methods, classes, and concepts for clearer intent. Use when asked to improve names, clarify naming, perform a naming pass, or run `/refactor:names`.

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

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. 品牌语气/词汇表/命名税/禁用词/品牌语言规范

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

Ensure tests use clear naming and cover edge cases with proper describe/it structure.

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

有馬記念分析システムの命名ドメイン適合性レビュー。関数名・変数名・型名が競馬ドメインの意図（馬・騎手・調教師・血統・レース・出走・着順・上がり3F・馬場・会場・枠順・ローテ）を表現しているか、汎用名・技術接尾辞・命名規則の逸脱（snake_case 混入・アンダースコア付きメソッド名）・同一概念に別名が混在していないか（venue と course、同名異義の型）を検証。Use when user says '命名レビュー', 'review naming', '名前チェック', or 'ドメイン命名確認'.

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

기존 코드에 담긴 암묵적인 명명, 구성, 오류 처리 관례를 읽어 AI가 참고할 규칙으로 정리합니다. 방침의 충돌을 하나씩 확인하고 코드 변경 후 규칙 갱신도 지원합니다.

• 오래된 코드베이스에 AI를 도입할 때
• 암묵적인 코딩 규약을 문서화할 때
• 명명과 구성 방침의 충돌을 정리할 때

Spring Boot와 Quarkus의 Java 코드를 명명, 불변 데이터, 예외 처리, 프로젝트 구조와 테스트 규약에 따라 작성하고 검토합니다. 빌드 파일로 프레임워크를 판별합니다.

• Java 코드의 규약 준수 검토
• Optional과 streams 사용 확인
• 패키지와 프로젝트 구조 정리

공통 기준으로 코드의 명명, 가독성, 원본 데이터를 바꾸지 않는 갱신 방식과 오류 처리를 검토합니다. 중복과 복잡한 구조를 찾아 유지보수하기 쉽게 정리합니다.

• 기존 코드의 명명과 가독성 검토
• 긴 함수와 깊은 조건 분기 정리
• 새 모듈의 코딩 규칙 통일

Plan the retirement of old APIs, features, and systems, then move their users to replacements in stages. The skill also guides database schema changes through additive steps that keep old and new application code compatible during rollout.

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

• Moving users from an old API to its replacement
• Planning the retirement of an unused feature
• Renaming production database columns in stages

Supports palette creation and contrast checks using color science references. It also covers color naming, pigment mixing, and historical color theory, helping you explore color choices for design and creative work.

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

• Creating a palette for a design
• Checking text and background contrast
• Choosing names for colors

Review pending database migration SQL before applying schema changes. Check references between tables, rollback coverage, required defaults, destructive operations, and naming conventions, then report errors, warnings, and suggestions with file paths and line numbers.

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

• Reviewing database migrations before applying them
• Checking foreign key targets and migration order
• Checking rollback SQL for missing operations

Guides code cleanup and restructuring by mapping dependencies, assessing test coverage, and planning small changes. Supports tasks such as extracting functions or renaming symbols, with checks after each step and recovery when verification fails.

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

• Extracting validation logic into a separate module
• Renaming symbols across related files
• Simplifying conditionals and repeated patterns

Set consistent Python conventions for naming, formatting, type checking, and documentation. Configure ruff and mypy or pyright, write clear function descriptions, and organize README and changelog content so a team can maintain shared standards.

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

• Set up Python linting and formatting
• Define shared team coding conventions
• Review type hints and function documentation

Prepare repository contributions by checking existing guidelines, related issues, branch naming rules, commit formats, and pull request templates. Organize changes into logical commits and assemble submissions that follow the project's documented contribution process.

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

• Preparing issues using repository templates
• Creating branches with the required naming format
• Grouping changes into clear commits

Create and check Git branch names using Conventional Branch rules. Choose a prefix for the task, normalize the description, detect the repository’s base branch, and create and switch to the new branch.

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

• Create a branch for a new feature or bug fix
• Check whether a branch name follows naming rules
• Include an issue number in a branch name

Keeps CopilotKit documentation aligned with released Inspector panels, the views shown in its local web overlay. It updates reader guidance and panel mappings when panels change, and checks quickstart instructions against supported platforms.

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

• Add documentation guidance for a released Inspector panel
• Update documentation after renaming or removing a panel
• Check Inspector instructions in web quickstarts

Keeps customer-facing CopilotKit Intelligence documentation consistent by applying an approved vocabulary to prose, navigation, buttons, and image descriptions. Checks disallowed alternatives and exceptions while preserving code identifiers and the labels users actually see in product controls.

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

• Standardizing terminology in customer documentation
• Reviewing navigation and button labels
• Checking terminology in image descriptions

Prepare a new month of tracking in Google Sheets by copying a template tab within the same spreadsheet and renaming the copy for the month you want to record.

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

• Preparing a tracking tab for a new month
• Reusing the same template each month
• Copying a template and naming it for the target month

Build reusable parts for n8n workflows instead of copying shared logic. This skill guides typed inputs, consistent outputs, naming, and execution settings so workflows and AI agents can call the same processing steps.

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

• Sharing common logic across workflows
• Splitting a large workflow into reusable parts
• Exposing shared processing as an AI agent tool

Guide changes to the published @kortix/sdk package with rules for preserving public APIs, writing failing tests before behavior changes, keeping the core independent of frameworks, and checking package installation. It also covers exports, streaming transport, and release version handling.

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

• Adding a public SDK feature or export
• Renaming public types while preserving compatibility
• Changing streaming or transport behavior

Create and maintain LifeOS skills, from initial file structure to validation and effectiveness testing. Update workflows, improve instructions, and refine descriptions so skills activate for appropriate requests, while checking naming conventions and handling of personal data.

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

• Creating a new LifeOS skill
• Adding workflows or tools to an existing skill
• Checking and correcting skill structure

Build reusable parts for n8n workflows instead of copying shared logic. This skill guides typed inputs, consistent outputs, naming, and execution settings so workflows and AI agents can call the same processing steps.

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

• Sharing common logic across workflows
• Splitting a large workflow into reusable parts
• Exposing shared processing as an AI agent tool

Check code for complex logic, duplication, naming issues, and oversized functions. Get a quality report with file locations and severity levels, plus guidance on splitting complex code and extracting shared logic during reviews or after refactoring.

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

• Checking code quality before a commit
• Reviewing code after refactoring
• Finding complex functions and duplicated code