執筆・創作のスキル

Maintain bidirectional consistency between story markdown files and GitHub Issues. Use when syncing story status with GitHub.

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

Generate low-fidelity wireframes (ASCII, SVG, or HTML) from user story files. Use when creating wireframes for UI stories.

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

Produce valid, consistently named Gherkin story files with correct IDs, timestamps, and tags. Use when writing or updating story files.

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

Create, read, update, and link GitHub Issues as story artifacts throughout the story lifecycle. Use when managing issues for stories.

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

爆款拆解复刻：把抖音/TikTok 爆款带货视频（链接、转写或口述结构）拆成 8 维结构与 5-beat 节拍，再映射到你的商品，输出拆解表 + 3 个复刻角度 + 可渲染 storyboard.json。Use when the user says 爆款, 拆解, 复刻, 对标, 仿拍, viral remake, breakdown, swipe file, copy structure, 竞品视频, remake a TikTok/Douyin product video, or wants to replicate a viral ecommerce short's structure with their own product.

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

开箱 / 对比评测模板：生成电商开箱视频与 A/B 对比评测的结构、口播稿、拍摄清单与分镜（含公平对比规则、测试设计、缺点与适合人群），可直接转成 storyboard.json 渲染。Use when the user wants an unboxing video, 开箱, 测评, 评测, 横评, 对比, review script, product comparison, versus video, or UGC-style creator review for an ecommerce product.

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

卖点分镜表：把商品卖点拆成 15–60 秒带货短视频的逐镜分镜表（时间码、画面、台词、字幕、花字、素材来源、运镜），并直接输出可渲染的 storyboard.json。Use when the user wants a storyboard, 分镜, 分镜脚本, shot list, 带货视频脚本, video script from selling points, or needs to plan a product video before generating or editing.

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

多语言本地化配音：把中文带货视频本地化为英语、日语、韩语、东南亚语（印尼/泰/越/马来/菲律宾）、西语等版本——本地化改写口播（不是直译）、选对 edge-tts 音色、生成对应字幕与花字，并用同一份 storyboard 一键渲染多语言成片。Use when the user wants dubbing, 多语言, 本地化, 翻译配音, 出海, localize a product video for TikTok Shop US/UK/SEA, English voice-over, or multiple language versions of one video.

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

漫画のあらすじや1話、シーンの欲求・対立・因果関係を構成相談またはレビューするときに使う。

This skill should be used when the user says "lock it", "go with that", "approved", "that's the standard", or explicitly establishes a project-wide pattern like "from now on all forms should use this approach". Formalizes approved decisions into locked standards that the system enforces going forward. Not needed for story-scoped decisions — only for project-wide patterns.

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

This skill should be used when a story has been captured but content direction is unresolved - the spark describes WHAT to build structurally but not WHAT goes in it. Reads the story spark, splits it into Resolved (structurally clear) vs. Assumed (would have to guess) content dimensions, and surfaces each assumption for the human to confirm, correct, or expand. Also classifies implementation risk tags (has-variants, has-data-pipeline, has-animation, has-touch-targets, diverges-from-existing) so plan-chunks translates them into acceptance criteria that name the implementation mechanism. Captures answers into

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

This skill should be used when the user asks to "brainstorm", "explore options", "get creative", "what if we...", or selects "Let's get creative" during story or cycle creation. NOT for a bare vague feature idea where generating options would mean inventing the premise first - that routes to /craft:riff (riff first, options after). Generates 2-3 creative options with trade-offs, visual direction for UI stories, and wireframes.

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

This skill should be used when the user asks to "plan chunks", "break this down", "plan the implementation", or when a story has status planning and needs implementation details before building. Required before any story can be implemented. Transforms story sparks into detailed chunk-by-chunk implementation plans with full technical specifics, file lists, and risk analysis. Supports parallel planning of multiple stories via batch mode.

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

Adhoc workflow for small targeted changes to existing behavior or appearance, without the full story ceremony. Use when the orchestrator encounters a bug with a clear root cause and surgical solution, OR a small enhancement to something already built (a different icon, wording, spacing, color). Triggers on: 'fix this', 'this is broken', 'the alignment is off', 'that button doesn't work', 'quick fix', 'patch this', 'tweak this', 'change the icon', 'adjust the wording', post-story corrections, or any situation where the write gate blocks a small targeted change. Acts NOW - a defect to file and fix later belongs in /craft:bugs, other deferred work in the notebook. Do NOT use for new features, design exploration, or changes requiring creative spark.

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

Enforcement layer for chunk and story validation. Invokes the chunk-validator agent (haiku), enforces the verdict, routes failures to refine-chunk or test-fix, captures CLI learnings. The orchestrator invokes this skill — never the agent directly.

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

A live visual Kanban board and continuity layer for long-running agentic tasks. Nobody wants to read a markdown plan or stare at raw HTML while an agent grinds for an hour, so Plandeck turns the plan into a board that organizes itself. Use it when a task is multi-step, long-running, or needs visual planning. Break the work into cards, declare which card depends on which, and Plandeck computes the critical path, auto-promotes cards to Ready as their dependencies clear, rolls up story-point estimates into an honest percent complete, and names the one next action. Plans, observed transitions, and last-known-good snapshots stay as plain files on disk, so they survive /clear and context resets. After a reset, run plandeck next to recover the single next move and its recent history. If the plan stops parsing, run plandeck doctor before using git. Renders a live board in the browser over SSE. Triggers on plan a project, break down a task, kanban board, task board, visual plan, long-running agent, agentic task, track dependencies, critical path, story-point estimates, what is next, mission journal, recover plan, plandeck.

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

Audit a MaaFramework/Maa-series project's Git history to learn how Pipeline JSON, interface options, Python AgentServer CustomAction code, and related data tables evolved. Use when asked to review a Maa project from initial commit through a target commit, map `action: Custom` pipeline nodes to `@AgentServer.custom_action(...)` implementations, find pipeline/custom/option patterns or breakages, and produce a report plus skill-improvement recommendations.

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

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

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

Browser History ACSet

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

Searches and explores Burp Suite project files (.burp) from the command line. Use when searching response headers or bodies with regex patterns, extracting security audit findings, dumping proxy history or site map data, or analyzing HTTP traffic captured in a Burp project.

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

> Persistent belief revision log wiring in-memory AGM BeliefSet to DuckDB time-travel storage. Triggers: belief revision, AGM postulates, time-travel query, belief history, AS-OF queries on propositions, persistent belief state, append-only belief log. >>>>>>> origin/main

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

Export AMP threads as markdown and fork continuation paths. Use when managing AMP conversation threads, exporting thread history, or branching thread execution across skills.

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

Interruption pattern detection and retrieval from Amp thread history. Use for analyzing tool rejection patterns and improving agent behavior.

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

When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' or 'sharpen the messaging.' Use this when the user already has copy and wants it improved rather than rewritten from scratch. For writing new copy, see copywriting.

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