kubit-validating-design

Use after any change to skeleton/, packages/core/, or docs/. Use to verify types compile and documentation is synchronized.

⭐32stars🔀2forks📁View on GitHub🕐Updated Jan 8, 2026⬇️1downloads

When & Why to Use This Skill

The Kubit Validating Design skill is a specialized developer tool designed to maintain project integrity by automating type-checking and documentation synchronization. It ensures that any modifications to core packages or project skeletons are reflected accurately in the documentation, preventing technical debt and 'spec drift' in complex codebases.

Use Cases

  • Post-Refactoring Validation: Automatically run TypeScript compilation checks after modifying core packages to ensure no breaking changes or type mismatches were introduced.
  • Documentation Alignment: Verify that SPEC.md and SKELETON_APP.md are updated in tandem with API or structural changes to keep the project roadmap and architecture guides accurate.
  • Agent Context Maintenance: Ensure .claude/CLAUDE.md is synchronized with documentation updates to prevent AI agent confusion and ensure the assistant has the latest project context.
  • Pre-Commit Quality Gate: Serve as a final validation checklist to confirm that all types compile and all documentation files are consistent before marking a development task as complete.
namekubit-validating-design
descriptionUse after any change to skeleton/, packages/core/, or docs/. Use to verify types compile and documentation is synchronized.

Validating Kubit Design Changes

Overview

After any change, verify types compile and docs are synchronized.

When to Use

  • After modifying skeleton/ files
  • After changing packages/core/ types
  • After updating docs/
  • Before considering a task complete

Validation Checklist

After ANY change:
[ ] tsc --noEmit passes in skeleton/
[ ] SPEC.md updated if API changed
[ ] SKELETON_APP.md updated if structure changed
[ ] CLAUDE.md updated if docs/ changed

Type Validation

Run from skeleton/ directory:

cd skeleton && npx tsc --noEmit

Common failures:

  • Missing type in packages/core/ for new skeleton usage
  • Import path typo
  • Decorator usage not matching type signature

Documentation Sync

If you changed... Also update...
skeleton/ structure docs/SKELETON_APP.md
API in packages/core/ docs/SPEC.md
Any file in docs/ .claude/CLAUDE.md
Test expectations docs/TEST_PLAN.md

Quick Verification Commands

# Type check
cd skeleton && npx tsc --noEmit

# List skeleton structure (compare to SKELETON_APP.md)
find skeleton -type f -name "*.ts" -o -name "*.tsx" | sort

Red Flags

  • Added to skeleton without adding types → tsc will fail
  • Changed API without updating SPEC → spec drift
  • Modified docs/ without updating CLAUDE.md → agent confusion
  • New pattern not in SKELETON_APP.md → incomplete documentation