sketch-dev-readiness

Enforce Sketch dev-readiness checks for dev server health, smoke tests, and quality gates.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/joelklabo/markdowntown-cli --skill sketch-dev-readiness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sketch-dev-readiness
Source: https://github.com/joelklabo/markdowntown-cli/tree/main/codex/skills/sketch-dev-readiness
Command: npx skills add https://github.com/joelklabo/markdowntown-cli --skill sketch-dev-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents premature completion claims by enforcing a reproducible dev-readiness checklist that verifies dev server health, log cleanliness, smoke tests, DevTools checks, proof video evidence, and quality gates before marking work as done.

Core Features & Use Cases

  • Dev server health: Start the dev server and confirm there are no build errors or runtime exceptions.
  • Log and smoke validation: Tail logs and run dev-smoke to confirm HTTP 200 responses and absence of build/runtime errors.
  • DevTools QA and proof: Perform DevTools console/network/performance checks and capture a proof video artifact (.webm) demonstrating behavior.
  • Quality gates: Ensure compile, lint, and unit tests pass before claiming completion.
  • Use Case: Use when a developer asks "are you done?", when CI or dev server errors appear, or when a proof of functionality is required for review.

Quick Start

Run the Sketch dev-readiness checklist by starting the dev server, reviewing logs, running dev-smoke, performing DevTools QA, generating a proof video, and confirming compile, lint, and unit tests are green.

Frequently Asked Questions about sketch-dev-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify dev server health and confirm there are no build errors?

To verify dev server health, start the dev server using pnpm dev and confirm there are no build errors or runtime exceptions. This ensures your front-end environment is stable before proceeding with further checks.

What's the best way to run a dev-smoke test and check for HTTP 200 responses?

The best way to run a dev-smoke test is to execute pnpm dev:smoke, which confirms HTTP 200 responses and checks for the absence of build or runtime errors in your logs. This validates your development environment.

How do I capture a .webm proof video artifact for DevTools QA?

To capture a .webm proof video artifact, perform DevTools console, network, and performance checks while recording the screen. This video demonstrates the application's behavior and serves as functional proof for review.

Do I need to pass compile, lint, and unit tests before claiming development work is complete?

Yes, you need to ensure compile, lint, and unit test results are green before claiming development work is complete. These quality gates prevent premature completion claims by enforcing a reproducible dev-readiness checklist.

Why does my dev-readiness checklist fail when CI or dev server errors appear?

Your dev-readiness checklist fails because it enforces strict verification of dev server health, log cleanliness, and smoke tests. Errors in CI or the dev server indicate incomplete work that must be resolved before merging or shipping.