sketch-dev-readiness

joelklabo's avatarfrom joelklabo

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.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 9, 2026
[Testing and QA]

When & Why to Use This Skill

The Sketch Dev Readiness skill is a comprehensive quality assurance tool designed to automate and enforce 'definition of done' protocols for software developers. It streamlines the pre-deployment phase by verifying dev server stability, executing linting and unit tests, and ensuring all quality gates are met before work is finalized, significantly reducing production errors and improving code reliability.

Use Cases

  • Pre-PR Validation: Automatically verify that code passes all linting, compilation, and unit test requirements before submitting a pull request.
  • Development Environment Health Checks: Use the skill to diagnose dev server errors and confirm that the local environment is running cleanly without log warnings.
  • Automated Proof of Work: Generate required proof-of-work video artifacts (.webm) to demonstrate feature functionality for reviewers and stakeholders.
  • Smoke Testing: Execute 'dev-smoke' gates to ensure core application workflows are intact after significant code changes or refactoring.
namesketch-dev-readiness
descriptionEnforce 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)

  1. Dev server starts cleanly: run pnpm dev and confirm no build errors.
  2. Log review: tail server output or use pnpm dev:logs.
  3. Dev-smoke gate: run pnpm dev:smoke and confirm success.
  4. DevTools QA: follow the DevTools QA checklist (see references).
  5. Proof video: run pnpm proof:video and confirm a .webm artifact.
  6. Quality gates: pnpm compile, pnpm lint, pnpm test:unit must 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.