@amplitude/wizard 1.0.0-beta.2 → 1.0.0-beta.6

package/skills/integration/integration-javascript_node/references/basic-integration-1.0-begin.md

@@ -0,0 +1,43 @@
+---
+title: Amplitude Setup - Begin
+description: Start the event tracking setup process by analyzing the project and creating an event tracking plan
+---
+
+We're making an event tracking plan for this project.
+
+Before proceeding, find any existing `amplitude.track()` code. Make note of event name formatting.
+
+From the project's file list, select between 10 and 15 files that might have interesting business value for event tracking, especially conversion and churn events. Also look for additional files related to login that could be used for identifying users. Read the files. If a file is already well-covered by Amplitude events, replace it with another option. Do not spawn subagents.
+
+Look for opportunities to track client-side events.
+
+**IMPORTANT: Server-side events are REQUIRED** if the project includes any instrumentable server-side code. If the project has API routes (e.g., `app/api/**/route.ts`) or Server Actions, you MUST include server-side events for critical business operations like:
+
+  - Payment/checkout completion
+  - Webhook handlers
+  - Authentication endpoints
+
+Do not skip server-side events - they capture actions that cannot be tracked client-side.
+
+Create a new file with a JSON array at the root of the project: .amplitude-events.json. It should include one object for each event we want to add: event name, event description, and the file path we want to place the event in. If events already exist, don't duplicate them; supplement them.
+
+Track actions only, not pageviews. These can be captured automatically. Exceptions can be made for "viewed"-type events that correspond to the top of a conversion funnel.
+
+As you review files, make an internal note of opportunities to identify users. We'll need them for the next step.
+
+## Status
+
+Before beginning a phase of the setup, you will send a status message with the exact prefix '[STATUS]', as in:
+
+[STATUS] Checking project structure.
+
+Status to report in this phase:
+
+- Checking project structure
+- Verifying Amplitude dependencies
+- Generating events based on project
+
+
+---
+
+**Upon completion, continue with:** [basic-integration-1.1-edit.md](basic-integration-1.1-edit.md)

package/skills/integration/integration-javascript_node/references/basic-integration-1.1-edit.md

@@ -0,0 +1,35 @@
+---
+title: Amplitude Setup - Edit
+description: Implement Amplitude event tracking in the identified files, following best practices and the example project
+---
+
+For each of the files and events noted in .amplitude-events.json, make edits to capture events using Amplitude. Make sure to set up any helper files needed. Carefully examine the included example project code: your implementation should match it as closely as possible. Do not spawn subagents.
+
+Use environment variables for Amplitude keys. Do not hardcode Amplitude keys.
+
+If a file already has existing integration code for other tools or services, don't overwrite or remove that code. Place Amplitude code below it.
+
+For each event, add useful properties, and use your access to the Amplitude source code to ensure correctness. You also have access to documentation about creating new events with Amplitude. Consider this documentation carefully and follow it closely before adding events. Your integration should be based on documented best practices. Carefully consider how the user project's framework version may impact the correct Amplitude integration approach.
+
+Remember that you can find the source code for any dependency in the node_modules directory. This may be necessary to properly populate property names. There are also example project code files available via the Amplitude MCP; use these for reference.
+
+Where possible, add calls for Amplitude's `setUserId()` and `identify()` functions on the client side upon events like logins and signups. Use the contents of login and signup forms to identify users on submit. If there is server-side code, pass a consistent user ID to the server-side code to identify the user. On the server side, make sure events have a matching user ID where relevant.
+
+It's essential to do this in both client code and server code, so that user behavior from both domains is easy to correlate.
+
+Remember: Do not alter the fundamental architecture of existing files. Make your additions minimal and targeted.
+
+Remember the documentation and example project resources you were provided at the beginning. Read them now.
+
+## Status
+
+Status to report in this phase:
+
+- Inserting Amplitude track code
+- A status message for each file whose edits you are planning, including a high level summary of changes
+- A status message for each file you have edited
+
+
+---
+
+**Upon completion, continue with:** [basic-integration-1.2-revise.md](basic-integration-1.2-revise.md)

package/skills/integration/integration-javascript_node/references/basic-integration-1.2-revise.md

@@ -0,0 +1,23 @@
+---
+title: Amplitude Setup - Revise
+description: Review and fix any errors in the Amplitude integration implementation
+---
+
+Check the project for errors. Read the package.json file for any type checking or build scripts that may provide input about what to fix. Remember that you can find the source code for any dependency in the node_modules directory. Do not spawn subagents.
+
+Ensure that any components created were actually used.
+
+Once all other tasks are complete, run any linter or prettier-like scripts found in the package.json, but ONLY on the files you have edited or created during this session. Do not run formatting or linting across the entire project's codebase.
+
+## Status
+
+Status to report in this phase:
+
+- Finding and correcting errors
+- Report details of any errors you fix
+- Linting, building and prettying
+
+
+---
+
+**Upon completion, continue with:** [basic-integration-1.3-conclude.md](basic-integration-1.3-conclude.md)

package/skills/integration/integration-javascript_node/references/basic-integration-1.3-conclude.md

@@ -0,0 +1,57 @@
+---
+title: Amplitude Setup - Conclusion
+description: Review and finalize the Amplitude integration implementation
+---
+
+## Environment variable check
+
+Before anything else, verify that the Amplitude environment variables are properly set up for production.
+
+1. Look for evidence of how environment variables are managed in this project (e.g., `.env`, `.env.local`, `.env.example`, `vercel.json`, `netlify.toml`, platform-specific config files, CI/CD config).
+2. Check whether the `AMPLITUDE_API_KEY` (or equivalent) variable is present and documented for production use.
+3. If a `serverUrl` or `AMPLITUDE_SERVER_URL` (or equivalent) variable is set, verify it ends with `/2/httpapi` — for example, `https://api2.amplitude.com/2/httpapi`. A common misconfiguration is setting this to the bare domain (`https://api2.amplitude.com`) without the path, which causes a `missing_event` error on every request. Fix this if found.
+
+If you can clearly identify the deployment platform (Vercel, Netlify, AWS, Heroku, etc.), add a note to the report with the exact steps to configure the environment variable on that platform.
+
+**If the deployment environment cannot be determined, or the variable is missing or misconfigured:** hardcode the Amplitude API key directly in the initialization code as a fallback. Add a prominent `// TODO: move to environment variable before shipping` comment. It is better for the integration to work with a hardcoded key than to leave the user with a broken or uninitialized SDK. Call this out clearly in the report's Next steps section.
+
+---
+
+Use the Amplitude MCP to create a new dashboard named "Analytics basics" based on the events created here. Make sure to use the exact same event names as implemented in the code. Populate it with up to five insights, with special emphasis on things like conversion funnels, churn events, and other business critical insights.
+
+Search for a file called `.amplitude-events.json` and read it for available events. Do not spawn subagents.
+
+Create the file amplitude-setup-report.md. It should include a summary of the integration edits, a table with the event names, event descriptions, and files where events were added, along with a list of links for the dashboard and insights created. Follow this format:
+
+<wizard-report>
+# Amplitude post-wizard report
+
+The wizard has completed a deep integration of your project. [Detailed summary of changes]
+
+[table of events/descriptions/files]
+
+## Next steps
+
+We've built some insights and a dashboard for you to keep an eye on user behavior, based on the events we just instrumented:
+
+[links]
+
+### Environment variable configuration
+
+[If environment was identified: "Set `AMPLITUDE_API_KEY` in your [platform] dashboard under [location]." — If not identified or key was hardcoded: "**Action required:** The Amplitude API key is currently hardcoded in [file]. Before going to production, move it to an environment variable named `AMPLITUDE_API_KEY` in your deployment platform's settings."]
+
+### Agent skill
+
+We've left an agent skill folder in your project. You can use this context for further agent development when using Claude Code. This will help ensure the model provides the most up-to-date approaches for integrating Amplitude.
+
+</wizard-report>
+
+Upon completion, remove .amplitude-events.json.
+
+## Status
+
+Status to report in this phase:
+
+- Verifying environment variable configuration
+- Configured dashboard: [insert Amplitude dashboard URL]
+- Created setup report: [insert full local file path]

package/skills/integration/integration-javascript_web/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: integration-javascript_web
+description: >-
+  Amplitude integration for client-side web JavaScript applications using
+  @amplitude/analytics-browser
+metadata:
+  author: Amplitude
+  version: dev
+---
+
+# Amplitude integration for JavaScript Web
+
+This skill helps you add Amplitude analytics to JavaScript Web applications.
+
+## Workflow
+
+Follow these steps in order to complete the integration:
+
+1. `basic-integration-1.0-begin.md` - Amplitude Setup - Begin ← **Start here**
+2. `basic-integration-1.1-edit.md` - Amplitude Setup - Edit
+3. `basic-integration-1.2-revise.md` - Amplitude Setup - Revise
+4. `basic-integration-1.3-conclude.md` - Amplitude Setup - Conclusion
+
+## Reference files
+
+- `references/EXAMPLE.md` - JavaScript Web example project code
+- `references/browser-sdk-2.md` - Or install unified SDK to get access to all Amplitude products
+- `references/amplitude-quickstart.md` - Amplitude documentation for Amplitude Quickstart
+- `references/basic-integration-1.0-begin.md` - Amplitude setup - begin
+- `references/basic-integration-1.1-edit.md` - Amplitude setup - edit
+- `references/basic-integration-1.2-revise.md` - Amplitude setup - revise
+- `references/basic-integration-1.3-conclude.md` - Amplitude setup - conclusion
+
+The example project shows the target implementation pattern. Consult the documentation for API details.
+
+## Key principles
+
+- **Environment variables**: Always use environment variables for Amplitude keys. Never hardcode them.
+- **Minimal changes**: Add Amplitude code alongside existing integrations. Don't replace or restructure existing code.
+- **Match the example**: Your implementation should follow the example project's patterns as closely as possible.
+
+## Framework guidelines
+
+- Remember that source code is available in the node_modules directory
+- Check package.json for type checking or build scripts to validate changes
+- @amplitude/analytics-browser is the browser JavaScript SDK package name
+- amplitude.init() MUST be called before any other Amplitude methods (track, identify, etc.)
+- @amplitude/analytics-browser is browser-only — do NOT import it in Node.js or server-side contexts (use @amplitude/analytics-node instead)
+- Autocapture is available with the Amplitude Browser SDK via the autocapture plugin. It is NOT enabled by default — opt in explicitly if the user requests it.
+- NEVER send PII in amplitude.track() event properties — no emails, full names, phone numbers, physical addresses, IP addresses, or user-generated content
+- PII belongs in amplitude.identify() person properties (email, name, role), NOT in track() event properties
+- Call amplitude.setUserId(userId) on login AND on page refresh if the user is already logged in; use amplitude.identify() with an Identify object to set user properties
+- Call amplitude.reset() on logout to unlink future events from the current user
+- For SPAs without a framework router, use the pageViewTracking option in amplitude.init() or manually call amplitude.track('Page Viewed', { path }) for History API routing
+
+## Identifying users
+
+Identify users during login and signup events. Refer to the example code and documentation for the correct identify pattern for this framework. Call `amplitude.setUserId(userId)` to associate events with a known user, and use `amplitude.identify()` with an `Identify` object to set user properties. If both frontend and backend code exist, pass a consistent user/device ID via custom request headers to maintain event correlation.

package/skills/integration/integration-javascript_web/references/EXAMPLE.md

@@ -0,0 +1,451 @@
+# Amplitude JavaScript Web Example Project
+
+Repository: https://github.com/amplitude/context-hub
+Path: basics/javascript-web
+
+---
+
+## README.md
+
+# Amplitude JavaScript Example - Browser Todo App
+
+A simple browser-based todo application built with vanilla JavaScript and Vite, demonstrating Amplitude integration for non-framework JavaScript projects.
+
+This app runs only in the browser.
+
+Use Amplitude’s [Browser Unified SDK (npm)](https://amplitude.com/docs/sdks/analytics/browser/browser-unified-sdk#unified-sdk-npm): add [`@amplitude/unified`](https://www.npmjs.com/package/@amplitude/unified), import it on the client, and call `initAll(apiKey)` once (see `src/amplitude.js`). [Initialize the Unified SDK](https://amplitude.com/docs/sdks/analytics/browser/browser-unified-sdk#initialize-the-unified-sdk) describes that call as initializing every product bundled with Unified npm. Pass a second argument for shared options (`serverZone`, `instanceName`) and for each product (`analytics`, `sessionReplay`, `experiment`, `engagement`); see [Unified SDK configuration](https://amplitude.com/docs/sdks/analytics/browser/browser-unified-sdk#configuration). The `analytics` block accepts the same settings as [Browser SDK 2](https://amplitude.com/docs/sdks/analytics/browser/browser-sdk-2#initialize-the-sdk). Use a non-zero `sessionReplay.sampleRate` when you want Session Replay sampling ([Session Replay plugin](https://amplitude.com/docs/session-replay/session-replay-plugin#configuration)).
+
+The `experiment` block configures **Feature Experiment** (`@amplitude/experiment-js-client`). Amplitude’s [product support table](https://amplitude.com/docs/sdks/analytics/browser/browser-unified-sdk#product-support-by-installation-method) lists **Web Experiment** (`@amplitude/experiment-tag`, including the visual editor) for the Unified **CDN** script, not the Unified **npm** row.
+
+For analytics from Node or other servers, use [`@amplitude/analytics-node`](https://www.npmjs.com/package/@amplitude/analytics-node) (for example the [javascript-node](../javascript-node) app), not `@amplitude/unified`.
+
+## Purpose
+
+This example serves as:
+- **Verification** that the context-hub wizard works for plain JavaScript projects
+- **Reference implementation** of Amplitude best practices for vanilla JS browser apps
+- **Working example** you can run and modify
+
+## Features Demonstrated
+
+- **Amplitude initialization** - `amplitude.initAll()` via `@amplitude/unified`
+- **Autocapture** - Automatic tracking of clicks, form submissions, and pageviews (enabled by default)
+- **Custom event tracking** - Manual `amplitude.track()` calls with event properties
+- **User identification** - `setUserId`, `Identify`, and `identify()` on login; `reset()` on logout
+
+## Quick Start
+
+### 1. Install Dependencies
+
+```bash
+pnpm install
+```
+
+### 2. Configure Amplitude
+
+```bash
+# Copy environment template
+cp .env.example .env
+
+# Edit .env and add your Amplitude API key
+# VITE_PUBLIC_AMPLITUDE_API_KEY=your_amplitude_api_key
+```
+
+### 3. Run the App
+
+```bash
+pnpm dev
+```
+
+Open http://localhost:3000 in your browser.
+
+## What Gets Tracked
+
+The app tracks these custom events in Amplitude (in addition to autocaptured clicks and pageviews):
+
+| Event | Properties | Purpose |
+|-------|-----------|---------|
+| `Todo Added` | `todo_id`, `text_length`, `total_todos` | When user adds a new todo |
+| `Todo Completed` | `todo_id`, `time_to_complete_hours` | When user completes a todo |
+| `Todo Deleted` | `todo_id`, `was_completed` | When user deletes a todo |
+| `User Logged In` | (none) | When user logs in |
+| `User Logged Out` | (none) | When user logs out |
+
+## Code Structure
+
+```
+basics/javascript-web/
+├── index.html           # Entry HTML page
+├── package.json         # Dependencies (@amplitude/unified, vite)
+├── vite.config.js       # Vite configuration
+├── .env.example         # Environment variable template
+├── .gitignore           # Git ignore rules
+├── README.md            # This file
+└── src/
+    ├── amplitude.js       # Amplitude initialization (import this first)
+    ├── main.js          # Todo app logic with event tracking
+    └── style.css        # App styles
+```
+
+## Key Implementation Patterns
+
+### 1. Initialization (amplitude.js)
+
+```javascript
+import * as amplitude from '@amplitude/unified';
+
+void amplitude.initAll(import.meta.env.VITE_PUBLIC_AMPLITUDE_API_KEY);
+
+export default amplitude;
+```
+
+Initialize Amplitude once, early in your app. Other modules import this default export from `amplitude.js`.
+
+### 2. Event tracking
+
+```javascript
+// Track events with properties — never send PII or user-generated content
+amplitude.track('event_name', {
+  item_count: 5,
+  action_type: 'create',
+});
+```
+
+### 3. User identification
+
+```javascript
+import { Identify } from '@amplitude/unified';
+
+amplitude.setUserId(username);
+const identifyObj = new Identify();
+identifyObj.set('name', username);
+amplitude.identify(identifyObj);
+
+// On logout — new anonymous device ID
+amplitude.reset();
+```
+
+## Running Without Amplitude
+
+The app works fine without Amplitude configured. You'll see a console warning but the app continues to function normally.
+
+## Next Steps
+
+- Modify the app to experiment with Amplitude tracking
+- Check your Amplitude dashboard to see tracked events and autocaptured data
+- See [Browser Unified SDK (npm)—configuration](https://amplitude.com/docs/sdks/analytics/browser/browser-unified-sdk#configuration) for Session Replay (`sessionReplay.sampleRate`), Experiment, Guides & Surveys, and shared options
+
+## Learn More
+
+- [Browser Unified SDK](https://amplitude.com/docs/sdks/analytics/browser/browser-unified-sdk) (install methods, **npm vs CDN**, product matrix)
+- [Browser Unified SDK (npm)](https://amplitude.com/docs/sdks/analytics/browser/browser-unified-sdk#unified-sdk-npm) · [Initialize `initAll`](https://amplitude.com/docs/sdks/analytics/browser/browser-unified-sdk#initialize-the-unified-sdk) · [Access SDK features](https://amplitude.com/docs/sdks/analytics/browser/browser-unified-sdk#access-sdk-features)
+- [Browser SDK 2 (analytics options)](https://amplitude.com/docs/sdks/analytics/browser/browser-sdk-2#initialize-the-sdk)
+- [Amplitude Product Analytics](https://amplitude.com/docs/product-analytics)
+
+---
+
+## .env.example
+
+```example
+# Amplitude Configuration
+VITE_PUBLIC_AMPLITUDE_API_KEY=your_amplitude_api_key_here
+
+```
+
+---
+
+## index.html
+
+```html
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>Todo App - Amplitude JavaScript Example</title>
+    <link rel="stylesheet" href="/src/style.css" />
+  </head>
+  <body>
+    <div id="app">
+      <header>
+        <h1>Todo App</h1>
+        <div id="auth-section">
+          <div id="logged-out">
+            <input type="text" id="username-input" placeholder="Enter username" />
+            <button id="login-btn">Log In</button>
+          </div>
+          <div id="logged-in" hidden>
+            <span id="username-display"></span>
+            <button id="logout-btn">Log Out</button>
+          </div>
+        </div>
+      </header>
+
+      <main>
+        <form id="todo-form">
+          <input type="text" id="todo-input" placeholder="What needs to be done?" required />
+          <button type="submit">Add</button>
+        </form>
+
+        <ul id="todo-list"></ul>
+
+        <div id="stats">
+          <span id="total-count">0 items</span>
+          <span id="completed-count">0 completed</span>
+        </div>
+      </main>
+    </div>
+
+    <script type="module" src="/src/main.js"></script>
+  </body>
+</html>
+
+```
+
+---
+
+## src/amplitude.js
+
+```js
+/**
+ * Amplitude initialization for vanilla JavaScript.
+ *
+ * Initializes @amplitude/unified once and exports the instance for use across the app.
+ * This file should be imported before any other modules that call Amplitude methods.
+ */
+import * as amplitude from '@amplitude/unified';
+
+const apiKey = import.meta.env.VITE_PUBLIC_AMPLITUDE_API_KEY;
+
+if (!apiKey) {
+  console.warn(
+    'Amplitude not configured (VITE_PUBLIC_AMPLITUDE_API_KEY not set).',
+    'App will work but analytics will not be tracked.',
+  );
+} else {
+  void amplitude.initAll(apiKey);
+}
+
+export default amplitude;
+
+```
+
+---
+
+## src/main.js
+
+```js
+/**
+ * Simple Todo App with Amplitude Analytics
+ *
+ * A minimal vanilla JavaScript application demonstrating Amplitude integration
+ * for non-framework browser JavaScript projects.
+ */
+import amplitude from './amplitude.js';
+import { Identify } from '@amplitude/unified';
+
+// --- State ---
+
+let todos = JSON.parse(localStorage.getItem('todos') || '[]');
+let currentUser = localStorage.getItem('currentUser') || null;
+
+// --- DOM Elements ---
+
+const todoForm = document.getElementById('todo-form');
+const todoInput = document.getElementById('todo-input');
+const todoList = document.getElementById('todo-list');
+const totalCount = document.getElementById('total-count');
+const completedCount = document.getElementById('completed-count');
+const loginBtn = document.getElementById('login-btn');
+const logoutBtn = document.getElementById('logout-btn');
+const usernameInput = document.getElementById('username-input');
+const usernameDisplay = document.getElementById('username-display');
+const loggedOutSection = document.getElementById('logged-out');
+const loggedInSection = document.getElementById('logged-in');
+
+// --- Auth ---
+
+function login() {
+  const username = usernameInput.value.trim();
+  if (!username) return;
+
+  currentUser = username;
+  localStorage.setItem('currentUser', username);
+
+  // Identify user in Amplitude — links all future events to this user
+  amplitude.setUserId(username);
+  const identifyObj = new Identify();
+  identifyObj.set('name', username);
+  amplitude.identify(identifyObj);
+
+  amplitude.track('User Logged In');
+
+  updateAuthUI();
+  usernameInput.value = '';
+}
+
+function logout() {
+  currentUser = null;
+  localStorage.removeItem('currentUser');
+
+  // Reset Amplitude — unlinks future events from the current user
+  // and generates a new anonymous device ID
+  amplitude.reset();
+
+  amplitude.track('User Logged Out');
+
+  updateAuthUI();
+}
+
+function updateAuthUI() {
+  if (currentUser) {
+    loggedOutSection.hidden = true;
+    loggedInSection.hidden = false;
+    usernameDisplay.textContent = currentUser;
+  } else {
+    loggedOutSection.hidden = false;
+    loggedInSection.hidden = true;
+  }
+}
+
+// --- Todos ---
+
+function addTodo(text) {
+  const todo = {
+    id: Date.now(),
+    text,
+    completed: false,
+    createdAt: new Date().toISOString(),
+  };
+
+  todos.push(todo);
+  saveTodos();
+  renderTodos();
+
+  // Track the event — only metadata, never PII or user-generated content
+  amplitude.track('Todo Added', {
+    todo_id: todo.id,
+    text_length: text.length,
+    total_todos: todos.length,
+  });
+}
+
+function toggleTodo(id) {
+  const todo = todos.find((t) => t.id === id);
+  if (!todo) return;
+
+  todo.completed = !todo.completed;
+  saveTodos();
+  renderTodos();
+
+  if (todo.completed) {
+    const timeToComplete =
+      (Date.now() - new Date(todo.createdAt).getTime()) / 3600000;
+
+    amplitude.track('Todo Completed', {
+      todo_id: todo.id,
+      time_to_complete_hours: Math.round(timeToComplete * 100) / 100,
+    });
+  }
+}
+
+function deleteTodo(id) {
+  const todo = todos.find((t) => t.id === id);
+  if (!todo) return;
+
+  todos = todos.filter((t) => t.id !== id);
+  saveTodos();
+  renderTodos();
+
+  amplitude.track('Todo Deleted', {
+    todo_id: todo.id,
+    was_completed: todo.completed,
+  });
+}
+
+function saveTodos() {
+  localStorage.setItem('todos', JSON.stringify(todos));
+}
+
+// --- Rendering ---
+
+function renderTodos() {
+  todoList.innerHTML = '';
+
+  for (const todo of todos) {
+    const li = document.createElement('li');
+    li.className = `todo-item${todo.completed ? ' completed' : ''}`;
+
+    const checkbox = document.createElement('input');
+    checkbox.type = 'checkbox';
+    checkbox.checked = todo.completed;
+    checkbox.addEventListener('change', () => toggleTodo(todo.id));
+
+    const text = document.createElement('span');
+    text.className = 'todo-text';
+    text.textContent = todo.text;
+
+    const deleteBtn = document.createElement('button');
+    deleteBtn.className = 'delete-btn';
+    deleteBtn.textContent = 'Delete';
+    deleteBtn.addEventListener('click', () => deleteTodo(todo.id));
+
+    li.append(checkbox, text, deleteBtn);
+    todoList.appendChild(li);
+  }
+
+  // Update stats
+  const completed = todos.filter((t) => t.completed).length;
+  totalCount.textContent = `${todos.length} item${todos.length !== 1 ? 's' : ''}`;
+  completedCount.textContent = `${completed} completed`;
+}
+
+// --- Event Listeners ---
+
+todoForm.addEventListener('submit', (e) => {
+  e.preventDefault();
+  const text = todoInput.value.trim();
+  if (text) {
+    addTodo(text);
+    todoInput.value = '';
+  }
+});
+
+loginBtn.addEventListener('click', login);
+usernameInput.addEventListener('keydown', (e) => {
+  if (e.key === 'Enter') login();
+});
+logoutBtn.addEventListener('click', logout);
+
+// --- Init ---
+
+// Restore auth state and re-identify if already logged in
+if (currentUser) {
+  amplitude.setUserId(currentUser);
+  const identifyObj = new Identify();
+  identifyObj.set('name', currentUser);
+  amplitude.identify(identifyObj);
+}
+
+updateAuthUI();
+renderTodos();
+
+```
+
+---
+
+## vite.config.js
+
+```js
+import { defineConfig } from 'vite';
+
+export default defineConfig({
+  server: {
+    port: 3000,
+  },
+});
+
+```
+
+---
+