[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FE6TP1HYWY8CMSWRRVXAC6":3,"skill-same:01M7FE6TP1HYWY8CMSWRRVXAC6":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FE6TP1HYWY8CMSWRRVXAC6","principle-keep-it-simple",null,"KISS, YAGNI and obvious code: decides whether a feature, option, flag, layer, dependency or abstraction should exist, presents the minimal version first, keeps what stays readable, and lands each change as if the design had planned for it. Use when proposing, designing, scoping, writing, changing or reviewing code, plans or specs.","Med-Karim-Ben-Boubaker\u002Fkarim-skills","Med-Karim-Ben-Boubaker","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63352044?v=4","01M7FE4PT628J1M137P2SH4M5M","Karim Ben Boubaker","01M7FE4PV4JZRQT69G3TNBR5D0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fprinciple-keep-it-simple\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: principle-keep-it-simple\ndescription: \"KISS, YAGNI and obvious code: decides whether a feature, option, flag, layer, dependency or abstraction should exist, presents the minimal version first, keeps what stays readable, and lands each change as if the design had planned for it. Use when proposing, designing, scoping, writing, changing or reviewing code, plans or specs.\"\n---\n\n# Keep It Simple\n\nEvery feature, command, flag, dependency, layer and pattern is a **liability**: someone must read, test and maintain it for as long as it exists. Build the least that solves the stated problem, write it so a new reader can change it alone, and land each change as if the design had planned for it.\n\n## Should it exist? The need test\n\nRun it on every item before you propose or build it:\n\n1. **Who needs it, for which task, now?** Name the person and the task. \"Might be useful\", \"for flexibility\" and \"best practice\" name no one.\n2. **Is there a cheaper path?** Something that already exists covers it; one README line covers it; it composes from existing pieces; it is a field or a row of data instead of a new command or code path.\n3. **Otherwise, cut it.**\n\nWhat survives gets **the simplest thing that could possibly work** that still meets the real constraints.\n\n## Present less\n\n- **Lead with the minimal version** that solves the stated problem, then a **Cut** list with one reason per item, so the user adds back only what they need.\n- **Every changed line traces to the request.** A nearby refactor, an extra test or a \"while I'm here\" is still unrequested: name it under **Noticed, not done** and keep it out of the diff.\n- **Reuse before you write:** existing code, then the standard library, then an installed dependency, then new code. Dependencies are features too.\n- **Rule of Three.** Abstract on the third repetition, not the first. A design pattern earns its place by solving a problem the code has today; otherwise it is **Speculative Generality**.\n- **Specialise only for a different mechanism.** A new branch, type or component per case needs a genuinely different way of parsing, modelling or processing, not just a different name.\n- **Subtract before you add,** and finish with a **delete pass**: reread the diff and remove every line the task doesn't need.\n\n## Keep what stays obvious\n\n**Complexity** is anything that makes code hard to understand or change. It shows as **change amplification** (one change, many edits), **cognitive load** (what a reader must hold in mind) and **unknown unknowns** (what a reader can't tell they need to know).\n\n- **Names** say what a thing is, in the domain's words (`GLOSSARY.md` when the repo has one). One concept, one name, everywhere. When no precise name comes, the design is murky: fix the design.\n- **Functions** do one thing at one level of abstraction. Extract a piece only when it is simpler to use than what it hides; a chain of pass-through functions raises cognitive load.\n- **No comments.** Say it in a name, a type or a test. The few comments that stay are listed in `remove-comments`.\n- **Locality.** What changes together lives together. Each piece of knowledge has one source of truth (**DRY** is about knowledge, not identical lines).\n- **Consistency.** Do things the way the codebase already does them. A second way to do the same thing is complexity.\n- **Smallest state scope.** Pure functions over mutation, locals over fields, derived values over copies kept in sync.\n\n## Land the change as if designed for it\n\n- **Redesign, then deliver.** Ask: if this requirement had existed on day one, what would the code look like? Move there in small verified steps. Often the right shape is smaller than the current one.\n- **One path.** When you replace an internal API, migrate every caller and delete the old one in the same change. Callers you control need no shims, aliases, flags or deprecation periods.\n- **Expand, migrate, contract** across a deploy boundary (public APIs, stored data, wire formats): add the new form, move readers and writers, then remove the old form. The removal is part of the task.\n- **Boy Scout Rule, scoped.** Tidy the lines the task already changes; anything further goes under **Noticed, not done**.\n\n## What stays\n\nSimplicity cuts scope, not quality. Whatever survives the need test gets finished: tests, error handling at the edges, security and data integrity are part of the feature. **Essential complexity**, the part the problem demands, stays; **accidental complexity** goes.\n\n## Example\n\nA request for a test-runner CLI \"as flexible as possible\" first produced eight commands (`list`, `run`, `show`, `add`, `gold`, `review`, `sign`, `check`), each with flags. After the need test:\n\n```\nProposal\n  e2e run [--set core|optional|all] [--case NAME]\n  e2e check SHA [BASE]\n\nCut\n  list, show   `ls` and the case files already answer them\n  add          rare; one README line covers it\n  gold, sign   a field in the case file, not a command\n  review       `run` followed by `check` composes it\n```\n\n**Terms:** KISS, YAGNI, essential vs accidental complexity, simplest thing that could possibly work, Rule of Three, Speculative Generality, gold plating, scope creep, change amplification, cognitive load, unknown unknowns, Four Rules of Simple Design, ubiquitous language, DRY, Common Closure Principle, principle of least astonishment, strategic vs tactical programming, tactical tornado, parallel change, expand–migrate–contract, strangler fig, Boy Scout Rule, Shotgun Surgery, Divergent Change.\n","# Keep It Simple\n\nEvery feature, command, flag, dependency, layer and pattern is a **liability**: someone must read, test and maintain it for as long as it exists. Build the least that solves the stated problem, write it so a new reader can change it alone, and land each change as if the design had planned for it.\n\n## Should it exist? The need test\n\nRun it on every item before you propose or build it:\n\n1. **Who needs it, for which task, now?** Name the person and the task. \"Might be useful\", \"for flexibility\" and \"best practice\" name no one.\n2. **Is there a cheaper path?** Something that already exists covers it; one README line covers it; it composes from existing pieces; it is a field or a row of data instead of a new command or code path.\n3. **Otherwise, cut it.**\n\nWhat survives gets **the simplest thing that could possibly work** that still meets the real constraints.\n\n## Present less\n\n- **Lead with the minimal version** that solves the stated problem, then a **Cut** list with one reason per item, so the user adds back only what they need.\n- **Every changed line traces to the request.** A nearby refactor, an extra test or a \"while I'm here\" is still unrequested: name it under **Noticed, not done** and keep it out of the diff.\n- **Reuse before you write:** existing code, then the standard library, then an installed dependency, then new code. Dependencies are features too.\n- **Rule of Three.** Abstract on the third repetition, not the first. A design pattern earns its place by solving a problem the code has today; otherwise it is **Speculative Generality**.\n- **Specialise only for a different mechanism.** A new branch, type or component per case needs a genuinely different way of parsing, modelling or processing, not just a different name.\n- **Subtract before you add,** and finish with a **delete pass**: reread the diff and remove every line the task doesn't need.\n\n## Keep what stays obvious\n\n**Complexity** is anything that makes code hard to understand or change. It shows as **change amplification** (one change, many edits), **cognitive load** (what a reader must hold in mind) and **unknown unknowns** (what a reader can't tell they need to know).\n\n- **Names** say what a thing is, in the domain's words (`GLOSSARY.md` when the repo has one). One concept, one name, everywhere. When no precise name comes, the design is murky: fix the design.\n- **Functions** do one thing at one level of abstraction. Extract a piece only when it is simpler to use than what it hides; a chain of pass-through functions raises cognitive load.\n- **No comments.** Say it in a name, a type or a test. The few comments that stay are listed in `remove-comments`.\n- **Locality.** What changes together lives together. Each piece of knowledge has one source of truth (**DRY** is about knowledge, not identical lines).\n- **Consistency.** Do things the way the codebase already does them. A second way to do the same thing is complexity.\n- **Smallest state scope.** Pure functions over mutation, locals over fields, derived values over copies kept in sync.\n\n## Land the change as if designed for it\n\n- **Redesign, then deliver.** Ask: if this requirement had existed on day one, what would the code look like? Move there in small verified steps. Often the right shape is smaller than the current one.\n- **One path.** When you replace an internal API, migrate every caller and delete the old one in the same change. Callers you control need no shims, aliases, flags or deprecation periods.\n- **Expand, migrate, contract** across a deploy boundary (public APIs, stored data, wire formats): add the new form, move readers and writers, then remove the old form. The removal is part of the task.\n- **Boy Scout Rule, scoped.** Tidy the lines the task already changes; anything further goes under **Noticed, not done**.\n\n## What stays\n\nSimplicity cuts scope, not quality. Whatever survives the need test gets finished: tests, error handling at the edges, security and data integrity are part of the feature. **Essential complexity**, the part the problem demands, stays; **accidental complexity** goes.\n\n## Example\n\nA request for a test-runner CLI \"as flexible as possible\" first produced eight commands (`list`, `run`, `show`, `add`, `gold`, `review`, `sign`, `check`), each with flags. After the need test:\n\n```\nProposal\n  e2e run [--set core|optional|all] [--case NAME]\n  e2e check SHA [BASE]\n\nCut\n  list, show   `ls` and the case files already answer them\n  add          rare; one README line covers it\n  gold, sign   a field in the case file, not a command\n  review       `run` followed by `check` composes it\n```\n\n**Terms:** KISS, YAGNI, essential vs accidental complexity, simplest thing that could possibly work, Rule of Three, Speculative Generality, gold plating, scope creep, change amplification, cognitive load, unknown unknowns, Four Rules of Simple Design, ubiquitous language, DRY, Common Closure Principle, principle of least astonishment, strategic vs tactical programming, tactical tornado, parallel change, expand–migrate–contract, strangler fig, Boy Scout Rule, Shotgun Surgery, Divergent Change.\n",{"name":5,"description":7},"main","03f9278801a451ca8b532ae5be7195296143861a","skills\u002Fprinciple-keep-it-simple",0,"https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker","https:\u002F\u002Fkarimbenboubaker.me\u002F","AI Engineer","2026-11-10 22:54:19",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Med-Karim-Ben-Boubaker\u002Fkarim-skills --skill principle-keep-it-simple",{"tool":39,"command":40},"bunx","bunx skills add Med-Karim-Ben-Boubaker\u002Fkarim-skills --skill principle-keep-it-simple",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Med-Karim-Ben-Boubaker\u002Fkarim-skills --skill principle-keep-it-simple","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fprinciple-keep-it-simple\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7FE8Y56P42CZS85V5NWGQ0B","write-walkthrough","Guide you through running a demo yourself that shows a fix or a new feature working: a few numbered steps in the chat, each a command to copy or a click to make, with what you should see.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-walkthrough\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7FE8SY1WVS77ZM15VSX9H08","write-spec","Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-spec\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7FE8Q2ZBJ61N6CEVFCVQPHR","write-questionnaire","Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-questionnaire\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7FE8JMMVYP23YHD3KQ43SH4","write-pr","Writes a PR or MR from a fixed template: the tickets it closes, a summary sketch, before and after evidence that proves each acceptance criterion (screenshots for visible changes), and merge danger (one-way or two-way door, blast radius). Use when opening, writing or updating a pull request or merge request.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-pr\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7FE8EEG42Z95804TK2KT89R","write-issue","Files and moves issues on the repo's tracker (GitLab, GitHub or local files): one kind (bug, feature, chore) and one stage each, a title, the kind's template, and what each later stage needs. Use when filing, relabelling, moving or closing an issue, when work should be recorded instead of done now, or to split big work into child tickets.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-issue\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7FE8AJW55TTN9R3KFHBC9T5","write-for-agents","How to write documents an agent reads: context pointers, information hierarchy, completion criteria, leading words and pruning, plus skill frontmatter and invocation mechanics. Use when creating or editing a skill, AGENTS.md, CLAUDE.md, or any doc an agent reaches through a pointer.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-for-agents\u002FSKILL.md",[],[]]