# Aether Development SOP (Frontend) > **Version:** 1.2 (2026-03-17) > **Location:** documentation/GUIDE__Development.md ## 1. Verification (The "Test-First" Mandate) **Rule:** No code is to be committed unless it has passed local verification. ### Required Checks 1. **Svelte Integrity:** `npx svelte-check` - **Zero Tolerance:** If a task introduces even a single svelte-check warning or error, it must not be merged. Resolve all warnings before committing. 2. **Type Safety:** Ensure interfaces in `src/lib/types/ae_types.ts` match backend schemas. 3. **Reactivity Check:** Verify Svelte 5 runes (`$state`, `$derived`) are not creating race conditions with Dexie `liveQuery`. 4. **Build Check:** For major changes, run `npm run build:dev` to ensure no SSR or build-time failures. 5. **Integration Tests:** For changes to badge print, event layouts, or auth/store logic, run the relevant Playwright test file(s): ```bash npx playwright test tests/event_badge_render.test.ts tests/event_badge_attendee_workflow.test.ts ``` Run the full suite with `npm run test:integration`. The badge tests (`event_badge_*.test.ts`) are the canonical integration test template. ## 2. Commit Policy - **Atomic Commits:** One component or one logic fix per commit. Do not batch unrelated changes. - **Safety:** Use `~/tmp/agents_trash` for file removal; never use `rm` directly on source files. - **Secrets:** Never commit `.env`, API keys, or passwords. ## 3. Coordination (The Handshake) You are not working in a vacuum. Coordinate with the Backend Agent via MCP tools. ### Mandatory Messaging Triggers - **Data Requirements:** When a UI feature requires a new field or endpoint. - **API Failures:** When a V3 endpoint returns unexpected data or errors. - **Blocked:** If stuck in a loop or lacking information, use `ae_send_message` to ask the Backend Agent, or flag for Scott. ### Tools - `ae_send_message` / `ae_inbox` — agent-to-agent messaging - `ae_task_list` / `ae_task_add` / `ae_task_complete` — shared Kanban board - `ae_log_work` — log activity to daily journal ## 4. Continuity (Before Starting Work) 1. Review `documentation/TODO__Agents.md` for active tasks. 2. Check `~/agents_sync/README.md` for fleet status and cross-agent tasks. 3. Describe your plan before making code changes across multiple files. ## 5. Key Documentation | File | Purpose | | --- | --- | | `documentation/TODO__Agents.md` | Active task list — read first | | `documentation/GUIDE__AE_API_V3_for_Frontend.md` | V3 API reference (authoritative) | | `documentation/GUIDE__SvelteKit2_Svelte5_DexieJS.md` | Dexie + liveQuery patterns | | `documentation/GEMINI__Svelte_and_Me.md` | Svelte 5 runes patterns | | `documentation/AE__Architecture.md` | System architecture overview | | `documentation/AE__Naming_Conventions.md` | Naming rules | | `documentation/PROJECT__AE_Events_Launcher_Native_integration.md` | Electron/Launcher reference | | `tests/README.md` | Playwright test guide — shared helpers, hard-won lessons, demo IDs | ## 6. Inline Field Editing — `element_ae_obj_field_editor` The standard component for single-field inline editing throughout the platform. Wraps a `PATCH /v3/crud/{obj_type}/{obj_id}` call behind a click-to-edit UI that respects `$ae_loc.edit_mode`. ```svelte import Element_ae_obj_field_editor from '$lib/elements/element_ae_obj_field_editor.svelte'; ``` ### Basic usage — text field with custom display Wrap the display content in the default snippet. The component renders it in view mode and swaps in the input on edit. ```svelte events_func.load_ae_obj_id__event_session({ api_cfg: $ae_api, event_session_id: session.id })} >

{session.name}

``` ### Field types | `field_type` | Input rendered | | --- | --- | | `text` (default) | `` — Enter key saves | | `textarea` | `