template-structure

Standardize project template directories and validate .claude subfolders and metadata.

2|2|Updated Nov 4, 2025
One-click install
npx skills add https://github.com/gizix/cc_projects --skill template-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-structure
Source: https://github.com/gizix/cc_projects/tree/main/.claude/skills/template-structure
Command: npx skills add https://github.com/gizix/cc_projects --skill template-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a consistent, well-organized directory structure for project templates, reducing setup time and confusion across teams.

Core Features & Use Cases

  • Standard Template Template: Provides a consistent root and subdirectories (commands, agents, skills) for new templates.
  • Guided Organization: Clear roles for each folder (commands, agents, skills) to speed onboarding.
  • Scalability: Facilitates adding more components (scripts/references/assets) without friction.

Quick Start

Create a new template folder named after your project and follow the Standard Template Structure, using the provided folders as blueprints (e.g., .claude/commands, .claude/agents, .claude/skills).

Frequently Asked Questions about template-structure

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

FAQPage Schema
How do I standardize project template directory structure across teams?

Standardizing template structure enforces consistent organization by applying a Standard Template Structure with defined subdirectories (.claude/commands, .claude/agents, .claude/skills) and required metadata. This reduces setup confusion and speeds onboarding across Python/Django, JavaScript/React, and Rust projects.

What directory layout should I use for organizing templates and scaffolding?

Follow the Standard Template Structure: place commands, agents, and skills in .claude subfolders, include root documentation, and use optional supporting files like reference.md, examples/, templates/, and scripts/. This enforces consistent naming conventions and required frontmatter fields in SKILL.md and component metadata.

Can I apply template structure validation to existing Django, React, and Rust projects?

Yes. Template structure validation works across Python/Django, JavaScript/React, and Rust frameworks. It checks .claude subfolders, enforces directory hierarchies, validates required frontmatter, and ensures file naming conventions conform to the Standard Template Structure.

What happens if my template is missing required metadata or folder organization?

Missing required frontmatter fields in SKILL.md, command, or agent metadata, or incorrect directory hierarchies, will fail validation. Ensure all components in .claude subfolders follow naming conventions and include mandatory metadata to pass compliance checks.

How do templates scale when adding new components like scripts or reference files?

The Standard Template Structure supports scalability by defining clear roles for each folder and allowing optional supporting files (reference.md, examples/, templates/, scripts/). This structure lets teams add new components without friction or reorganization.