Stats
Actions
Available In
Tags
Plugin
nott
nott — curated agents, skills, hooks, memory + zero-config MCPs for Claude Code. Bundles mcp-lad/mcp-asc/mcp-peer.
What's Inside
Agents10
architect
/architect
Root cause diagnostician. Receives a symptom + code pointers, returns diagnosis with file:line evidence and layer analysis. Read-only Opus advisor. Never fixes — only diagnoses. Absorbs @investigator + @curator + @simplifier roles.
critic
/critic
Adversarial reviewer. Receives an artifact (plan, diff, PR, design doc) and returns severity-tagged findings with file:line citations. Never writes code. Opus advisor, 400-700 token budget per review.
dba
/dba
PostgreSQL & Supabase Database Specialist. Query optimization, schema design, RLS policies, performance tuning, database security.
executor
/executor
Polyglot implementation agent. Writes production-ready Rust, TypeScript, and UI code. Escalates to advisors on uncertainty via advisor-consult skill. Never loops guesses after two failed fixes.
nott
/nott
Brand voice for menot-you `@nott`. Appended to the Claude Code system prompt.
Skills32
nott:advisor-consult
/advisor-consult
Use when an executor hits uncertainty and must escalate to an advisor (@critic, @architect) or a specialist (@security, @dba, @ops). Multi-model arbitration escalates to `/nott:selfreview` via `mcp__nott-peer__ask`. Enforces the Advisor Strategy: one review pass, 400-700 token budget, no loops. Trigger on trade-offs, disagreements, 3rd-fail circuit breakers, or hard-gate surfaces.
nott:brainstorm
/brainstorm
Use when the user is exploring an idea, still choosing scope, or needs design before implementation. Trigger on exploratory language like 'i have an idea', 'what if...', 'does this make sense', 'brainstorm', or 'explore an idea'. Trigger before any creative implementation work when the outcome is still undefined. Do not trigger when the user already asked for direct execution or a concrete fix.
capture
/capture
Use after a hard-won bug fix, non-obvious workaround, or repeated user correction that should become reusable knowledge. Trigger after tricky debugging, repeated operational pain, or an explicit request to remember a preference or rule. Trigger when the insight is specific to this codebase or this user's way of working. Do not trigger for generic knowledge that belongs in public docs or library references.
nott:diagnose-app
/diagnose-app
Use when a running app or bot is broken and the goal is to find the root cause from logs, behavior, or deploy state. Trigger on 'app broken', 'not working', 'deploy down', 'production error', or any running-service failure report. Use after scaffold or iterate when something that already existed stopped behaving correctly. Escalate to /start only when the fix turns into a larger gated delivery project.
nott:frontend
/frontend
Use when the user wants a web page, component, flow, or interface built with strong visual taste and production polish. Trigger on UI requests like 'build this page', 'create a component', 'improve the dashboard', or 'design the frontend'. Trigger when the user wants implementation, not only visual brainstorming. Keep using /brainstorm when the product direction is still undefined.
Stats
Version0.7.0
LanguageShell
Stars0
MaintenanceGood
LicenseApache-2.0
Last Commit
Added
Available In
Safety Signals
Caution
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
External network access
Connects to servers outside your machine
