Skills publicadas
Mostrando 12 de 154adversary
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'.
notebook
Project notes system to prevent AI context loss and reasoning loops. Init notes, save mid-flow, recover context, migrate messy notes, resolve lessons. Subcommands: /notebook, /notebook save, /notebook recover, /notebook migrate.
architect
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.
notebook
Project notes system to prevent AI context loss and reasoning loops. Init notes, save mid-flow, recover context, migrate messy notes, resolve lessons. Subcommands: /notebook, /notebook save, /notebook recover, /notebook migrate.
eat
URL (YouTube, article, X/Twitter thread, podcast) or file path to extract from
eye
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'.
elevate
Shifts the model from compliant executor to critical expert advisor. Identifies the domain, adopts top-tier expert perspective, understands the PURPOSE, returns ranked proposals to elevate the work. Works across UI/UX, copy, architecture, planning, code, strategy, branding. Invoke ONLY via /elevate — do NOT trigger on 'make this better' or 'what am I missing'.
vet
A directory path, file path, or natural language scope like "auth layer" or "API routes". Omit to vet the entire project.
fortify
"setup" = install testing infra only. "check" = audit gaps and report, don't write tests. "full" or omitted = setup + audit + write + run + verify.
recon
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
architect
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.
memento
Context handoff for fresh sessions. Saves unsaved session knowledge to notebook, then produces a short orientation block to paste into a new chat. Use when user says '/memento', 'hand off context', 'prepare for fresh chat', 'save and brief', or before clearing context. NOT for: recovering context (use /notebook recover) or saving a single note.