kest

Key principles for designing reliable, polyglot libraries. Use this skill when making structural or design decisions for the Kest toolkit.

Use this skill when you need documentation for a third-party library, SDK, or API before writing code that uses it (e.g. "use the OpenAI API", "call the Stripe API"). Fetch the docs with chub before answering, rather than relying on training knowledge. Also used for maintaining project-specific context via the :sync-docs task.

This skill should be used when the user asks to "configure moon", "set up moonrepo", "create moon tasks", "run moon commands", "configure moon workspace", "add moon project", "moon ci setup", "moon docker", "moon query", "migrate to moon v2", or mentions moon.yml, .moon/workspace.yml, .moon/toolchains.yml, moon run, moon ci, or moonrepo in general.

Core architectural principles governing the design, layout, and execution of the Kest toolkit. Strictly reference these principles before creating new components or refactoring.

This skill should be used when the user asks to "install proto", "configure proto", "manage tool versions", "pin versions", "set up .prototools", "install node version", "install rust version", "install python version", "proto plugins", or mentions proto commands, .prototools file, or multi-language version management.

Standard software engineering and testing practices (TDD, SRP, DI) for library development. Reference this skill before writing tests or designing new logic.