skills

Assisted learning skill for JavaScript developers exploring new technologies. Use when the user wants to learn, understand, or explore a new programming language (Elixir, Swift, Go, Rust, Python, etc.), a new tool or platform (Kubernetes, Docker, Terraform, Redis, Kafka, etc.), or a new architectural approach or paradigm (containerization, microservices, object pooling, distributed systems, event sourcing, CQRS, DDD, etc.). Triggers on: "teach me", "explain", "how does X work", "X for JavaScript developers", "learn X", "what is X", "compare X to JS", "I want to understand X", "show me how X works", "help me learn", "bridge from JS to X", "what's the equivalent of X in Y", or any question about unfamiliar technology from a JS developer's perspective. Does NOT generate project code — provides explanations, comparisons, diagrams, and insights. Stores learning progress in trekker as persistent memory across sessions.

Design, architect, plan, and review software structure. Use when the user says "design the architecture", "plan this feature", "how should we build this", "break this down", "propose approaches for", "what's the best way to structure", "create a technical plan", "think through the design", "evaluate options for building", "review the architecture", "analyze the codebase", "find pain points", "what should we improve", "audit the structure", or any medium-to-large task, structural change, refactoring, creative/idea work, multi-component change, architecture review, or technology selection. Produces multi-solution analysis with tradeoffs, composable module design, and architecture-first implementation plans.