# Quick Create

## Objective

Create a common record from anywhere without leaving what you're doing.

A compact creation surface, reachable from anywhere in the app, holding only the fields a record genuinely requires.

## Before You Begin

This feature is being added to an application that already exists and already
works. Do not scaffold a new project, and do not assume a blank slate.

Inspect the codebase first and establish:

- The existing application structure and where code of this kind already lives.
- The framework and version in use.
- The existing design system — colours, spacing, typography, and component conventions.
- Existing UI components you can reuse instead of writing new ones.
- The existing database structure, if this feature needs to persist anything.
- The existing authentication and authorization system, if this feature is user-scoped.
- Dependencies already installed, so you don't add a library that duplicates one.
- The existing test setup and conventions.

Only start writing code once you understand the above. If the application
already implements part of this feature, extend it rather than replacing it.

## Implementation Instructions

1. Pick the record types users create most and include only their required fields. If the short form needs eight fields, that record does not belong here.
2. Filter the list of creatable types by the current user's permissions, evaluated on the server. A hidden menu item is not authorisation.
3. Prefill defaults from the current context — the workspace, project, or record being viewed — and never from a workspace the user has since left. Stale context leaks data across boundaries.
4. When validation needs a field the short form does not have, expand to the full form with everything the user already typed still in place. Losing their input is the fastest way to make them stop using this.
5. Return focus to whatever triggered the creation, and refresh the affected list in place rather than reloading the page.
6. Do not build a keyboard-driven command launcher here. Invocation by keystroke is owned by Command Palette; register this as an action there rather than building a second one.

## UI and UX Requirements

Match the application's existing design system exactly. Reuse its components,
spacing, and typography. This feature should look like it was always there.

## Responsive Requirements

Works on mobile, tablet, and desktop. Touch targets are large enough to hit on a
phone, and nothing overflows horizontally at 320px.

## Accessibility Requirements

- Fully keyboard navigable.
- Correct semantic elements and ARIA roles.
- Visible focus states.
- Meets WCAG AA contrast.
- Dynamic changes are announced to screen readers.
- Respects prefers-reduced-motion.

## Edge Cases

- Closing mid-entry must either warn or preserve a draft — silent discard of typed content is unacceptable.
- A double submit must not create two records; disable and guard server-side with an idempotency key.
- Creating from a filtered list may produce a record that does not match the filter — say so rather than appearing to create nothing.
- A record type the user could create when the surface opened may be revoked before they submit; handle the rejection cleanly.
- On mobile the surface must not be covered by the on-screen keyboard.
- The created record must be reachable immediately — link to it, do not just close.

## Testing

Exercise the feature end to end in the running application. Cover every edge case
above, then run the existing test suite and confirm nothing regressed.

## Acceptance Criteria

- [ ] The surface is reachable from every main screen.
- [ ] Only record types the user may create are offered, enforced server-side.
- [ ] Defaults come from live context and never from a stale or foreign workspace.
- [ ] Escalating to the full form preserves all entered data.
- [ ] The underlying list updates and focus returns to the trigger on success.
- [ ] Duplicate submissions cannot create duplicate records.
- [ ] The feature matches the existing design system.
- [ ] No existing functionality is broken.

## Adaptation Rules

- Match the existing design system. Do not introduce a new colour palette,
  spacing scale, or component library.
- Reuse existing components and utilities wherever they fit.
- Follow the naming, file layout, and code style already present.
- Do not upgrade, replace, or remove existing dependencies to make this
  feature fit. Adapt the feature to the app, not the app to the feature.
- Do not break existing functionality. If a change is genuinely required in
  existing code, make the smallest one that works and say so.
- If something in these instructions conflicts with how the application is
  built, follow the application and explain the deviation.

## Final Verification

Before you report the work as done:

1. Re-read the acceptance criteria above and check each one against what you
   actually built.
2. Run the application and exercise the feature end to end.
3. Run the existing test suite and confirm you have broken nothing.
4. Check the feature on mobile, tablet, and desktop widths.
5. Check keyboard navigation and focus handling.
6. Summarize what changed: files added, files modified, and anything you
   deliberately did differently because of how this application is built.

If any acceptance criterion is unmet, fix it before reporting completion.