Writing & Editing

Apply Clean Code, SOLID, and maintainability principles when writing, reviewing, or refactoring application code. Use when improving code quality, reducing duplication, simplifying complex logic, or restructuring code.

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

网文工业化写作引擎（免费公开版）：小说大纲、章节生成、润色、P0-A/P0-B 分级合规质检、快速/深度两档质检（三档结论）、行文逻辑通顺度检测、叙事一致性强制检查、世界观物质/经济自洽检查、设定库跨章自洽、爽点节奏量化、AI味/文风漂移检测。适配番茄、QQ阅读网文平台，内置抽屉项目隔离。

Writes and edits text in simplified technical English, based on ASD-STE100. Use when writing docs, specs, plans, READMEs, comments or commit messages, or when the user asks for plain technical text.

Run the review station on the current branch. Calls the verifier, then the reviewer subagent, and writes a findings summary for the human. Use when a change is ready for review.

Vietnamese academic research, thesis planning, writing, revision and citation checks, adapted from Imbad0202/academic-research-skills. Use for làm luận, tiểu luận, luận văn, khóa luận, đề cương, tổng quan tài liệu and academic follow-ups. Prioritize the current assignment and confirmed project; use Harvard by default or APA when required. Exclude unrelated chat and repository maintenance.

Routes each task to a suitable model tier in Claude Code, Codex, or another agent that can start subagents on a chosen model (for example Gemini CLI or Antigravity CLI), following the user's routing preferences. Keeps small tasks local, delegates discovery, routine coding, and testing to cheaper subagents, and sends difficult decisions and risky reviews to a stronger one. Use when deciding whether to delegate, writing subagent handoffs, or setting routing preferences, or when asked to "save tokens", "use cheaper models", "fan out subagents", "stay inside my quota", or "efficient-frontier-routing help".

Content Research command - write a detailed content brief for a chosen opportunity. Use only when the user invokes cr-brief or asks for the content-research "brief" action. Entry point for the content-research skill.

>- Comprehensive guide and operational framework for engineering world-class, human-grade GitHub READMEs and technical repository documentation. Use whenever creating, auditing, or refactoring a README for open-source tools, self-hosted services, developer utilities, or client-server applications. Enforces clear documentation guidelines, the 30-second rule, dual-audience narrative balance, copy-pasteable quickstarts, and high-signal visual showcases.

>- Create a Clanker Ship ticket for work the person describes, following the team's ticket instructions. Use when the person asks to file, create, open or write up a ticket, bug or task. Fetches the team's live instructions with get_agent_instructions and creates the ticket with create_ticket.

>- Mentor a user who builds a project to learn how it works. They write the core; you do all other work and keep it fun. Use when the user says "teach me", "guide me", "mentor me", "hints only", "no spoilers", "Socratic", or "help me learn X by building it", or when a project file says the project is for learning. Do not use for normal feature work. Do not use when the first request is "just fix it" or "write it for me".

Use when the desk needs a side (LONG, SHORT, or ABSTAIN) and an invalidation level for a market, on a CEX (Bybit V5 linear) or DEX (Hyperliquid perps), from closed bars only. Writes the vote and a failure note; never sizes or sends orders.

Use when evaluating a skill OR plugin's lifecycle across agents: detecting capability degradation after a model update, judging whether a new skill/plugin is effective and fits the user, or auditing whether to keep/rewrite/retire one. Works in WorkBuddy (skills), DeepSeek harness (plugins), and other hosts via adapters. Triggers: '评测这个 skill', '评测这个插件', '模型升级后 skill 还灵不灵', '新 skill 好不好用', '这个 skill 适合我吗', 'deepseek 插件好不好用', '跨 agent 评估能力', '做个 skill 并按评测流程走'.

Use when evaluating a skill OR plugin's lifecycle across agents: detecting capability degradation after a model update, judging whether a new skill/plugin is effective and fits the user, or auditing whether to keep/rewrite/retire one. Works in WorkBuddy (skills), DeepSeek harness (plugins), and other hosts via adapters. Triggers: '评测这个 skill', '评测这个插件', '模型升级后 skill 还灵不灵', '新 skill 好不好用', '这个 skill 适合我吗', 'deepseek 插件好不好用', '跨 agent 评估能力', '做个 skill 并按评测流程走'.

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.

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