'readability' 검색 결과

Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functions, comments, error handling, and class design.

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

Set dressing and environmental storytelling placement for interiors and exteriors using prop density, narrative clusters, and readability rules via MCP.

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

Art direction for racing and sports games in Blender with track landmarks, stadium kits, and high-speed readability.

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

Art direction for survival and survival-horror gameplay spaces in Blender emphasizing resource props, crafting readability, and tension routes.

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

Art direction for soulslike games in Blender with monumental melancholy spaces, fog gates, bonfire landmarks, and lethal readability.

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

Optimize content for search engines with keyword analysis, readability scoring, meta descriptions, and competitor comparison. Use this when users want to improve SEO, optimize blog posts, or analyze content for search performance.

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

Internal harness probe for the OI-3 readability-guidance spike. Use only when explicitly told to invoke spike-probe. Verifies that a freshly-created project skill renders into a subagent's context via the Skill tool.

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

OI-3 spike harness — the FORKED (context fork) readability-guidance variant. Same payload as the inline variant but declared to run in a forked context. Use only when a spike consumer skill invokes it.

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

OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

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

OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

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

OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

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

Surfaces Han's shared standard for explaining technical work to a reader who will not implement it into the calling skill's own context, so the caller writes its escalations, confirmation turns, and stops as a concrete outcome the reader could observe rather than as a mechanism. Use when a skill is about to ask a person a question, stop for an input, or explain a technical consequence to someone who will not open the code. Governs what a run says to a person in a turn, where readability-guidance governs the shape of a written deliverable. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Carries guidance only and adds no self-check step.

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

Publication-figure overlay for draw.io. Use instead of drawio whenever the diagram is for a paper, thesis, dissertation, journal, conference, IEEE/ACM submission, manuscript, camera-ready, Word/LaTeX figure, or other publication. Applies venue, figure-type, color, caption/legend, formula, and paper-readability gates for architecture, workflow, roadmap, network-topology, and replicated paper figures.

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

Optimize content for search engines with keyword analysis, readability scoring, meta descriptions, and competitor comparison. Use this when users want to improve SEO, optimize blog posts, or analyze content for search performance.

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

On-page SEO optimization techniques including keyword density, meta tags, heading structure, and readability. Use when optimizing existing content or validating new content against SEO requirements.

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

Restructure and improve Isabelle or Coq proofs to enhance readability, modularity, and maintainability without changing semantics. Use when proofs are long and monolithic, have repeated patterns, use unclear naming, lack documentation, or when the user asks to refactor, clean up, improve, or reorganize their formal proofs.

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

Reorganizes markdown documents into well-structured, consistent format while preserving content and improving readability. Use when Claude needs to: (1) Fix heading hierarchy issues (skipped levels, multiple h1s), (2) Generate or update table of contents, (3) Standardize formatting (lists, code blocks, emphasis, links), (4) Improve grammar and spelling, (5) Add missing standard sections (installation, usage, etc.), (6) Remove redundant or duplicate content, (7) Restructure technical docs, READMEs, or long-form content for better organization and flow.

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

Generates meaningful comments and documentation for code to improve maintenance and readability. Use when adding documentation to Python or Java code, including function/method docstrings, class documentation, inline explanations for complex logic, and code annotations (TODO, FIXME). Analyzes existing comment style in the codebase to match conventions. Produces clear, concise comments that explain the "why" not just the "what", following best practices for each language.

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

Suggest and apply code refactorings to improve readability, maintainability, and code quality. Use this skill when improving existing code structure, eliminating code smells, applying design patterns, simplifying complex logic, extracting duplicated code, renaming for clarity, or preparing code for new features. Provides specific before/after examples, explains benefits, identifies risks, and ensures behavior preservation through tests.

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

Improve typography by fixing font choices, hierarchy, sizing, weight consistency, and readability. Makes text feel intentional and polished.

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

Proofread and correct text for grammar, spelling, punctuation, style, clarity, and consistency, with support for multiple style guides and readability analysis. Use when the user requests proofreading or provides relevant inputs for this workflow.

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

Provider-independent title design and kinetic typography direction for video, animation, ads, explainers, social hooks, brand films, lyric/text videos, title cards, main titles, lower thirds, captions-as-design, and other motion-led text. Use when an agent must plan, prompt, implement, hand off, iterate, or QA typography hierarchy, readability, timing, reveal/hold/exit, motion semantics, line breaks, safe areas, localization, brand constraints, accessibility, flashing/motion safety, or production specs for animated text.

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

Provider-independent captions and media accessibility direction for AI agents producing or finishing generated videos, ads, social clips, explainers, avatar videos, documentaries, podcasts/video recuts, training media, and localized content. Use when planning, authoring, reviewing, localizing, burning in, exporting, or QAing captions, subtitles, SDH, transcripts, audio description, flashing/motion safety, caption readability, or accessible media handoff files.

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

Provider-independent workflow for producing terminal, IDE, documentation, browser, desktop, and application demonstration videos. Use when choosing authentic capture, browser automation, synthetic UI, or hybrid treatment; scripting actions and narration; resetting demo state; protecting secrets and personal data; directing cursor/callouts; creating crop variants; and reviewing workflow truth, readability, accessibility, and provenance.

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