All authors
Claude Skills by theishandubey
github.com/theishandubey13 skills0 installs0 views
- Benchmark ChecklistVet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.Votes: 0GitHub stars: 2
- Diagnosing BugsDiagnosis loop for hard bugs and performance regressions. Use when a bug fix needs real diagnosis - the cause is not obvious, the bug is intermittent, or something got slow - or when asked to diagnose or debug.Votes: 0GitHub stars: 2
- Parallel BuildOrchestrate a parallel implementation run - split plans into file-disjoint tasks, dispatch parallel-implementer agents in isolated worktrees, merge their branches back one at a time and verify the integrated result. Use in the main session for work sized for 2 or more simultaneous implementers.Votes: 0GitHub stars: 2
- Plan ExecutionHow workers execute a handoff plan or spec from the orchestrator - drift check, verify gates, scope, STOP conditions, approvals and the report. Preloaded by implementer, parallel-implementer, fixer and doc-writer.Votes: 0GitHub stars: 2
- Plan HandoffHow planning advisors write implementation and rollout plans for a worker with zero context - file location, numbering, the plan template, the index and the quality bar. Preloaded by architect, backend-engineer, frontend-engineer and sre.Votes: 0GitHub stars: 2
- PortlessSet up and use portless for named local dev server URLs (e.g. https://myapp.localhost instead of http://localhost:3000). Use when integrating portless into a project, configuring dev server names, setting up the local proxy, working with .localhost domains, or troubleshooting port/proxy issues.Votes: 0GitHub stars: 2
- Principle Attack The PremiseApply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.Votes: 0GitHub stars: 2
- Receiving Code ReviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationVotes: 0GitHub stars: 2
- Supabase Postgres Best PracticesPostgres best practices maintained by Supabase, for Postgres running anywhere: schema design, column types, indexes, migrations, RLS policies, connection pooling, locking and query performance. Use when designing or reviewing a Postgres schema, migration or RLS policy, writing non-trivial SQL, or diagnosing slow queries, timeouts, connection exhaustion, locking or bloat.Votes: 0GitHub stars: 2
- TestingHow implementers and fixer test their changes - unit tests for every change, end-to-end tests only when the user asks, the shape of each, setting up a harness, how to run them and output discipline. Preloaded by implementer, parallel-implementer and fixer.Votes: 0GitHub stars: 2
- UnslopCut AI tells from any writing.Votes: 0GitHub stars: 2
- Vercel React Best PracticesReact and Next.js performance guidelines from Vercel Engineering - waterfalls, bundle size, server components, data fetching, re-renders and rendering. Use when writing or reviewing React or Next.js code where performance matters; read only the rule files that apply.Votes: 0GitHub stars: 2
- Verification Before CompletionUse when about to claim work is complete, fixed, or passing, before reporting a task done, committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysVotes: 0GitHub stars: 2