project-conventions

Standardize project structure by defining a canonical base layout with directories like _devprocess/, src/, docs/, and memory/, along with strict file naming and frontmatter conventions to ensure coherence and enable reliable automation across teams.

Initialize a greenfield project by applying a base structure and binding rules that guide scaffolding and handoffs throughout the V-Model, ensuring downstream skills can rely on a standardized directory layout and documentation.

Frontmatter conventions are required to enable reliable automation, file discovery, and cross-skill validation. Standardizing frontmatter ensures that downstream skills can correctly parse and process project documentation.

Yes, you can use these project structure templates for onboarding and bootstrap. The conventions provide guidance for consistent starter templates and documentation, ensuring new projects follow the standardized directory layout immediately.

This project setup skill applies specifically to greenfield projects and cross-skill workflows. It guides initialization, scaffolding, and handoffs throughout the V-Model to establish coherence from the start of a new project.

A limitation of enforcing workflow bindings is that other skills must reference these conventions to maintain consistency. If downstream skills do not comply with the standardized directory structures and frontmatter, cross-skill validation and automation may fail.