Add k8s tooling and extend Claude sample rules (#9)

* Add Kubernetes tooling: helm, kubectx, kluctl, kind, ko, oras

* Extend Claude sample rules: thinking, simplicity, surgical edits, goals, tooling

Add behavioral guidance covering pre-implementation reasoning, minimal
implementations, scoped edits, verifiable success criteria, and tool
preferences (yq for YAML, draft PRs by default).

Author: IvanKuzyshyn

AGENTS.md

@@ -55,7 +55,7 @@ The repository provides a two-step setup process:
    - Detects platform (macOS only currently)
    - Prompts `[Y/n]` for each tool (Enter = yes, `n` = skip)
    - Installs Homebrew if missing
-   - Installs packages: stow, k9s, kubectl, awscli, gh, jq, yq, ncdu, git, go, mise, gitleaks
+   - Installs packages: stow, k9s, kubectl, kubectx, helm, kind, ko, oras, kluctl, awscli, gh, jq, yq, ncdu, git, go, mise, gitleaks
    - Installs casks: ghostty (terminal emulator), raycast (productivity launcher), cursor (AI code editor), docker (Docker Desktop)
    - Installs Rust via rustup
    - Installs oh-my-zsh with plugins (zsh-autosuggestions, zsh-syntax-highlighting)

Brewfile

@@ -7,6 +7,12 @@ brew "ncdu"
 brew "go"
 brew "k9s"
 brew "kubectl"
+brew "kubectx"
+brew "helm"
+brew "kind"
+brew "ko"
+brew "oras"
+brew "kluctl/tap/kluctl"
 brew "awscli"
 brew "mise"
 brew "gitleaks"

configs/claude/.claude/CLAUDE.sample.md

@@ -40,3 +40,67 @@ Always find the root cause. Never fix a symptom or add a workaround.
 # Comments
 
 When writing code comments, describe "why" not "what". Never make descriptive comments that redundantly encode what can trivially be understood by reading well-named variables and functions.
+
+# Think Before Coding
+
+Don't assume. Don't hide confusion. Surface tradeoffs.
+
+Before implementing:
+
+- State your assumptions explicitly. If uncertain, ask.
+- If multiple interpretations exist, present them — don't pick silently.
+- If a simpler approach exists, say so. Push back when warranted.
+- If something is unclear, stop. Name what's confusing. Ask.
+
+# Simplicity First
+
+Minimum code that solves the problem. Nothing speculative.
+
+- No features beyond what was asked.
+- No abstractions for single-use code.
+- No "flexibility" or "configurability" that wasn't requested.
+- No error handling for impossible scenarios.
+- If you write 200 lines and it could be 50, rewrite it.
+
+Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
+
+# Surgical Changes
+
+Touch only what you must. Clean up only your own mess.
+
+When editing existing code:
+
+- Don't "improve" adjacent code, comments, or formatting.
+- Don't refactor things that aren't broken.
+- Match existing style, even if you'd do it differently.
+- If you notice unrelated dead code, mention it — don't delete it.
+
+When your changes create orphans:
+
+- Remove imports/variables/functions that YOUR changes made unused.
+- Don't remove pre-existing dead code unless asked.
+
+The test: every changed line should trace directly to the user's request.
+
+# Goal-Driven Execution
+
+Define success criteria. Loop until verified.
+
+Transform tasks into verifiable goals:
+
+- "Add validation" → "Write tests for invalid inputs, then make them pass"
+- "Fix the bug" → "Write a test that reproduces it, then make it pass"
+- "Refactor X" → "Ensure tests pass before and after"
+
+For multi-step tasks, state a brief plan:
+
+1. [Step] → verify: [check]
+2. [Step] → verify: [check]
+3. [Step] → verify: [check]
+
+Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
+
+# Tools Usage
+
+- For YAML file validation, always use `yq`. Never write a Python script for verification.
+- When opening a GitHub pull request, always open it as a draft unless directly asked to open a normal pull request.

install.sh

@@ -19,7 +19,7 @@ echo "✅ Platform: macOS"
 
 # ── Item registry ──────────────────────────────────────────────────
 
-add_item "homebrew-tools" "16 packages via Brewfile"
+add_item "homebrew-tools" "22 packages via Brewfile"
 add_item "rust"           "via rustup"
 add_item "oh-my-zsh"      "zsh framework"
 add_item "nvm"            "Node.js version manager"