How do I install the Permix skill?

Run npx skillmds@latest add letstri/permix in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Permix safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Permix?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Permix free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Permix?

letstri (@letstri) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Permix by letstri — Agent Skill

Name: Permix
Author: letstri

Permix

Applies Permix authorization once a schema exists: permix.check() paths and ReBAC callbacks, frontend bindings (permix/react, permix/vue, permix/solid, permix/svelte) with SSR dehydrate/hydrate for Next.js and TanStack Start, and server middleware (permix/express, hono, fastify, nest, trpc, orpc, node, elysia). Use for anything past initial setup — checking permissions, gating UI, or protecting routes. For creating the schema and first `permix.setup()`, use permix-getting-started first.

letstri 45f2b62 4 files · 14.6 KB Updated Sep 17, 2026

File contents

Permix — check, frontend, server

Assumes a permix instance already exists (see permix-getting-started). Load the reference file that matches the task instead of reading everything:

Task	Reference
`permix.check()` paths, callbacks, `~all`/`~any`, ReBAC/ABAC with entity data, `isReady`	references/check.md
React, Vue, Solid, or Svelte UI — `PermixProvider`, `usePermix`, `createComponents`, SSR `dehydrate`/`hydrate` for Next.js / TanStack Start	references/frontend.md
Protecting Express, Hono, Fastify, NestJS, tRPC, oRPC, Node, or Elysia routes — `setupMiddleware`, `checkMiddleware`, or Nest `guard` / `@Check`	references/server.md

Rules that apply everywhere

Authorization must run on the server. Client-side check (React/Vue/Solid/Svelte) is UX only — mirror every path with checkMiddleware in references/server.md.
Use the same schema and path strings (post.update, not ad-hoc strings) across client hooks and server middleware, or types and behavior drift apart.
check before isReady throws PermixNotReadyError — gate UI with isReady/isReadyAsync, and call setupMiddleware before checkMiddleware on the server.
SSR hydrate alone is not enough. It only restores booleans; call setup again on the client for function-based/ReBAC rules — see the SSR section of references/frontend.md.

---name: permixdescription: Applies Permix authorization once a schema exists: permix.check() paths and ReBAC callbacks, frontend bindings (permix/react, permix/vue, permix/solid, permix/svelte) with SSR dehydrate/hydrate for Next.js and TanStack Start, and server middleware (permix/express, hono, fastify, nest, trpc, orpc, node, elysia). Use for anything past initial setup — checking permissions, gating UI, or protecting routes. For creating the schema and first `permix.setup()`, use permix-getting-started first.---# Permix — check, frontend, serverAssumes a `permix` instance already exists (see **permix-getting-started**). Load the reference file that matches the task instead of reading everything:| Task | Reference || --- | --- || `permix.check()` paths, callbacks, `~all`/`~any`, ReBAC/ABAC with entity data, `isReady` | [references/check.md](references/check.md) || React, Vue, Solid, or Svelte UI — `PermixProvider`, `usePermix`, `createComponents`, SSR `dehydrate`/`hydrate` for Next.js / TanStack Start | [references/frontend.md](references/frontend.md) || Protecting Express, Hono, Fastify, NestJS, tRPC, oRPC, Node, or Elysia routes — `setupMiddleware`, `checkMiddleware`, or Nest `guard` / `@Check` | [references/server.md](references/server.md) |## Rules that apply everywhere- **Authorization must run on the server.** Client-side `check` (React/Vue/Solid/Svelte) is UX only — mirror every path with `checkMiddleware` in [references/server.md](references/server.md).- **Use the same schema and path strings** (`post.update`, not ad-hoc strings) across client hooks and server middleware, or types and behavior drift apart.- **`check` before `isReady`** throws `PermixNotReadyError` — gate UI with `isReady`/`isReadyAsync`, and call `setupMiddleware` before `checkMiddleware` on the server.- **SSR `hydrate` alone is not enough.** It only restores booleans; call `setup` again on the client for function-based/ReBAC rules — see the SSR section of [references/frontend.md](references/frontend.md).

Frequently asked questions