verify-ssot

Validate SSOT imports from designated core packages and prevent local redefinitions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/junnv93/equipment_management_system --skill verify-ssot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-ssot
Source: https://github.com/junnv93/equipment_management_system/tree/main/.claude/skills/verify-ssot
Command: npx skills add https://github.com/junnv93/equipment_management_system --skill verify-ssot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SSOT import validation ensures that types, enums, and constants are imported from the correct packages and that local redefinitions do not occur, maintaining a single source of truth across the codebase.

Core Features & Use Cases

  • Validate imports of core SSOT items (UserRole, EquipmentStatus, etc.) from @equipment-management/schemas.
  • Enforce that permissions, API endpoints, and related constants come from their designated packages (e.g., @equipment-management/shared-constants).
  • Detect and prevent local redefinitions of SSOT items and ensure icon libraries adhere to lucide-react standards.
  • Use case: when adding a new SSOT type, run the verification to ensure it’s sourced from the SSOT bundles and not redefined locally.

Quick Start

Run the SSOT import verification after adding or updating types, enums, or permissions to ensure imports originate from the correct packages.

Frequently Asked Questions about verify-ssot

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

FAQPage Schema
How do I enforce single source of truth imports for shared types and enums?

Validate SSOT imports by ensuring shared types, enums, and constants are sourced from designated core packages rather than redefined locally. This maintains a single source of truth across backend and frontend codebases during code changes.

What is SSOT import validation and when should I run it?

SSOT import validation is a static analysis process that checks whether types and constants originate from correct packages. Run it after adding or updating SSOT items like UserRole or EquipmentStatus, and in CI checks to enforce conformance.

How do I prevent local redefinitions of types and constants in my monorepo?

Prevent local redefinitions by running SSOT import verification to detect duplicated types, enums, or permissions. This ensures dependencies on SSOT bundles are correctly referenced from packages like @equipment-management/shared-constants.

Can I validate that icon libraries follow lucide-react standards in CI?

Yes, SSOT import verification checks that icon libraries adhere to the lucide-react standard. It integrates into CI checks to enforce SSOT conformance across both backend and frontend codebases during changes.

Does SSOT import validation work with both backend and frontend codebases?

SSOT import validation applies to both backend and frontend codebases. It verifies that permissions, API endpoints, and related constants come from their designated packages, ensuring consistent SSOT conformance across the entire project.

Why should I validate SSOT imports instead of allowing local type redefinitions?

Validating SSOT imports prevents local type redefinitions that break the single source of truth. Sourcing types, enums, and constants from designated packages like @equipment-management/schemas ensures package consistency and reduces runtime errors.