Writing & Editing

Turn a plain-language task description into a minimal prompt template — extracts {{variable}} placeholders, detects output format, assembles a ROLE/TASK/INPUT/CONSTRAINTS/OUTPUT scaffold. Use when the user asks to write or templatize a prompt for an LLM.

Write and debug Lua scenes for the Fibaro Home Center 3 / Yubii Home (HC3, firmware 5.x) — declarations (triggers and conditions — device, cron, sunrise/sunset, global variables, custom events, central scene buttons), actions code, sourceTrigger, scene variables, restart option, and the choice between a scene and a QuickApp. Use this skill whenever the user wants an automation, a rule, a "when X then Y" on an HC3, converts a block scene to Lua, asks why a scene does not start, or mentions fibaro scenes, even without the word "Lua".

Write release notes from the commits since the last tag. Use when the user asks for release notes, a changelog entry or "what shipped".

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

依据真实调查资料撰写、修改全国大学生市场调查与分析大赛报告，建立发现到建议的证据链，并准备摘要、图表、附录与答辩。用于市调报告成稿、润色、结构诊断及汇报准备。

为小红书撰写种草/干货类中文文案，含标题、正文与标签。当用户说"写篇小红书""帮我写种草文"或给一个产品/主题求文案时使用。

Write a clear git commit message for the staged changes, following the repository's existing convention (Conventional Commits if it uses them). Use when asked to commit, write a commit message, or describe staged changes.

Quy ước chung của TinyCorn Studio cho mọi repo/tool (tạo dự án mới, khởi tạo repo, README, CHANGELOG, .gitignore, commit message, tài liệu, cấu trúc dự án). Use when starting a new project/tool, initializing a repository, writing docs, or when asked about commit/changelog/gitignore conventions. Also use to check existing repos against the standard.

Write a pull request title and description for the current branch from its diff and commits, in the team's PR format. Use before opening a PR.

TypeScript coding workflow and idioms, including React, Next.js, Recharts, and Zod. Use when writing, reviewing, or refactoring TypeScript, TSX, or JSDoc-typed JavaScript, or editing tsconfig.json, package.json, workspace, or Biome, oxlint, or oxfmt config.

Rust coding workflow and idioms. Use when writing, reviewing, or refactoring Rust code, or editing Cargo.toml.

Learn-by-doing mode for any technical task (code, terminal, git, cloud/infra, databases, config, data tooling). The user does the work with their own hands; Claude explains each step — and every part of each command or code fragment the user may not know — before they run it, then inspects and actually verifies what they did and gives a clear verdict (correct / optional improvement / must fix, always with the reason) before moving on. Depth adapts to the user's level in that specific topic, from total beginner to senior engineer. Use this whenever the user invokes /guided-practice or says things like "teach me while I do it", "I want to do it myself", "walk me through it and I'll type it", "explain step by step and check my work", "don't write it for me, guide me", "coach me through this", or asks to be reviewed step by step while they build something. Do not use for ordinary "do X for me" requests where the user wants the result, not the practice.

Writes, debugs, and reviews end-to-end tests that drive a whole app through a browser, a CLI, or an API the way a user would. Covers choosing which journeys deserve an e2e test, stable locators, waiting on conditions instead of time, isolated test data, debugging failures from traces, and fixing flaky tests at the cause. Defaults to Playwright when a repo has no e2e tool yet. Use when adding or changing an e2e test, an e2e test fails or is flaky in CI, or reviewing e2e tests in a diff.

Writes and maintains project roadmaps as Markdown files in the repository. Each roadmap has phases, work items with stable IDs and checkable acceptance criteria, explicit dependencies, a list of unresolved decisions, and a changelog. Use when asked to create, update, reconcile with recent work, restructure, or review a roadmap or delivery plan.

Manages Android performance profiling and debugging. Triggers when the user asks to record or analyze Android performance data, such as system traces, heap dumps, method recordings, callstack samples, memory allocations, or investigate bottlenecks, jank, memory leaks, and app startup issues on Android, or when the user asks to write, debug, or execute ad-hoc SQL queries. Applies to both user and system apps or services.

Set up and run a "chief of staff" session that stands between the owner (the human) and several other Claude Code sessions in the Claude desktop app. It relays the owner's words word for word, gathers every session's questions into one numbered round with recommended answers, keeps hand-offs between sessions moving, resends work that stalled, keeps a short status page, and says when a session needs a fresh restart (with a prompt the session writes for its own replacement). Use this whenever someone runs three or more Claude sessions on one project and wants one point of contact; when they say they're tired of copying messages between sessions, reading every chat, or losing track of who is waiting for whom; when they ask for a manager, coordinator, project-manager, lead or orchestrator session; or when they want long sessions restarted without losing what's in the chat. Use it even if they never say "chief of staff".

Give the human owner a live board, a Claude artifact with its own small database, for everything only they can decide or do. Each decision or task gets its own card, with a recommended answer, answer buttons, steps to tick, text to copy and files; the owner answers from their phone whenever they like, the answer wakes the agent through a comment, and the agent acts and archives the item. Use this whenever an agent has several open questions or owner-only tasks (approvals, uploads, sign-ins, purchases, account changes), when the owner says questions get lost or buried in chat, when they ask for a dashboard, inbox, to-do board, decision board or "desk" for what's waiting on them, or when a chief-of-staff or manager session needs a home for its "waiting for the owner" list.

Shows the skills that /already-told-you:run drafted from your history, lets you pick, shows each file, and installs only the ones you approve - for all projects (~/.claude/skills) or just one project. Never overwrites an existing skill without asking.

Adds the rules from section B of your Already Told You report ("What you keep explaining") to the right CLAUDE.md - yours for every project or one project's - inside a marked already-told-you block. Shows the diff first and writes only what you approve. Re-running refreshes the block instead of duplicating it.

研究某個工具、函式庫、框架或技術，並撰寫一篇給新手看的 HackMD 風格 Markdown 教學文章，內容涵蓋功能特色、安裝方式、使用範例等說明。當使用者要求撰寫教學、教學文章、教學文件、入門指南，或要給 HackMD 用的技術文章時，務必使用此技能——特別是當使用者指名某個具體的技術/產品/工具，並希望得到一篇經過研究、可直接貼到 HackMD 的完整文章，而不只是聊天室裡的簡短回答。當使用者要求使用編號式章節標題（1. / 1.1 / 1.1.1 的格式）的文件風格內容，並打算用於 HackMD 或類似的 Markdown 筆記工具時，也應觸發此技能。產出的文件一律使用繁體中文撰寫。

Create conventional commit messages. Use when the user says "commit this", "save changes", "git commit", asks to commit code, write a commit message, or format git history. Follows conventional commits specification.

Write or update README.md files from folder contents and conversation history. Use when asked to write, refresh, or fix a README.

>- Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers after debugging sessions, mistakes, corrections, architectural decisions, or any insight worth preserving across sessions. Use on 'add to brain', 'remember this', 'write a note', or brain/ modifications.

>- Write, revise, diagnose, or plan scientific prose the way Strunk, Zinsser, Alley, and Heard teach it: journal papers, book chapters and monographs, grant proposals, theses, titles, abstracts, cover letters, responses to reviewers, and reviews. Use this skill whenever the user wants scientific or technical text drafted or tightened, says a passage is dense, wordy, unclear, flat, or reads badly, wants paste-ready revisions for Word, asks what is wrong with a section, asks how to structure a paper or chapter, or asks about a writing rule (active or passive, first person, hedging, starting with because), even when they name no book and never say "skill". Covers writing process, document structure, paragraphs, sentences, words, figures and tables, revision, review, and the author's own standing preferences through an editable house-style file. Not for citation mechanics and reference managers, venue selection or peer-review simulation, developmental editing of a whole monograph, or agent-to-user chat.