Require concise justification before adding new repository extensions or automation.
npx skills add https://github.com/lhohan/agentfiles --skill less-is-more
Please help me install this Agent Skill. Skill: less-is-more Source: https://github.com/lhohan/agentfiles/tree/main/.agents/skills/less-is-more Command: npx skills add https://github.com/lhohan/agentfiles --skill less-is-more
This skill discourages unnecessary expansions of the repository by guiding users to apply the principle before adding new extensions, agents, skills, prompts, packages, or automation.
Review the current need and record a clear justification before adding anything new to the repository.
High-intent search queries and answers about installing and using this skill.
To prevent repo bloat, apply a minimalism principle that requires a concise justification before adding any new extensions, agents, skills, prompts, or packages. This enforces incremental changes and stops feature creep.
Enforcing minimalism in repo management involves implementing checks that require a clear justification for each new addition. Directing changes to documentation for explicit decision records ensures only needed automation is added.
Manage automation change requests by applying a minimalism check that discourages setup growth. Require a concise justification for the new automation and record the decision in documentation to prevent bloat.
Yes, writing decision records is required when adding new prompts or skills. The minimalism workflow directs you to document a concise justification in the repository documentation to prevent unnecessary expansions.
Avoid adding new extensions when you cannot provide a concise justification for the addition. If the change does not serve a clear, needed purpose, the minimalism principle directs you to prevent bloat and skip the expansion.
BerryKuipersRecord code quality metrics before refactoring into a timestamped JSON baseline.
mauricioacpDefine MVP scope and enforce backlog discipline to prevent feature creep.
TabTabGoGenerate, edit, and validate Expo EAS workflow YAML files against schema standards.
Mathews-TomAudit dependency trees for licenses, CVEs, maintenance health, and bloat.
