「polish」の検索結果

Run the repo's lint, format-check and test suite, then fix anything that fails. Use before opening a PR or when asked to "polish" or "clean up" the repo.

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

Use for Korean prose polishing. Triggers: Korean polish, proofread Korean, 윤문, 다듬어, 다듬어줘, 자연스럽게, 매끄럽게, 교정, 고쳐줘, AI투, 번역투.

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

Final quality pass fixing alignment, spacing, consistency, interaction states, and micro-details before shipping. Executes changes (unlike design-audit and design-critique which are report-only). Triggers on polish, finishing touches, final pass, something looks off, pre-launch, good to great.

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

Polish screen recordings with Recordly (open-source Screen Studio alternative) — auto-zooms, cursor animations, webcam overlays, styled backgrounds, timeline editing. Also includes Slant: browser-based 3D perspective renderer with 12 animation presets and MP4/GIF export. Triggers on screen recording, demo video, Recordly, screen capture polish, product walkthrough, 3D perspective, Slant.

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

Alternate /pr-review and /pr-address on a PR until the PR is truly mergeable — no new review findings, zero unresolved inline threads, zero unaddressed top-level reviews or issue comments, all CI checks green, and two consecutive quiet polls after CI settles. Use when the user wants a PR polished to merge-ready without setting a fixed number of rounds.

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

Use when /design-variants generates distinct design directions and a gallery for selection. Not for one polished artifact: use polished-web-prototype. Not for token-system picking: use design.

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

Use when /polished-web-prototype runs or a user builds an artifact from a mockup, design plan, or brief. Not for variant galleries: use design-variants. Not for live audits: use web-design-review.

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

Use when asked to prototype one design question through a cheap logic or UI experiment, including button-driven state-model checks. Not for polished artifacts: use polished-web-prototype.

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

Review or polish a product UI for accessibility, brand fidelity, hierarchy, rhythm, responsive behavior, themes, interaction states, and generic AI-template patterns. Use for visual audits, accessibility checks, UX polish, UI critique, or pre-ship design review. Do not use for generic code review, backend review, or API design.

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

Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid. Also use for Archify, interactive or animated HTML diagrams, インタラクティブ図, 動く構成図. When an editable .drawio file is required, use the draw.io workflow instead and treat Archify HTML only as a supplement.

Polishing pass over all open beads. Run 4–6 times. "Check your beads N times, implement once." Use after plan-to-beads and between refinement rounds.

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

Polishing pass over all open beads. "Check your beads N times, implement once." Run 4–6 times. Use after /plan-to-beads and between refinement rounds.

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

Inject juice and game feel into gameplay code using the project's chosen middleware. Use when adding screen shake, tweens, particles, audio feedback, haptics, hitstop, or any form of "juice" to gameplay events. Triggers on requests like "add juice", "make this feel better", "add screen shake", "polish this feature", "add feedback to this action", "make the hit feel impactful", "add particles when", "screen shake on damage", "tween this", "add camera shake", "make this snappy", or any game feel, polish, or feedback work. Always reads ProjectConfig.yaml -> feel_tools and docs/GFD.md Feedback Matrix before generating code.

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

Use when building, reviewing, or improving frontend UI that needs product-specific design direction, design-system generation, Master/Page overrides, distinctive visual identity, anti-generic interface choices, first-screen hierarchy, UI polish, chart UX, interaction states, responsive behavior, or visual QA. Interface polishing, interactive state.

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

Full autonomous design pipeline — builds fast, then the safety net polishes it. Chains: design-setup → design-build → (design-audit ∥ design-optimize) → design-polish → design-animate. Ships production-grade interfaces end to end.

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

Assemble a finished piece from human-written fragments via an orchestrated two-loop pipeline - an assembly loop (assembler + cold reviewer) that sequences the fragments into a draft, then a polish loop (polisher + cold reviewer), then frequency analysis and a catalog-deslop pass with a regression gate. Two modes with opposite fidelity contracts - stitch mode preserves the author's exact wording, narrative mode preserves every idea but may rewrite freely. Use when the user says "mosaic", "assemble my fragments", "stitch these notes into a post", or provides a fragments file to turn into a finished piece. For writing from a topic with research, use article-factory; for prose from scratch, use the prose skill.

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

Elite frontend design taste for building, reviewing, and polishing web interfaces. Use whenever the user wants to design, redesign, shape, critique, audit, polish, or improve any UI (landing pages, portfolios, dashboards, product UI, components, forms, onboarding, empty states) or asks to make something look better / premium / modern, fix the styling, add or fix animations, or make a design feel less generic ("AI slop"). Covers typography, color, spacing, layout, visual hierarchy, motion, micro-interactions, component states, accessibility, responsive behavior, UX copy, and anti-pattern detection.

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

Premium UI/UX design audit and refinement skill. Conducts systematic visual audits of existing apps and produces phased, implementation-ready design plans. Use this skill whenever the user asks to audit a UI, improve an app's visual design, make an interface feel more polished or premium, review design consistency, fix visual hierarchy, or refine spacing/typography/color. Also trigger when the user says "design review", "make it look better", "UI polish", "visual refinement", "design pass", "audit the design", or references making an app feel more professional. This skill is purely visual — it does not touch functionality, logic, or features. It elevates what exists.

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

Take a chosen visual to finished, production-ready state. Runs cleanup + refinement passes (fix artifacts, balance composition, color-grade, sharpen text, conform to spec/aspect) using image edit/regenerate. Use when the user says "polish this", "finalize", "clean up the image", "production-ready", "fix the artifacts", or has a selected visual that needs finishing. Final stage of the Creative Production set.

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

Bilingual JD/CV/Resume tailoring and resume polish skill for job applications. Use when the user provides a job description, JD, role posting, existing CV/resume, LinkedIn profile, portfolio, or career notes and wants to optimize, rewrite, polish, or customize a resume/CV for ATS keywords, recruiter screening, interview-ready evidence, and role fit. 适用于根据招聘 JD、岗位描述、目标公司、现有简历/CV/LinkedIn/profile 进行简历优化、简历润色、岗位匹配、ATS 关键词映射、经历深挖、项目证据提炼和中英文求职简历定制。

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

Frontend UI design, critique, audit, polish. Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.

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

Use when reviewing an app for launch-readiness — Product Hunt polish, first impression, visual hierarchy, onboarding, empty states, screenshots, positioning, and the tiny details that make it feel premium.

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

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.

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