244건 · 관련도순
Builds frosted-glass interface components using translucent backgrounds, background blur, subtle borders, and soft shadows. Provides shared CSS settings and examples for consistent cards, navigation bars, modals, and buttons, with guidance on readability and browser support.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare scientific figures for papers, reports, and saved deliverables by checking data fidelity, chart choice, labels, axes, and color consistency. Verify exported figures for overlapping text and readability while keeping fonts, palettes, and framing configurable.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Pre-publication quality gate for authored Markdown — heading structure, on-disk link resolution, readability, accessibility, terminology. Use when reviewing docs before publishing, wiring a docs CI gate, or auditing a Markdown corpus.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audits a legal document against legal design principles. Scores the document on six pillars: language patterns (bureaucratese, archaisms, passive voice, nominalization), readability (Flesch Reading Ease and language-specific equivalents), structure and navigation, hidden conditions (material obligations buried away from their headings), statutory duplication (restating the law instead of citing it), and visual hierarchy where layout is available. Assessment-only; does not rewrite the document. Works on English, French, and German documents, inferring the applicable jurisdiction from the document's language and textual signals: governing-law clause, statute citations, party addresses. Use when a user shares a legal document (contract, NDA, T&C, privacy policy, internal policy) asking how good the drafting is from a legal design perspective, whether it is readable, whether it contains buried clauses or restates the law, or how it scores on Flesch / LIX / Amstad / Kandel-Moles readability metrics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need framework-agnostic SQL guidance — schema naming, relational table design, query readability, indexes, transactions, database security, migrations, testing, and monitoring — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Review SQL schema or migrations; Improve SQL query performance and readability; Design relational tables and indexes; Review database transaction, security, or monitoring practices. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OI-3 spike harness — the INLINE (non-forked) readability-guidance variant. Surfaces the shared readability standard into the calling skill's own context. Use only when a spike consumer skill invokes it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates and maintains project documentation for features, systems, and components. Use when documenting how a feature, system, or component works — including writing, updating, or organizing docs. Does not scan or detect the project's technology stack — use project-discovery for repository analysis and config detection. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not create or update coding standards — use coding-standard instead. Does not generate PR descriptions — use update-pr-description for that. Does not produce runbooks for operational scenarios — use runbook for that. Does not rewrite existing prose for readability — use edit-for-readability for that. Does not produce an ephemeral, understand-now overview of code or a PR — use code-overview for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Makes working code easier to read and change without altering what it does, and proves the behaviour stayed the same. Use when someone says "simplify this", "clean up this function", "this file is a mess", "reduce the complexity", "refactor for readability", "tidy my diff before the PR", or when a linter reports high cyclomatic complexity or deep nesting. Covers pinning current behaviour with characterization tests, measuring complexity, choosing a named refactoring, applying it in small verified steps, and reporting suspected bugs found on the way instead of fixing them silently.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes and optimizes content readability using Flesch-Kincaid scoring, Hemingway Editor API integration, and Grammarly Text API. Generates SEO-optimized rewrites targeting specific grade levels.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve UI typography by fixing font choices, type scale, hierarchy, weight, and readability so text feels intentional. Use when the user mentions fonts, typography, type scale, readability, text hierarchy, or sizing that feels off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when analyzing published content (blog posts, social media, newsletters) for sentiment, structural quality, hook effectiveness, readability, topic classification, and engagement correlation. Invoke for daily post analysis, content audits, or engagement driver identification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Two-phase code quality skill: (1) review codebase for structural smells — file LOC, method LOC, accidental complexity, test readability — producing a structured report, then (2) fix all smells via provable refactorings with ACN micro commits and green-bar-at-all-times discipline. Use this skill when the user says 'sweep', 'code review', 'find code smells', 'check method lengths', 'review for complexity', 'tidy up the codebase', 'refactor smells', or asks about long methods, test readability, or accidental complexity. Also trigger when users ask to 'clean up' or 'improve code quality' across multiple files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve UI typography by fixing font choices, type scale, hierarchy, weight, and readability so text feels intentional. Use when the user mentions fonts, typography, type scale, readability, text hierarchy, or sizing that feels off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Google-grade software engineering culture encompassing Code Readability, Design Doc Review, Blameless Postmortem, Testing Philosophy, Code Review standards, and engineering excellence practices distilled from Google's internal engineering culture documented in "Software Engineering at Google" and real Google/Brain/DeepMind experience. USE WHEN: establishing engineering standards, reviewing code quality, designing development workflows, onboarding engineers, setting code review guidelines, adopting Google-level engineering excellence, or building an engineering culture that promotes maintainability, readability, and quality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test naming conventions and best practices specialized skill. Used when naming test methods, improving test readability, and establishing naming standards. Covers three-part naming method, Chinese naming recommendations, test class naming, etc. Keywords: test naming, test naming, naming conventions, naming conventions, three-part naming, three-part naming, method_scenario_expected, method_scenario_expected, how to name tests, test readability, naming best practices, test report, test documentation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
변수와 함수 이름, 가독성, 데이터 갱신, 오류 처리를 공통 기준으로 검토합니다. 새 개발과 코드 리뷰에서 유지보수하기 쉬운 작성 방식을 맞춥니다.
Python 코드 작성과 검토에서 PEP 8, 타입 힌트, 예외 처리와 패키지 구성을 정리합니다. 가독성, 유지보수성, 메모리 효율을 고려한 개선을 돕습니다.