'conventions' 검색 결과

MCP server documentation conventions for high-quality generated skills. Use when writing tool descriptions, `_meta` annotations, or input schemas for MCP extraction.

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

CLI documentation conventions for generated skills. Use when improving Commander descriptions, help text, positional argument docs, and config-surface correlation.

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

Add projections to collections to rename fields or map nested JSON paths to flat column names. Use when renaming fields for destination conventions, flattening nested paths to columns, or creating field aliases. Use when user says "rename field", "flatten nested JSON", "map JSON path to column", "field alias", or "projection".

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

Dart 3 modern features (through 3.10) and Effective Dart best practices including records, patterns, sealed classes, dot shorthands, null-aware collection elements, and wildcard variables. Use when adopting Dart 3.7+ syntax, using dot shorthands for enums or static members, using null-aware elements in lists or maps, using wildcard _ parameters, improving code quality, or reviewing Dart code conventions.

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

Guides test implementation following the test pyramid (75% unit, 20% integration, 5% E2E), Arrange-Act-Assert pattern, and project coverage thresholds (branches 70%, functions 80%, lines 80%, statements 80%). Covers test naming conventions, test independence, mock and stub patterns, test data management with fixtures and builders, and CI integration. Use when writing tests, reviewing test code, or setting up test infrastructure.

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

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re...

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

Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

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

Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.

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

Bootstrap a new Gradle module in any Kotlin Android project. Walks the user through choosing one of three module types — library module (`com.android.library`), feature module (regular Android library that hosts a feature/UI, install-time only), or dynamic feature module (`com.android.dynamic-feature`, on-demand/conditional/instant delivery). Use whenever the user wants to add a module, modularize code, extract a util/data/ui layer, create a new feature, set up Play Feature Delivery, or asks "should this be a library or feature module?". Discovers the project's existing conventions (plugin aliases, namespaces, sibling modules, version catalog) instead of hardcoding any. Pushes back on bad combos (e.g. utility code in a dynamic feature). Stops at scaffolding; app-level wiring is out of scope.

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

Use this skill for any Ionic Vue + Capacitor mobile work: Vue architecture, Composition API, TypeScript, state, env config, shared conventions. Required for every implementation task alongside mobile-testing.

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

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

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

Create well-formatted git commits following project conventions with emoji, type, and scope

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

Generates standard operating procedures for B2B SaaS marketing operations: campaign naming conventions, UTM governance, tool administration, workflow QA, data hygiene, lead routing, and incident response playbooks. Use when setting up or auditing marketing ops processes, onboarding a new marketing ops hire, standardizing campaign tracking, fixing broken lead routing, cleaning up HubSpot or CRM data, building QA checklists for campaign launches, or creating incident response procedures for marketing system failures. Also use when asked to "fix our UTM mess," "standardize campaign naming," "build a QA checklist," "audit our marketing ops," or "create an ops runbook." Designed for B2B SaaS marketing teams running HubSpot with multi-geo, multi-segment operations.

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

Remove AI writing patterns and enforce rigorous technical-prose conventions in Japanese. Derived from hardikpandya/stop-slop + k16shikano japanese-tech-writing. NEVER 33 + 論証と構成の規範 + 用語と register の自然さ + クイックチェック 28 + 5 軸スコアリング + 翻訳調 AI 語の検出を含む。Use when drafting, editing, or reviewing Japanese text to eliminate predictable AI tells and tighten argumentation.

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

Core Swift development workflows for Xcode and Swift tooling, including project setup, dependency management, concurrency guidance, language/runtime best practices, and troubleshooting build or package resolution issues. Use when working on Swift tasks across a codebase, especially package/tooling/runtime work and cross-cutting Swift conventions (mutation semantics, naming, enum/file rules, import hygiene), including in SwiftUI projects.

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

Write, review, or improve Swift APIs using Swift API Design Guidelines for naming, argument labels, documentation comments, terminology, and general conventions. Use when designing new APIs, refactoring existing interfaces, or reviewing API clarity and fluency.

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

Project code patterns and conventions. Auto-loads when implementing, designing, verifying, or reviewing code. Provides detailed pattern definitions with code examples.

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

Scaffold a new training recipe for the Tinker cookbook following repo conventions. Use when the user wants to create a new recipe, training script, or experiment.

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

Guide for testing conventions and CI pipelines — unit tests, integration smoke tests, pytest markers, and GitHub Actions workflows. Use when the user asks about testing, CI, running tests, or adding tests for a recipe.

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

Living project knowledge for OpenFoodJournal — an iOS 26 food journaling app with AI-powered nutrition scanning. Consult this skill FIRST when starting any work on this project. Contains architecture decisions, data models, service contracts, current state, known issues, and conventions. Update this skill whenever requirements, architecture, or project state changes so it stays accurate across sessions.

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

UI/UX design system and component patterns for OpenFoodJournal. Use when building new views, adding UI components, styling elements, presenting sheets, or modifying any view file. Contains the project's design tokens, component catalog, animation conventions, and layout patterns so new UI stays visually consistent with the existing app.

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

Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.

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

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

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

Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.

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