Skip to content

docs: add Aurelius-to-Nerva full-stack workflow guide #127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PAMulligan merged 1 commit into from
Jun 13, 2026
Merged

docs: add Aurelius-to-Nerva full-stack workflow guide #127

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,8 @@ Structured interview (7-10 questions) that generates an OpenAPI spec, then feeds

Takes an [Aurelius](https://github.com/PMDevSolutions/Aurelius) frontend `build-spec.json` and generates the matching backend API. This enables a full-stack workflow: design in Figma, build frontend with Aurelius, generate backend with Nerva, share a typed API client.

See the [Aurelius → Nerva walkthrough](docs/schema-to-api/aurelius-pipeline.md) for a worked example: a frontend `build-spec.json`, the OpenAPI spec it generates, the component-to-endpoint mapping, and the typed client that bridges both sides.

## Directory Structure

```
Expand Down Expand Up @@ -205,6 +207,7 @@ Nerva is the backend counterpart in a family of Claude Code-integrated developme
| Architecture | [`docs/onboarding/architecture.md`](docs/onboarding/architecture.md) | System architecture overview |
| Troubleshooting | [`docs/onboarding/troubleshooting.md`](docs/onboarding/troubleshooting.md) | Common issues and solutions |
| Pipeline guide | [`docs/schema-to-api/README.md`](docs/schema-to-api/README.md) | 10-phase pipeline deep dive |
| Aurelius pipeline | [`docs/schema-to-api/aurelius-pipeline.md`](docs/schema-to-api/aurelius-pipeline.md) | Generate a backend from an Aurelius frontend build-spec |
| API standards | [`docs/api-development/README.md`](docs/api-development/README.md) | TypeScript, Hono, testing conventions |
| Agent catalog | [`.claude/CUSTOM-AGENTS-GUIDE.md`](.claude/CUSTOM-AGENTS-GUIDE.md) | All 24 agents with use cases |
| Plugin reference | [`.claude/PLUGINS-REFERENCE.md`](.claude/PLUGINS-REFERENCE.md) | Plugin configuration and commands |
Expand Down
9 changes: 9 additions & 0 deletions docs/schema-to-api/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,15 @@

Convert an OpenAPI specification into a fully working, tested API server through an automated 10-phase pipeline.

## Where the Spec Comes From

The pipeline below starts from an OpenAPI specification. Write that spec by hand, or generate it:

- **From an Aurelius frontend** -- [`/build-from-aurelius`](./aurelius-pipeline.md) reads a frontend `build-spec.json`, infers the API it needs, generates the OpenAPI spec, and feeds it into the phases below. See the [Aurelius → Nerva walkthrough](./aurelius-pipeline.md).
- **From a conversation** -- `/build-from-conversation` generates the spec through a structured interview.

Both converge on the same 10 phases.

## Pipeline Overview

| Phase | Name | Description |
Expand Down
Loading
Loading