Skip to content

coreyhaines31/makerskills / skills/castmate

castmate

Flagged

When you want to pull in the right AI model for the right job: hand a task to another agent CLI (Codex, Claude, Gemini, Grok, Amp, OpenCode, Cursor, Kiro, Antigravity), or send one prompt to several at once for independent opinions, then synthesize. Delegate mode gives one castmate the job, optionally with write access ('have codex write the migration'). Fan-out mode runs read-only reviews in parallel. Rounds mode lets castmates build on and challenge each other's findings. Calls the official CLIs you already have installed and logged in (Gemini CLI needs an API key on personal accounts); no MCP. Triggers on '/castmate,' 'ask codex,' 'have gemini do this,' 'get a second opinion,' 'what would other models say,' 'fan this out,' 'cross-check this with another model,' 'delegate this to codex.' Advisor personas for founder questions go to maker-council. Personal models, casting rules, and run outputs live in ~/.config/makerskills/castmate/.

references/presets/hotspots.md

View on GitHub
# hotspots

Default rounds: 4. Read-only.

You are auditing for high-impact performance bottlenecks, with emphasis on asymptotic complexity and scaling behavior.

Prioritize:
- Hot-path issues over cold-path micro-optimizations
- Large wins with low implementation risk
- Evidence-backed findings over speculative tuning

Look for:
- Accidental O(n^2)+ patterns: nested scans, repeated sort/filter passes, per-item linear lookups
- N+1 access patterns across database, API, filesystem, queue, or cache boundaries
- Unbounded traversal/fan-out work that grows poorly with input size
- Repeated expensive work that should be cached, memoized, batched, or precomputed
- Serialization/parsing churn on hot paths (JSON encode/decode loops, repeated cloning/transforms)
- Large allocations/copies in tight loops instead of incremental reuse
- Missing pagination, streaming, chunking, or backpressure that causes latency/memory spikes

Multi-round rule:
- Prioritize novel hotspots not already reported in prior rounds.
- If you repeat a hotspot, add stronger evidence, better complexity analysis, or a lower-risk fix.

For each finding, include:
- severity: critical | high | medium | low
- confidence: high | medium | low
- location: file path + function/method name
- evidence: exact code path and operation causing the cost
- complexity: define input variables (for example n, m) and estimate before/after Big-O
- impact: expected latency/throughput/memory effect and where it appears
- minimal fix: smallest safe change (index/map usage, batching, caching, pagination, etc.)
- validation idea: benchmark/profiling or test strategy to confirm the gain

Skip tiny micro-optimizations unless they are clearly on a critical hot path.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall