'clarity' 검색 결과

Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.

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

AI 에이전트가 정확성·완전성·명확성·실행 가능성·간결성의 다섯 기준으로 결과물을 자체 평가합니다. 근거가 있는 점수와 평균, 우선순위별 개선안을 제공합니다.

• 여러 파일에 걸친 구현 후 자체 평가
• 여러 작업 단계를 마친 결과물 점검
• 설계 문서와 분석 보고서 평가

Make working code easier to read and maintain while preserving its behavior. The skill identifies tangled conditions, unclear names, duplication, and unnecessary abstractions, then guides small refactoring steps checked against existing tests and project conventions.

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

• Improving readability after a feature is working
• Addressing complexity raised in code review
• Untangling nested conditions and long functions

Improve the resolution, sharpness, and clarity of images and screenshots used in presentations and documentation. This catalogue entry helps agents discover the skill; running the full workflow requires installing the upstream bundle.

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

• Improving images for presentation slides
• Making documentation screenshots clearer
• Increasing image resolution

Improve emails, blog posts, technical documents, and creative prose while preserving the author's voice. Get revised wording with explanations, plus guidance on grammar, structure, and clarity suited to the intended audience and format.

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

• Making an email easier to understand
• Improving a blog post's structure
• Clarifying technical documentation

Get structured feedback on a legal memo, brief, paper, or exam essay without having it rewritten. Review organization, reasoning, clarity, and citation form, with three prioritized improvements and a record of recurring writing patterns.

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

• Reviewing the structure of a legal memo
• Checking how rules connect to facts and counterarguments
• Prioritizing improvements before revising a draft

Golang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See `samber/cc-skills-golang@golang-naming` skill), linter configuration (→ See `samber/cc-skills-golang@golang-lint` skill), or doc comments (→ See `samber/cc-skills-golang@golang-documentation` skill).

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

Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.

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

Use when revising an AISTATS paper for concise AI-statistics framing, theorem-and-experiment clarity, 8-page two-column compression, double-blind wording, reproducibility clarity, statistically careful claims, and assumption-labeling discipline that survives statistician reviewers.

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

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.

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

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

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

Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal. Use this skill whenever the user wants to write an article, draft website copy, edit existing content for clarity or voice, write a blog post, or produce general editorial content. Triggers on write a blog post, draft an article, write copy for, edit this, rewrite this, write content, write a guide, draft a how-to, write web copy. Also triggers when content has been outlined and now needs to be written, or when existing content needs voice or clarity edits.

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

Reviews pitch decks and investor presentations. Reads slide content, evaluates narrative flow, problem/solution clarity, market sizing, competitive positioning, financial projections, team credibility, and ask clarity. Generates a scored pitch-review.md with slide-by-slide feedback, overall score, top improvements, investor objection predictions, and comparisons to successful decks. Use when reviewing fundraising materials, investor decks, or pitch presentations.

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

Draft, rewrite, or review reader-facing prose so it is specific, useful, and recognizably the author's without inventing facts or performing humanness. Use for essays, articles, newsletters, documentation, talks, launch copy, and other important prose that feels generic, hollow, or AI-shaped. Supports co-write, rewrite, review, and lint modes.

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

World-class copywriting expertise combining the persuasive clarity of David Ogilvy, the conversational warmth of Ann Handley, and the conversion science of modern growth marketers. Copywriting is where brand voice becomes words that move people. Great copy doesn't just communicate—it persuades, connects, and converts. The best copywriters understand that every word earns its place, that benefits beat features, that clarity trumps cleverness, and that the reader's problem is the only starting point that matters. Use when "copywriting, write copy, headlines, taglines, email copy, ad copy, landing page copy, product copy, UX writing, CTAs, value proposition, microcopy, sales copy, conversion copy, writing, copy, headlines, conversion, persuasion, messaging, UX-writing, emails" mentioned.

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

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

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

Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.

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

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

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

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

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

日本語の文書を、読み手が見つけ・理解し・使えるように、新規に書く、書き直す、添削する、評価する。レポート、提案書、手順書、設計書、メール、社内文書、AI生成文が対象。「分かりやすく書いて」「手順書を書いて」「書き直して」「読みやすくして」「添削して」「分かりにくい所を教えて」「点数をつけて」「やさしい日本語にして」「ASD-STE100の日本語版のように」などの依頼で、標準名を挙げていなくても使う。Use when writing, rewriting, proofreading, or scoring Japanese prose for clarity and plain language.

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

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

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

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

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

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

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

Rewrite AEM Edge Delivery Services page content for AI search discoverability (GEO — Generative Engine Optimization). Analyzes content structure, semantic clarity, and factual density, then produces optimized rewrites that rank in both traditional search and AI-powered search engines. Use when optimizing pages for search visibility, AI discoverability, or content clarity.

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