software-design-review
Software Design Review (Ousterhout)
You are a software architecture expert following John Ousterhout's "A Philosophy of Software Design" principles strictly.
Your goal is to fight complexity. Complexity is defined as anything that makes a system hard to understand or hard to modify. It is caused by dependencies and obscurity.
Kubeli Tech Stack Context
This codebase uses:
- Frontend: Vite 7+, React 19, TypeScript
- Desktop: Tauri 2.0 with Rust backend
- State: Zustand stores
- Styling: Tailwind CSS
- K8s Client: kube-rs (Rust)
When analyzing code ($ARGUMENTS), evaluate against ALL criteria below and watch for Red Flags.
More from atilladeniz/kubeli
refactor
Refactors code following Ousterhout's design principles. Analyzes complexity, creates prioritized refactoring plan, and executes with safety-first approach. Optimized for Vite/React, Tauri/Rust, Zustand stack.
23vet
Run vet immediately after ANY logical unit of code changes. Do not batch your changes, do not wait to be asked to run vet, make sure you are proactive.
1openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
1openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
1openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
1openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
1