Use cases
Use cases
The prompts below are samples. Each shows which Skill Claude Code would load and what it points to.
Add an API client for a new service
A new backend publishes an OpenAPI spec and the app needs typed hooks for it.
Sample messages
- Sample prompt: “Add an api-client package for the orders service from its swagger spec.”
- Skill: kubb-react-query
- Uses: @cogs/fetch-client, @cogs/react-query, @cogs/kubb-transforms
Make a list page shareable
A table’s filters and page reset when someone shares the link.
Sample messages
- Sample prompt: “Paginated, filterable table with shareable URLs; reset the page on filter change.”
- Skill: nuqs-table-url-state
- Uses: @cogs/nuqs
A 401 right after deploy
A service deployed cleanly, but every call to an upstream API now fails auth.
Sample messages
- Sample prompt: “Fresh 401 after deploying to Render; check the env vars.”
- Skill: env-doctor, then config-lint for the local files
- Uses: cogs-env-doctor check, config-lint
Convert a form
A form built from raw inputs and useState needs validation from the API’s schema.
Sample messages
- Sample prompt: “Convert this form to shadcn Form with zodResolver and the generated schema.”
- Skill: shadcn-react-hook-form-forms
- Uses: react-hook-form, zod, optionally @cogs/react-hook-form
Install the plugin or a package
The plugin installs from the catesworks/cogs marketplace in Claude Code; the published @cogs/* packages install from npm with no auth token. There is no hosted service and no account.