Menu
minimum-diff — change only what was requested; recommend before implementing when asked.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Alpine.js adapter for @stainless-code/alpine-layers; plugin magics, x-layer-outlet, layerStack data, and JS hooks for typed layer stacks
Angular adapter for @stainless-code/angular-layers (signals + DI + imperative renderStack); use when wiring provideLayerClient, renderStack/useStackHandles, useLayerGroup, useMutationFlow, or createStackHook
UI-agnostic layer stack engine for @stainless-code/layers. Use for opening layers imperatively from anywhere, ordered named stacks, typed await or fire-and-forget calls, lifecycle control, blockers, validation, singleton updates, serial or nested layers, multi-stack orchestration, or building a library/framework adapter.
Lit adapter for @stainless-code/lit-layers; open UI from anywhere and manage ordered, named stacks with typed or fire-and-forget `open` via Reactive Controllers and custom elements
Preact adapter for @stainless-code/preact-layers — use for awaitable confirm flows, singleton toasts, nested drawers, stack subscriptions, and custom layer hosts
React adapter for @stainless-code/react-layers; open UI from anywhere and manage ordered, named stacks with typed or fire-and-forget `open`
| name | minimum-diff |
| description | minimum-diff — change only what was requested; recommend before implementing when asked. |
| disable-model-invocation | true |
All reference. Apply every default below for the rest of the turn (or until the user widens scope).
Change only what was requested. No adjacent redesign, restyle, or opportunistic cleanup unless asked.
Done when: every edited path maps to an explicit request.
When the user asks for a recommendation, trade-off, or rationale before implementation — answer first. Do not edit until they confirm.
Done when: the recommendation landed before code changes (unless they already authorized implementation).
When the user names a rule or skill that covers the task, follow it. Do not invent a parallel workflow.
Done when: the named process was loaded and used; freestyle only where it is silent.
