「rewrite」の検索結果

A complete marketing department in one skill. Website and landing-page audits with weighted 0-100 scores, copywriting with panel scoring and AI-slop removal, an 18-tactic ad hook engine, GEO/AEO for getting cited by ChatGPT/Perplexity/AI Overviews, paid-ads creative diagnosis and production briefs, email sequences, LinkedIn/X writing, launch playbooks, positioning and offer design, competitor teardowns, app store optimization, honest analytics and test design. Use for ANY marketing task — audit, write, rewrite, diagnose, score, plan, launch, position, price, analyze — whenever the user mentions marketing, growth, conversion, copy, ads, hooks, CPM, ROAS, SEO, GEO, email, social, landing pages, funnels, launches, competitors, brand, positioning, pricing, or app stores, or says "my landing page sucks", "nobody's converting", "why are my CPMs up", "AI doesn't recommend us", "write me 20 hooks". Route via the table inside; fan out subagents for multi-dimensional work. Not for pure engineering, legal, or finance.

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

Use when the user needs to turn a real software engineering / computer science project and an existing thesis draft into a submission-ready undergraduate thesis manuscript. Trigger for requests such as "根据项目把论文改成定稿", "按学校模板排版成最终版", "复制初稿后生成定稿 Word", "为定稿降查重", "根据PaperPass报告降AIGC", "继续在手改初稿上改", "恢复原来的图表和数据库说明", or when academic-paper-strategist has already produced an evidence-backed rewrite plan. Outputs a cleaned manuscript, final DOCX workflow, and a separate rework report.

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

Use when the user needs to plan, de-risk, or ground a software engineering / computer science undergraduate thesis from a real codebase before final writing. Trigger for requests such as "根据项目写毕业论文", "先做论文大纲", "用真实项目材料规划论文", "检查论文是否脱离代码", "根据检测报告降查重", "根据AIGC报告改写定稿", "继续在手改初稿上改", or when an existing draft thesis must be reworked against a school format sample. Produces an evidence-backed outline, chapter rewrite plan, figure plan, and handoff package for academic-paper-composer.

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

Rewrite AI-generated copy in Spanish and English so it sounds direct, concrete and human while preserving meaning, facts and numbers exactly. Use when drafts feel robotic, verbose or translated and need short active sentences without em-dashes.

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

Produces human-sounding text that avoids detectable AI writing patterns. Activates on any writing task — tweets, emails, articles, bios, captions, reports, copy, messages, LinkedIn posts, cover letters, README files, or any content where the output must not read as AI-generated. Enforces banned vocabulary, structural variety, punctuation discipline, accuracy rules, and voice calibration. Use when the user says "write," "draft," "rewrite," "make this sound human," "anti-slop," "not AI," or any variation of wanting authentic-sounding output.

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

Use whenever the user asks to "humanize", "make this sound more human", "rewrite to avoid AI detection", "make this less AI-sounding", "add a human voice", or "write like a person". Also use when the user pastes text and asks why it reads as robotic, generic, flat, or AI-like, or when generating new text in a register where AI tells (em dashes, semicolons, hedges, banned vocabulary like "delve", "leverage", "robust") would damage credibility.

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

Writing self-loop for surveys: run the strict section-quality gate, then rewrite only the failing `sections/*.md` files until the report is PASS.

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

Rewrite subsection openers so they stop reading like a generated table-of-contents: remove \"overview/narration\" stems and reduce repeated opener cadences across H3s.

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

Audit and rewrite evaluation/numeric claims to ensure they carry minimal protocol context (task + metric + constraint) and avoid underspecified model naming.

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

Rewrite limitation passages so the paper keeps limitations without falling into count-based slot phrases (e.g., \"Two limitations…\") across many H3s.

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

Score an existing reader-facing deliverable and emit a deterministic PASS/FAIL scorecard plus bounded repair plan; use after synthesis, not to rewrite content.

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

DO NOT INVOKE when the primary request explicitly asks to convert, migrate, modernize, or rewrite a legacy/old-style project to SDK style; use msbuild-modernization. Migration prompts often mention ToolsVersion, explicit Compile/Reference entries, packages.config, or Microsoft.CSharp.targets, but merely reviewing or auditing a file that contains those patterns remains in scope here. USE FOR broad review, audit, lint, or maintainability/correctness checks of project/build files, including custom targets; prioritized cross-cutting findings; discrete anti-patterns; F# ordering/FS0039; cross-platform paths; and focused Import safety verdicts. Review/audit is analysis-only unless fixes are requested. For concrete property/item defects use property-patterns/item-management; use target-authoring for implementation and extension-points for NuGet auto-import/layout discovery. Exclude non-MSBuild systems.

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

ALWAYS USE when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for "review" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected/actual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext/lifecycle; timeout/cancellation; OS/CI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest/non-.NET code.

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

Publish local .claude skills/loops to Ametyst — verbatim, flattened, no brain rewrite; optional retire-local (MOVE originals to deprecated-skills/, never delete) makes Ametyst the source of truth.

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

Review tweet drafts in Claude Code against 8 voice rules. Scores 1-10, breaks down every rule, and rewrites anything that scores below 7.

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

Writes (or rewrites) a spec, PRD, PR-FAQ or shaped pitch and grades it against what the best product teams actually do. Use when you ask 'write a PRD', 'how do I spec this', 'PR/FAQ', 'working backwards doc', 'shape this project', 'do we even need a PRD', or 'engineering says the spec isn't detailed enough'. Draws on 56 insights from 38 Lenny's Podcast guests incl. Ryan Singer, Bill Carr and Lane Shackleton.

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

将用户文案转换为知乎风格，携带2-3个特色关键词（指南、教程、秘籍等），按10项写作技巧改写，末尾附加Tags；当用户需要将产品介绍、攻略分享等内容改写为知乎爆款文案时使用

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

小红书文案改写能力；当用户需要将文案改写为小红书风格时使用

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

多平台文案改写能力；当用户需要将文案改写为公众号/视频号/抖音/快手/哔站/小红书/知乎风格，或批量输出多平台改写结果时使用

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

一位公众号爆款文案撰写专家。具有硬核的公众号文案功底，不管给你什么文案，你总能把该文案转化为一篇高阅读数的公众号文案，文案中必定会包含一些具有公众号特色的词汇。这个角色需要具备精通语言的能力，这个角色的任务是通过语言的艺术表达，使句子更加生动、吸引人、有趣和具有说服力。

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

Translate a complete mathematical modeling contest problem sentence by sentence into precise modeling language, preserve every substantive condition and definition, expose hidden constraints, draw a mandatory Mermaid cross-question flowchart, audit omissions, and deliver one easy-to-open Markdown report. For Huawei Cup (CPGMCM) graduate-contest problems, additionally prepend a plain-language layer that rewrites the background and questions as a primary-school word problem with a mandatory term-mapping table. Optionally render the finished report as one standalone HTML page on request. Use whenever a user supplies a CUMCM, CPGMCM, or other modeling problem and asks to interpret, translate, unpack, read closely, identify requirements, or avoid missing details before modeling.

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

Audit and rewrite an Instagram profile end-to-end for 2026: profile photo, searchable NAME field weighted with a keyword, @handle, bio (150 chars: value plus topic plus proof), goal-matched link, category label, story highlights, the first-9 grid, and up to 3 pinned posts. Triggers on "review my Instagram profile", "fix my bio", "optimize highlights", "profile audit". The whole follow decision happens on the profile header. Not for writing captions (use ig-caption-writer).

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

Canonical rules for writing tests in the Shift codebase. Use whenever you add, rewrite, or review a `.test.ts` or `.spec.ts` file — or any time you're about to mock, stub, or spy your way around a testing problem. Covers TestEditor-based tests and desktop E2E tests driven through EditorDriver.

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

When the user needs to create, critique, or optimize a landing page for conversion -- including headline rewrites, CTA placement, layout restructuring, or full page copy drafts.

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