catcatcatstudio

Staged build methodology for software projects: technical spike → design notes → build plan → stage-by-stage execution with professional-grade testing. Use when user says '/architect', 'new project', 'start a project', 'build this from scratch', wants to plan/build with structured methodology, or resumes an in-progress staged build. NOT for: quick scripts or one-off fixes.

X/Twitter content intelligence with a social graph. Scout reply opportunities, pulse- check topic lanes, track competitors, mirror your accounts, prospect clients. Graph- first — built around accounts and topics YOU care about, not generic search. Use when user says 'xray', 'x research', 'search x', 'scout', 'pulse', 'track', 'mirror', 'prospect', '/xray', or needs real-time X discourse / engageme

What to go scorched-earth on — a directory or file path, a URL, or a topic/question. Omit to use the current project or ask.

Design judgment via design-director taste — reads design intent, assesses whether execution serves it, returns opinionated verdict with clear direction. Scales from one element to a whole app. Always judgment, never fixing. Invoke ONLY via /eye — do NOT trigger on 'review the design' or 'how does it look'.

Staged build methodology for software projects: technical spike → design notes → build plan → stage-by-stage execution with professional-grade testing. Use when user says '/architect', 'new project', 'start a project', 'build this from scratch', wants to plan/build with structured methodology, or resumes an in-progress staged build. NOT for: quick scripts or one-off fixes.

Pre-build decision intelligence. Produces opinionated decision brief — the senior- consultant week-1 output before scope, stack, or approach are locked. Surfaces traps and edges, calibrated to project scope (prototype vs production vs enterprise). Use when user says '/recon', 'what to watch out for building X', 'where's the edge', 'common mistakes with X', starts a new project, or hits domain unce

Pre-build decision intelligence. Produces opinionated decision brief — the senior- consultant week-1 output before scope, stack, or approach are locked. Surfaces traps and edges, calibrated to project scope (prototype vs production vs enterprise). Use when user says '/recon', 'what to watch out for building X', 'where's the edge', 'common mistakes with X', starts a new project, or hits domain unce

A directory path, file path, or natural language scope like "auth layer" or "API routes". Omit to vet the entire project.

Adversarial pressure-test of a decision, plan, or piece of work. Articulates the case FOR the current approach, then spawns a subagent to steel-man the best alternative, returns a synthesis with mandatory verdict. Invoke ONLY via /adversary — do NOT trigger on 'what do you think' or 'any concerns'.

What to go scorched-earth on — a directory or file path, a URL, or a topic/question. Omit to use the current project or ask.

URL (YouTube, article, X/Twitter thread, podcast) or file path to extract from

Pro mode — engineering standard enforcement. Forces senior-engineer behavior: root-cause discipline, layer awareness, current-gen API verification, blast-radius thinking, caller-first API design, no stubs, no sycophantic agreement, no unverified assumptions. Invoke via /prodev or 'prodev' — always run via Skill tool, never skip or summarize.