kiln

This skill should be used when the user asks to "clean up", "remove slop", "simplify", "unslop", "reduce complexity", "tighten up", "cleanup before PR", "review for unnecessary complexity", "too verbose", "over-engineered", "remove unnecessary code", "AI generated mess", "simplify this branch", "reduce abstractions", "test bloat", "bloated tests", "test case bloat", or tests that only verify library or dependency behavior. Also use it for a dedicated simplification pass after AI generation. Do not use it as a substitute for correctness, security, performance, or architecture review. Report findings by default and apply fixes only when explicitly requested.

This skill should be used when the user asks to "create a Lottie", "generate a Lottie animation", "make a Bodymovin JSON", "fix a Lottie", "make a seamless loop", "make a large Lottie", "make a 30 MB Lottie", or mentions lottie-web, Bodymovin, Skottie, dotLottie, .lottie, or Lottie JSON.

This skill should be used when the user asks to create an infographic from repository documentation, Markdown docs, ADRs, specs, diagrams, research summaries, runbooks, or inline context. It writes copy-paste-ready image prompts by default, and if the user explicitly asks to generate, render, make, or create the actual image and an image generation tool is available, it should pass the generated prompt to that tool.

Teach languages, frameworks, concepts, debugging approaches, and problem-solving in a tutoring style that prioritizes hints, guided questions, and mental models over direct implementation. Use when the user says things like "teach me", "help me learn", "walk me through", "give me hints", "explain this", "don't just solve it", "don't edit my code", or when the user is working through an exercise, tutorial, kata, unfamiliar codebase, or new framework and wants explanation-first help without unsupervised code changes.

A design review and UI improvement skill for frontend interfaces. This skill should be used when the user asks to "review a design", "review a screenshot", "improve the UI", "make this look better", "fix the design", "check spacing", "improve visual hierarchy", "choose colors", "pick fonts", "review my CSS", "review my Tailwind", "make this more professional", "design feedback", "fix the layout", "improve typography", "check contrast", "add depth", "polish the UI", or is working on frontend code (HTML, CSS, JSX, TSX, Svelte, Vue) where design quality matters.

This skill should be used when the user asks to "optimize", "make faster", "speed up", "reduce memory", "improve performance", "reduce latency", "improve throughput", "profile", "benchmark", or mentions "slow code", "too slow", "performance bottleneck", "high memory usage", "allocation pressure", "GC pressure", "cache misses", or "hot path". Also applicable when reviewing code for performance characteristics, estimating the cost of an operation, or selecting data structures for performance.

This skill should be used when the user asks to "review SwiftUI code", "check HIG compliance", "audit iOS design quality", "generate SwiftUI views", "create an iOS screen", "improve SwiftUI design", "iterate on SwiftUI feedback", "fix accessibility in SwiftUI", "modernize SwiftUI code", "check deprecated APIs", "review this screenshot for iOS design", "add animations to SwiftUI", "add haptics to SwiftUI", or is working with SwiftUI views where design quality, accessibility, or Apple HIG compliance matters. Provides 40 enforceable rules, design token references, modern API guidance, animation/haptics patterns, and visual review rubrics for iOS design excellence.