「polishing」の検索結果

Workflow for de novo assembly, scaffolding, polishing, contamination review, and assembly QC.

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

Workflow for nanopore or PacBio long-read QC, alignment, polishing, methylation-aware analysis, and structural variant discovery.

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

Build or resume mathematical-modeling competition work, including CUMCM, MCM/ICM, graduate and regional contests, data challenges, and open-topic statistical modeling. Guide problem framing, modeling, computation, validation, Chinese or English LaTeX writing, and reviewed PDF/source delivery using current official requirements. Not for ordinary paper polishing.

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

Edit drafts into natural prose, inspect AI-sounding patterns, or review how a specified audience might respond passage by passage. Zero Slop runs inside the user's existing AI assistant with local tools that protect source details. Use for humanizing or de-slopping writing, polishing outward-facing prose, social drafts, final editorial checks, or an explicit simulated reader review. Preserve facts, voice and format; reader simulations are hypotheses, not human feedback.

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

把一条平淡的中文 tweet/推文/帖子改写成"有真实事实支撑 + 带互动钩子"的高参与度版本,每次给 2-3 个不同钩子的版本,风格务必短、白、口语。只要用户贴出一条中文 tweet/推文/微博/帖子,并提到"润色""改写""优化""让它更有互动""涨互动""涨粉""提高回复""帮我把这条发得更好"等任何意图,就使用本 skill——哪怕用户没明确说"用 skill"。也适用于把某个观点/事实/日常做成"忍不住想回答"的提问帖或填空帖时。

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

Best practices for AI-driven English-to-Chinese translation. This skill should be used when the user asks to "translate to Chinese", "update the Chinese translation", "improve Chinese translation", "fix translation quality", "review Chinese translation", or when translating any English text into Chinese. Also applies when polishing an existing Chinese translation of English content.

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

Route new policy briefing, policy update, regulatory update deck, regulatory change deck, compliance change summary, legal update deck, or legal/product policy presentation requests here before generic AIPPT. Use this whenever the user wants a new policy interpretation deck with timelines, impacts, risks, and recommended actions. Do not use this scene pack for email memos, FAQ-only outputs, compliance copy polishing, or non-deck legal writing.

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

Remove telltale signs of AI-generated "slop" writing. Use when polishing READMEs, docs, marketing copy, or public-facing text, or when text "sounds like ChatGPT".

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

Iterative UI/UX polishing workflow for web applications. The exact prompt and methodology for achieving Stripe-level visual polish through multiple passes.

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

Convert markdown plans into beads with dependencies using br CLI. Use when creating task graphs, polishing beads before implementation, or bridging planning to agent swarm execution.

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

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.

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

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

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

Reset review context when bead polishing or code review has flatlined. Requires starting a brand-new Claude / Codex session. Use when you're seeing the same small edits round after round.

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

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.

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

Revise an already accepted article, essay, paper, statement, or manuscript under strict minimal-change constraints while still satisfying reviewer comments, supervisor feedback, or requested edits. Use when the user asks for minimal edits, smallest necessary changes, preserve the current voice, keep the existing style, avoid broad rewriting, or implement requested revisions without unnecessary polishing.

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

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.

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

Use when synchronizing frontend project documentation with source-of-truth files such as package.json, lockfiles, config, env examples, routes, API clients or server routes, schemas, components, tests, CI, build/deploy config, ADRs, changelogs, or migration notes. Do not use for general prose polishing only; Chinese triggers include document synchronization, update README, docs sync, environment variable documentation, command list, API Document synchronization.

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

Iterative manuscript improvement workflow where a reviewer agent critiques, an author agent revises, a verifier checks the revision, and the loop repeats until acceptance or a human-pause condition is reached. Use for virtual peer review, reviewer-author revision loops, rebuttal preparation, resubmission polishing, journal paper improvement, response-to-reviewers drafting, and deciding when additional data, experiments, theory, modeling, or author judgment is required before further revision.

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

Evidence-first academic research workflow for topic ideation, scholarly search, paper reading, literature and systematic reviews, study and experiment design, statistics and data analysis, scientific figures, manuscript drafting and polishing, citation checks, peer review, rebuttals, submission packages, theses, and paper-to-presentation work. Use when an agent must plan, execute, audit, write, revise, or package research while keeping claims traceable to verified sources, data, analysis, or official requirements.

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

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.

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

Playbook for Aceternity UI, Refero MCP, Mobbin MCP, and Godly when building or polishing web UI — what each source is for and how agents should use it.

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

Resolve repository documentation authority, repair reading paths and explanations, or shape a bounded public projection. Maintain docs after a bounded change when indirect reader promises, generated or paired sources, version/evidence boundaries, or unclear authority need attention. Ordinary known updates stay in normal development; not for isolated prose polishing, code review, or broad runtime audits.

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

Turn content into a responsive, presenter-friendly slide deck published at a live URL via ReportRoom. Use when the user says "make this a deck", "turn this into slides", "presentation for", or wants something to present rather than read. Not for long-form documents (use report-publisher) or polishing an existing deck (use report-designer).

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