lethilu4796

Generates and validates API documentation, OpenAPI specs, and integration guides. Use when adding or modifying API endpoints.

Expert backend engineer for building server routes, API endpoints, database operations, services, and middleware. Adapts to any backend framework based on project context.

Performs comprehensive code review focusing on quality, patterns, and best practices. Use proactively after significant code changes.

Analyzes database schemas, queries, migrations, and performance. Use for Prisma schema reviews, query optimization, and migration planning.

Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.

Creates and maintains project documentation, README files, API docs, changelogs, and architecture documents. Use after features are completed or when docs need updating.

Expert frontend engineer for building UI components, pages, forms, state management, and client-side logic. Adapts to any frontend framework based on project context.

Designs system architecture, plans features, breaks work into tasks, and makes technology decisions. Use when starting new projects or designing new features.

Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.

Reviews code for OWASP Top 10 vulnerabilities, authentication flaws, and injection attacks. Use proactively after writing API endpoints or auth code.

Mechanical verification of implementation plans. Run on EVERY plan before ExitPlanMode. Checks counts, paths, wiring, policies, examples, and completeness.

Generate a changelog from git history since a tag, date, or commit

Validate database schema integrity and check for common issues

MUST use before any git push to main/master/production, or when user mentions 'deploy', 'going live', 'push to prod', 'ready to ship', 'merge to main', 'release'. Also trigger before any npm publish for CLI tools. Also triggers on: 'audit', 'check vulnerabilities', 'are our deps safe?', 'npm audit', 'yarn audit'.

Run E2E tests or interactive browser verification. Triggers on: 'run e2e', 'e2e test', 'browser test', 'check in browser', 'verify UI', 'interactive test'.

Structured pre-feature requirements gathering. Run before writing any new feature or API endpoint to clarify scope, acceptance criteria, and technical constraints.

Scaffold a new project with standard structure, configs, and CLAUDE.md

Restore session context at the start of every new conversation. Auto-triggers on session start, or when user says 'continue', 'what were we doing', 'where did we leave off'.

Register an existing project in AI MemoryCore. Use when starting work on a new repo or when a project needs its own context file. Triggers on: 'register project', 'add project to memory', 'track this project', 'create project file'.

Scan git diffs for project-specific anti-patterns. Triggers on: 'scan diff', 'check diff', 'anti-pattern check', 'pattern scan', 'review changes'.

Run a comprehensive multi-perspective code review on recent changes. Also triggers on 'is this secure?', 'security review', 'check for vulnerabilities', 'could this be exploited?' for security-focused review.

MUST use when user says 'save diary', 'write diary', 'diary entry', 'update diary', or 'document session'. Also auto-trigger at the end of any significant session (feature shipped, major bug fixed, architecture decision, new project started).

MUST use when user says 'save', 'save session', or explicitly wants to preserve session state. {USER_NAME} does NOT use slash commands — also trigger proactively when significant work has been completed and session context should be persisted. For session endings (bye/done/goodbye), use the session-end skill instead which combines save-session + save-diary.

MUST use when user says 'bye', 'goodbye', 'good night', 'gnight', 'done for today', 'that's all', 'that's it', 'see you', 'see ya', 'let's stop', 'stopping here', 'wrapping up', 'signing off', 'closing down', 'done', 'finished for now', 'talk later', 'cya'. The user does NOT use slash commands — detect these natural session-ending phrases and run the full wrap-up automatically.

MUST use when user describes a multi-step feature to build, says 'let's build', 'new project', 'let's implement', or when a task clearly requires more than 3 steps and no plan exists yet. Do NOT trigger for simple additions like adding a comment, renaming a variable, or single-file changes.

Show project status dashboard across registered repositories

MUST use when user asks 'what's new?', 'any updates?', 'latest versions?', 'breaking changes?', 'should we upgrade?', 'what changed in X?', or when starting a new project to check if dependencies are current. Also trigger proactively at the start of major upgrade sessions.

MUST use after implementing new features or bug fixes, when user asks 'run the tests', 'are tests passing?', 'test this', or before any deployment step. Also trigger when tests were previously failing and fixes were applied.