
Claude Skills by thedixitjain
github.com/thedixitjain'Avoid the top Replit anti-patterns: ephemeral filesystem, public secrets, port binding, Nix gotchas, and database limits. Use when reviewing Replit code, onboarding developers, or auditing existing Replit apps for common mistakes. Trigger with phrases like \"replit mistakes\", \"replit anti-patterns\", \"replit pitfalls\", \"replit what not to do\", \"replit code review\". '
'Migrate to Replit from Heroku, Railway, Vercel, or local development environments. Use when moving an existing app to Replit, migrating databases, or converting Docker/buildpack apps to Replit''s Nix-based system. Trigger with phrases like \"migrate to replit\", \"heroku to replit\", \"move to replit\", \"replit migration\", \"railway to replit\", \"convert to replit\". '
'Optimize Replit app performance: cold start, memory, Nix caching, and deployment speed. Use when experiencing slow startup, high memory usage, deployment timeouts, or optimizing Replit container resource usage. Trigger with phrases like \"replit performance\", \"optimize replit\", \"replit slow\", \"replit cold start\", \"replit memory\", \"replit startup time\". '
'Implement Replit reference architecture with best-practice project layout, data layer, and deployment. Use when designing new Replit apps, reviewing project structure, or establishing architecture standards for production Replit applications. Trigger with phrases like \"replit architecture\", \"replit best practices\", \"replit project structure\", \"how to organize replit\", \"replit production layout\". '
'Upgrade Replit Nix channels, migrate between database types, and update deployment targets. Use when upgrading Nix channel versions, migrating from Replit DB to PostgreSQL, switching deployment types, or updating system dependencies. Trigger with phrases like \"upgrade replit\", \"replit nix upgrade\", \"migrate replit database\", \"replit version update\", \"replit channel update\". '
| Where new brain files go. Decision protocol for filing brain pages by primary subject, not by format or source. Reference for all brain-writing skills.
Generate a comprehensive repository summary and narrative story from commit history
Use RepoPrompt CLI for token-efficient codebase exploration
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
Use at executor review checkpoints to dispatch the code-reviewer agent with structured context — git range, workflow contracts, and verification evidence.
Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.
Pre-commit review: security scan, quality gates, auto-fix.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Find all FIXME comments across the codebase and fully implement the work they describe. Use when the user asks to fix, resolve, or address FIXME comments, or when running the \"fixme\" command. Runs a discovery script to find every FIXME, expands multiline comment blocks, groups related FIXMEs across files into a single implementation task, completes the full underlying code changes, removes the FIXME comments only after the work is done, and verifies that no FIXMEs remain.
Use when you need to resolve an in-progress git merge/rebase conflict.
Debug REST/GraphQL APIs: status codes, auth, schemas, repro.
\"Retell AI architecture variants \\u2014 AI voice agent and phone call\\ \\ automation.\\nUse when working with Retell AI for voice agents, phone calls, or\\ \\ telephony.\\nTrigger with phrases like \\\"retell architecture variants\\\", \\\"retellai-architecture-variants\\\"\\ , \\\"voice agent\\\".\\n\"
\"Retell AI debug bundle \\u2014 AI voice agent and phone call automation.\\n\\ Use when working with Retell AI for voice agents, phone calls, or telephony.\\nTrigger\\ \\ with phrases like \\\"retell debug bundle\\\", \\\"retellai-debug-bundle\\\", \\\"voice\\ \\ agent\\\".\\n\"
\"Retell AI incident runbook \\u2014 AI voice agent and phone call automation.\\n\\ Use when working with Retell AI for voice agents, phone calls, or telephony.\\nTrigger\\ \\ with phrases like \\\"retell incident runbook\\\", \\\"retellai-incident-runbook\\\",\\ \\ \\\"voice agent\\\".\\n\"
\"Retell AI migration deep dive \\u2014 AI voice agent and phone call automation.\\n\\ Use when working with Retell AI for voice agents, phone calls, or telephony.\\nTrigger\\ \\ with phrases like \\\"retell migration deep dive\\\", \\\"retellai-migration-deep-dive\\\"\\ , \\\"voice agent\\\".\\n\"
\"Retell AI performance tuning \\u2014 AI voice agent and phone call automation.\\n\\ Use when working with Retell AI for voice agents, phone calls, or telephony.\\nTrigger\\ \\ with phrases like \\\"retell performance tuning\\\", \\\"retellai-performance-tuning\\\"\\ , \\\"voice agent\\\".\\n\"
\"Retell AI reference architecture \\u2014 AI voice agent and phone call\\ \\ automation.\\nUse when working with Retell AI for voice agents, phone calls, or\\ \\ telephony.\\nTrigger with phrases like \\\"retell reference architecture\\\", \\\"retellai-reference-architecture\\\"\\ , \\\"voice agent\\\".\\n\"
\"Retell AI upgrade migration \\u2014 AI voice agent and phone call automation.\\n\\ Use when working with Retell AI for voice agents, phone calls, or telephony.\\nTrigger\\ \\ with phrases like \\\"retell upgrade migration\\\", \\\"retellai-upgrade-migration\\\"\\ , \\\"voice agent\\\".\\n\"
Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.
>- Review Playwright tests for quality. Use when user says \"review tests\", \"check test quality\", \"audit tests\", \"improve tests\", \"test code review\", or \"playwright best practices check\".
Comprehensive code review workflow - parallel specialized reviews → synthesis
Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)
Review and refactor code in your project according to defined instructions
Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to \\\"simplify code\\\", \\\"review changed code\\\", \\\"check for code reuse\\\", \\\"review code quality\\\", \\\"review efficiency\\\", \\\"simplify changes\\\", \\\"clean up code\\\", \\\"refactor changes\\\", or \\\"run simplify\\\".
Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to \"simplify code\", \"review changed code\", \"check for code reuse\", \"review code quality\", \"review...
Perform a Maestro-style code review with findings ordered by severity and concrete file references
Perform a Maestro-style code review with findings ordered by severity and concrete file references
Reviews an open pull request against coding standards, security, and test coverage, then posts a structured review comment and either approves or requests changes. Use when the user says review this PR, check the PR, look at PR #N, or review pull request.
Pre-landing PR review. (gstack)
Review code changes only for maintainability risks: unnecessary complexity, poor readability, duplication, weak separation of concerns, and misalignment with repository conventions. Use when the user explicitly asks for maintainability review, code quality review, clean code review, complexity review, readability review, simplification review, or how to simplify changed code without changing behavior.
Review code changes only for performance and efficiency risks (N+1 queries, repeated work, bad asymptotics, missing batching/caching, blocking I/O, memory growth). Use when the user explicitly asks for a performance review of a diff/PR.
Build a human-facing reading guide for a GitHub pull request (where to start, what each file changes, what it impacts) using the reviewer PR session + code graph. Use when the user asks to walk a human reviewer through a PR (\"PR walkthrough\", \"гид по PR\", \"как читать этот PR\", \"проведи по PR\"). NOT a bug review (see review-pr). Requires the reviewer MCP server + base index.
Review a GitHub pull request with the RAG + code-graph pipeline (reviewer MCP server). Use when the user asks to review a PR (\"review PR 123\", \"заревьюй PR\", a PR URL). Requires ParadeDB/Neo4j running and a built base index.
Build or update the reviewer base index (vector store + code graph) from a local repo clone. Use when the user asks to \"index the codebase\", \"build the index\", \"sync the code\", \"rebuild the graph\", \"просиндексируй код\", \"построй индекс\".
Authoring and debugging scripts for Rhinoceros 3D (Rhino 8 and later). Use when asked to write RhinoScript (VBScript / .rvb / .vbs), RhinoPython, or RhinoCommon-based scripts; automate Rhino modeling tasks; build command macros; manipulate Rhino geometry, layers, blocks, or document objects; pick objects from the viewport; control redraw and undo; or load and run scripts from the Rhino Script Editor. Covers `rhinoscriptsyntax`, `scriptcontext`, the `Rhino.*` RhinoCommon namespaces (`Rhino.Geo...
| 設計・アーキテクチャ観点のレビューエージェント。 依存関係、境界設計、データモデル、API設計等の個別スキルへルーティングする。
| パフォーマンス観点のレビューエージェント。 N+1クエリ、メモリ効率、キャッシュ戦略、可観測性の観点でコード変更を評価する。
Roast code with aggressive humor while preserving a factual staff review; --fix can apply selected CRITICAL/HIGH fixes.
| CRITICAL: Use for Robius app architecture patterns. Triggers on: Tokio, async, submit_async_request, 异步, 架构, SignalToUI, Cx::post_action, worker task, app structure, MatchEvent, handle_startup
Interactive onboarding that learns your communication style, audiences, and data sources to configure personalized status briefings. Paste in examples of updates you already write, answer a few questions, and roundup calibrates itself to your workflow.
Router-First Architecture
Deterministic debugging with rr record-replay. Use when debugging crashes, ASAN faults, or when reverse execution is needed. Provides reverse-next, reverse-step, reverse-continue commands and crash trace extraction.
Use when positioning an RSS (Robotics: Science and Systems) submission within the literature — covering the robotics-conference lanes (RSS/ICRA/IROS/CoRL) plus journals and ML venues, handling fast-moving arXiv concurrency in robot learning, keeping self-references double-blind, and turning related work into claim-sharpening contrasts.
> High-performance CLI proxy that reduces LLM token consumption by 60-90%. Transparently rewrites 100+ common dev commands (git, gh, cargo, npm, docker, kubectl, aws, etc.) via PreToolUse hook. Single Rust binary, zero dependencies.