langgenius
Guide for implementing oRPC contract-first API patterns in Dify frontend. Triggers when creating new API contracts, adding service endpoints, integrating TanStack Query with typed contracts, or migrating legacy service calls to oRPC. Use for all API layer work in web/contract and web/service directories.
bunx add-skill langgenius/dify -s orpc-contract-firstLoadingβ¦
web/contract/
βββ base.ts # Base contract (inputStructure: 'detailed')
βββ router.ts # Router composition & type exports
βββ marketplace.ts # Marketplace contracts
βββ console/ # Console contracts by domain
βββ system.ts
βββ billing.ts
Create contract in web/contract/console/{domain}.ts
base from ../base and type from @orpc/contractpath, method, , inputoutputRegister in router at web/contract/router.ts
billing: { invoices, bindPartnerStack }Create hooks in web/service/use-{domain}.ts
consoleQuery.{group}.{contract}.queryKey() for query keysconsoleClient.{group}.{contract}() for API calls{ params, query?, body? } format{paramName} in path, match in params object/billing/* β billing: {})@/types/, use type<T>() helperexport type ConsoleInputs = InferContractRouterInputs<typeof consoleRouterContract>
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.