Skills catalog

These are the agent skills we use to build JustHold. Each page renders the live SKILL.md from our agents folder so you can read and reuse the playbooks. The application source stays private; the skills are published to showcase how we engineer with Cursor agents.

Foundation

Skill	When to use
`justhold-project`	Anywhere in the JustHold monorepo; stack, three app shells, defaults
`web-service-stack`	Shared Next.js foundation, code placement, three-shell layout
`nextjs-rsc-patterns`	App Router pages/layouts, Server/Client boundaries, proxy
`api-supabase-routes`	REST handlers with auth gate, Zod, scoped Supabase queries
`supabase-clients`	Server, browser, and service Supabase clients (never expose service role)

Product conventions

Skill	When to use
`justhold-i18n`	Locales, messages, admin English-only exception
`justhold-design-tokens`	Palette, Fraunces/Geist fonts, radius
`justhold-ui-layout`	UI primitives and public / member / admin shells
`justhold-mdx-content`	Admin CMS MDX posts (Supabase metadata + R2 bodies)
`cursor-style-desktop-demo`	Landing multi-window Play demos (Cursor get-started style)

Quality and process

Skill	When to use
`justhold-testing`	Vitest unit/integration and Playwright e2e
`justhold-git-commits`	Step-narrative commits; split diffs; message style

How to reuse

Open a skill page above and copy the body into .agents/skills/<id>/SKILL.md in your project (or your Cursor skills folder).
Keep the YAML frontmatter (name, description) so agents can discover the skill.
See Agents for how skills and rules fit together.

Vendored helpers such as supabase, shadcn, and migrate-radix-to-base stay in-repo for our agents but are not published page-by-page here.

Private app, public playbooks

JustHold’s application code is private. These skills are shared so others can reuse our engineering conventions with Cursor agents.