Results for “minimal-change”

Guides minimal-diff code changes by defining contracts and invariants, choosing a stable seam, and proving the result with an executed check.

Reviews and repairs risky or unclear code with minimal validated changes, running a fixed-point loop until the diff is clean across two consecutive review cycles.

Keeps AI coding agents tightly scoped to only change what the user explicitly requested, using the simplest viable solution and asking before expanding scope.

Help determine pricing strategy for a product or service using minimalist entrepreneur principles. Use when setting initial prices, considering price changes, or figuring out what to charge.

Drive implementation in the smallest possible meaningful increments, pausing for feedback after each step to keep work reviewable and easy to course-correct.

Delivers a small, bounded code change through inspection, a mini-plan, implementation, testing, review, and adversarial verification. Use for bug fixes, configuration changes, and features expected to touch no more than five files.

极简编辑风预设 — 基于 taste-anti-slop 的低 VARIANCE 配置。克制、留白、排版驱动。适用于作品集、文档站、编辑类产品。

Diagnoses and fixes build, type, and runtime errors with minimal changes, covering TypeScript, PyTorch, and other build systems.

Mixup: Beyond Empirical Risk Minimization

Use when building a minimum viable product with maximum constraints

Pure switch/case reducers for the chota-react-saga template — initial-state file, three-phase async cases per CRUD verb, optimistic mutations with `previousState<Items>` rollback, fall-through SUCCESS/ERROR for toggle and delete.

Orchestrate altering an existing, working feature to new desired behavior by updating tests first, then changing implementation, reviewing, and committing with gated approval.

Flamingo: A Visual Language Model for Few-Shot Learning

**When:** Not important (contact info)

Diagnose and fix retention problems using the Fogg Behavior Model (B=MAP), covering motivation, ability, prompts, and tiny habits.

Review any business decision, plan, or strategy through the minimalist entrepreneur lens, providing a gut-check and simplification advice.

Guide building a minimum viable product the minimalist entrepreneur way — manual first, then processized, then productized. Use when someone is ready to build their first product or struggling with scope.

Multimodal Few-Shot Learning with Frozen Language Models

Apple HIG: Interaction Patterns

Creates minimal, monochrome Keynote-style presentations with arrow-key navigation, accent lines, and mono lists.

Design the small details—triggers, rules, feedback, loops, and modes—that separate good products from great ones, based on Dan Saffer's framework.

LIMA: Less Is More for Alignment

Monitors a watchlist of Polymarket markets and surfaces meaningful shifts in price, volume, comments, or resolution proximity, with position context and optional Bankr integration.

Design the small details -- triggers, rules, feedback, loops and modes -- that separate good products from great ones. Use when the user mentions "microinteraction", "button feedback", "loading state", "toggle design", "animation detail", "interaction polish", "state transitions", or "input feedback". Also trigger when designing form validation responses, progress indicators, confirmation dialogs, or any UI element where the user expects immediate feedback. Covers trigger design, state rules, feedback mechanisms, and progressive loops. For overall UI polish, see refactoring-ui. For affordance design, see design-everyday-things.

Update or correct an existing skill file based on judge feedback or improved understanding.

Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).

Generates ultra-minimalist, editorial-style web interfaces with warm monochrome palettes, typographic contrast, bento-grid layouts, and muted pastel accents, rejecting generic SaaS design trends.

当完成一个创作（文章、产品原型等）后，因自我怀疑或追求完美而犹豫是否发布时

YAGNI-first code-minimalism ladder — before writing code, check in order: does this need to exist? already in the codebase? stdlib? native platform feature? installed dependency? one line? Cuts unnecessary code/tokens while never trading away validation, error handling, security, or accessibility. Triggers on: 'ponytail mode', 'write minimal code', 'don't over-engineer this', 'yagni', 'is there already something for this', 'use native instead of a library', 'keep this simple', 'fewest lines possible', 'lazy senior dev mode'.

当一段改动已经写完、要在收尾或合并前对它做一次独立审查时使用——如"审一遍这条分支、review 这次改动、这批代码有没有问题、帮我把关再合"。先把 BASE..HEAD 生成一份审查包一次读完，再按 correctness / readability / architecture / security / performance 五轴加测试质量逐项判定，输出带 file:line 的 Critical / Important / Minor 分级 findings。composable 层能力单元，通常由 execute-task 在整体验收时调用。不要用于：改动还没写完、只想跑测试、要的是动手修复而不是审查、评审需求或技术方案本身。