Menu
The "Search First" rule and standards for creating pure utility functions and hooks with discovery tags.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
ZGO API development standards including pagination, error handling, and RESTful design
Test patterns, mocking strategies, and organization best practices
Standardized error format, error code clusters, and API client usage for consistent error handling.
Specifications for Zustand stores, React Query hooks, and the Service-Hook-Type pattern with optimistic updates.
Strict rules for environment variable management using Zod validation and src/config/env.ts.
Guidelines for managing internationalization (i18n) in the project using next-intl and unified translation patterns.
| name | utility-tooling |
| description | The "Search First" rule and standards for creating pure utility functions and hooks with discovery tags. |
This skill ensures a lean and consistent codebase by enforcing the "Search First" rule before any new utility or hook is implemented. It provides standards for creating and documenting internal tools.
Before writing a new utility function or React hook, you MUST:
src/utils/index.ts: Scan exports for existing utilities.src/hooks/: Browse file names and signatures for existing logic.date-fns: All date manipulations.lodash-es: Complex object/array operations (use sparingly).validator: Complex string validation.Intl, URL, Crypto, etc.package.json.Use discovery tags in JSDoc headers:
@util: Marks a pure utility function.@hook: Marks a reusable React hook./**
* @util
* @description Format a currency value using Intl.NumberFormat.
*/
export function formatCurrency(value: number) { ... }
src/utils/[category].ts, exported via index.ts, with tests in __tests__/.src/hooks/use-[purpose].ts and follow React Hook rules.[!TIP] Minimalism: Favor native Web APIs over external libraries whenever possible.