encurehq
- 7 skills
- 0 followers
- 17 hours ago last updated
- ▌ Add Issue · encurehqDraft and publish a Linear issue whose description is a complete, phased execution plan another agent can pick up cold and run. Use when the user says "create a Linear issue for X", "file a ticket for X", "add an issue to Linear", "write up a plan and put it in Linear", or wants work handed off to a teammate/agent via a Linear issue rather than implemented right now.
- ▌ Elysia Zod · encurehq bundleDecode Elysia + Zod validation errors fast. Use when an HTTP request to an Elysia backend returns 4xx (especially 400 or 422) and the response body/logs contain a Zod valueError/customError. Maps the six most common error shapes to their exact fixes. Assumes drizzle-zod (createInsertSchema/createSelectSchema); adapt for hand-written schemas.
- ▌ Elysia Pattern · encurehq bundleScaffold a new Elysia + Drizzle + Zod backend module the canonical way — a Repository/Policy/Service trio, a routes file, and a one-line registration in the aggregator. Use when the user says "add a new module/resource/table to the backend", "create a service for X", "add CRUD endpoints for Y", or needs a new Elysia route group backed by a Drizzle service.
- ▌ I18N Next Intl · encurehq bundleKeep next-intl translations in sync across every locale. Use whenever you add or change a user-facing string — a new t("...") call, a useTranslations namespace, a toast, a button or form-field label, a dialog title/description, or an error message. next-intl ships one JSON message file per locale; touch one locale and the others render the literal {namespace}.{key} at runtime.
- ▌ Setup Agent First · encurehq bundleSetup repo as agent-first docs - bootstraps or retrofits a repository with AGENTS.md, structured how-to/reference/explanation docs, an ADR convention, and an optional automation layer, so AI coding agents can work in it without per-session hand-holding.
- ▌ Next Tanstack Query · encurehq bundleUse when reading or writing data in a Next.js App Router app with TanStack Query — a data fetch or mutation, prefetching for a route, hydrating a client query, a form or dialog that submits, an optimistic update, or cache invalidation after a write. Use when the user says "fetch X", "load data for", "prefetch", "hydrate", "table blanks when I search", "mutate", "submit form", "optimistic update", "toast on success", "invalidate cache after a write", or "rollback on error".
- ▌ Next Monorepo Pattern · encurehq bundleUse when working in a Next.js App Router monorepo with a shared packages/ui — adding a route/page, a form or dialog, a list/table component, or deciding where a component/hook/util belongs. Use when the user asks where a component/hook/util/page should live, whether something is server or client, or whether a form should be role-specific. For the data-fetching/mutation pattern itself (prefetch, hydrate, useQuery, server actions, optimistic updates), see next-tanstack-query.