'naming' 검색 결과

Facilitate idea generation sessions that actually produce diverse, useful options instead of degenerating into the first plausible answer. Use for product ideation, feature exploration, problem-reframing, naming, design alternatives, strategic option-generation, or any task where the failure mode is "we picked the obvious thing too fast." Covers solo and group sessions, divergence/convergence discipline, technique selection (SCAMPER, Crazy Eights, How Might We, 6-3-5 Brainwriting, Reverse Brainstorming, Worst Possible Idea, Random Stimulus), facilitation moves for handling dominant voices and groupthink, and structured convergence to a shortlist with rationale. Outputs a session artifact with options generated, evaluation, shortlist, and the rejected-but-interesting list.

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

Next.js route metadata, per-route favicons, OpenGraph, and Twitter cards. Use when adding a route or layout, adding a favicon or social share image, auditing missing metadata, naming tab titles, or touching createRouteMetadata, createDynamicRouteMetadata, generateFaviconMetadata, or titlePrefix.

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

Entry point and shared rules for structural changes to the live Matrx database. Use before any DDL: dropping, merging, or renaming a table, changing a function, RPC, trigger, or policy, hunting straggler tables, or starting a deprecated, schema move, or canonicalization (it routes to those skills).

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

Keeps a fiction story bible and checks text against it. Trigger to build, extend or extract (from a manuscript) a story, lore or world bible; to check chapters, game strings or generated drafts for contradictions or timeline breaks; to track a world timeline with branches and who is alive, or chart it; to brief a local model from canon; for naming rules; to share canon across repos; or say lorescribe (bible, manuscript, check, timeline, names, brief, audit). Research is researchscribe's; line edits commscribe's; real-data charts dataviz's; art pixelsmith's; audio soundsmith's; model runs lmstudiorunner's or comfyrunner's; no prose drafting.

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

Testing knowledge base for PHP 8.5 projects. Provides testing pyramid, AAA pattern, naming conventions, isolation principles, DDD testing guidelines, and PHPUnit patterns.

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

Generates PHPUnit unit tests for PHP 8.5. Creates isolated tests with AAA pattern, proper naming, attributes, and one behavior per test. Supports Value Objects, Entities, Services.

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

Generates DDD Domain Events for PHP 8.5. Creates immutable event records with metadata, past-tense naming. Includes unit tests.

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

[71] CLOSE. Quick, safe cleanup after completing a milestone. Fix objective issues only (syntax errors, dead code, poor naming). Must be <5% of main task time, <30 seconds per fix, and reversible. Use after key points, not after every small change.

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

Java coding standards for Spring Boot services: naming, immutability, Optional usage, streams, exceptions, generics, and project layout.

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

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

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

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

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

Normalizes GitHub issue and PR titles by removing any bracketed [NemoClaw] tag case-insensitively, even when the tag appears later in the title. Use when cleaning issue tags, bulk-renaming titles, or normalizing repo title hygiene.

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

根据用户指定的长度、领域（如机械、影视灯光）、稀有度及风格要求，生成品牌名或产品名。支持中英文命名，提供详细的创意释义。

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

Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.

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

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

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

Power BI semantic modeling assistant for building optimized data models. Use when working with Power BI semantic models, creating measures, designing star schemas, configuring relationships, implementing RLS, or optimizing model performance. Triggers on queries about DAX calculations, table relationships, dimension/fact table design, naming conventions, model documentation, cardinality, cross-filter direction, calculation groups, and data model best practices. Always connects to the active model first using power-bi-modeling MCP tools to understand the data structure before providing guidance.

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

Comprehensive technology-agnostic prompt for analyzing and documenting project folder structures. Auto-detects project types (.NET, Java, React, Angular, Python, Node.js, Flutter), generates detailed blueprints with visualization options, naming conventions, file placement patterns, and extension templates for maintaining consistent code organization across diverse technology stacks.

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

Best practices for git workflow automation including atomic commits, branch naming, conventional commit format, and changelog generation.

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

Scaffold course exercise directories with numbered sections, exercise variants, required readmes, and repo-specific validation. Use when creating exercise stubs, adding a course section, or safely renaming exercises.

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

.NET testing fundamentals overview and navigation center. Triggered when users ask about "how to write .NET tests", ".NET testing getting started", "required testing tools", "testing best practices", "learn testing from scratch", and other general testing needs. Recommends appropriate sub-skills based on specific requirements, covering testing fundamentals, test data, assertions, mocking, special scenarios, and other 19 fundamental skills. Keywords: dotnet testing, .NET testing, testing getting started, how to write tests, testing best practices, unit test, unit test, xunit, 3A pattern, FIRST principle, assertion, assertion, mock, stub, NSubstitute, test data, AutoFixture, Bogus, validator, FluentValidation, TimeProvider, IFileSystem, code coverage, ITestOutputHelper, test naming

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

Designs public .NET APIs. Naming, parameter ordering, return types, error patterns, extensions.

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

Defines baseline C# conventions loaded first -- naming, file layout, style rules.

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

Git commit and pull request conventions. USE FOR: writing commit messages; checking Conventional Commits and gitmoji; branch naming; rebase workflow on develop; PR titles and target branch. PRIORITY: this skill overrides other rules when creating commits/PRs. DO NOT USE FOR: code implementation (use code-implementation skill); testing (use test-writing skill); general documentation (use documentation skill).

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

Audit images across AEM Edge Delivery Services pages for SEO and performance. Checks alt text quality, missing dimensions, lazy loading on LCP images, fetch priority, file naming, and decorative image handling. Generates a per-page report with specific fix instructions for alt text (in the source document) and performance attributes (in block code or scripts). Use when optimizing Core Web Vitals, improving image accessibility, or auditing image SEO.

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