Project Integrity Validator FAQs

Question 1

When is the best time to run the validate-counts skill?

Accepted Answer

It is best used as a final check before creating a release, after bulk-adding components, or whenever the Project Overview in your CLAUDE.md looks outdated.

Question 2

Does this tool modify my files automatically?

Accepted Answer

No, it is a validation-only tool that identifies discrepancies and reports them with precise locations so you can review and fix them manually or via build scripts.

Question 3

Why is count validation important in AI development?

Accepted Answer

It prevents 'documentation drift' where your project overview or manifests claim to have a different number of skills or agents than what actually exists in the source code, which can confuse AI models and developers.

Question 4

Can I use this for non-OrchestKit projects?

Accepted Answer

While specifically designed for OrchestKit file structures, the validation logic can be adapted for any project requiring consistency between source directories and configuration manifests.

Question 5

What specific files does the validator check?

Accepted Answer

It compares the physical /src directory against CLAUDE.md, manifests/ork.json, and internal hook configuration files to ensure every component is accounted for.

Project Integrity Validator

Key Features

Use Cases

Project Integrity Validator

Key Features

Use Cases