菜单
Route Pkl design work to concise best-practice and advanced-pattern reference catalogs. Use when choosing a Pkl modeling pattern, reviewing configuration design, or looking for versioned official examples without loading a large monolithic skill.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | pkl-pattern-catalogs |
| description | Route Pkl design work to concise best-practice and advanced-pattern reference catalogs. Use when choosing a Pkl modeling pattern, reviewing configuration design, or looking for versioned official examples without loading a large monolithic skill. |
Choose the smallest relevant catalog, confirm the pattern against the installed Pkl version, and prove it by evaluating the real consumer module.
Read best-practices.md for common module design, constraints, amendments, projects, tests, rendering, and editor workflows.
Read advanced-patterns.md for extension points, late binding, generators, package APIs, multi-file output, custom renderers, external readers, command modules, bindings, and code generation.
pkl:test proves the behavior at a real entrypoint.Design OpenAPI component schemas with discriminated variants, constrained primitives, subtype/composition choices, nullability, examples, and invalid-state prevention.
Set up a repository for marketplace-driven AI tooling. Use when onboarding a new repo, refreshing a checked-in marketplace reference, installing core marketplace plugins, or documenting which configured marketplaces should be available by default.
Use when validation, authorization, normalization, or state checks produce facts later code must retain. Replace primitive contracts, flags, sentinel states, string protocols, and call-order conventions with proof-carrying values in any language.
Use when Kotlin work needs type-driven modeling, parse-dont-validate boundaries, semantic package layout, explicit failures, API review, or package cohesion checks.
Pkl engineering for typed configuration contracts, expressions, amendments, evaluation, formatting, tests, projects, dependencies, rendering, and packages. Use when a repository contains `.pkl` modules or `PklProject`, or when configuration behavior should be modeled and enforced with Apple Pkl.
Use when creating or validating referential plugin manifests, marketplace entries, primitive references, or payload-to-reference plugin conversions.