「clarity」の検索結果

Improve image quality by enhancing resolution, sharpness, and clarity. Perfect for screenshots, documentation, presentations, and social media images.

日本語の概要は準備中です。原文の説明を表示しています。

Use when refining a draft user prompt before sending it to a coding agent. Decomposes goal/context/constraints/acceptance/output-format, detects ambiguity and model-coupled framing, then emits a model-agnostic rewrite. Supports --analyze, --score, and --deep. NOT for prompts from scratch (mk:brainstorming), plans/reviews (mk:elicit), implementation plans (mk:plan-creator), or general codebase scouting (mk:scout).

日本語の概要は準備中です。原文の説明を表示しています。

Pre-routing ambiguity analysis — scores request clarity and asks clarifying questions when needed (inspired by ouroboros)

日本語の概要は準備中です。原文の説明を表示しています。

Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.

日本語の概要は準備中です。原文の説明を表示しています。

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.

日本語の概要は準備中です。原文の説明を表示しています。

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.

日本語の概要は準備中です。原文の説明を表示しています。

[Code Quality] Use when you need to simplify and refine code for clarity, consistency, and maintainability while preserving all functionality.

日本語の概要は準備中です。原文の説明を表示しています。

Establish or audit a structural quality contract for any agent-operated engineering repository: app, library, CLI/tool, plugin, harness, or meta repo. Use when a repo needs charter clarity, docs/decision ownership, type-native validation gates, evidence paths, safe action policy, cold-start legibility, maturity proof, repair-loop routing, consumer/producer owner-boundary routing, command surface evolution, evolutionary simplicity (see references/evolutionary-simplicity.md), or a repo ecology pass to decide what should be compressed, merged, removed, updated, created, retired, or moved to checks.

日本語の概要は準備中です。原文の説明を表示しています。

Writing quality guidelines, formatting conventions, and styling constraints for documentation. Trigger when: - Writing, editing, or auditing documentation files, READMEs, markdown files, or guides. - Modifying files with suffixes like: *.md, *.qmd, *.txt, *.rst. - Prompt contains keywords: doc, documentation, spelling, grammar, headers, links, table alignment, Divio, tone, voice, clarity.

日本語の概要は準備中です。原文の説明を表示しています。

Research and stress-test open-source project names, from collision checks to launch-ready decisions. Use when the user asks to name or rename a project, compare candidate names, screen GitHub or package namespace risk, verify language or mythology claims, or improve SEO/GEO clarity. Perform live web and registry research, separate brand from category descriptor, classify collisions, and return one evidence-backed recommendation.

日本語の概要は準備中です。原文の説明を表示しています。

Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.

日本語の概要は準備中です。原文の説明を表示しています。

Generate custom quality checklists for validating requirements completeness and clarity. Use to create unit tests for English that ensure spec quality before implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Review product designs before engineering handoff or release for flow and state coverage, business-rule alignment, implementation clarity, accessibility, responsiveness, analytics, and testability.

日本語の概要は準備中です。原文の説明を表示しています。

Review meeting minutes documents for completeness, action item clarity, decision documentation, and consistency with source materials like hearing sheets. Use when validating meeting minutes quality or preparing minutes for distribution.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when you need to review presentation materials from an audience perspective to improve their quality and effectiveness. Evaluates content clarity, visual design, logical flow, engagement factors, and Marp technical compatibility. Triggers include "review my presentation", "check my slides", "presentation feedback", or when a user has completed a draft presentation and wants comprehensive quality review.

日本語の概要は準備中です。原文の説明を表示しています。

Refactor test files to improve behavioral coverage, clarity, structure, assertions, fixture setup, mocking strategy, and remove implementation-detail or low-value tests. Use when asked to clean up, declutter, consolidate, or improve tests.

日本語の概要は準備中です。原文の説明を表示しています。

Audit code quality focusing on deep modules, naming, model hygiene, and architectural clarity. Use after a burst of development, when codebase structure needs assessment, or to make code more agent-navigable.

日本語の概要は準備中です。原文の説明を表示しています。

Pre-ingestion verification for epistemic quality in RAG systems with 9-point verification and Two-Round HITL workflow

日本語の概要は準備中です。原文の説明を表示しています。

Improve the clarity and voice of AI-assisted academic writing (papers, theses, rebuttals) and

日本語の概要は準備中です。原文の説明を表示しています。

Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Write, review, or improve Swift APIs using Swift API Design Guidelines for naming, argument labels, documentation comments, terminology, and general conventions. Use when designing new APIs, refactoring existing interfaces, or reviewing API clarity and fluency.

日本語の概要は準備中です。原文の説明を表示しています。

Review code for readability, then simplify it to be easy to follow and understand. Use this skill when the user wants to simplify code, improve readability, clean up for handoff, make code skimmable, reduce complexity, refactor for clarity, strip boilerplate, prepare code for future maintainers, or make a codebase easier to pick up. Trigger liberally — any request touching readability, simplification, cleanup, or "make this easier to understand" should use this skill. Also trigger when the user says things like "review this", "clean this up", "tidy this", "make this simpler", "reduce complexity", "flatten this", "strip the noise", or "I want to understand this code quickly next time I open it".

日本語の概要は準備中です。原文の説明を表示しています。

Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".

日本語の概要は準備中です。原文の説明を表示しています。