'casing' 검색 결과

Create or modify a konsistent.json configuration file that enforces structural conventions in a TypeScript codebase. Use when the user wants to enforce consistent code structure, validate exports/imports across files, ensure directories contain required files, enforce naming patterns, add/remove/update convention rules, configure case map overrides for acronyms or special casing (kebabToPascalMap, kebabToCamelMap), or troubleshoot why konsistent is reporting violations. Triggers on: "konsistent", "konsistent.json", "enforce conventions", "structural consistency", "consistent exports", "consistent structure", "code conventions config", "add convention", "update convention", "fix konsistent errors", "case map", "case override", "acronym casing".

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

Audit and improve stable names, aliases, vocabulary, field casing, routes, ports, packages, and agent-search discoverability.

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

Create and edit .pptx presentations with PptxGenJS, a library for building PowerPoint files. Use it for sales pitches, project kickoff briefs, and presentations that showcase a design system’s shared design rules.

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

• Creating a sales presentation
• Preparing a project kickoff brief
• Showcasing a design system

Prepare spreadsheet data for analysis by finding extra spaces, inconsistent capitalization, numbers stored as text, mixed date formats, and duplicates. Review proposed fixes, apply traceable formula-based changes, and compare results before and after cleanup.

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

• Cleaning spreadsheet data before analysis
• Standardizing dates and text capitalization
• Finding duplicate rows and mixed data types

Helps users get started with Onchain OS, find OKX.AI role registration guidance, or reach support resources. It identifies the purpose of a question and routes it to the appropriate guide.

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

• Getting started with Onchain OS
• Finding OKX.AI role registration guidance
• Finding support for bugs, complaints, or feedback

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.

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

TikTok Shop content creation strategy and planning. Trending formats, viral hooks, product showcasing, hashtag strategy, and content calendar development. Use when the user asks about TikTok content strategy, viral content creation, TikTok marketing, or content planning.

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

Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.

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

Framework for demonstrating AI capabilities in legal contexts. Provides detailed personas across tenant law, business contracts, startup disputes, employment claims, and consumer protection with progressive complexity scenarios. Use when: (1) Demonstrating AI-powered legal triage or intake systems, (2) Showcasing responsible AI-assisted client interactions, (3) Training staff on appropriate AI use in legal contexts, (4) Creating realistic scenarios for legal tech presentations, (5) Developing educational materials about AI in legal services, or (6) Testing AI-powered legal information systems in controlled environments.

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

Clean a local FF&E CSV schedule by normalizing casing, dimensions, units, language, materials, and formatting. Use when asked to clean, fix, or standardize product data.

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

Single-track / single-episode music-player mockup template — glassmorphic iOS-Music style player card with ambient album-art wash, for showcasing one song, one podcast episode, or one audio jingle as a shareable interactive surface.

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

Use when a carrier asks about tire program design, when to retread vs replace, position management (steer vs drive vs trailer), inflation pressure standards, casing management, scrub rates, road-call prevention, or vendor program selection (Bridgestone, Michelin, Continental, Goodyear). Covers 49 CFR 393.75 and DOT roadside out-of-service criteria.

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