verify-recipe

Execute type checks, tests, and linting to verify Styleframe recipes.

91|4|Updated Jun 20, 2025
One-click install
npx skills add https://github.com/styleframe-dev/styleframe --skill verify-recipe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-recipe
Source: https://github.com/styleframe-dev/styleframe/tree/main/.claude/skills/verify-recipe
Command: npx skills add https://github.com/styleframe-dev/styleframe --skill verify-recipe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The QA workflow helps teams consistently validate that a created recipe passes TypeScript type checks, runs theme-specific tests, and satisfies lint rules, then emits a structured verification report for traceability.

Core Features & Use Cases

  • Typecheck orchestration: executes the repo-wide TypeScript type checks to catch type errors early.
  • Test orchestration: runs the theme test suite to ensure design-system components remain correct.
  • Lint enforcement: runs lint across relevant packages to enforce coding standards.
  • Verification artifact: writes .context/recipe-<name>/verification.md with a detailed summary and failure details.
  • Standalone compatibility: can verify any existing recipe without requiring prior artifacts.
  • Actionable feedback: includes precise file:line references and suggested sub-skills to guide fixes.

Quick Start

Run /verify-recipe for a target recipe to generate its verification report.

Frequently Asked Questions about verify-recipe

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

FAQPage Schema
How do I automate end-to-end recipe validation for type checks, tests, and linting?

To automate recipe validation, execute TypeScript type checks, theme-specific tests, and linting across the repository. The process catches failures early and outputs a structured verification artifact with precise file paths and line numbers.

What is the best way to report TypeScript type errors and lint failures in a recipe?

Reporting type errors and lint failures is handled by running an automated verification process that generates a markdown artifact. This report includes precise file:line references and suggests sub-skills to guide subsequent fixes.

Can I verify an existing recipe without requiring prior artifacts or dependencies?

Yes, you can verify any existing recipe standalone without requiring prior artifacts. The verification process executes type checks, tests, and lint rules directly on the target recipe within the repository.

How do I generate a verification report with actionable feedback for a recipe?

Generate a verification report by running the verification command for a target recipe. This produces a verification.md file inside the recipe context directory, containing a detailed failure summary and suggested sub-skills for fixes.

Does recipe verification work with implement-recipe, showcase-recipe, and document-recipe workflows?

Yes, recipe verification ensures compatibility with implement-recipe, showcase-recipe, and document-recipe workflows. It produces a structured verification.md artifact that integrates seamlessly into these downstream workflow stages.