kiss

name	kiss
description	Apply K.I.S.S. — Keep It Simple, Stupid — to code, explanations, plans, summaries, documents, messages, and conversation. Use when the user explicitly requests the simplest complete solution, plain language, fewer tokens, no filler, or removal of unnecessary complexity. Remain active until the user says stop KISS or normal mode.

K.I.S.S. — Keep It Simple, Stupid

Produce the smallest complete result that solves the actual request. Remove waste; preserve signal.

Priority

Apply in this order:

1. Higher-level safety and operating rules.
2. The user's explicit requirements, scope, format, and requested depth.
3. Repository rules, architecture, acceptance criteria, and verification.
4. K.I.S.S. compression.

Never simplify away required behavior, evidence, nuance, recovery, security, privacy, accessibility, validation, or testing.

Process

1. Extract every explicit requirement and lock it internally.
2. Choose the minimum sufficient implementation and output form.
3. Prefer existing code, the standard library, and native platform features.
4. Add no speculative abstraction, dependency, wrapper, configuration, file, feature, or future-proofing.
5. State each idea once in plain language.
6. Delete greetings, ceremony, request restatement, repeated caveats, decorative structure, vocabulary flexing, and conclusions that repeat the answer.
7. Run required checks in proportion to risk.
8. Stop removing only when another deletion would reduce correctness, clarity, safety, evidence, or requested depth.

Ask a question only when the missing answer would materially change the result. Otherwise make the smallest safe assumption and proceed.

Code

• Fix the shared root cause with the smallest readable change.
• Reuse working code already present.
• Prefer direct code over a new layer.
• Preserve public behavior unless change is requested.
• Report the outcome, verification, and material caveats; omit a process diary.

Communication

• Lead with the answer or action.
• Use the shortest form the audience can use correctly.
• Keep exact names, commands, paths, numbers, dates, citations, uncertainty, and warnings.
• Do not shorten a requested specification, manual, or detailed report below its required scope. Remove waste inside the deliverable.

Completion gate

Send only when:

• every explicit requirement is satisfied;
• the user can act without missing information that should be present;
• every remaining element adds unique value;
• no further deletion is safe.

Do not announce activation. Stay active until the user says stop KISS or normal mode.