@yottagraph-app/aether-instructions 1.1.42 → 1.1.43

package/{rules/architecture.mdc → skills/aether/architecture.md}

@@ -1,15 +1,10 @@
----
-description: "Project structure, navigation patterns, data architecture, server routes, agents, MCP servers. Read when adding pages, navigation, or server-side functionality."
-alwaysApply: false
----
-
 # Aether Architecture
 
 Aether is an app framework built on Nuxt 3 + Vue 3 + Vuetify 3 + TypeScript. It follows standard Nuxt conventions -- pages in `pages/`, components in `components/`, composables in `composables/`, server routes in `server/api/`.
 
 **Tech stack**: Nuxt 3 (SPA), Vue 3 Composition API (`<script setup>`), Vuetify 3, TypeScript (required), Auth0 (automatic).
 
-**Data source**: This app runs on the Lovelace platform (entities, news, filings, sentiment, relationships, events). See the `data` rule for how your app accesses that data. Do not call external APIs for data the platform provides.
+**Data source**: This app runs on the Lovelace platform (entities, news, filings, sentiment, relationships, events). See [data.md](data.md) in this skill for how your app accesses that data. Do not call external APIs for data the platform provides.
 
 ## Project Structure
 
@@ -26,13 +21,13 @@ mcp-servers/        # MCP servers (Python, deploy to Cloud Run)
 
 ## Data Architecture
 
-| Store | Purpose | When to use |
-|---|---|---|
-| Platform data (Query Server / Postgres per your architecture) | Lovelace knowledge graph or synced local data | See the `data` rule |
-| KV (Upstash Redis) | User preferences, lightweight state | Settings, watchlists, UI state that should persist |
-| Neon Postgres | App-specific relational data | Custom tables, complex queries (if provisioned — see the `storage` rule for how to check) |
+| Store                                                         | Purpose                                       | When to use                                                                                     |
+| ------------------------------------------------------------- | --------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| Platform data (Query Server / Postgres per your architecture) | Lovelace knowledge graph or synced local data | See [data.md](data.md)                                                                          |
+| KV (Upstash Redis)                                            | User preferences, lightweight state           | Settings, watchlists, UI state that should persist                                              |
+| Neon Postgres                                                 | App-specific relational data                  | Custom tables, complex queries (if provisioned — see [storage.md](storage.md) for how to check) |
 
-See the `storage` rule to check which stores are available, then `pref` (client-side KV) and `server` (Neon usage) for detailed patterns.
+See [storage.md](storage.md) for backend selection and server-side usage (both KV and Neon Postgres), plus [pref.md](pref.md) for the client-side `Pref<T>` pattern.
 
 ## Adding Pages
 
@@ -115,8 +110,8 @@ Use server routes when you need to proxy external APIs (avoid CORS), access
 data server-side, or keep secrets off the client. Call them from client code
 with `$fetch('/api/my-data/fetch')`.
 
-See the `server` rule for file-routing conventions and Neon Postgres patterns.
-See `server-data` when calling the platform Query Server from server routes.
+See [server.md](server.md) for file-routing conventions and [storage.md](storage.md) for Neon Postgres patterns.
+See [server-data.md](server-data.md) when calling the platform Query Server from server routes.
 
 ## Beyond the UI: Agents, MCP Servers, and Server Routes
 
@@ -124,7 +119,7 @@ Aether apps are more than just a Nuxt SPA. The project contains three additional
 
 ### `agents/` -- ADK Agents (Python)
 
-Each subdirectory is a self-contained Python agent that deploys to Vertex AI Agent Engine. See the `agents` cursor rule for development patterns. Agents are deployed via the Broadchurch Portal UI or the `/deploy_agent` Cursor command, both of which trigger `deploy-agent.yml`. Use the `useAgentChat` composable to build a chat UI that talks to them.
+Each subdirectory is a self-contained Python agent that deploys to Vertex AI Agent Engine. See [agents.md](agents.md) for development patterns. Agents are deployed via the Broadchurch Portal UI or the `/deploy_agent` Cursor command, both of which trigger `deploy-agent.yml`. Use the `useAgentChat` composable to build a chat UI that talks to them.
 
 **Agent query path:** The app talks to Agent Engine directly — the portal is
 only in the auth path. The flow is:
@@ -142,7 +137,7 @@ project detail page for IAM health status.
 
 ### `mcp-servers/` -- MCP Servers (Python)
 
-Each subdirectory is a FastMCP server that deploys to Cloud Run. See the `mcp-servers` cursor rule. Deployed via Portal UI or `/deploy_mcp`, triggering `deploy-mcp.yml`. Agents can connect to MCP servers as tool providers.
+Each subdirectory is a FastMCP server that deploys to Cloud Run. See [mcp-servers.md](mcp-servers.md). Deployed via Portal UI or `/deploy_mcp`, triggering `deploy-mcp.yml`. Agents can connect to MCP servers as tool providers.
 
 ### `broadchurch.yaml`
 
@@ -157,11 +152,10 @@ Use these to build whatever UI fits the app:
   local Nitro streaming route (`/api/agent/:agentId/stream`) which calls
   Agent Engine directly with a tenant SA token. Handles streaming, session
   management, and response parsing. Shows clear error messages when IAM
-  permissions are missing. See the `agents` cursor rule for details.
+  permissions are missing. See [agents.md](agents.md) for details.
 - **`useTenantConfig()`** -- Fetch the tenant's runtime config (deployed
   agents, feature flags, MCP servers) from the Portal Gateway.
 - **`useElementalClient()`** -- When using the Elemental API from the client,
-  see the `data` rule.
+  see [data.md](data.md).
 - **`usePrefsStore()` / `Pref<T>`** -- KV-backed user preferences. See
-  the `pref` rule.
-
+  [pref.md](pref.md).

package/{rules/branding.mdc → skills/aether/branding.md}

@@ -1,8 +1,3 @@
----
-description: Apply when working on visual styling, colors, typography, theming, branding, or UI appearance.
-alwaysApply: false
----
-
 # Lovelace Branding
 
 The `lovelace-branding` skill (`skills/lovelace-branding/`) is the single source of truth for all brand specifics -- colors, typography, patterns, assets, and usage guidelines. Read the skill before making branding decisions. Start with `SKILL.md` for the file index.
@@ -15,13 +10,13 @@ Single dark theme. No light mode, no theme switching.
 
 These files are project-owned. Consult the branding skill for the values and patterns they should implement.
 
-| File | Role |
-|------|------|
-| `assets/brand-globals.css` | `:root` CSS variables and global typography/layout |
-| `assets/fonts.css` | `@font-face` declarations |
-| `assets/theme-styles.css` | Theme-aware CSS utility classes |
-| `composables/useLovelaceTheme.ts` | Theme color palette and Vuetify theme activation |
-| `composables/useThemeClasses.ts` | Theme-aware class combination utilities |
+| File                              | Role                                               |
+| --------------------------------- | -------------------------------------------------- |
+| `assets/brand-globals.css`        | `:root` CSS variables and global typography/layout |
+| `assets/fonts.css`                | `@font-face` declarations                          |
+| `assets/theme-styles.css`         | Theme-aware CSS utility classes                    |
+| `composables/useLovelaceTheme.ts` | Theme color palette and Vuetify theme activation   |
+| `composables/useThemeClasses.ts`  | Theme-aware class combination utilities            |
 
 ## Integration
 

package/{rules/cookbook-data.mdc → skills/aether/cookbook-data.md}

@@ -1,17 +1,12 @@
----
-description: "Data-fetching UI recipes: entity search, news feed, filings, gateway helpers. Read with the `data` rule when building pages that use the Query Server or platform data."
-alwaysApply: false
----
-
 # Data-fetching cookbook
 
-Copy-paste patterns that call the Elemental API, gateway, or helpers. For platform API details see the `data` rule. Pure UI patterns (tables, forms, charts) are in the `cookbook` rule.
+Copy-paste patterns that call the Elemental API, gateway, or helpers. For platform API details see [data.md](data.md) in this skill. Pure UI patterns (tables, forms, charts) are in [cookbook.md](cookbook.md).
 
 ## 1. Entity Search Page
 
 Search for entities by name and display results. Uses `$fetch` directly
 because `POST /entities/search` (batch name resolution with scored ranking)
-is not wrapped by the generated `useElementalClient()` — see the `data` rule.
+is not wrapped by the generated `useElementalClient()` — see [data.md](data.md).
 
 ```vue
 <template>
@@ -182,8 +177,8 @@ for runtime flavor/PID discovery and `buildGatewayUrl()` for gateway access.
                 const vals = valueMap.get(neid) ?? {};
                 return {
                     neid,
-                    name: namePid ? (vals[namePid] as string) ?? neid : neid,
-                    sentiment: sentimentPid ? (vals[sentimentPid] as number) ?? null : null,
+                    name: namePid ? ((vals[namePid] as string) ?? neid) : neid,
+                    sentiment: sentimentPid ? ((vals[sentimentPid] as number) ?? null) : null,
                 };
             });
         } catch (e: any) {
@@ -215,12 +210,7 @@ Simpler version of recipe #1 using the pre-built `searchEntities()` helper.
             {{ error }}
         </v-alert>
         <v-list v-if="results.length" class="mt-4">
-            <v-list-item
-                v-for="r in results"
-                :key="r.neid"
-                :title="r.name"
-                :subtitle="r.neid"
-            />
+            <v-list-item v-for="r in results" :key="r.neid" :title="r.name" :subtitle="r.neid" />
         </v-list>
         <v-empty-state
             v-else-if="searched && !loading"
@@ -266,7 +256,7 @@ properties are then fetched via `useElementalClient()`.
 **Important:** For graph-layer entities (person, organization, location),
 use `findEntities` with a `linked` expression. For property-layer entities
 (documents, filings, articles), use `getPropertyValues` with the
-relationship PID. See the `data` rule for the two-layer architecture.
+relationship PID. See [data.md](data.md) for the two-layer architecture.
 
 ```vue
 <template>
@@ -366,7 +356,7 @@ relationship PID. See the `data` rule for the two-layer architecture.
             });
 
             const docNeids = (propRes.values ?? []).map((v: any) =>
-                String(v.value).padStart(20, '0'),
+                String(v.value).padStart(20, '0')
             );
 
             function getEntityNameUrl(neid: string) {
@@ -379,15 +369,14 @@ relationship PID. See the `data` rule for the two-layer architecture.
             const names = await Promise.all(
                 docNeids.map(async (neid: string) => {
                     try {
-                        const res = await $fetch<{ name: string }>(
-                            getEntityNameUrl(neid),
-                            { headers: { 'X-Api-Key': getApiKey() } },
-                        );
+                        const res = await $fetch<{ name: string }>(getEntityNameUrl(neid), {
+                            headers: { 'X-Api-Key': getApiKey() },
+                        });
                         return res.name || neid;
                     } catch {
                         return neid;
                     }
-                }),
+                })
             );
 
             filings.value = docNeids.map((neid: string, i: number) => ({
@@ -430,11 +419,7 @@ Type-ahead search that shows results in a dropdown as the user types. Uses
             @click:clear="onClear"
         />
 
-        <v-card
-            v-if="showMenu && suggestions.length > 0"
-            class="search-dropdown"
-            elevation="8"
-        >
+        <v-card v-if="showMenu && suggestions.length > 0" class="search-dropdown" elevation="8">
             <v-list density="compact">
                 <v-list-item
                     v-for="item in suggestions"
@@ -457,7 +442,7 @@ Type-ahead search that shows results in a dropdown as the user types. Uses
             icon?: string;
             flavors?: string[];
         }>(),
-        { label: 'Search', icon: 'mdi-magnify', flavors: undefined },
+        { label: 'Search', icon: 'mdi-magnify', flavors: undefined }
     );
 
     const emit = defineEmits<{

package/{rules/cookbook.mdc → skills/aether/cookbook.md}

@@ -1,13 +1,8 @@
----
-description: "Copy-paste UI patterns for common pages: data table, form, chart, dialog, master-detail. For Query Server / data-fetching recipes see `cookbook-data`."
-alwaysApply: false
----
-
 # UI Pattern Cookbook
 
 Copy-paste patterns using the project's actual composables and Vuetify components. Adapt to your needs.
 
-**Data-fetching recipes** (entity search, news feed, filings, gateway helpers) live in the `cookbook-data` rule.
+**Data-fetching recipes** (entity search, news feed, filings, gateway helpers) live in [cookbook-data.md](cookbook-data.md).
 
 ## 2. Data Table Page
 
@@ -98,9 +93,7 @@ Form with field validation, submit handler, and user feedback.
                 variant="outlined"
                 class="mb-3"
             />
-            <v-btn type="submit" color="primary" :loading="saving" :disabled="!valid">
-                Save
-            </v-btn>
+            <v-btn type="submit" color="primary" :loading="saving" :disabled="!valid"> Save </v-btn>
         </v-form>
     </v-container>
 </template>

package/{rules/cursor-cloud.mdc → skills/aether/cursor-cloud.md}

@@ -1,8 +1,3 @@
----
-description: Cursor Cloud environment quirks (Node managed by env, dev server auto-started, skip browser testing during initial setup). Apply when the environment check in AGENTS.md indicates Cursor Cloud ($HOME under /root or /home/ubuntu, or a dev-server terminal was auto-started), or when the user mentions Cursor Cloud.
-alwaysApply: false
----
-
 If you are in Cursor Cloud, the `environment.json` install step runs
 `init-project.js` and `npm install` automatically, and starts a dev server
 on port 3000.
@@ -59,4 +54,4 @@ check) and `npm run format:check` (Prettier). See Verification Commands.
 
 **Before committing:** always run `npm run format` — the husky pre-commit
 hook runs `lint-staged` with `prettier --check` and will reject
-unformatted files.
+unformatted files.

package/{rules/data.mdc → skills/aether/data.md}

@@ -1,7 +1,3 @@
----
-description: "Data access via Elemental API: client usage, schema discovery, entity search, API gotchas, MCP servers. Read when building features that fetch or display data from the Query Server."
-alwaysApply: false
----
 # Data — Elemental API (platform data source)
 
 **This app is built on the Lovelace platform.** The Query Server is the
@@ -81,10 +77,10 @@ Test those with curl before implementing them in code.
 The gateway proxy authenticates on your behalf — no Auth0 tokens needed.
 Read `broadchurch.yaml` for the three values you need:
 
-| YAML path | Purpose |
-|---|---|
-| `gateway.url` | Portal Gateway base URL |
-| `tenant.org_id` | Your tenant ID (path segment) |
+| YAML path            | Purpose                              |
+| -------------------- | ------------------------------------ |
+| `gateway.url`        | Portal Gateway base URL              |
+| `tenant.org_id`      | Your tenant ID (path segment)        |
 | `gateway.qs_api_key` | API key (sent as `X-Api-Key` header) |
 
 Build the request URL as `{gateway.url}/api/qs/{tenant.org_id}/{endpoint}`
@@ -141,9 +137,9 @@ Elemental API patterns. **Use these instead of writing from scratch:**
 
 ```typescript
 const { flavors, properties, flavorByName, pidByName, refresh } = useElementalSchema();
-await refresh();                                // fetches once, then cached
-const articleFid = flavorByName('article');      // → string | null
-const namePid = pidByName('name');              // → string | null
+await refresh(); // fetches once, then cached
+const articleFid = flavorByName('article'); // → string | null
+const namePid = pidByName('name'); // → string | null
 ```
 
 Handles the dual response shapes (`res.schema.flavors` vs `res.flavors`)
@@ -152,14 +148,20 @@ and the `fid`/`findex` naming inconsistency automatically.
 ### `utils/elementalHelpers` — Gateway URL Helpers
 
 ```typescript
-import { buildGatewayUrl, getApiKey, padNeid, searchEntities, getEntityName } from '~/utils/elementalHelpers';
-
-const url = buildGatewayUrl('entities/search');   // full gateway URL
-const key = getApiKey();                          // from runtimeConfig
-const neid = padNeid('4926132345040704022');       // → "04926132345040704022"
+import {
+    buildGatewayUrl,
+    getApiKey,
+    padNeid,
+    searchEntities,
+    getEntityName,
+} from '~/utils/elementalHelpers';
+
+const url = buildGatewayUrl('entities/search'); // full gateway URL
+const key = getApiKey(); // from runtimeConfig
+const neid = padNeid('4926132345040704022'); // → "04926132345040704022"
 
 const results = await searchEntities('Microsoft'); // batch name search
-const name = await getEntityName(neid);            // display name lookup
+const name = await getEntityName(neid); // display name lookup
 ```
 
 ## Client Usage
@@ -174,7 +176,10 @@ const client = useElementalClient();
 
 const schema = await client.getSchema();
 const entities = await client.findEntities({
-    expression: JSON.stringify({ type: 'comparison', comparison: { operator: 'string_like', pid: 8, value: 'Apple' } }),
+    expression: JSON.stringify({
+        type: 'comparison',
+        comparison: { operator: 'string_like', pid: 8, value: 'Apple' },
+    }),
     limit: 5,
 });
 ```
@@ -185,8 +190,8 @@ All methods return data directly and throw on non-2xx responses.
 
 **Entity search and lookup:**
 
-| Method | Signature | Purpose |
-|---|---|---|
+| Method         | Signature                  | Purpose                                 |
+| -------------- | -------------------------- | --------------------------------------- |
 | `findEntities` | `(body: FindEntitiesBody)` | Expression-based search (see `find.md`) |
 
 > **Entity search**: Use `findEntities()` with `string_like` on the name PID
@@ -201,25 +206,25 @@ All methods return data directly and throw on non-2xx responses.
 
 **Properties and schema:**
 
-| Method | Signature | Purpose |
-|---|---|---|
-| `getSchema` | `()` | All entity types (flavors) and properties (PIDs) |
+| Method              | Signature                                | Purpose                                                                              |
+| ------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------ |
+| `getSchema`         | `()`                                     | All entity types (flavors) and properties (PIDs)                                     |
 | `getPropertyValues` | `(body: { eids: string, pids: string })` | Property values (eids: JSON array of NEID strings; pids: JSON array of numeric PIDs) |
-| `summarizeProperty` | `(pid: number)` | Summary stats for a property |
+| `summarizeProperty` | `(pid: number)`                          | Summary stats for a property                                                         |
 
 **Relationships and graph:**
 
-| Method | Signature | Purpose |
-|---|---|---|
+| Method         | Signature                        | Purpose                                                      |
+| -------------- | -------------------------------- | ------------------------------------------------------------ |
 | `findEntities` | `(body: { expression, limit? })` | Find linked entities via `linked` expression (see `find.md`) |
 
 **Other:**
 
-| Method | Signature | Purpose |
-|---|---|---|
-| `getHealth` | `()` | Health check |
-| `getStatus` | `()` | Server status and capabilities |
-| `adaMessage` | `(body: AdaMessageBody)` | Ada AI chat |
+| Method       | Signature                | Purpose                        |
+| ------------ | ------------------------ | ------------------------------ |
+| `getHealth`  | `()`                     | Health check                   |
+| `getStatus`  | `()`                     | Server status and capabilities |
+| `adaMessage` | `(body: AdaMessageBody)` | Ada AI chat                    |
 
 ## Discovery-First Pattern
 
@@ -230,16 +235,16 @@ types or property names. Instead, discover them at runtime:
 1. **Get the schema** — `client.getSchema()` returns all entity types (flavors)
    and properties (PIDs) available in the system. See `schema.md`.
 
-   The schema response contains:
-   - **Flavors** (entity types): Company, Person, GovernmentOrg, etc.
-     Each flavor has a numeric ID and a human-readable name.
-   - **PIDs** (properties): name, country, industry, lei_code, etc.
-     Each PID has a type (`data_str`, `data_int`, `data_nindex`, etc.).
-   - Properties with type `data_nindex` are references to other entities —
-     resolve them with another `getPropertyValues` call.
+    The schema response contains:
+    - **Flavors** (entity types): Company, Person, GovernmentOrg, etc.
+      Each flavor has a numeric ID and a human-readable name.
+    - **PIDs** (properties): name, country, industry, lei_code, etc.
+      Each PID has a type (`data_str`, `data_int`, `data_nindex`, etc.).
+    - Properties with type `data_nindex` are references to other entities —
+      resolve them with another `getPropertyValues` call.
 
-   Use flavor names in `findEntities()` expressions and PID names in
-   `getPropertyValues()`.
+    Use flavor names in `findEntities()` expressions and PID names in
+    `getPropertyValues()`.
 
 2. **Search with expressions** — `client.findEntities()` uses a JSON expression
    language to search by type, property value, or relationship. See `find.md`.
@@ -269,10 +274,10 @@ For reliable agent behavior, prefer typed semantics over string heuristics:
 
 There are two schema endpoints with **different response shapes**:
 
-| Endpoint | Flavors at | Flavor ID field | Detail level |
-|----------|-----------|-----------------|--------------|
-| `GET /schema` | top-level (`res.flavors`) | `findex` | Rich (display names, units, domains) |
-| `GET /elemental/metadata/schema` | nested (`res.schema.flavors`) | `fid` | Basic (name + type only) |
+| Endpoint                         | Flavors at                    | Flavor ID field | Detail level                         |
+| -------------------------------- | ----------------------------- | --------------- | ------------------------------------ |
+| `GET /schema`                    | top-level (`res.flavors`)     | `findex`        | Rich (display names, units, domains) |
+| `GET /elemental/metadata/schema` | nested (`res.schema.flavors`) | `fid`           | Basic (name + type only)             |
 
 The TypeScript client's `getSchema()` calls `/elemental/metadata/schema`,
 so the response nests data under `.schema`. The generated types may suggest
@@ -296,12 +301,12 @@ The flavor identifier has **different field names** depending on the endpoint:
 Same value, different key. Always use a fallback:
 
 ```typescript
-const articleFlavor = flavors.find(f => f.name === 'article');
+const articleFlavor = flavors.find((f) => f.name === 'article');
 // Always use String() — safe for small IDs (12) and required for large ones
 const articleFid = String(articleFlavor?.fid ?? articleFlavor?.findex ?? '');
 
 // When building a FID lookup map:
-const fidMap = new Map(flavors.map(f => [String(f.fid ?? f.findex), f.name]));
+const fidMap = new Map(flavors.map((f) => [String(f.fid ?? f.findex), f.name]));
 ```
 
 The `is_type` expression in `/elemental/find` always uses the `fid` key
@@ -352,14 +357,14 @@ const filingNeid = String(res.values[0].value).padStart(20, '0'); // "0492613234
 ```typescript
 // WRONG — PIDs are numbers, not strings:
 const values = await client.getPropertyValues({
-  eids: JSON.stringify(['00416400910670863867']),
-  pids: JSON.stringify(['name', 'country', 'industry']),  // FAILS
+    eids: JSON.stringify(['00416400910670863867']),
+    pids: JSON.stringify(['name', 'country', 'industry']), // FAILS
 });
 
 // CORRECT — use numeric PIDs from getSchema():
 const values = await client.getPropertyValues({
-  eids: JSON.stringify(['00416400910670863867']),
-  pids: JSON.stringify([8, 313]),  // 8=name, 313=country (from schema)
+    eids: JSON.stringify(['00416400910670863867']),
+    pids: JSON.stringify([8, 313]), // 8=name, 313=country (from schema)
 });
 ```
 
@@ -409,7 +414,7 @@ const res = await client.getPropertyValues({
 const docNeids = (res.values ?? []).map((v) => String(v.value).padStart(20, '0'));
 ```
 
-See the **cookbook-data** rule for a full "Get filings for a company" recipe.
+See [cookbook-data.md](cookbook-data.md) in this skill for a full "Get filings for a company" recipe.
 
 ### Expression language pitfalls
 
@@ -455,14 +460,17 @@ source-specific schemas.
   `getPropertyValues()` with the relationship PID. Values are entity IDs
   that must be zero-padded to 20 characters.
 
-See the **cookbook-data** rule (news feed recipe) for a full example.
+See [cookbook-data.md](cookbook-data.md) (news feed recipe) for a full example.
 
 ## Error Handling
 
 ```typescript
 try {
     const data = await client.findEntities({
-        expression: JSON.stringify({ type: 'comparison', comparison: { operator: 'string_like', pid: 8, value: 'Apple' } }),
+        expression: JSON.stringify({
+            type: 'comparison',
+            comparison: { operator: 'string_like', pid: 8, value: 'Apple' },
+        }),
         limit: 5,
     });
 } catch (error) {
@@ -479,7 +487,9 @@ functions instead:
 import { getArticle } from '@yottagraph-app/elemental-api/client';
 
 const response = await getArticle(artid);
-if (response.status === 404) { /* handle not found */ }
+if (response.status === 404) {
+    /* handle not found */
+}
 ```
 
 ## Lovelace MCP Servers
@@ -490,25 +500,25 @@ data exploration. **Check your tool list** — if tools like
 exploration interface before writing code. If they don't appear, the
 servers aren't connected; use curl and the skill docs instead.
 
-| Server | What it provides |
-|---|---|
-| `lovelace-elemental` | Knowledge Graph: entities, relationships, events, sentiment, schema discovery |
-| `lovelace-stocks` | Stock/financial market data |
-| `lovelace-wiki` | Wikipedia entity enrichment |
-| `lovelace-polymarket` | Prediction market data |
+| Server                | What it provides                                                              |
+| --------------------- | ----------------------------------------------------------------------------- |
+| `lovelace-elemental`  | Knowledge Graph: entities, relationships, events, sentiment, schema discovery |
+| `lovelace-stocks`     | Stock/financial market data                                                   |
+| `lovelace-wiki`       | Wikipedia entity enrichment                                                   |
+| `lovelace-polymarket` | Prediction market data                                                        |
 
 ### MCP Tool Quick Reference
 
-| Tool | Purpose | Use to verify... |
-|---|---|---|
-| `elemental_get_schema` | Discover entity types (flavors), properties, and relationships | Flavor IDs, property IDs, data types |
-| `elemental_get_entity` | Look up entity by name or NEID; returns properties | Entity resolution, property shapes |
-| `elemental_get_related` | Related entities with type/relationship filters | Relationship types and traversal |
-| `elemental_get_relationships` | Relationship types and counts between two entities | Edge types between specific entities |
-| `elemental_graph_neighborhood` | Most influential neighbors of an entity | Graph connectivity |
-| `elemental_graph_sentiment` | Sentiment analysis from news articles | Sentiment data availability |
-| `elemental_get_events` | Events for an entity or by search query | Event categories and shapes |
-| `elemental_health` | Health check | Server connectivity |
+| Tool                           | Purpose                                                        | Use to verify...                     |
+| ------------------------------ | -------------------------------------------------------------- | ------------------------------------ |
+| `elemental_get_schema`         | Discover entity types (flavors), properties, and relationships | Flavor IDs, property IDs, data types |
+| `elemental_get_entity`         | Look up entity by name or NEID; returns properties             | Entity resolution, property shapes   |
+| `elemental_get_related`        | Related entities with type/relationship filters                | Relationship types and traversal     |
+| `elemental_get_relationships`  | Relationship types and counts between two entities             | Edge types between specific entities |
+| `elemental_graph_neighborhood` | Most influential neighbors of an entity                        | Graph connectivity                   |
+| `elemental_graph_sentiment`    | Sentiment analysis from news articles                          | Sentiment data availability          |
+| `elemental_get_events`         | Events for an entity or by search query                        | Event categories and shapes          |
+| `elemental_health`             | Health check                                                   | Server connectivity                  |
 
 MCP tools handle entity resolution, PID lookups, and NEID formatting
 automatically. Use them to discover IDs and verify data exists before

package/{rules/deployment.mdc → skills/aether/deployment.md}

@@ -1,8 +1,3 @@
----
-description: App, agent, and MCP server deployment targets (Vercel, Vertex AI Agent Engine, Cloud Run). Apply when pushing to main, running /deploy_agent or /deploy_mcp, or explaining how code reaches production.
-alwaysApply: false
----
-
 ### App (Nuxt UI + server routes)
 
 Vercel auto-deploys on every push to `main`. Preview deployments are created for
@@ -16,4 +11,4 @@ the Portal UI or `/deploy_agent` in Cursor.
 ### MCP Servers (`mcp-servers/`)
 
 Each subdirectory in `mcp-servers/` is a Python FastMCP server. Deploy via
-the Portal UI or `/deploy_mcp` in Cursor.
+the Portal UI or `/deploy_mcp` in Cursor.

package/{rules/design.mdc → skills/aether/design.md}

@@ -1,8 +1,3 @@
----
-description: "DESIGN.md workflow, feature docs, starter app is placeholder. Read when starting work, planning features, or updating project design."
-alwaysApply: false
----
-
 # Design
 
 Read `DESIGN.md` before starting any work. It is the source of truth for project vision, architecture, and current implementation status.
@@ -58,4 +53,4 @@ If the user is implementing a change that has no feature doc, encourage them to
 
 **Exception for initial app builds:** When building a new app from scratch via `/build_my_app`, skip per-page feature docs. They add overhead during greenfield builds where the entire app is being created at once. Start using feature docs once the initial app is built and you're iterating on individual features.
 
-It is a good practice to close out one feature doc and start a new one as the focus of the work shifts. It is acceptable to be working with multiple feature docs at once, if the user is working on multiple unconnected or loosely connected features. The sections of the feature doc are flexible and you should add or remove sections to fit the needs of the project.
+It is a good practice to close out one feature doc and start a new one as the focus of the work shifts. It is acceptable to be working with multiple feature docs at once, if the user is working on multiple unconnected or loosely connected features. The sections of the feature doc are flexible and you should add or remove sections to fit the needs of the project.

package/{rules/env.mdc → skills/aether/env.md}

@@ -1,8 +1,3 @@
----
-description: .env variable reference (APP_ID, USER_NAME, QUERY_SERVER_ADDRESS, etc.). Apply when adding env vars, configuring Auth0 bypass, or inspecting runtime config.
-alwaysApply: false
----
-
 | Variable                           | Purpose                          | Default                                 |
 | ---------------------------------- | -------------------------------- | --------------------------------------- |
 | `NUXT_PUBLIC_APP_ID`               | Unique app identifier            | derived from directory name             |

package/{rules/git-support.mdc → skills/aether/git-support.md}

@@ -1,11 +1,6 @@
----
-description: "Git commit workflow and conventions. Apply when finishing implementation work, making commits, or troubleshooting git/pre-commit failures."
-alwaysApply: false
----
-
 # Git Workflow
 
-This rule applies both when an agent is committing its own work and when helping a user commit theirs.
+This guidance applies both when an agent is committing its own work and when helping a user commit theirs.
 
 ## Committing
 
@@ -14,9 +9,9 @@ Commit when you finish a meaningful unit of work — a feature, a fix, a refacto
 ### Steps
 
 1. **Run formatting first** — this is required or the commit will fail:
-   ```bash
-   npm run format
-   ```
+    ```bash
+    npm run format
+    ```
 2. **Stage all files** — always use `git add -A`.
 3. **Commit** with the message format below.
 4. **Verify the commit succeeded** with `git status`. If it failed, see Pre-commit Failure Troubleshooting below. Do not proceed until the commit is confirmed.