# rdev Terminology

**Last Updated:** 2026-02-05
**Confidence:** High

## Summary

Distinguishing between rdev code (the platform) and generated project code (skeleton) prevents confusion when discussing implementations.

## Core Terms

| Term | Definition | Code Location |
|------|------------|---------------|
| **platform** | rdev API itself—handlers, services, adapters, workers | `cmd/rdev-api/`, `internal/`, `pkg/api/` |
| **skeleton** | Monorepo base that ships in every generated project | `templates/skeleton/` |
| **component templates** | Templates for services, workers, apps, CLIs added to skeleton | `templates/components/` |
| **generated project** | A project created by rdev (contains skeleton + components) | Lives in Gitea repos |

## Usage Examples

- "Add auth middleware to **platform**" → edit `internal/auth/`
- "Add auth middleware to **skeleton**" → edit `templates/skeleton/pkg/auth/`
- "Platform's work queue" → `internal/adapter/postgres/work_queue.go`
- "Skeleton's job queue" → `templates/skeleton/pkg/queue/` (planned)

## File Pointers

- Platform entry: `cmd/rdev-api/main.go`
- Skeleton root: `internal/adapter/templates/templates/skeleton/`
- Component registry: `internal/adapter/templates/registry.go`

## Related

- [Composable Monorepo](./features/composable-monorepo.md) - Skeleton + component architecture
- [Template Provider](./services/template-provider.md) - How templates are seeded
