Docs & Writing

varunk130 Skill

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content.

zio Skill

Shared integration checklist for new ZIO library documentation pages. Include after writing any new reference page or how-to guide to ensure it is wired into the site navigation.

zio Skill

Stop and consult this skill whenever your response would involve any fact or code related to ZIO HTTP. Covers: installation and setup, routing (Routes, RoutePattern, PathCodec), handlers and HandlerAspect, the declarative Endpoint API and HttpCodec, client and server configuration, middleware, request/response/headers/cookies, WebSockets, Server-Sent Events, Body and binary codecs, form data, template DSL, OpenAPI documentation and code generation, authentication (basic, digest, bearer, JWT, OAuth, WebAuthn), TLS/SSL/mTLS, testing, ZIO Config integration, Datastar/HTMX integration, migration, and any ZIO HTTP library versions or dependencies. Trigger this even for coding tasks that import zio.http, content that mentions ZIO HTTP features or types, or comparisons involving ZIO HTTP. Any time you would otherwise rely on memory for ZIO HTTP details, verify here instead — your training data may be outdated or wrong.

zio Bundle

Decide, from a bare PR number, whether it needs a full new page, a subsection on an existing page, or nothing at all — then name the right skill for the job, writing nothing itself. Use when the user asks to document a PR and it is not already clear whether that means a new page or an addition to one that exists.

zio Skill

Use this skill once to automatically install the ZIO skill attribution hook. After installation, all commits will automatically track which skills were used and include their versions.

zio Bundle

Make one or more existing ZIO documentation pages reachable by adding inbound prose links from pages that already discuss their subject. Use when a page is finished but nothing links to it, or the user asks to "cross-link", "make reachable", or "fix orphan pages".

zio Bundle

Write a how-to guide on a specific topic in a ZIO library. Use when the user asks to write a guide or walkthrough that teaches how to accomplish a concrete goal using the library's data types and APIs.

zio Bundle

Write a reference documentation page for a specific data type in a ZIO library. Use when the user asks to document a data type, write an API reference for a type, or create a reference page for a class/trait/object.

zio Skill

Turn a GitHub pull request into one subsection appended to a page that already documents the area it touches — no new page, no sidebar edit. Use for a PR that only enhances or fixes something already documented, or when the docs-document-pr skill names this as the subsection case.

zio Bundle

Prose style rules for documentation (reference pages, how-to guides, tutorials). Use this skill whenever writing or editing documentation to ensure consistency, clarity, and professionalism across all docs.

zio Bundle

Use when a documentation section exists but lacks motivation or use-cases — thin sections that show a signature and a toy example but never explain why a reader would choose this API over alternatives.

zio Skill

Organize related data types into logical categories within sidebars.js. Use this skill to group data types by functionality (e.g., "Collections", "Type System", "Resource Management", "DI & Configuration"). Supports manual categorization (specify types and category) or automatic analysis (scan docs/reference/ and suggest intelligent groupings). The skill updates sidebars.js while preserving existing structure, maintains alphabetical order, and verifies syntax validity.

zio Bundle

Shared reference for mdoc code block modifiers and Docusaurus admonitions used across ZIO library documentation skills. Include when writing any documentation that contains Scala code blocks.

zio Bundle

Fill in the missing `description` and `keywords` frontmatter fields on one documentation page, without touching anything else on it. Use when a page has no description or keywords for Docusaurus to index it with, or the user asks to "backfill metadata" or "add frontmatter".

zio Skill

Remove redundant content from documentation. Use when sections repeat information unnecessarily, type definitions appear multiple times, concepts are introduced more than once, or transition words clutter meaning. Reduces cognitive load through deduplication and strategic cross-referencing.

zio Skill

Fix compliance issues in a documentation file against writing style and mdoc conventions.

zio Skill

How to commission and verify a page's companion example files — the standalone runnable Scala a page pulls in with mdoc:embed or SourceFile.print. Use when a documentation page embeds example files rather than relying only on inline mdoc blocks, to delegate the build and check what came back.

zio Bundle

Add a missing section to an existing data type reference page. Use when a required section (such as "Construction", "Predefined Instances", "Comparison", or "Advanced Usage") is entirely absent from an existing docs/reference/*.md file. The user provides the doc path and a description of what section is needed and why.

zio Skill

Analyze a recent docs-* skill execution to close the feedback loop. Identifies deviations from documented workflow, unclear instructions, missing edge cases, and better approaches. Applies targeted improvements to the skill file based on what was learned. Run after any docs-* skill to capture retrospective insights.

zio Bundle

Use when extracting and categorizing public members from a Scala data type for documentation completeness checks.

zio Bundle

Use when checking if documentation covers all public members of a Scala data type.

zio Bundle

Find and report undocumented areas of a ZIO library project that need documentation coverage in the docs directory. Generates a TODO-style report.

zio Bundle

Group an existing reference section into categories — propose the grouping from what the pages document, write each category's index page, and update sidebars.js without moving any file. Use when reorganizing an already-written reference section (any set of pages, not only single-type reference pages), rather than writing a new page.

edbertchan Bundle

Default communication rule, two parts. (1) Brevity: before finishing any response, check whether it would run over roughly 150 words or lean on unexplained jargon. If so, and the user has not explicitly asked for full technical detail in the same turn, replace it with an ELI5 answer under 40 words instead. Also triggers immediately on a literal ELI5 request in the user's message (eli5, ELI5, Eli5, "ELI 5" with a space, or an explicit word cap like "< 40 words"), even with no other context. Fires most often on debugging "why" questions, architecture explanations, and PR summaries. (2) Shape: every response, regardless of length, leads with the outcome or action, skips preamble and closing pleasantries, numbers multi-step work, and states errors matter-of-factly. Consolidates the former i-have-adhd skill's structural rules — that skill's content stays in this repo as the upstream-tracked fork, but its rules now live here as the always-on default instead of behind a separate manual toggle.

edbertchan Bundle

Apply when a product has two (or more) scorers that both emit weights, priorities, or rankings — especially hand-authored theme/report priorities beside learned historical-case tag weights. Name which scorer produced which number; never imply one sets the other unless wiring is explicit.

lyl1015 Skill

分镜剧本写作技能。用户输入一段剧情、粗略想法、短剧梗概、小说片段、广告创意、角色关系或一句话概念时，用这个 skill 将其扩展成类似《星光便利店》格式的可生产 Markdown 分镜剧本：Basic Info、Characters、Fixed Scenes、按时间轴分 Shot 的 Visual/Dialogue/Audio/Emotional Beat 表格、Production Notes、Medium Lock、角色卡与场景 Base 生成计划、视频片段生成计划。凡是用户说“写成分镜剧本、分镜脚本、storyboard script、按上面格式、生成类似这种格式、把这段变成短剧分镜、拆成镜头剧本、60 秒短片脚本”等，都应优先使用本 skill。

lyl1015 Skill

分镜视觉资产生成技能。用户已经有分镜剧本、Storyboard Script、Shot 表、Characters / Fixed Scenes / Script Markdown，或说“从这个分镜剧本生成角色图/场景图/定妆图/场景 Base/道具图/视觉锚点/参考图”时，必须使用本 skill。它不写剧本、不改剧情、不生成视频，专门从已完成剧本中提取涉及到的角色、场景与关键道具，并直接生成或落画布为可复用视觉资产。

lyl1015 Bundle

Use when converting a methodology, SOP, training document, framework, lecture outline, PDF, deck, or dense internal note into a canvas-native course, explainer, or training video workflow.

scaryrawr Bundle

Use this skill to turn a video or audio recording (a talk, meeting, or demo) into written content: documentation, a blog post, tutorial, changelog, or notes. Handles transcription, takeaway synthesis, screenshot/frame selection, and grounded drafting from local OpenAI-compatible media models. Not for real-time transcription, generic video editing, or non-generative media processing.

scaryrawr Skill

Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.

kaakati Skill

Transfer pricing policy design, documentation, and defense aligned with OECD Guidelines and the arm's length principle. USE THIS SKILL when the user asks about transfer pricing, intercompany pricing, TP documentation, arm's length pricing, intercompany transactions, benchmarking studies, comparability analysis, functional analysis, FAR analysis, advance pricing agreements, master file, local file, Country-by-Country Reporting, management fees, intercompany loans, cost sharing arrangements, or MAP/arbitration for double taxation disputes.

kaakati Skill

USE THIS SKILL when the user asks to create an executive summary, build a board presentation, write a board memo, design a strategy deck, synthesize findings into a deliverable, create a recommendation document, build a board-ready report, structure a presentation, or prepare C-suite communication. Trigger terms: "executive summary", "board presentation", "board memo", "strategy deck", "executive briefing", "board deck", "board-ready", "C-suite", "recommendation memo", "synthesis", "deliverable", "presentation structure", "pyramid principle", "SCR", "situation complication resolution", "one-pager", "decision document", "steering committee".

kaakati Skill

Internal controls design and evaluation using the COSO 2013 framework. USE THIS SKILL when the user asks about SOX compliance, COSO framework, control design, internal controls, control environment, risk-control matrices, control deficiencies, material weakness, ITGCs, segregation of duties, control testing, or any engagement involving the design, documentation, or assessment of internal controls over financial reporting. Produces COSO-aligned control frameworks, risk-control matrices, testing plans, and deficiency remediation roadmaps.

mthines Skill

Bounded review-apply-resolve convergence loop for a GitHub PR (draft PRs are fine). Runs up to N=5 iterations of pr-reviewer → implement-suggestion (--resolve-all) → polish simplify, converging until every review thread is resolved — through a fix OR a reply (answered question, recorded rationale) — so the PR is left with zero open threads (only genuine human-judgment flags stay open). On convergence it also refreshes the PR description to match the shipped diff and, best-effort, notes the linked Linear ticket. Use after opening a draft PR to converge the branch to a clean, review-ready state before undrafting. Also converges CI: after each iteration's push it reads the check state and delegates a red mechanical failure to ci-auto-fix, so convergence means zero open threads AND CI not red (--no-ci opts out; create-pr and autonomous-workflow pass it because they own their own CI phase). On a UI PR it also runs the committed preview-spec block against the live preview deployment once at exit (report-only, never

mthines Skill

Review branch changes or a PR for code quality, tests, documentation, and commit hygiene. Routes to the `review-loop` skill for a bounded review-apply-simplify convergence loop, or to `pr-reviewer` directly for a one-shot read-only review. Invoke with /review-changes.

mthines Bundle

Reviews whether a change takes the most optimal approach for its stated intent and, when it does not, researches the code, validates a concretely better approach via holistic analysis, and either proposes it (report mode) or applies it behind a confidence gate (apply mode). Judges four axes — codebase-fit, simplicity, performance, robustness — at the approach level, deferring line-level and failure-mode findings to code-quality, critical, and holistic-review. Stays silent when the approach is already optimal (quiet early-exit). A `plan` mode reviews a drafted plan's approach at plan time (aw-planner Phase 1) — the cheapest moment to switch. Called by the reviewer and pr-reviewer agents, the polish skill, and aw-planner as a default-on lens; also runnable standalone. Triggers on "is this the best approach", "better way to do this", "is this optimal", "optimize this approach", "rethink the approach", "/optimize-approach".