Enforce Sketch Magic dev-readiness gates. Use when asked “are you done?”, when dev server errors appear, when proof video is required, or when verifying compile/lint/test/dev-smoke status.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
npx agent-skills-cli listSkill Instructions
name: sketch-dev-readiness description: Enforce Sketch Magic dev-readiness gates. Use when asked “are you done?”, when dev server errors appear, when proof video is required, or when verifying compile/lint/test/dev-smoke status.
Sketch Dev Readiness
Overview
Define the exact steps required before claiming work is complete: dev server health, log review, DevTools checks, proof video, and quality gates.
Workflow (do not skip)
- Dev server starts cleanly: run
pnpm devand confirm no build errors. - Log review: tail server output or use
pnpm dev:logs. - Dev-smoke gate: run
pnpm dev:smokeand confirm success. - DevTools QA: follow the DevTools QA checklist (see references).
- Proof video: run
pnpm proof:videoand confirm a.webmartifact. - Quality gates:
pnpm compile,pnpm lint,pnpm test:unitmust be green.
Failure rule
If any step fails or logs show errors, do not claim done. Create a follow-up task and fix the issue first.
References
references/dev-readiness.md— detailed gate list and log locations.
More by joelklabo
View allNostrstack API development (Fastify + Prisma) including routing patterns, services, tenancy resolution, LightningProvider integration, and Nostr endpoints. Use when editing apps/api (routes, services, providers, Prisma schema, OpenAPI) or adding API features/tests.
Release readiness and monitoring workflow for Sketch Magic. Use when preparing launch checklists, verifying telemetry, or validating health endpoints before a public release.
Use this when running or adding tests (compile/lint/unit/E2E), updating test utilities, or working with Playwright/visual testing in markdowntown.
Lightning/LNbits integration for nostrstack, including regtest flows, staging/prod config, observability, and payment/zap behavior. Use when editing payment flows, Lightning provider code, or running LNbits-related tests.
