Loading...
Loading...
Found 8 Skills
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
Bounded codebase exploration and architecture mapping. Use when discovery is needed before implementation. Do NOT use for broad refactoring — use do-plan instead.
Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.
Use when exploring unfamiliar code, mapping architecture, finding symbols or relationships, tracing callers, callees, data flow or dependencies, assessing impact, auditing dead or complex code, or handling explicit Codebase Memory requests. Otherwise skip tasks confined to a supplied known file, tiny one-file check, exact literal, configuration value, error string, or non-code text.
Deep architectural context building for security audits. Use when conducting security reviews, building codebase understanding, mapping trust boundaries, or preparing for vulnerability analysis. Inspired by Trail of Bits methodology.
Load PROACTIVELY when starting work on an unfamiliar codebase or setting up a new project. Use when user says "help me understand this codebase", "onboard me", "what does this project do", "set up my environment", or "map the architecture". Covers codebase structure analysis, architecture mapping, dependency auditing, convention and pattern detection, developer environment setup, and documentation of findings for rapid productive contribution.
Teaches beginners and vibe coders how their own project works in plain, simple English. Explains the architecture, what each file and folder does, how the frontend, backend, database and API connect, how a click becomes a request, and what the runtime is (for example Node.js). Gives a transparent code quality score out of 100, security red flags, a prioritized fix list with ready-to-paste prompts, big-tech best practices, and feature ideas, all as structured cards and tables. Use when the user asks to explain, understand, tour, map, review, score, rate or improve their codebase, asks what a file does or what happens when a button is clicked, asks if their app is safe, or mentions vibe teacher.
Deep codebase analysis — populate wiki with architecture, concepts, entities