Claude Code framework that scaffolds, documents, and maintains your project following Clean Code and SOLID. Detects the stack, generates an opinionated CLAUDE.md, keeps living docs (ADRs/PRDs/plans), and ships specialist subagents that refactor with stack-aware judgment. v1.4 adds Skipper Memory (queryable cited…
Software architect. Reasons about layer separation, dependencies, module boundaries and folder structure. Applies the laws declared in CLAUDE.md (mandatory structure, anti-patterns). Can write structural refactors. Use for "is this structure ok?" or "where should this live?" questions.
The analyst. Runs in an isolated subagent (context fork) when invoked by the update skill. Reads git diff, identifies documentable decisions and writes docs directly. Be conservative — when in doubt, don't write.
Next.js 14+ App Router specialist. Knows RSC, Server Actions, the Container Pattern (Page→Container→presentational), layered architecture (app/actions/data/domain/presentation/global), Supabase SSR, standardized ServerActionResponse, react-hook-form+Zod. Applies the laws from a nextjs-fullstack or nextjs-supabase…
Node.js backend specialist (Fastify + Zod + Drizzle). Knows layered architecture (routes → services → repositories), JWT with @fastify/jwt, global error handling, OpenAPI with fastify-type-provider-zod. Applies the laws from the node-api stack. Can write refactors and new endpoints. Use for Node API.
React Native + Expo specialist. Knows expo-router, data/domain/presentation layers, Zustand, Zod, NativeWind, expo-secure-store, deep linking, Supabase Auth on mobile. Applies the laws from an expo-supabase or expo-node stack CLAUDE.md. Can write refactors and create features. Use for RN/Expo questions.
React + Vite specialist. Knows features-first, TanStack Query, Zustand, react-router, Tailwind/shadcn, Zod. Applies the laws from a react-vite-supabase or react-vite-node stack CLAUDE.md. Can write refactors, extract hooks, create new features. Use for React SPA questions.
The captain. Reads the project context (CLAUDE.md, diff, paths, user intent) and decides which specialist to invoke. Doesn't write code or docs — only routes. Coordinates the team based on the case.
Clean Code and SOLID coach. Reviews specific functions, classes and components. Detects SRP, OCP, LSP, ISP, DIP violations. Refactors directly when asked. Use for "does this component respect SRP?", "refactor", "smells bad", "extract hook".
Supabase specialist. Knows RLS policies, auth flow (cookies + JWT), Storage, Realtime, Edge Functions, SQL migrations, type generation. Applies the laws from CLAUDE.md when Supabase is present. Can write migrations, policies and queries. Use for RLS, auth, queries, migrations, Realtime questions.
Invokes the architect — subagent that reasons about project structure, layers and dependencies. Applies the laws declared in CLAUDE.md. Use for "is this structure ok?", "where should this live?", structural refactors.
Free-form question that captain Skipper routes to the right specialist based on edited paths, intent (keywords) and project stack. Shortcut when you're not sure which specialist to invoke manually. Use for "is this structure ok?", "this smells bad", open questions.
Facilitate a decision (problem then real options then tradeoffs then recommendation) and capture it as a complete, pre-filled ADR — the brainstorm-to-decision loop. Use when you are about to make, or just made, a technical or product decision with real alternatives and want it recorded instead of lost in a chat thread.
Diagnoses the health of docs/ — stale docs (code moved while the doc didn't), stub ADRs/PRDs/plans with unfilled template placeholders, broken intra-doc links, and empty folders. Read-only, reports a severity table. Use periodically or before a release.
Memory-aware grilling to lock the objective before building. Consults the project's existing decisions (ADRs/PRDs) FIRST, then asks only the genuinely-open clarifying questions, and states an explicit goal + acceptance criteria grounded in those decisions. Use before implementing anything non-trivial, or whenever the…
Creates the initial docs/ structure for the project type (app, service or library), with a protocol README.md in each folder, then detects the stack and offers to apply an opinionated profile. Use once when adopting the plugin in a project.
Looks up libraries/patterns in official docs (WebSearch + WebFetch) scoped to the current stack. Useful for "what lib should I use for X?", "shadcn or radix?", "latest TanStack Query API". The stack specialist performs the search and summarizes with judgment.
Invokes the Next.js 14+ App Router specialist. Knows RSC, Server Actions, route handlers, middleware, next-auth, Supabase SSR. Applies the laws from an nextjs- stack. Can write. Use for Next.js questions/refactors.
Invokes the Node.js backend specialist (Fastify + Zod + Drizzle). Knows routes/services/repositories layers, JWT, global error handling. Applies the laws from a node-api stack. Can write. Use for Node API questions/refactors.
Invokes the React Native + Expo specialist. Knows expo-router, data/domain/presentation layers, Zustand, NativeWind, expo-secure-store, Supabase Auth on mobile. Applies the laws from an expo- stack. Can write. Use for RN/Expo questions/refactors.