ChivukulaVirinchi

Concrete worked recipes for building canonical shapes in SolidWorks via the Kalpataru MCP — cube, cube-with-hole, cylinder, plate, L-bracket, revolved shaft. Use when the user asks for any of these (or anything similar to them) so the model doesn't have to derive the tool sequence from first principles.

Build a parametric part from scratch in SolidWorks. Sketch-then-feature workflow, correct feature ordering, and how to chain features so the topology stays valid.

How to author a fully-defined SolidWorks sketch via Kalpataru. Geometric entity types, constraints, dimensions, and degree-of-freedom (DOF) tactics.

Diagnose Kalpataru/SolidWorks failures — sketch under-constrained, rebuild errors, missing entities, stale references after topology changes. Use whenever a tool returns ok=false or rebuild_status="failed".

Parametrically edit an existing SolidWorks feature — change a depth, radius, count, or angle without rebuilding the part from scratch. The safest way to modify geometry because no topology changes are introduced.

Read and explore an existing SolidWorks part — its features, faces, edges, and topology. Use when the user wants you to modify or build on top of geometry that's already in the document.

Drive SolidWorks via the Kalpataru MCP server — create parts, query geometry, edit features, and manage documents. Use when the user wants to model anything in SolidWorks (bracket, housing, shaft, gear, assembly, etc.).

Elixir implementation — decision tables, templates, anti-patterns for idiomatic code. ALWAYS use when writing Elixir code, choosing control-flow constructs, writing OTP callbacks, writing tests/TDD, or refactoring toward idiomatic form.

Elixir architectural planning — the decisions made BEFORE writing code. Covers project layout, domain boundaries (contexts, aggregates), data ownership, multi-tenancy, process architecture and supervision, inter-context communication (direct call, PubSub, Registry, GenStage, Broadway, Oban, event sourcing), configuration, resilience (bulkheads, circuit breakers, retries, timeouts), architectural styles (hexagonal, modular monolith, CQRS, event-driven), growing from small to large, distributed systems, and anti-patterns. ALWAYS use when designing, architecting, structuring, or planning an Elixir application. ALWAYS use when choosing between umbrella/single-app, contexts, process placement, or supervision strategy. ALWAYS use when starting a new Elixir project or major refactor. For writing the code itself, also load elixir-implementing.

Code review, debugging, and profiling for Elixir. ALWAYS use when reviewing PRs, debugging issues, or profiling performance. For writing code → load implementing.