---
title: "Project Templates"
description: "Choose the starter project structure and component library that fit your process."
canonical_url: "https://rosette.dev/docs/templates"
markdown_url: "https://rosette.dev/docs/templates.md"
source_url: "https://github.com/PreFab-Photonics/rosette/blob/12c8f77896959b1b099e63a2f5ba02d433215527/www/content/docs/templates/index.mdx"
docs_channel: "main"
docs_revision: "12c8f77896959b1b099e63a2f5ba02d433215527"
---

# Project Templates

`rosette init` offers two project templates. Both include project configuration,
generated API contracts, and a project-local `components/` package. When you select
an agent harness, Rosette also installs its routing, verification, and
component-authoring skills. The templates differ in how much process and component
content they provide.



- [Generic](/docs/templates/generic): Preconfigured silicon-photonics layers, DRC, and the full editable component catalog.





- [Blank](/docs/templates/blank): Minimal configuration and component-authoring helpers, with no public components.



After initialization, the files in your project are authoritative. In particular,
agents should read `components/__init__.py` and the relevant component source rather
than assuming that the starter catalog is unchanged.

The [component-authoring guide](/docs/templates/component-authoring) applies to both templates:
extend the generic catalog or build a project-specific library from the blank scaffold.