packages/cli/skills/pikku-schema-cfworker/SKILL.md
Use when setting up JSON schema validation for Cloudflare Workers in a Pikku app. Covers CFWorkerSchemaService as a lightweight alternative to AJV. TRIGGER when: code uses CFWorkerSchemaService, user asks about schema validation on Cloudflare Workers, or @pikku/schema-cfworker. DO NOT TRIGGER when: user asks about AJV schema validation (use pikku-schema-ajv).
npx skillsauth add pikkujs/pikku pikku-schema-cfworkerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill as an execution checklist, not reference material.
pikku-meta when available; otherwise run the relevant pikku meta ... --json command and inspect only the focused output you need..pikku, node_modules, vendored packages, or broad build artifacts.pikku-verify or pikku all when functions, wirings, schemas, or generated clients may have changed.@pikku/schema-cfworker provides JSON schema validation using @cfworker/json-schema, a lightweight validator compatible with Cloudflare Workers (no eval or new Function). Implements the SchemaService interface from @pikku/core.
yarn add @pikku/schema-cfworker
CFWorkerSchemaServiceimport { CFWorkerSchemaService } from '@pikku/schema-cfworker'
const schema = new CFWorkerSchemaService(logger: Logger)
Methods:
compileSchema(schema: string, value: any): void — Compile and register a JSON schemavalidateSchema(schemaName: string, json: any): void — Validate data against a compiled schema (throws on failure)getSchemaNames(): Set<string> — Get all registered schema namesgetSchemaKeys(schemaName: string): string[] — Get property keys for a schemaimport { CFWorkerSchemaService } from '@pikku/schema-cfworker'
const createSingletonServices = pikkuServices(async (config) => {
const logger = new ConsoleLogger()
const schema = new CFWorkerSchemaService(logger)
return { config, logger, schema }
})
Use this instead of @pikku/schema-ajv when deploying to Cloudflare Workers, as AJV uses eval which is not permitted in the Workers runtime.
documentation
Deprecated — use pikku-middleware instead. Tag middleware (addTagMiddleware) is now documented as a section within the pikku-middleware skill, alongside global HTTP middleware, execution order, and the service-to-service bearer auth pattern.
testing
Use when adding authorization checks to Pikku functions or routes — pikkuPermission, pikkuAuth, per-function permissions, pattern-based permissions, or understanding OR/AND permission logic. TRIGGER when: user wants to restrict who can call a function, check resource ownership, add role-based access, or understand where permission checks belong. DO NOT TRIGGER when: user asks about middleware or request interception (use pikku-middleware), authentication strategies (use pikku-security), or session management.
testing
Use when adding any middleware to a Pikku app — global HTTP middleware, tag-scoped middleware (including service-to-service bearer auth), per-route middleware, session-setting middleware, or understanding middleware execution order and priority. TRIGGER when: user wants middleware on some or all routes, machine-to-machine auth, tag-scoped cross-cutting concerns, global interceptors, or middleware priority/order questions. DO NOT TRIGGER when: user asks about permissions/authorization checks (use pikku-permissions), auth strategies like authBearer/authCookie (use pikku-security), or deployment.
documentation
Standard cleanup to run right after a Pikku template is cloned or scaffolded into a new project. TRIGGER when: a Pikku template was just cloned/scaffolded (via `pikku create`, `git clone <template>`, or the user says "I cloned the kanban template / starter / template"), or the working tree still looks like an untouched template (template README, placeholder `@project/*` name in package.json). DO NOT TRIGGER when: working in an established project mid-feature, or editing the template repo itself.