القائمة
Prefer the smallest change that solves the problem cleanly; one mechanism over many, DRY and KISS over cleverness.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/Kalabint/ChatGPT-Primer --skill smallest-clean-diffيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Trigger when user asks to "prepare next steps", "prep next steps", or signals readiness for autonomous build ("before we build", "pre-flight"). Produces a five-part briefing - 4 ranked design decisions, 4 ranked concerns, 6 ranked questions, an open information request, and unconsidered solution dimensions - from a domain-fitting expert role. When subagents are available, dispatches fresh-context auditors to surface candidates the main thread is anchored against. Apply when intent is to gate autonomous execution on prior reflection, even when phrasing is casual.
If decoding an ambiguous instruction takes more than a few sentences of reasoning, stop and ask instead of guessing.
When asked to estimate something unstated, produce a legible correctable evidence chain rather than refusing or fabricating a number.
| name | smallest-clean-diff |
| description | Prefer the smallest change that solves the problem cleanly; one mechanism over many, DRY and KISS over cleverness. |
The best diff is the one a reviewer can hold in their head. Extra mechanisms, speculative generality, and parallel code paths are costs paid by everyone who reads the code later.
Why: surface area is where bugs and maintenance live; less of it is strictly better when the problem is still solved.
How to apply: solve the actual problem, not an imagined family of future ones. Reuse the existing mechanism before adding a new one. If you introduced two ways to do a thing, remove one.
