validating

Validate UI sprint components' physics and rigor compliance via Markdown reports.

2|Updated Jan 2, 2026

Search Tags:#UI #quality #validate #sprint #automated-checks #Rigor

Ready to run

npx skills add https://github.com/0xHoneyJar/rune --skill validating

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validating
Source: https://github.com/0xHoneyJar/rune/tree/main/.claude/skills/validating
Command: npx skills add https://github.com/0xHoneyJar/rune --skill validating

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the verification of UI sprint components by running physics and rigor checks to prevent unsafe or non-compliant code from progressing.

Core Features & Use Cases

Automated physics validation: Check components for correct physics adherence and protected capabilities.
Rigor checks: Validate web3 safety and code correctness during sprint reviews.
Use Case: During a sprint validation, run /validate physics to scan modified .tsx/.jsx files and generate a report for review.

Quick Start

Use the /validate physics command to run physics checks on the current sprint, then review the Markdown report in grimoires/loa/a2a/.

Frequently Asked Questions about validating

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

FAQPage Schema

How do I automate physics and rigor checks for UI sprint components?▼

Automated physics and rigor checks for UI sprint components are performed using the /validate physics and /validate rigor commands, which scan modified .tsx/.jsx files and output structured Markdown reports.

What are physics and rigor validations in sprint reviews?▼

Physics and rigor validations are automated checks that verify UI sprint components for correct physics adherence, protected capabilities, web3 safety, and code correctness to prevent non-compliant code from progressing.

How do I run a physics validation on .tsx and .jsx files?▼

To run a physics validation on .tsx and .jsx files, execute the /validate physics command during a sprint review to scan modified components and output a structured Markdown report to the grimoires/loa/a2a directory.

Can I integrate automated component checks into my sprint review workflow?▼

Yes, you can integrate automated component checks into your sprint review workflow, as the validation process supports review workflows by outputting structured Markdown reports to ensure code compliance and web3 safety.

Where do the validation reports for sprint components get saved?▼

Validation reports for sprint components get saved as structured Markdown files in the grimoires/loa/a2a directory, providing a reviewable output for physics and rigor compliance checks.

Does this validation tool require any external dependencies to run?▼

No external dependencies are required to run this validation tool, as it operates independently to perform physics and rigor checks on UI sprint components without needing additional setup.