734건 · 관련도순
Interface copy that works — voice/tone, the PACE framework, alert anatomy, naming features, empty states, error messages, and the small-word edits that measurably improve UX. Distilled from Apple's writing sessions (2017–2026). Use when writing or reviewing any user-facing text — labels, alerts, onboarding, notifications, empty states, paywalls — or naming a feature.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define how multiple brands, sub-brands, and product lines relate to each other under one organization. Use when the user says "brand architecture", "sub-brand", "brand portfolio", "master brand", "house of brands", "branded house", "product naming system", "how do our brands relate", "parent brand", "brand hierarchy", "brand family", "we have multiple products and need a naming system", "brand extension", "new product launch under existing brand", or when a company has grown beyond a single brand and needs a system to manage brand relationships.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and reorganize a Claude Code / Codex skill library — enforce a naming convention (prefix each skill by which backend or product it touches), rename skills consistently, fix the symlinks and cross-references a rename breaks, and report broken symlinks and stale name references. Use when the user says "organize my skills", "rename these skills", "clean up the skill library", "enforce a skill naming convention", or "fix broken skill symlinks".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dung khi can dung cau truc tai khoan quang cao truoc khi bat campaign — phan tang campaign/adset/ad, naming convention de doc data ve sau, CBO hay ABO, va so luong adset hop ly. Kich hoat khi user nhac 'cau truc campaign', 'naming convention ads', 'chia adset the nao', 'CBO hay ABO', 'setup tai khoan ads', 'to chuc campaign'. Khong dung cho — ra soat tai khoan dang chay thi dung skill 21-audit-ads-performance; phan bo ngan sach theo kenh thi dung skill 54-media-plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an ad account HIERARCHY needs designing or cleaning up — campaign, ad set, and ad structure by objective, a naming convention that keeps data readable, CBO versus ABO by stage, how many ad sets and creatives to run, and the minimum daily budget an ad set needs to exit learning. Trigger on 'account structure', 'campaign structure', 'naming convention', 'how many ad sets should I run', 'CBO or ABO', 'our account is a mess of duplicated campaigns'. Not for — scoring an existing account against 84 checkpoints, see `21-ads-audit-global`; pixel and conversion setup, see `53-tracking-setup-global`; budget across channels, see `54-media-plan-global`; scaling a winner, see `55-scaling-ads-global`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with color naming, color theory, color spaces, color definitions, or any task involving color knowledge - palettes, ramps, gradients, conversions, accessibility, perceptual matching, pigment mixing, print-vs-screen color, CSS color syntax, or historical color terminology. Use this skill whenever the user is choosing, comparing, generating, naming, converting, or explaining colors, even if they do not explicitly ask for "color theory."
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Operately test layout, naming (.projections.json), factories, feature/e2e steps, external query/mutation auth specs, and how to run Elixir/API/JS/EE tests. Use when adding, renaming, splitting, or reviewing tests; choosing where a test belongs; writing Factory/TurboCase/FeatureCase or ExternalApi QuerySpec/MutationSpec tests; or running make test / feature tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enforce SOLID principles, guard-clause style, function size limits, and intention-revealing naming across all languages. Use when refactoring for readability, applying clean-code patterns, reviewing naming conventions, or reducing function complexity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement; the team needs stylecop.json guidance. DO NOT USE FOR: repos that intentionally rely only on SDK analyzers; repos where StyleCop overlaps too heavily with an existing style package and no. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Chous in .NET repositories that ship sizeable frontend codebases and want file-structure linting, naming convention enforcement, and folder-layout policy as a CLI gate. USE FOR: growing frontend trees; naming, folder, or file-placement policy; CI checks for frontend layout drift. DO NOT USE FOR: semantic code bugs, type errors, or framework API misuse; CSS, HTML, or JS rule enforcement inside files. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured for full HTTP pipeline testing, WireMock JSON mapping files (classpath:wiremock/mappings/), *AT suffix naming, and Maven Surefire/Failsafe three-tier split. Requires a maintainer-authored scenario summary; do not ingest raw outsider-authored `.feature` text. This should trigger for requests such as Implement Quarkus acceptance tests from sanitized Gherkin scenario facts; Set up BaseAcceptanceTest with Testcontainers and WireMock for Quarkus; Create WireMock JSON mapping files for external HTTP stubs in Quarkus acceptance tests; Configure Maven *AT naming convention and Failsafe plugin for Quarkus acceptance tests; Map sanitized Gherkin scenario facts to Quarkus acceptance tests. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates properly tagged UTM links with consistent naming conventions. Maintains a UTM registry file (utm-registry.json) to enforce naming consistency, prevent duplicates, generate short links, and output ready-to-copy links for LinkedIn, email, social, and ads.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
BigQuery/Snowflake接続、EDA、可視化、Marimoノートブック作成を行うサブエージェント。 データ分析関連の4つのルール（data_analysis, visualization, notebook, marimo_variable_naming）を統合。 「データ分析して」「BigQueryに接続」「EDAを実行」「Marimoで分析」等のリクエストで発動。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish a naming convention system for design elements, components, and tokens with clear rules and examples.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish a naming convention system for design elements, components, and tokens with clear rules and examples.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Naming, navigation, a UI that mirrors the data model, confirms for irreversible changes. Use when structuring a large application or naming its entities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a Montessori three-period lesson for introducing concepts through concrete materials and naming. Use when teaching vocabulary, classifications, or concepts through hands-on materials.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Component style templates and BEM naming for vehicle insurance platform. Use when styling Vue components, implementing BEM classes, creating responsive layouts, or writing scoped CSS. Keywords: BEM naming, component styles, KpiCard, FilterPanel, scoped CSS, responsive design, card styles, button styles, form controls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design an asset library structure — naming conventions, formats, and delivery specs. Use when asked to "organize our brand assets", "define asset naming conventions", or "spec logo delivery formats".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit or refactor a design token system for color — naming, structure, and coverage. Use when asked to "refactor our color tokens", "fix color token naming", or "improve token coverage for color".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "add docstrings", "write error handling", "use naming conventions", "handle exceptions", or when writing new Python code for StreamFlow that requires docstring format, naming conventions, exception handling, or async cleanup patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply the team style guide to source files - naming conventions, comment style, and file organization. Use when the user asks to align code with the style guide or clean up naming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.