AGENT SKILL

principle-laziness-protocol

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

License 许可
MIT
所属仓库
mmdmcy/fluttAIrbar
最近更新
2026-11-14
Stars
★ 0
Forks
0

01 前言 Front Matter

name
principle-laziness-protocol
description
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

02 资源文件 1

03 SKILL.md 正文

Laziness Protocol

Writing code is cheap for you, which makes over-engineering easy. Counter it by borrowing a human maintainer's fatigue. Aim for the most result with the least code and complexity.

  • Prefer deletion. When asked to refactor or improve, look for removals before additions.
  • Maintain a flat call hierarchy. Avoid deep call chains. A rich interface that hides substantial work is not a deep call chain. If answering a question requires tracing through more than 3 files or layers, flatten it.
  • Consolidate decisions. Do not repeat the same choice in several places. Put it behind one source of truth and pass the result as a simple flag.
  • Minimize the diff. Make the smallest change that solves the problem. Fewer lines beat "elegant" boilerplate.
  • Question the threading. If a task asks you to pass a new signal through types, schemas, pipelines, or similar layers, stop and look for a more direct path.
  • Sweat the small leaks. Remove tiny pass-throughs, representation leaks, and duplicated choices before they spread. Small leaks compound into permanent coordination costs.

Prime directive: If a human developer would find the code exhausting to maintain, it is a bad solution. Be lazy. Stay simple.

04 同仓库更多 Skills

mmdmcy
mmdmcy/fluttAIrbar

fluttairbar

Check the AI command-line tools on this device (Claude Code, Codex, OpenCode, Pi, Cursor Agent, Grok Build, fx, Ori, ZCode) for their installed and newest versions and safe updates, and how much of the Claude, Codex and Cursor subscriptions signed in here is used, which agent skills, hooks and instructions file each coding agent has, and whether conversation history is kept on two devices, with fluttAIrbar's command line `fluttairbar-cli`. Use when asked whether AI tools are up to date, how much usage or limit is left, when a limit resets, before updating an AI command-line tool, or which skills an agent has.

★ 0
mmdmcy
mmdmcy/fluttAIrbar

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

★ 0
mmdmcy
mmdmcy/fluttAIrbar

unslop

Cut AI tells from any writing. Must always apply.

★ 0
mmdmcy
mmdmcy/fluttAIrbar

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

★ 0
mmdmcy
mmdmcy/fluttAIrbar

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for $technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

★ 0
mmdmcy
mmdmcy/fluttAIrbar

teach

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

★ 0