- Skills
- 79
- 仓库
- 1
- 职业覆盖
- 6
- 场景覆盖
- 5
- Stars
- ★ 0
Sarthak Chawla 的 Skills 79
sample-skill
暂无简介
synthetic-review-candidate
Candidate for smoke testing an evaluation runner only.
synthetic-review-baseline
Baseline for smoke testing an evaluation runner only.
review
Run the existing user-invoked review bundle and independently adjudicate its findings.
review-adjudication
Verify generated or human review findings before fixing, defending, replying, resolving, or reusing them as learned guidance. Use within a review, review-comment fix, monitor, or readiness workflow.
monitor-mr
Monitor review findings and CI using the shared adjudication procedure.
migrate-to-codex
Migrate supported instruction files, skills, agents, and MCP configuration into Codex project and global files. USE FOR: move existing agent definitions and MCP setup into Codex global configuration, migrate supported skills into Codex project files, convert supported Claude Code configuration to Codex. DO NOT USE FOR: PostgreSQL database migrations, moving a database schema to a new server, unrelated data migrations.
fix-mr-comment
Verify and fix unresolved review claims using the shared adjudication procedure.
create-mr
Create a draft merge or pull request with repository title policy and a concise description; ready creation requires an explicit human request.
web-design-guidelines
Review existing UI code for Web Interface Guidelines compliance. USE FOR: "audit UI accessibility", "sanity-check a site's UX and web interface practices", "check accessibility in UI files and report findings". DO NOT USE FOR: building or redesigning a new UI without a review request.
vercel-react-best-practices
Apply Vercel Engineering performance guidance when writing, reviewing, or refactoring React and Next.js code. USE FOR: "optimize Next.js data fetching and bundle size", "review a React component for performance problems", "read-only performance review of a Next.js page". DO NOT USE FOR: non-React software or general Python performance work.
organization-best-practices
Guidance and enforcement rules for Better Auth's organization plugin. USE FOR: implement multi-tenant organizations teams and role-based access control with Better Auth, model team membership and roles inside each organization, advise on Better Auth organization-plugin team and role structure without changing code. DO NOT USE FOR: generic roles for an auth provider that does not use Better Auth's organization plugin, unrelated authentication providers.
nodejs-backend-patterns
Build production-ready Node.js backend services with Express or Fastify, including middleware, error handling, authentication, database integration, and API design. USE FOR: build a Fastify REST API, structure a Node GraphQL service for a microservices architecture, improve error handling in a Node REST API, create Node.js servers or backend services. DO NOT USE FOR: React component tests, frontend-only implementation or testing.
frontend-testing
Generate or review Vitest and React Testing Library tests for frontend components, hooks, and utilities. USE FOR: "write Vitest tests for a React component", "review coverage gaps in a React hook spec", "review an existing frontend Vitest spec". DO NOT USE FOR: backend or API tests, Playwright or Cypress end-to-end tests, or conceptual questions without frontend code context.
frontend-code-review
Review pending frontend changes or specific frontend files against code-quality, performance, and business-logic checklists. USE FOR: "review a React component diff", "review pending .tsx changes", "review only a .tsx file". DO NOT USE FOR: creating new React components or implementing changes without a review request.
component-refactoring
Refactor high-complexity React components by reducing branching, extracting hooks, or splitting components. USE FOR: "reduce high measured complexity in a large React component", "extract stateful logic into hooks and split a complex component". DO NOT USE FOR: simple or well-structured components, third-party wrappers, or requests that explicitly ask for tests without refactoring.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing.