# A feature end to end

A step of the [Cloud application](https://gradus.kazet.blog/tree/cloud-application) tree on Gradus, in the Frontend area: Second app, UI, browser tests.

Page: https://gradus.kazet.blog/tree/cloud-application/step/feature-end-to-end

Build the spec as one vertical slice: data, API, screens, tests and events, shipped dark behind a flag, then on for you, then for everyone.

Usually comes after: [Pick the next feature](https://gradus.kazet.blog/tree/cloud-application/step/pick-next-feature).

Leads to: [Did it work?](https://gradus.kazet.blog/tree/cloud-application/step/feature-review).

## Prompt for your AI assistant

```
Read the newest spec in docs/product/features and docs/index.md. Register a flag for this feature, off by default. Build it as one vertical slice in small pull requests: data changes by expand and contract, the data access layer, endpoints with their contract and scoped to the current user, screens with their loading, empty and error states, the events from the spec and tests at each level, including a browser test over the new path. Merge and deploy each stage with the flag off. Turn it on for me, walk through it in production together with me, then turn it on for everyone. Finish by listing what differs from the spec.
```

Every step of the tree: https://gradus.kazet.blog/tree/cloud-application/llms.txt