validate-space

Validate project spaces for required docs and alignment with ideas.

69|7|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/TaylorHuston/local-life-manager --skill validate-space
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-space
Source: https://github.com/TaylorHuston/local-life-manager/tree/main/.claude/skills/validate-space
Command: npx skills add https://github.com/TaylorHuston/local-life-manager --skill validate-space

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate project spaces to ensure required structure, boilerplate docs, and alignment with ideas/ planning docs.

Core Features & Use Cases

  • Space validation against a standard project layout
  • Ensures presence of CLAUDE.md, README.md, and, when applicable, package.json for JS/TS projects
  • Verifies required directories docs/, docs/specs/, and docs/adrs/ exist and are up to date
  • Cross-references ideas/ planning docs to keep implementations aligned

Quick Start

Run the skill against a project space to validate its structure, for example: /validate-space leaf-nextjs-convex

Frequently Asked Questions about validate-space

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

FAQPage Schema
How do I validate project structure and ensure required docs exist?

Project structure validation checks for required boilerplate files like CLAUDE.md and README.md, verifies the docs/ directory tree, and cross-references ideas/ planning docs to keep implementations aligned.

What standard documentation should be in my project's docs directory?

Required docs in the docs/ directory include architecture-overview.md, api-overview.md, data-model.md, deployment.md, security.md, testing-overview.md, and ui-guide.md to enforce project consistency.

How do I check if my project planning docs match the actual implementation?

Cross-referencing ideas/ planning docs validates alignment by checking that the documented ideas and specifications exist and accurately match the current project implementation details.

Can I validate multiple project spaces at once for directory consistency?

Space validation applies to individual spaces or multiple projects, checking for required structure, boilerplate docs, and applicable package.json files across all specified project directories.

Does project space validation work for JavaScript and TypeScript projects?

Project space validation works for JS/TS projects by ensuring the presence of package.json alongside required boilerplate docs like README.md and the standard docs/ directory tree.

What happens if my project is missing the docs/specs/ or docs/adrs/ directories?

Space validation enforces consistency by failing the check when required directories like docs/, docs/specs/, and docs/adrs/ do not exist or are not properly maintained in the project.