kaizen
starsforks
How to install kaizen?
omnigentx/jarvis/kaizen
$npx -y skills add omnigentx/jarvis --skill kaizenRESERVED — Continuous improvement methodology. Apply small iterative improvements, error-proof designs, follow established patterns, avoid over-engineering.
SKILL.md
| 1 | # Kaizen: Continuous Improvement |
| 2 | |
| 3 | Adapted from [NeoLabHQ/context-engineering-kit](https://github.com/NeoLabHQ/context-engineering-kit/tree/master/plugins/kaizen/skills/kaizen). |
| 4 | |
| 5 | > **⚠️ RESERVED:** Available for cross-role use when needed. |
| 6 | |
| 7 | ## Core Philosophy |
| 8 | |
| 9 | Small improvements, continuously. Error-proof by design. Follow what works. Build only what's needed. |
| 10 | |
| 11 | ## The Four Pillars |
| 12 | |
| 13 | ### 1. Continuous Improvement |
| 14 | - Make smallest viable change that improves quality |
| 15 | - One improvement at a time — verify before next |
| 16 | - Always leave code better than you found it |
| 17 | - Iterative refinement: make it work → make it clear → make it efficient |
| 18 | |
| 19 | ### 2. Error-Proofing (Poka-Yoke) |
| 20 | - Make invalid states unrepresentable (use types) |
| 21 | - Validate at system boundaries, safe everywhere else |
| 22 | - Early returns prevent deep nesting |
| 23 | - Fail at startup, not in production |
| 24 | |
| 25 | ### 3. Standardized Work |
| 26 | - Follow existing codebase patterns (consistency over cleverness) |
| 27 | - New pattern only if significantly better |
| 28 | - Automate standards: linters, type checks, tests, CI/CD |
| 29 | - Document "why", not "what", in comments |
| 30 | |
| 31 | ### 4. Just-In-Time (YAGNI) |
| 32 | - Build for current requirements, not imaginary futures |
| 33 | - **Current need → Simple solution** |
| 34 | - Abstract only when pattern proven across 3+ cases |
| 35 | - Optimize based on measurement, not assumptions |
| 36 | |
| 37 | ## Quick Decision Guide |
| 38 | |
| 39 | | Question | Action | |
| 40 | |---|---| |
| 41 | | Is this needed NOW? | If no → don't build it | |
| 42 | | Does a library solve this? | If yes → use it | |
| 43 | | Can I explain in one sentence? | If no → simplify | |
| 44 | | Is there a pattern for 3+ cases? | If yes → abstract | |
| 45 | | Have I measured the bottleneck? | If no → don't optimize | |
People who liked this also viewed
6 picksType
- lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026
- lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026
- lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。 当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026
- lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026
- lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026
- lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026
