247건 · 관련도순
Use when editing a draft, checking for AI voice patterns, reviewing prose quality, running readability analysis, auditing consistency, or validating SEO requirements on finished content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when website or web app UI work needs practical design guidance for hierarchy, layout, readability, responsiveness, and interaction quality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when existing copy needs tightening for clarity, accuracy, tone consistency, or executive readability without changing the underlying message.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for simplifying and refining code after coding sessions. Use when cleaning up complex code, reviewing PRs for readability, or applying consistent refactoring patterns. Triggers on simplify code, refactor, clean up, code review, コード整理, リファクタ, 複雑さ削減, コードレビュー.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a Duck Critic producer-critic loop: you (main) keep producing the plan/code/tests and gate your own work at checkpoints with a different-model critic, revising until it passes. Use when asked for rubber duck, ラバーダック, 別モデルレビュー, second opinion, critic, or a different-model code review, design review, plan critique, or review by another model/agent harness. Not for readability refactoring or code cleanup alone.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured code review discipline: correctness, design, readability, and security checks with actionable feedback. Use when reviewing diffs, PRs, or code snippets before merge or after writing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write readable, maintainable code: naming, small functions, clear control flow, and honest abstractions. Use when writing new code, refactoring, or reviewing for readability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing, redrawing, or validating research-paper figures and tables, including Matplotlib plots, LaTeX tables, benchmarks, captions, legends, annotations, color, and typography. Preserves exact evidence and checks rendered PDFs for clipping, overlap, and readability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform a direct five-axis code review across correctness, security, performance, readability, and maintainability. Use when the user asks for `/review`, PR review, security review, pre-merge review, production readiness review, or blocking issue assessment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform structured code reviews focusing on correctness, readability, security, and maintainability. Use this skill when reviewing pull requests, evaluating code changes, or establishing review standards for a team.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. This skill should be used after implementing features or bug fixes to clean up code, when refactoring for readability, or when reducing unnecessary complexity. It launches the code-simplifier subagent provided by the code-simplifier@claude-plugins-official plugin.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive SEO analysis for any website or business type. Orchestrates 52 sub-skills (52 active): full site audits, technical SEO (CWV/INP), schema, E-E-A-T content quality, images, sitemaps, GEO for AI Overviews, llms.txt generation, AI crawler audit, plus live GSC and Ahrefs MCP data. GSC: overview, drops, opportunities, brand-vs-nonbrand, cannibalization, compare, content-decay, index-issues, new-keywords. Ahrefs: overview, backlinks, keywords, competitors, content-gap, broken-links, new-links, anchor-analysis, dr-history, top-pages. Cross-MCP: serp, content-brief, brand-radar, site-audit-pro, report. Local: log-analysis, ai-content-check, internal-links, local, migration-check, obsidian-kb. AI Readability: llms-txt, robots-ai. Performance: lighthouse-audit, core-web-vitals, page-experience. Quality & AI Search: rich-results, ai-optimization, eeat-audit, helpful-content. Triggers on: "SEO", "audit", "schema", "Core Web Vitals", "sitemap", "E-E-A-T", "AI Overviews", "GEO", "technical SEO", "content quality", "structured data", "GSC", "Ahrefs", "backlinks", "keywords", "search console", "domain rating", "local SEO", "migration", "lighthouse", "pagespeed", "LCP", "INP", "CLS", "page experience", "interstitials", "mobile friendly", "rich results", "rich snippets", "schema eligibility", "AI optimization", "AI search readiness", "EEAT", "trust signals", "helpful content", "people-first", "content quality gate".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate, validate, or audit llms.txt files for AI search visibility. Crawls site structure, generates spec-compliant Markdown index for LLMs. Use when user says "llms.txt", "llm txt", "AI crawlers", "generate llms", "LLM file", "AI readability file".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Content quality and E-E-A-T analysis with AI citation readiness assessment. Enhanced with live Ahrefs (actual keyword rankings, positions) and GSC (search query performance) data to validate static E-E-A-T analysis with real user behavior. Use when user says "content quality", "E-E-A-T", "content analysis", "readability check", "thin content", or "content audit".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research-grounded workflow for designing, reviewing, and improving video game user interfaces, including HUDs, menus, navigation, focus states, onboarding/tutorials, objective tracking, input prompts, readability, accessibility, and destructive-action flows. Use when asked how to make good game UI, critique a game UI or HUD, propose UI/UX guidelines, design menu or gameplay interfaces, compare HUD vs diegetic/spatial presentation, create a UI design brief, or run a usability/accessibility review for PC, console, mobile, or VR games.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert any pile of documents (PDF, Word, HTML pages, wiki exports, PowerPoint slides) into clean, LLM-ready markdown context: inventories the sources, picks the right extractor per file type (pdftotext or PyMuPDF for PDF, pandoc or mammoth for docx, readability extraction for HTML.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluate page content for usefulness, E-E-A-T, readability, thinness, and AI citation readiness, plus last-mile draft cleanup (AI-typical phrasing and invisible Unicode watermark characters). Use for content-only analysis, not full-page technical checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create and manage writing personas with NNGroup 4-dimension tone framework (Funny-Serious, Formal-Casual, Respectful-Irreverent, Enthusiastic-Matter-of-fact). Personas define readability targets, sentence length distribution, vocabulary tier, contraction frequency, and summary box label. Used by blog-write and blog-rewrite to enforce consistent voice. Use when the user says "create persona", "use persona", "list personas", or wants tone sliders and writing rules saved as structured JSON. Not for measuring style from existing posts (blog-style) or for audience, positioning, and taboo-phrase context files (blog-brand).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform thorough code reviews with actionable, prioritized feedback. Use when a user asks to review code, check code quality, find bugs, review a pull request, audit code for issues, or get feedback on implementation. Covers correctness, security, performance, readability, and best practices across languages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Concise communication mode. Cuts ~60-70% of output tokens while keeping natural, readable English. Drops filler, hedging, and pleasantries but maintains grammar and sentence flow. Elaborate on request -- ask for detail and get it, then auto-return to concise. Use when user says "concise mode", "be concise", "less verbose", or invokes /concise. Also triggers when user requests token efficiency with readability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conducts multi-axis code review across correctness, readability, architecture, security, and performance. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Triggers on "review my PR", "review this diff", "code review", "review this changeset", "is this ready to merge", "pre-merge review".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use ONLY when the user explicitly says: 'use the skill web-to-markdown ...' (or 'use a skill web-to-markdown ...'). Converts webpage URLs to clean Markdown by calling the local web2md CLI (Puppeteer + Readability), suitable for JS-rendered pages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects and fixes color contrast violations using WCAG 2.1 guidelines and perceptual analysis. Expert in contrast ratio calculation, color blindness simulation, and providing accessible alternatives. Activate on "check contrast", "color accessibility", "WCAG audit", "readability check", "contrast ratio", "hard to read", "can't see text". NOT for general color theory (use color-theory-palette-harmony-expert), brand color selection (use web-design-expert), or non-visual accessibility (use ux-friction-analyzer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.