kuya-egg
- 12 skills
- 0 followers
- 15 hours ago last updated
- ▌ Kata · kuya-egg bundleImplement software through small, repeatable, integrated vertical slices with clear exit criteria and honest verification. Use when a design is understood and code needs to be built or changed.
- ▌ Andon · kuya-egg bundleMake software health, failure, degradation, and recovery visible through useful observability and diagnostics. Use when adding logs, metrics, traces, health checks, alerts, incident signals, or operational feedback.
- ▌ Kanso · kuya-egg bundleChoose simple, maintainable software designs by removing speculative complexity, comparing alternatives, and making explicit tradeoffs. Use for architecture, API, data-model, dependency, and scope decisions.
- ▌ Hansei · kuya-egg bundleReflect on failures, incidents, reviews, and completed software work to turn evidence into durable tests, guardrails, documentation, and process improvements.
- ▌ Jidoka · kuya-egg bundleDebug software by making failures visible, reproducing them, finding contributing causes, and adding durable regression protection. Use for bugs, failing tests, incidents, regressions, flaky behavior, and unexplained production errors.
- ▌ Kaizen · kuya-egg bundleImprove software continuously through small, safe, behavior-preserving changes that reduce maintenance cost. Use for refactoring, cleanup, technical debt, naming, duplication, dead code, or post-change polish.
- ▌ Shukka · kuya-egg bundlePrepare software for responsible release, migration, deployment, rollback, and handoff with evidence about compatibility, health, ownership, and recovery.
- ▌ Kodawari · kuya-egg bundleReview software with careful attention to correctness, maintainability, security, operations, and meaningful detail. Use for diffs, branches, pull requests, architecture decisions, or final quality checks.
- ▌ Nemawashi · kuya-egg bundleClarify software goals, constraints, stakeholders, and risks before consequential design or implementation work. Use for greenfield ideas, ambiguous requirements, architecture decisions, or changes where misunderstanding would be costly.
- ▌ Poka Yoke · kuya-egg bundlePrevent software mistakes through strong boundaries, safe defaults, meaningful tests, and mechanically enforced invariants. Use for TDD, validation, schemas, authorization, edge cases, regression coverage, or reliability-sensitive behavior.
- ▌ Genchi Genbutsu · kuya-egg bundleInspect the real repository, environment, dependencies, and runtime evidence before designing or changing software. Use for greenfield construction, unfamiliar codebases, uncertain behavior, or any task where assumptions could create rework.
- ▌ Monozukuri Core · kuya-egg bundleUmbrella skill of the monozukuri suite. Guide consequential software work as durable craftsmanship: inspect reality, simplify deliberately, make small safe changes, prevent defects, verify with evidence, and leave the system maintainable. Use for features, refactors, debugging, reviews, migrations, tests, and releases in greenfield or existing code. Skip for trivial one-line edits, pure questions, and throwaway scripts.