Skip to main content

For developers

How to extend a service built from the template while keeping specs, tests, and public documentation aligned.

SectionFor developers / Project development
PurposeDeveloper overview
UpdatedJul 6, 2026
AuthorTemplate Maintainers
Versionv1.2.0
Reading time1 min

For developers

This section is for teams building a service from the template. It explains the project conventions that matter when adding product features, API routes, settings screens, or documentation.

The public user documentation remains the primary surface. Developer pages describe how to extend the template without breaking the behavior that users rely on.

Development model

The template follows Feature Slice Design. Application routes stay thin in src/app, while business logic, schemas, repositories, actions, and feature UI live under src/features.

What to keep aligned

When a visible behavior changes, update the matching surfaces together:

  • OpenSpec capability under openspec/specs;
  • implementation under src/features and thin routes under src/app;
  • E2E scenarios under e2e/specs;
  • public documentation under src/features/documents-system/content;
  • release or weekly notes when the change is published.

Start here