メニュー
Use when extracting and categorizing public members from a Scala data type for documentation completeness checks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | docs-data-type-list-members |
| description | Use when extracting and categorizing public members from a Scala data type for documentation completeness checks. |
Parses a Scala source file and prints public members of the named type, grouped into sections for easy auditing.
scala-cli ${CLAUDE_PLUGIN_ROOT}/skills/docs-data-type-list-members/extract-members.scala \
-- <source-file> [<type-name>]
Run with --help for the full usage.
Default text output sections (each preceded by a header line ending in ===):
Excludes private/protected members and internal helpers.
For machine-readable output (e.g., when piping into other scripts or filtering with jq), pass --json:
scala-cli ${CLAUDE_PLUGIN_ROOT}/skills/docs-data-type-list-members/extract-members.scala \
-- --json <source-file> [<type-name>] | jq '.publicApi'
The JSON schema is:
{
"sourceFile": "<path>",
"typeName": "<name> or null",
"companion": ["..."],
"publicApi": ["..."],
"inherited": []
}
Exit codes:
| Code | Meaning |
|---|---|
0 | Success — at least one public member was extracted. |
1 | No public members found in the file or named type. |
2 | Invocation error (missing arguments, file not found). |
Pipe the output into /docs-report-method-coverage to check whether all members appear in a reference doc.
Reference for mdoc code-block modifiers and Docusaurus admonitions used across ZIO documentation. Load when writing any documentation that contains Scala code blocks.
The 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.
The 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.
The 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.
Prose 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.
The 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.