react-native-patterns
React Native / Expo patterns for Frappe-backed mobile apps. Reference for Axios API calls, React Query v4, Redux Toolkit, React Navigation, expo-location,…
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-14 00:15
Coding & development
41,046 results
confidence-check
Pre-implementation confidence check. Used before starting complex tasks such as new feature development, bug fixes, and code refactoring. Triggered automatically, no manual invocation required.
unopim-backend-dev
Backend PHP development for UnoPim. Activates when writing PHP code, creating classes, models, repositories, events, listeners, or tests; or when the user…
unopim-datagrid
DataGrid development for UnoPim admin panel. Activates when creating or modifying listing pages, adding columns, actions, filters, or mass actions; or when the…
unopim-git
Git and GitHub operations for UnoPim. Activates when creating branches, writing commit messages, or creating pull requests; or when the user mentions git,…
vaadin-usage-review
Reviews Vaadin code for custom workarounds where an official Vaadin API or component already exists, and reports them without editing anything. Use when asked…
react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js…
woocommerce
WooCommerce development for WordPress e-commerce including custom product types, payment gateways, shipping methods, hooks, REST API, and store optimization.…
wp-theme-development
WordPress theme development best practices and standards. Use when building new themes, creating custom templates, implementing theme features, working with…
fullstack-product-specification
Define fullstack product changes with clear UI journeys, API contracts, domain model updates, non-functional requirements, and release constraints. Use this…
nodejs-nestjs-backend-microservices
Build Node.js and NestJS backend microservices with contract-first APIs, resilient runtime behavior, secure defaults, and operational readiness. Use for…
cspell
This skill should be used when users encounter cspell unknown word warnings, spelling errors from cspell diagnostics, or CI/linting failures on unrecognized…
inspect-deps
Audit and test dependency version upgrades in an isolated worktree with before/after trade-off analysis.
api-and-interface-design
Guide stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing frontend-backend boundaries.
code-simplification
Simplify code for clarity. Use to refactor code to improve clarity without changing behavior; use when code works but is harder to read, maintain, or extend than it should be; use when reviewing code that has accumulated unnecessary complexity.
constraint-driven-development
Establish a project's quality line as a written contract, and stop the agent from quietly lowering it. Through interviews, determine which dimensions the user cares about; when the user has no numbers in mind, provide reasonable default thresholds; record everything in CONSTRAINTS.md; and watch the diff for signs of the quality line being weakened—newly added @ts-ignore or eslint-disable...
doubt-driven-development
Before every non-trivial decision is finalized, conduct an adversarial review with a fresh context. Use it when you want to cross-examine every assumption before proceeding, stress-test a plan to expose hidden failure modes, when correctness matters more than speed, when working with unfamiliar code, when the risk is high (production auth, security-sensitive logic, high-risk migrations, irreversible operations), or whenever verifying a confident output now is cheaper than debugging it later.
incremental-implementation
Deliver changes in thin, verifiable increments. Use when implementing any feature or change that touches multiple files, or when picking up the next task in a plan. Use when rolling out a change behind a feature flag, when about to write a lot of code at once, or when a task is too large to land in one step.
performance-optimization
Optimize the frontend, backend, query, and database performance of an application. Use when there are performance requirements, a performance regression is suspected, Core Web Vitals or load times need improvement, N+1 query patterns need to be fixed, or profiling exposes bottlenecks.
source-driven-development
Ground every implementation decision in official documentation. Use when you want to verify an approach against official docs before implementing, or when you need authoritative, source-cited code that doesn't contain outdated patterns. Use when building with any framework or library where correctness matters.
spec-driven-development
Create a spec before coding. Use when starting a new project, feature, or major change and there is no specification yet. Use when writing a PRD or requirements document with goals and scope, or when requirements are unclear, ambiguous, or just a vague idea. Use when a single requirement spans multiple independently testable capabilities and needs to be decomposed into a module capability map before specification.
compose-recomposition-performance
Use when investigating Jetpack Compose recomposition performance, skippable/restartable composables, composables.txt or compiler reports, Layout Inspector…
compose-side-effects
Use when writing or reviewing Jetpack Compose code with LaunchedEffect, DisposableEffect, SideEffect, rememberCoroutineScope, rememberUpdatedState,…
compose-slot-api-pattern
Use when designing or reviewing a reusable Jetpack Compose component whose visual regions vary by caller, or when primitive content parameters and boolean…