checker

Validates one screen's source code against a single Recursica skill's pre-flight checklist.

1|Updated May 29, 2026
One-click install
npx skills add https://github.com/borderux/recursica-knowledge --skill checker-borderux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checker
Source: https://github.com/borderux/recursica-knowledge/tree/main/agents/barb/subagents/checker
Command: npx skills add https://github.com/borderux/recursica-knowledge --skill checker-borderux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design system rulebooks are too large to fit in one review context, so screens ship with violations nobody checked. This Skill checks one screen against exactly one Recursica skill, walking its pre-flight checklist item by item so no rule is silently skipped. ## Core Features & Use Cases - Item-by-item verdicts: Returns pass, violation, or not-applicable for every checklist item, with file and line for each violation. - Mechanical violation flagging: Identifies violations invited by the code itself, such as props accepting optional prose or missing component slots, so they can be fixed once at the source. - Honest uncertainty handling: Distinguishes genuine not-applicable items from rules that need a rendered check, avoiding false passes. - Use Case: Barb dispatches one checker instance per applicable skill during a design review; each instance reads only its assigned skill and the screen's source files, then returns structured verdicts for aggregation. ## Quick Start Dispatch this agent with one Recursica skill and the source files of one screen, and ask it to walk the skill's pre-flight checklist and return a verdict per item.

Frequently Asked Questions about checker

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

FAQPage Schema
How do I check a screen against Recursica design system rules?▼

Dispatch one checker instance per applicable skill with the screen's source files. Each checker reads its single skill, walks the pre-flight checklist item by item, and returns a pass, violation, or not-applicable verdict for every item.

What output does a design rule checker return per checklist item?▼

Each item returns the verbatim checklist text, a verdict of pass, violation, or not-applicable, plus file and line for violations. It also includes evidence and a mechanical flag indicating whether the code structure invited the violation.

Can the checker verify rules about rendered layout from source code?▼

No. Rules about rendered results like centering, overflow, or resolved type styles cannot be answered from source. The checker marks them violation with evidence noting a rendered check is needed, rather than passing them falsely.

Why does the checker only read one skill instead of all of them?▼

The full skills corpus does not fit in a single context, and reading many skills shallowly produced reviews where rules had zero influence on code. One skill per checker ensures thorough, item-by-item coverage.

What are the limitations of source-only design rule checking?▼

The checker has read-only tools and cannot edit code or render screens. Violations require a file and line to count as findings, and render-dependent rules must be deferred to a separate visual verification stage.