Writing Skills

Write outcome-based job descriptions and role scorecards.

Write a decision-ready PRD for cross-functional alignment. See also: writing-specs-designs (build-ready spec).

Define or refresh a product North Star metric + driver tree.

Create a build-ready spec + design doc (user flows, prototype brief, acceptance criteria). See also: writing-prds (decision-level PRD).

Generate procedural 3D models from natural-language requests by writing a constrained buildModel(ctx) module that uses Three.js, bundled builders and helpers, deterministic validation and export scripts, PNG previews, and optional browser visual review. Use when needs to create, revise, export, or visually audit programmatic 3D assets in GLB, glTF, OBJ, or STL without Blender or another DCC tool.

>- Turn a vague bug report into a VERIFIED minimal reproduction and then a failing regression test, agent-driven end to end. Covers extracting the implicit repro from a thin report (env, build, steps, data), the reproduce-minimize-isolate-capture loop, git bisect to find the introducing commit, building a deterministic minimal repro (fixed seeds, frozen time, stubbed network), writing the failing regression test BEFORE the fix (red) and confirming the fix flips it green, and writing repro evidence back into the ticket. Distinguishes flaky-not-reproducible from environment-specific. that broke it," "git bisect," "make the repro deterministic," "write a failing test for this bug," "regression test for a defect," "can't reproduce this bug." reproducing them — that is ai-bug-triage. Generating tests from specs rather than from a defect — that is ai-test-generation.

Design, implement, review, or troubleshoot safe refinement of editable 2D canvas strokes. Use for handwriting smoothing, automatic text layout cleanup, optional font-guided handwriting normalization, freehand cleanup, geometric shape snapping, diagram cleanup, stroke-style normalization, semantic stroke replacement, and previewable or undoable refinement pipelines in whiteboards, note apps, drawing tools, annotation systems, and pen-input SDKs. Do not use for general raster image editing, prose rewriting, or renderer bugs unrelated to stroke transformation.

Use this agent when you need to create or update README files following the Ankane-style template for Ruby gems. This includes writing concise documentation with imperative voice, keeping sentences under 15 words, organizing sections in the standard order (Installation, Quick Start, Usage, etc.), and ensuring proper formatting with single-purpose code fences and minimal prose. Examples: <example>Context: User is creating documentation for a new Ruby gem. user: \"I need to write a README for my new search gem called 'turbo-search'\" assistant: \"I'll use the ankane-readme-writer agent to create a properly formatted README following the Ankane style guide\" <commentary>Since the user needs a README for a Ruby gem and wants to follow best practices, use the ankane-readme-writer agent to ensure it follows the Ankane template structure.</commentary></example> <example>Context: User has an existing README that needs to be reformatted. user: \"Can you update my gem's README to follow the Ankane style?\" assistant: \"Let...

Use this agent when you need to review and edit text content to conform to Every's specific style guide. This includes reviewing articles, blog posts, newsletters, documentation, or any written content that needs to follow Every's editorial standards. The agent will systematically check for title case in headlines, sentence case elsewhere, company singular/plural usage, overused words, passive voice, number formatting, punctuation rules, and other style guide requirements.

Produces concise, clear documentation by applying Elements of Style principles. Use when writing or improving any technical documentation (READMEs, guides, API docs, architecture docs). Not for code comments.

Use when user asks to create, write, edit, or test a skill. Also use when documenting reusable techniques, patterns, or workflows for future Claude instances.

This skill provides comprehensive support for the writing process from ideation through revision. Use this skill when helping users write essays, articles, or creative pieces through interactive collaboration. The skill supports co-evolving outline and prose, voice-based input processing, multiple writing styles, and connection to the user's PKM system for enriched content.

>- Reviews proposed or existing work for unnecessary complexity and triages complexity-increasing recommendations without editing the reviewed targets. Use this skill when asked to simplify or decomplex source, tests, configuration, dependencies, plans, designs, or architecture; challenge over-engineering; audit unnecessary complexity; or triage recommendations that would add complexity. Do not use for general defect review, implementation or fixes, style-only cleanup, or conceptual explanations that need no durable review report.

Use this skill when building, enriching, auditing, or uploading B2B paid ads audiences to Google Customer Match, Meta/Facebook Custom Audiences, or LinkedIn Matched Audiences. Triggers on phrases like '/deepline-ads-audience', '/deepline-ads-audiences', 'upload this audience', 'create custom audiences', 'personal email hashes', 'increase Facebook match rate', 'Google ads audience', 'Meta audience', 'FB audience', or any workflow that turns CRM/customer/contact data into paid ads upload lists. Skip for outbound prospecting sequences, cold email, or pure campaign copywriting.

Guides PRD, ADR, Design Doc, and Work Plan creation. Use when: planning features, writing specs, or creating technical documents.

Prose guardrails for speq artifacts and GitHub PRs, issues, and comments — front-loaded (BLUF), terse, unambiguous writing anchored in established style and requirements standards. Triggered by /speq-mission, /speq-audit, /speq-implement, /speq-plan-pr, /speq-implement-pr, planner-agent, plan-reviewer, and recorder-agent.

Comprehensive SwiftUI localization audit - finds and fixes hardcoded strings, missing translations, and rawValue usages. Use when auditing code for localization issues, checking for untranslated strings, or preparing for App Store international launch.

Use when writing or modifying code for s&box, sbox, the Facepunch sandbox engine, or any Source 2 game project in C#. Triggers on mentions of s&box, sbox, sandbox game, Facepunch engine, Source 2 game, `.sbproj`, `.razor` with `PanelComponent`, `@inherits PanelComponent`, `Sandbox.Component`, `GameObject` + `Components.Get<T>`, `Scene.Trace`, `CharacterController` + `.Move()`, `SkinnedModelRenderer`, `NavMeshAgent`, `[Sync]`, `[Rpc.Broadcast]`, `[Property]`, `INetworkListener`, `ISceneEvent`, `PlayerController` in C#. Also triggers on any file with `using Sandbox;` or `using Sandbox.UI;` that isn't Unity/Godot/Unreal. Writes idiomatic s&box C# components, Razor UI, and networking code; prevents Unity-pattern leakage.

Evaluate UI designs against usability heuristics, UX laws, interaction patterns, interaction design principles, information architecture, and content quality. Conduct heuristic evaluations, structured design critiques, pattern-based reviews, posture analysis, excise audits, IA evaluations, and UX writing reviews. Provides specific, actionable feedback grounded in established principles rather than subjective opinion.

Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text. Use when writing or editing any text that appears in apps, websites, or software interfaces, designing conversational flows, establishing voice and tone guidelines, auditing product content for consistency and usability, reviewing UI strings, or improving existing interface copy. Applies UX writing best practices based on four quality standards — purposeful, concise, conversational, and clear. Includes accessibility guidelines, research-backed benchmarks (sentence length, comprehension rates, reading levels), expanded error patterns, tone adaptation frameworks, and comprehensive reference materials.

Translate structured documents (DOCX) to RTL languages (Arabic, Hebrew, Urdu) while preserving exact formatting, table structures, colors, and layouts. Handles quote normalization, multi-pass translation matching, and RTL-specific formatting patterns.

Translate DOCX to RTL languages (Arabic, Hebrew, Urdu) preserving exact formatting, tables, colors, layouts. Handles quote normalization and multi-pass matching.

Use when asked to create, review, or revise a multi-step implementation, bug-fix, or change plan before editing code, including existing plans that may use a legacy task-by-task template. Produce a problem-first plan that non-technical readers and implementers can both understand.

Phase-1 (S2) of the comic-author suite — compile the project's ART_BIBLE.md into an EXECUTABLE convergence target, not aesthetic prose. The bible is the ONE visual dialect read verbatim into every bake prompt AND into every visual reviewer's rubric (`style_consistency`/`identity_consistency` literally = 'conforms to this file'). A `bootstrap` parses the bible into immutable per-dimension `style_anchor` wiki nodes (palette / line / shading / two-world warm-vs-cyber lighting / identity-lock / per-world STYLE_PREFIX / text-mode / forbidden / by-design exceptions); a deterministic `validate` lints candidate authoring text against the FORBIDDEN list + identity-lock + world-mismatch; an append-only `update` Gemini-harvests recurring drift from KEEP panels into by-design exceptions. Auto-bootstrap if the bible is missing; otherwise LEAVE LOCKED. Locked anchors are immutable — pivoting the style = a fresh project, never an in-place edit.

Phase-1 comic-author step — turn a LOCKED, user-approved outline into the page-first storyboard that IS the authoring source of truth: a fixed page order BEFORE any prose, the MOTIF STATE TABLE (the master per-panel continuity ledger), a fixed 9-field per-panel spec, and one deduped canonical asset contract. Decompose beats→pages→panels, 抽卡 K page/panel-order lineages by feasibility, then fill every panel one unit at a time. Writes a storyboard_spec + a motif_ledger (read by comic-continuity-audit) + N panel_spec nodes. Use when the user says "做分镜", "storyboard", "排页", "panel spec", "分镜稿", or the outline layer is locked and approved and you need the per-panel authoring layer the thin comic-author SOP defers to. Two-stage under the N1 contract: a PROVISIONAL structural gate pass on draft assets now, the FINAL asset-resolution validation after the asset layer locks.

Use when you have a spec or requirements for a multi-step task, before touching code

> Generates rigorous devil's advocate critiques from methodological, theoretical, and practical perspectives. Use when the user asks to challenge their own work, find weaknesses, stress-test assumptions, anticipate reviewer objections, or argue against their research claims. Run BEFORE writing a draft for stronger papers.

> Writes a complete IMRaD-structured academic paper draft (Abstract, Introduction, Related Work, Methods, Results, Discussion, Conclusion, References) from the user's notes, documents, and wiki content. Use when the user asks to write a paper, create a manuscript, generate a draft, or produce academic writing. Do NOT use for short summaries — only for full paper-length output.

Implements and debugs browser Proofreader API integrations in JavaScript or TypeScript web apps. Use when adding Proofreader availability checks, monitored model downloads, proofread flows, correction metadata handling, or permissions-policy checks for built-in proofreading. Don't use for generic prompt engineering, server-side LLM SDKs, or cloud AI services.

Implements and debugs browser Summarizer, Writer, and Rewriter integrations in JavaScript or TypeScript web apps. Use when adding availability checks, model download UX, session creation, summarize or write or rewrite flows, streaming output, abort handling, or permissions-policy constraints for built-in writing assistance APIs. Don't use for generic prompt engineering, server-side LLM SDKs, or cloud AI services.

文案诊断助手适合市场营销、运营、产品、销售在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。

文案诊断助手适合内容创作者、市场营销、运营、内容媒体在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成内容诊断、优化建议、执行清单。

文案诊断助手适合内容创作者、市场营销、运营、内容媒体在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成内容诊断、结构化优化建议、可执行发布清单。

文案诊断助手适合内容创作者、市场营销、运营、内容媒体在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成主题地图、内容缺口、优先级路线图。

说服力文案助手适合内容创作者、市场营销、运营、内容媒体在用户提出“这句文案有说服力吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成内容诊断、优化建议、执行清单。

文案诊断助手适合内容创作者、市场营销、运营、内容媒体在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成内容诊断、优化建议、执行清单。

转化实验助手适合内容创作者、市场营销、运营、内容媒体在用户提出“这个改动值得测吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成内容诊断、结构化优化建议、可执行发布清单。

文案诊断助手适合内容创作者、市场营销、运营、内容媒体在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成说服力诊断、可复制改稿、风险词提示。

用户旅程地图助手适合内容创作者、市场营销、运营、内容媒体在用户提出“用户卡在哪一步”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成转化问题诊断、文案和结构建议、实验清单。

HR 专业助手适合人力资源、manager、运营、software在用户提出“HR 文档怎么更稳”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成转化问题诊断、文案和结构建议、实验清单。

中文润色去AI味 助手适合市场营销、运营、内容创作者、产品在用户提出“怎么去AI味”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成AI 写作痕迹诊断、自然化改写稿、问题片段说明。

销售线索判断助手适合销售、市场营销、运营、software在用户提出“这个线索值得跟吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成转化问题诊断、文案和结构建议、实验清单。

AI 视频剪辑诊断助手适合市场营销、运营、software、内容媒体在用户提出“这段素材怎么剪”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成剪辑结构诊断、片段取舍和时间点建议、字幕配音与平台重构清单。

文案诊断助手适合内容创作者、运营、市场营销、内容媒体在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。

文案诊断助手适合市场营销、运营、产品、software在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。

转化实验助手适合市场营销、运营、产品、销售在用户提出“这个改动值得测吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。

文案诊断助手适合technical、管理者、software、知识库在用户提出“这段文案能打动人吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。