review-community-standard-componentization-wiring-knowledge

Name: review-community-standard-componentization-wiring-knowledge
Availability: InStock
Author: Theo

Confirms new public exports have production callers, integration tests, runtime metrics, and valid wiring declarations.

Updated May 13, 2026

Search Tags:#metrics #integration-tests #componentization #wiring #wiring-triad #static-caller #orphan-export

Ready to run

npx skills add https://github.com/usetheodev/theo-ui --skill review-community-standard-componentization-wiring-knowledge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-community-standard-componentization-wiring-knowledge
Source: https://github.com/usetheodev/theo-ui/tree/main/.claude/skills/review-community-standard-componentization-wiring-knowledge
Command: npx skills add https://github.com/usetheodev/theo-ui --skill review-community-standard-componentization-wiring-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This knowledge skill provides the wiring-review layer for agents, enforcing the canonical wiring triad (static caller presence, integration tests, and runtime metrics) during re-validation of public exports to ensure robust, auditable wiring.

Core Features & Use Cases

Validates that new public exports have a production caller and are not orphaned
Guides evidence collection for integration tests and runtime metrics
Supports canonical patterns for dead-wiring or ADR-based deferrals when appropriate

Quick Start

Run this knowledge skill during wiring reviews to confirm each new public export satisfies static caller, integration test, and metric requirements.

Frequently Asked Questions about review-community-standard-componentization-wiring-knowledge

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

FAQPage Schema

How do I verify that new public exports have a production caller and are not orphaned?▼

To verify public exports are not orphaned, check that each new export has at least one production caller, explicitly excluding tests, barrels, and bin entries from the static caller count. This confirms the export is used in production wiring.

What is the wiring triad for componentization validation?▼

The wiring triad for componentization is a canonical standard requiring static caller presence, integration tests against real boundaries, and declared runtime metrics to ensure robust and auditable codebase wiring.

How do I check for integration tests and runtime metrics when validating public exports?▼

Check for integration tests and runtime metrics by guiding evidence collection to confirm new public exports are tested against real boundaries and explicitly declare runtime metrics for monitoring during the re-validation process.

Can I defer wiring requirements for dead-wiring or ADR-based exceptions?▼

Yes, you can defer wiring requirements by following canonical patterns for dead-wiring or ADR-based deferrals, allowing exceptions to the static caller, integration test, and metric mandates when appropriately documented.

When do I need to run a wiring review for componentization?▼

You need to run a wiring review when validating canonical definitions and verifying wiring discipline across a codebase, specifically during re-validation to ensure new public exports satisfy the static caller, integration test, and metric requirements.