@yottagraph-app/aether-instructions 1.1.41 → 1.1.43

package/rules/aether.mdc

@@ -1,21 +0,0 @@
----
-alwaysApply: true
----
-
-# Aether
-
-**Stack:** Nuxt 3 (SPA), Vue 3 Composition API (`<script setup>`), Vuetify 3, TypeScript (required), Auth0.
-
-**Structure:** `pages/` (file-based routing), `components/`, `composables/`, `server/api/`, `agents/` (Python ADK), `mcp-servers/` (Python FastMCP).
-
-**Data:** This app runs on the Lovelace platform -- entities, news, filings, sentiment, relationships, events. See the `data` rule for access patterns and gotchas. Skill docs: `skills/data-model/` (entity types, properties, relationships; `SKILL.md` first), `skills/elemental-mcp-patterns/` (MCP response shapes, property type handling, Python patterns for agent tools). Do NOT call external APIs for data the platform provides.
-
-**Storage:** KV (Upstash Redis) for preferences and lightweight state via `Pref<T>` from `usePrefsStore()`. Neon Postgres for relational data if connected (check `.env` for `DATABASE_URL`).
-
-**Source of truth:** `DESIGN.md` -- read before starting work, update when changing features. The starter UI is placeholder -- replace freely. Feature docs in `design/` for implementation planning.
-
-**Git:** Commit meaningful units of work. Run `npm run format` before commit. Message format: `[Agent commit] {summary}`. Push directly to main — do NOT create PRs or feature branches.
-
-**First action for a new project:** Run `/build_my_app`.
-
-**Task-specific rules:** `architecture` (project structure, navigation, server routes, agents, MCP), `data` (Elemental API / data access patterns and gotchas), `cookbook` (copy-paste UI patterns), `cookbook-data` (data-fetching recipes), `design` (DESIGN.md workflow, feature docs), `ui` (page templates, layout patterns), `pref` (KV preferences), `branding` (colors, fonts), `server` (Nitro routes, Neon Postgres), `server-data` (server-side Elemental API from routes), `agents` (ADK agents), `agents-data` (agents calling Elemental API), `something-broke` (error recovery, build failures).

package/rules/server-data.mdc

@@ -1,54 +0,0 @@
----
-description: "Calling the Elemental API from Nitro server routes via the Portal Gateway. Read when proxying Query Server calls server-side."
-alwaysApply: false
-globs: server/**
----
-
-# Server routes: Elemental API (Query Server)
-
-Server routes can call the Elemental API through the Portal Gateway proxy,
-just like client-side code does. The gateway URL, tenant org ID, and API key
-are available via `useRuntimeConfig()`.
-
-**NEVER use `readFileSync('broadchurch.yaml')` in server routes.** The YAML
-file is read at build time by `nuxt.config.ts` and its values flow into
-`runtimeConfig`. Nitro serverless functions (Vercel) don't bundle arbitrary
-project files — `readFileSync` will crash with ENOENT in production even
-though it works locally.
-
-```typescript
-export default defineEventHandler(async (event) => {
-  const { public: config } = useRuntimeConfig();
-
-  const gatewayUrl = config.gatewayUrl;   // Portal Gateway base URL
-  const orgId = config.tenantOrgId;       // Tenant org ID (path segment)
-  const apiKey = config.qsApiKey;         // API key for X-Api-Key header
-
-  if (!gatewayUrl || !orgId) {
-    throw createError({ statusCode: 503, statusMessage: 'Gateway not configured' });
-  }
-
-  const res = await $fetch(`${gatewayUrl}/api/qs/${orgId}/entities/search`, {
-    method: 'POST',
-    headers: {
-      'Content-Type': 'application/json',
-      ...(apiKey && { 'X-Api-Key': apiKey }),
-    },
-    body: { queries: [{ queryId: 1, query: 'Microsoft' }], maxResults: 5 },
-  });
-
-  return res;
-});
-```
-
-Available runtime config keys (all under `runtimeConfig.public`):
-
-| Key | Source | Purpose |
-|---|---|---|
-| `gatewayUrl` | `broadchurch.yaml` → `gateway.url` | Portal Gateway base URL |
-| `tenantOrgId` | `broadchurch.yaml` → `tenant.org_id` | Tenant ID for API path |
-| `qsApiKey` | `broadchurch.yaml` → `gateway.qs_api_key` | API key sent as `X-Api-Key` |
-| `queryServerAddress` | `broadchurch.yaml` → `query_server.url` | Direct QS URL (prefer gateway) |
-
-Build the request URL as `{gatewayUrl}/api/qs/{tenantOrgId}/{endpoint}`.
-See the `data` rule for endpoint reference and response shapes.