@wocha/skills
v0.1.0
Published
Wocha agent skills for Cursor and AI coding assistants
Maintainers
Readme
@wocha/skills
Agent skills for integrating Wocha authentication with AI coding assistants like Cursor, Claude Code, and GitHub Copilot. Follows the Agent Skills format.
Installation
npx skills add @wocha/skillsTarget specific agents:
npx skills add @wocha/skills --agent cursor claude-code github-copilotFrom a GitHub repository (development):
npx skills add wocha-dev/wocha/sdks/skillsWhat happens after install
When you ask your AI assistant to "add Wocha login to my app":
- The wocha-quickstart router skill reads
package.json,requirements.txt,go.mod, orGemfile - It detects your framework and selects the matching skill
- The assistant follows step-by-step instructions to install the SDK, configure env vars, and wire up auth
You do not pick skills manually — framework detection handles routing.
Available skills (17)
| Skill | Covers | |-------|--------| | wocha-quickstart | Framework detection router | | wocha-nextjs | Next.js App Router — middleware, server helpers, org switching | | wocha-react | React SPA — PKCE, hooks, protected routes | | wocha-vue | Vue 3 — composables, router guards | | wocha-express | Express — JWT validation, permission middleware | | wocha-python | Python — Management API, FastAPI/Django patterns | | wocha-go | Go — Management API, HTTP middleware | | wocha-sdk | Management API (TypeScript, Python, Go) | | wocha-migration | Migrate from Auth0, Clerk, Firebase, Supabase | | wocha-mfa | TOTP, passkeys, backup codes, org enforcement | | wocha-organisations | Multi-tenancy, membership, hierarchy, SSO per org | | wocha-webhooks | Handler setup, signature verification, retries | | wocha-permissions | SpiceDB schema, checks, relationships | | wocha-testing | Mocks, test sessions, Playwright/Cypress E2E | | wocha-cli | All CLI commands and local dev workflows | | wocha-enterprise | SAML SSO, SCIM, admin portal, custom domains | | wocha-feature-flags | Flag creation, evaluation, org/user overrides |
Framework detection
The quickstart router applies these rules (first match wins):
| Detection signal | Skill |
|------------------|-------|
| package.json has "next" | wocha-nextjs |
| package.json has "react" (not Next/RN) | wocha-react |
| package.json has "vue" (not Nuxt) | wocha-vue |
| package.json has "express" | wocha-express |
| requirements.txt has "django" | wocha-python |
| requirements.txt has "fastapi" | wocha-python |
| go.mod present (HTTP server) | wocha-go |
| Gemfile has "rails" | Rails quickstart docs |
See wocha-quickstart.md for the full decision tree.
Example prompts
Add Wocha authentication to my appSet up Wocha in my Next.js project with protected routesMigrate from Auth0 to WochaAdd passkeys and TOTP MFASet up SAML SSO for my B2B customersDocumentation
- Wocha docs
- llms.txt — full docs index for AI assistants
- Getting started
Package exports
Individual skills are importable via subpath exports:
// Node.js — read skill content programmatically
import { readFileSync } from "fs";
import { fileURLToPath } from "url";
import { dirname, join } from "path";
const skillPath = join(
dirname(require.resolve("@wocha/skills/package.json")),
"skills/wocha-nextjs.md"
);Or use named exports: @wocha/skills/wocha-nextjs.
Manifest: @wocha/skills/manifest → skills/index.json.
