What is the difference between contract and enforcement tests in this skill?

Contract tests verify that the design's 'promises' are met, while enforcement tests ensure that violations of those contracts result in errors rather than just warnings.

Does this skill work with existing documentation?

Yes, it utilizes @design_ref annotations to link test cases directly to specific markdown design files, making it easy to integrate with existing workflows.

Can I use this for flow path verification?

Absolutely. The skill includes specific patterns for verifying that actual code execution paths and state transitions match the intended logic described in architectural diagrams.

How does this skill help prevent architectural drift?

It actively compares the three sources of truth—design documents, scaffolds, and runtime code—to identify inconsistencies where implementation has diverged from the original design.

Functional Testing Bridge

Name: Functional Testing Bridge
Author: tettuan

bytettuan

Security & Testing

Bridges design documentation and runtime implementation to ensure architectural integrity and cross-layer consistency.

About

The Functional Testing skill provides a rigorous framework for Claude to align system design with actual implementation. By focusing on the 'Three-Layer Consistency' model—Design Docs, Scaffolds, and Runtime—it ensures that code adheres to specifications through contract testing, drift detection, and flow path verification. It is particularly effective for complex systems where maintaining synchronization between documentation and code is critical, helping developers catch architectural deviations and dead references early in the development lifecycle.

Key Features

Cross-layer consistency verification between specs and runtime
Contract and enforcement testing for strict rule validation
Automated drift detection to identify architectural deviations
0 GitHub stars
Dead reference detection for maintaining documentation accuracy
System boundary and flow path verification

Use Cases

Ensuring new code implementations strictly follow design document constraints
Verifying complex state transitions and system boundaries against specifications
Auditing large repositories for outdated API references in documentation

About

Key Features

Cross-layer consistency verification between specs and runtime
Contract and enforcement testing for strict rule validation
Automated drift detection to identify architectural deviations
0 GitHub stars
Dead reference detection for maintaining documentation accuracy
System boundary and flow path verification

Use Cases

Ensuring new code implementations strictly follow design document constraints
Verifying complex state transitions and system boundaries against specifications
Auditing large repositories for outdated API references in documentation