SuperAPI AI Directory
Partner中文AI newsFavorites

Skills

Find an Agent Skill for your task. Read the guide and copy the install command.

Updated 11-15 00:13

Coding & development

41,168 results

react-performance

Make React and Next.js performance changes that are measured, evidence-backed, and behaviorally safe. Routes to the right rule catalogue — vercel-react-best-practices for the 72 prioritized React/Next rules, vercel-composition-patterns for component API shape, next-best-practices for App Router semantics, core-web-vitals and performance for field metrics and non-React budgets — then governs how a rule is applied here: baseline first, one hypothesis at a time, behavior tests unchanged and green, and the house functional and typing rules winning where a micro-optimization would trade them away. Use when React or Next.js feels slow — a search box or list that stutters or lags while typing, a page that burns CPU while it sits open, a sluggish dashboard, jank on scroll, a screen that takes too long to appear — when a bundle, waterfall, re-render, or hydration problem is suspected, when reviewing a diff for performance, or when a performance rule appears to conflict with immutability, TDD, or type-safety guidance. For rendering-tier decisions and browser-observable proof see front-end-testing and react-testing; for flow logic driving the re-renders see xstate.

Coding & development6 installs

render-code-shape

Render the shape of code — module boundaries, the types that cross them, signatures, and a cited call graph — for code that already exists or a change about to be built. Every name, type, and path is read from source and cited, or marked NEW; bodies collapse to one line of intent. Use when asking how something composes, tracing what a request actually touches, pseudocoding a change before implementing it, onboarding to an unfamiliar path, or producing the shape a plan and its tests will be checked against. Read-only: the render is the deliverable, never the edit. For judgments about whether the shape is good see codebase-design; for where files should live see structure-codebase; for a rendered picture see diagrams; for fault localization see debugging.

Coding & development6 installs

eliteforge-java-fe-consensus-spec

Constrains the frontend-backend interface consensus for the EliteForge Java project. When the user designs interfaces, API contracts, interface documentation, Controller input/output parameters, frontend-backend integration contracts, request/response structures, Param/VO, unified response body, service status codes, error codes, paginated responses, request methods, request URLs, Long field precision, enum CODE, Accept-Language internationalization, or mentions "frontend-backend consensus" "response content"…

Coding & development6 installs