PeekAndPoke

Use when someone asks to apply code style rules, check code style, clean up code style, or follow project code conventions.

Use when working on the klangscript module, implementing klangscript language features, working on the parser or interpreter, or needing klangscript architecture knowledge.

Autonomous tutorial generator — brainstorms a tutorial idea, implements it, self-reviews, and links it into the registry. Designed for /loop.

Use when working with Kraft UI framework, io.peekandpoke.kraft, Kraft components, VDom, Kraft routing, Kraft forms, Kraft modals, Kraft toasts, Kraft popups, or any io.peekandpoke.kraft.* package.

Use when working with ultra libs, io.peekandpoke.ultra, ultra.html events, ultra streams, ultra common utilities, or any io.peekandpoke.ultra.* package.

Use when working on the sprudel / sprudel-ksp module, implementing sprudel DSL functions, writing sprudel tests, or needing sprudel architecture knowledge.

Use when working on the klangblocks module, implementing block editor features, working on AST-to-blocks conversion, code generation, or round-trip testing for the visual block editor.

Use when creating new skills, optimizing existing skills, or auditing skill quality. Guides skill development following Claude Code official best practices.

Use when someone asks to release a new version, cut a release, bump the version, publish to Maven Central, or tag a release. Covers the full repo-wide version bump and release workflow.

Use when someone asks to set up Karakum, generate Kotlin externals from TypeScript .d.ts files, convert a TypeScript library to Kotlin, or wrap a new npm package with typed externals.

Use when writing, reviewing, or fixing Kotlin code style. Enforces import rules, naming conventions, and tooling preferences. Also use when someone asks to check code style, fix imports, or review code conventions.

Use when someone asks to add a library to the docs site, create documentation pages, update the docs site, add a new docs section, or work on peekandpoke.io. Also use when someone mentions "docs-site", "documentation website", or "add to the website".

Updates the three external Kraft example projects to match the current Ultra/Kraft version. Use when releasing a new version or upgrading Kotlin.

Use when someone asks for a six thinking hats analysis, six hats method, thinking hats brainstorm, or multi-perspective analysis on a topic.

Use when creating new skills, optimizing existing skills, or auditing skill quality. Guides skill development following Claude Code official best practices.