「writing」の検索結果

Find the angle that makes something sell. Use this skill whenever the user mentions positioning, angles, differentiation, unique selling proposition, 'how do I stand out', 'what makes us different', value proposition, messaging framework, or 'find the hook'. Also trigger when copy isn't converting (often a positioning problem), when marketing feels generic, when launching a product, creating a lead magnet, writing a landing page, or entering a crowded market. Even if the user is about to write copy without established positioning, run this first — the angle informs everything downstream. Generates 3-5 positioning angles with competitive web research and validation.

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

End-to-end social content campaign pipeline. Takes a marketing goal and produces scheduled, on-brand social posts with visuals across postiz-supported platforms, while keeping Typefully for X/thread specialist flows and fallback coverage. Chains: CMO strategy, content writing with voice calibration, AI slop audit, selective Paper MCP visual design, and routed scheduling via postiz or Typefully. Each phase has a human gate. Use this skill whenever someone wants to plan and execute a batch of social posts — not just one-off tweets. Triggers include: "social campaign", "schedule posts", "pre-launch content", "content calendar", "social content pipeline", "build up content", "I need social media content for my launch", "help me build social presence", "plan a week of posts", "batch social content", "social media strategy", or any request involving multiple scheduled posts with optional visuals.

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

Trigger when: (1) User wants to create an educational/explainer video, (2) User has a vague concept they want visualized, (3) User mentions "3b1b style" or "explain like 3Blue1Brown", (4) User wants to plan a Manim video or animation sequence, (5) User asks to "compose" or "plan" a math/science visualization. Transforms vague video ideas into detailed scene-by-scene plans (scenes.md). Conducts research, asks clarifying questions about audience/scope/focus, and outputs comprehensive scene specifications ready for implementation with ManimCE or ManimGL. Use this BEFORE writing any Manim code. This skill plans the video; use manimce-best-practices or manimgl-best-practices for implementation.

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

Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.

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

Build applications and agents with Exa's API Platform: search, contents, answer, context, Agent API, monitors, websets, OpenAI-compatible endpoints, and exa-py / exa-js. Use when choosing Exa endpoints, writing Exa API calls, integrating semantic web search or research into products, or debugging Exa request shapes. Load references/ on demand for endpoint details.

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

当用户混淆了广告文案和文学创作的目标，或正在纠结"文案够不够有创意"时调用。 适用于：文案评审时陷入"够不够漂亮"的争论、团队创意方向偏离销售目标、 新手文案写手建立正确的职业认知。核心信号：用户在问"文案够不够有创意"而不是 "文案能不能卖货"。不适用于：纯文学创作、品牌视觉设计讨论。

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

当用户纠结文案该写长还是写短时调用。适用于：规划广告/邮件/着陆页篇幅、 别人说"没人看长文案"时需要决策依据、产品复杂不知道该写多少。 核心信号：用户在问"文案写多长合适""会不会太长了"。 不适用于：已有明确篇幅要求、纯社交媒体短文案。

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

当用户需要将产品/服务/个人的特点转化为对受众有吸引力的利益点时调用。 适用于：写产品文案不知从何下笔、准备销售话术、撰写简历或自我介绍、 做产品定位思考。核心信号：用户在列举产品特点但不清楚"别人为什么要在乎"。 不适用于：纯技术文档、产品规格说明（此时特色本身就是目的）。

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

当用户需要组织一段有说服力的销售文案/演示/邮件，且需要完整的逻辑结构时调用。 适用于：写产品介绍页面、准备销售演示、写长篇销售信/邮件、设计着陆页。 核心信号：用户有多个卖点但不知道按什么顺序排列、在写"说服型"文案。 不适用于：纯信息传递、品牌口号创作、单句slogan。

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

当用户需要按公式化方法构造广告标题，或想把产品信息转化为有力标题时调用。 适用于：从零开始写标题、把产品卖点转化为标题、需要快速产出多个标题方案。 不适用于：评估已有标题（用headline-four-functions）、分析竞品（用headline-eight-types）。

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

当用户需要为广告/邮件/着陆页创作标题，且需要选择标题的写法风格时调用。 适用于：标题创作卡壳、想尝试不同风格的标题、分析竞品标题属于哪种类型。 不适用于：标题评估（用headline-four-functions）、正文写作。

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

当用户需要撰写或评估广告标题/邮件主题/页面首屏文案时调用。 适用于：写产品标题但不知如何组织、评估现有标题是否有效、 设计直邮信封文案或网站首屏。核心判断：用户正在处理"第一印象"文案。 不适用于：正文写作、视觉设计、品牌策略讨论。

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

当用户需要深入理解目标客户的心理动机来撰写有共鸣的文案时调用。 适用于：写文案前分析客户心理、客户画像不够深入、文案太平面缺乏情感共鸣、 做用户调研准备。核心信号：用户在问"客户到底在想什么""怎么打动他们"。 不适用于：纯功能型产品文案（技术规格就够了）、不需要情感共鸣的B2B技术文档。

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

Use when editing a draft, checking for AI voice patterns, reviewing prose quality, running readability analysis, auditing consistency, or validating SEO requirements on finished content.

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

Use when planning a multi-article content strategy from a research corpus, creating domain maps for content topology, building production plans for pillar and cluster articles, or tracking cross-article production.

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

Use when organizing raw material into a coherent structure, defining the throughline of a piece, building an outline, or making strategic decisions about what to include and cut from generated content.

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

Use when creating nonlinear outlines, generating mindmap diagrams for article structure, mapping a knowledge domain visually, or bridging raw ideas into structured options for the user to select from.

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

Use when scoring finished content against quality dimensions, evaluating whether a piece meets publishable standards, or determining which workflow phase needs rework based on quality gaps.

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

RED-GREEN-MUTATE-KILL MUTANTS-REFACTOR workflow for writing production code. Use before ANY production code change - new features, bug fixes, or behavior changes. Triggers on starting implementation work of any kind. Covers the cycle itself - failing test first, minimum code to pass, mutation verification, refactor assessment. For how to write good tests, see testing. For the refactoring step in detail, see refactoring. TDD is non-negotiable.

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

Go code refactoring with automated tools: gofmt -r, gopatch, and rsc.io/rf. Use this skill when performing mechanical rewrites across a codebase — renaming identifiers, migrating API calls, moving types between packages, rewriting expressions, or replacing deprecated patterns. Triggers when the task involves bulk code transformation, API migration, structural rewrite, or the user mentions gofmt -r, rf, gopatch, coccinelle-style patching, or large-scale rename/move in Go.

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

The complete Go development skill. REQUIRED for ALL Go work — writing, refactoring, reviewing, generating, scaffolding, or discussing Go code, including any change to .go files. Use whenever the user mentions Go, Golang, go.mod, a Go package, or asks to build a Go backend service, CLI, library, script, MCP server (Model Context Protocol), or AI/LLM agent with tool calling or ReAct-style reasoning. Routes by project type to the right architecture, conventions, and review checklist. Highly opinionated; overrides generic Go style and lint guidance on conflicts.

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

文章を書く時の心得。ソースコードのコメント、PR概要欄、ドキュメント、wikiのどこに書く時も変わらない、解釈のブレを起こさない文の書き方と、強調記号とカッコ書きの扱いを定める。 ソースコードのコメント、PR概要欄、ドキュメント、wikiの文章を書く時、直す時、レビューする時に読み込む。

Calculates CRAP (Change Risk Anti-Patterns) score for .NET methods, classes, or files. Use when the user asks to assess test quality, identify risky untested code, compute CRAP scores, or evaluate whether complex methods have sufficient test coverage. Requires code coverage data (Cobertura XML) and cyclomatic complexity analysis. DO NOT USE FOR: writing tests, general test execution unrelated to coverage/CRAP analysis, or general code coverage reporting without CRAP context.

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

Use when developing in packages/agent-core-v2 (the DI × Scope agent engine) — adding or modifying a domain Service, choosing a LifecycleScope, wiring DI dependencies, splitting a domain across scopes, owning or migrating a config section, gating behavior behind an experimental flag, raising coded errors, working on the permission system, writing DI/Scope tests, porting business logic from agent-core (v1) to v2, triaging a main-branch commit against v2, or exposing a v2 domain over server-v2 while keeping the /api/v1 wire contract compatible with released clients. Self-contained guide organized by development stage (orient → design → implement → test → verify) plus align workflows for v1→v2 migration, main-branch commit triage, and server-v2 wire exposure; each file carries the rules, examples, and red lines for its step.

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