zio
- 50 skills
- 0 followers
- 17 hours ago last updated
- ▌ Docs Integrate · zioShared 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.
- ▌ Docs Module Ref · zioWrite reference documentation for a module containing multiple related data types. Use when documenting a cohesive domain model (HTTP model, resource management) where types work together. Produces comprehensive type-level pages plus module-level narrative showing relationships, patterns, and composition.
- ▌ Zio HTTP Knowledge · zioStop 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.
- ▌ Docs Document Pr · zio bundleDecide, 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.
- ▌ Setup Skill Hook · zioUse 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.
- ▌ Docs Cross Linker · zio bundleMake 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".
- ▌ Docs How To Guide · zio bundleWrite 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.
- ▌ Docs Data Type Ref · zio bundleWrite 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.
- ▌ Docs Pr Subsection · zioTurn 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.
- ▌ Docs Writing Style · zio bundleProse 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.
- ▌ Docs Enrich Section · zio bundleUse 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.
- ▌ Docs Organize Types · zioOrganize 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.
- ▌ Docs Check Compliance · zioAudit a documentation file against a rule skill. Checks each rule, fixes violations with separate commits, then compiles with mdoc. Reusable across any rule skill and doc file.
- ▌ Docs Mdoc Conventions · zio bundleShared 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.
- ▌ Docs Backfill Metadata · zio bundleFill 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".
- ▌ Docs Reduce Redundancy · zioRemove 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.
- ▌ Docs Verify Compliance · zioFix compliance issues in a documentation file against writing style and mdoc conventions.
- ▌ Docs Companion Examples · zioHow 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.
- ▌ Docs Add Missing Section · zio bundleAdd 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.
- ▌ Docs Skill Retrospection · zioAnalyze 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.
- ▌ Docs List Undocumented Prs · zio bundleScans merged GitHub PRs (from latest commit back to an upstream base ref) and produces a documentation-coverage audit report. Processes 20 PRs per batch and asks before continuing to the next batch. Skips PRs already checked in previous runs using a persistent state file. For each new PR, determines whether documentation is required based on labels, changed files, and content signals, then checks whether docs exist and grades coverage using four rubric levels: Well Documented, Partially Documented, Stub, or Not Documented. Outputs a focused report showing only PRs that require docs, sorted by coverage gap severity. Use this skill whenever the user wants to know which merged PRs are missing documentation, wants a documentation debt audit, or asks "what needs to be documented?", "which PRs have no docs?", or similar coverage questions. Invoke it even if the user just says "doc audit" or "show me undocumented changes."
- ▌ Docs Data Type List Members · zio bundleUse when extracting and categorizing public members from a Scala data type for documentation completeness checks.
- ▌ Docs Report Method Coverage · zio bundleUse when checking if documentation covers all public members of a Scala data type.
- ▌ Docs Find Documentation Gaps · zio bundleFind and report undocumented areas of a ZIO library project that need documentation coverage in the docs directory. Generates a TODO-style report.
- ▌ Docs Organize Reference Docs · zio bundleGroup 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.
- ▌ Critique · zio bundleA coordinator-only critique-fix loop for driving an existing documentation page to approval — a fresh critic delegate reports severity-tagged findings, a fresh fixer delegate resolves them, capped at three rounds with HIGH findings iterating longest and MEDIUM getting one chance. Load when reviewing an already-written page against source, siblings, and consistency, not when writing new content.
- ▌ Cross Linker · zio bundleMake an orphan documentation page reachable — find the existing pages that should mention it, and add one prose link from each, without touching code, headings or frontmatter. Load when retro-fitting links into a docs tree rather than writing a new page.
- ▌ Ascii Diagram · zioHow to produce an ASCII diagram that is actually aligned — generate it from a Python script with a width assertion, never by hand. Use when a page needs a box-and-arrow diagram, such as a module reference's "How They Work Together" section or a tutorial's data-flow picture.
- ▌ Writing Style · zio bundleProse and code style rules for ZIO documentation (reference pages, how-to guides, tutorials). Load whenever writing or editing docs to keep prose consistent, clear, and professional.
- ▌ Enrich Section · zio bundleExpand a thin documentation section — one with a signature and a toy example but no motivation — into one that explains why a reader would choose this API, using the five-part expansion pattern (opening sentence, motivation, contrast, signature, realistic example). Load when a section exists but reads as reference-only, not when it is entirely absent.
- ▌ Markdown Table · zioHow to produce a Markdown table that is aligned and structurally valid — generate it from a Python script with a cell-count and escaping check, never by hand. Use when a page compares things across three or more columns, such as a type roster, an edge-case table, or a variant comparison.
- ▌ Module Subpages · zioHow to write the per-type subpages of a hierarchical module reference — the per-type loop, sub-domain nesting, and the sub-domain index page. Use when a module's design plan chose the hierarchical layout (core-family or multi-domain shapes); a flat module page has no subpages.
- ▌ How To Checklist · zio bundleThe review checklist a ZIO how-to guide must pass before it is considered done. Load when reviewing a finished how-to guide for content, technical accuracy, examples, and integration.
- ▌ How To Structure · zio bundleThe section template, section-design rules, and drafting rules for goal-oriented ZIO how-to guides — including the mandatory Problem section and how its "before" example is fenced. Load when designing a how-to guide's structure before writing.
- ▌ Mdoc Conventions · zioReference for mdoc code-block modifiers and Docusaurus admonitions used across ZIO documentation. Load when writing any documentation that contains Scala code blocks.
- ▌ Backfill Metadata · zio bundleWrite a Docusaurus page's `description` and `keywords` frontmatter from the page's own content — length and form rules, and what makes a keyword worth indexing. Load when filling metadata on an existing page rather than authoring a new one.
- ▌ Reduce Redundancy · zio bundleRemove lexical, structural, and semantic redundancy from a finished documentation page — repeated definitions, decorative transitions, motivations argued twice — without cutting meaning. Load when editing an existing page for repetition rather than writing a new one.
- ▌ Companion Examples · zioHow to commission and verify a page's companion example files — the standalone runnable Scala a page pulls in with mdoc:embed. Use when a documentation page embeds example files rather than relying only on inline mdoc blocks.
- ▌ Tutorial Checklist · zio bundleThe review checklist a ZIO tutorial must pass before it is considered done. Load when reviewing a finished tutorial for content, technical accuracy, examples, and integration.
- ▌ Tutorial Structure · zio bundleThe section template, section-design rules, and narrative-planning method for learning-oriented ZIO tutorials. Load when designing a tutorial's structure before writing.
- ▌ Add Missing Section · zio bundleInsert one missing section — Construction, Predefined Instances, Comparison, Advanced Usage, or Motivation — into an existing data-type reference page, at its canonical position, fully written and mdoc-verified. Load when a required section is entirely absent from a reference page (not when it exists but is thin).
- ▌ Zio Knowledge · zioStop and consult this skill whenever your response would involve any fact or code related to ZIO core or the ZIO ecosystem. Covers: ZIO effects and type aliases (ZIO, Task, UIO, UEffect), fibers and fiber management, concurrency primitives (Hub, Queue, Ref, Semaphore), Software Transactional Memory (STM), ZIO Streams (ZStream, ZSink, ZPipeline, ZChannel), ZIO Test framework and test utilities, ZLayer and dependency injection patterns, error management and error types, scheduling and retries, resource management and scoping, ZIO Config, ZIO Schema, ZIO JSON, ZIO Kafka, and all official ZIO libraries and integrations. Trigger this for any ZIO coding task, type signatures, library features, architectural patterns, or comparisons involving ZIO. Any time you would otherwise rely on memory for ZIO details, verify here instead — your training data may be outdated or wrong.
- ▌ Module Ref Checklist · zio bundleThe review checklist a ZIO module reference must pass before it is considered done. Load when reviewing a finished module reference for the module narrative, layout correctness, type coverage, and examples.
- ▌ Module Ref Structure · zio bundleThe section template and drafting rules for a ZIO module reference — documentation of a cohesive domain model of several related types (e.g. an HTTP model, resource management), flat single-page or hierarchical index+subpages. Load when planning or writing a module reference.
- ▌ Docs Examples · zioShared procedure for creating and documenting companion examples. Covers directory structure, file templates, example creation, compilation, linting, and embedding with SourceFile. Used by docs-data-type-ref, docs-module-ref, docs-how-to-guide, and docs-tutorial.
- ▌ Docs Research · zioShared research procedure for documentation skills. Find source files, tests, examples, patterns, and GitHub history when researching a topic. Used by docs-how-to-guide, docs-tutorial, and docs-data-type-ref.
- ▌ Docs Tutorial · zio bundleWrite a tutorial for newcomers learning a topic in a ZIO library. Use when the user asks to write a tutorial or learning guide that teaches concepts step-by-step in a linear path. Tutorials are learning-oriented (for newcomers with no prior knowledge) unlike how-to guides which are task-oriented.
- ▌ Data Type Ref Checklist · zio bundleThe review checklist a ZIO data type reference page must pass before it is considered done. Load when reviewing a finished reference page for structure, API coverage, technical accuracy, and examples.
- ▌ Data Type Ref Structure · zio bundleThe section template and drafting rules for a ZIO data type reference page (docs/reference/<type>.md). Load when planning or writing an API reference page for a single data type.
- ▌ Organize Reference Docs · zio bundleGroup 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. Load when reorganizing reference docs rather than writing a new page.