@yottagraph-app/aether-instructions 1.1.7 → 1.1.8

package/commands/build_my_app.md

@@ -73,10 +73,10 @@ Then read these files to understand what's available:
 1. `DESIGN.md` -- project vision and current status
 2. `broadchurch.yaml` -- project config (name, gateway URL, etc.)
 3. **The `api` cursor rule** -- this is critical. It describes the Query Server, the platform's primary data source. Build against platform APIs, not external sources.
-4. The **elemental-api skill docs** in `skills/elemental-api/` -- start with `SKILL.md` for API overview, then `entities.md`, `schema.md`, etc.
+4. **`.cursor/skills/`** — Each subdirectory is one skill. List them, open each skill’s entry (usually `SKILL.md`) and follow its structure to learn what is documented (APIs, schemas, helpers, etc.).
 5. `.cursor/rules/` -- scan rule names to know what other patterns are available
 
-**Important: Use the platform's data.** This app runs on the Lovelace platform, which provides a Query Server with entities, news, filings, sentiment, relationships, events, and more. Read the `api` rule and the skill docs to understand what data is available. Use `getSchema()` to discover entity types and properties at runtime.
+**Important: Use the platform's data.** This app runs on the Lovelace platform, which provides a Query Server with entities, news, filings, sentiment, relationships, events, and more. Read the `api` rule and the skills under `.cursor/skills/` to understand what data is available. Use `getSchema()` to discover entity types and properties at runtime.
 
 Key capabilities:
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@yottagraph-app/aether-instructions",
-    "version": "1.1.7",
+    "version": "1.1.8",
     "description": "Cursor rules, commands, and skills for Aether development",
     "files": [
         "rules",

package/rules/aether.mdc

@@ -8,7 +8,7 @@ alwaysApply: true
 
 **Structure:** `pages/` (file-based routing), `components/`, `composables/`, `server/api/`, `agents/` (Python ADK), `mcp-servers/` (Python FastMCP).
 
-**Data:** The Query Server (Elemental API) is the primary data source -- entities, news, filings, sentiment, relationships, events. Use `useElementalClient()` from `@yottagraph-app/elemental-api/client`. Do NOT call external APIs for data the platform provides. Discovery-first: use `getSchema()` to discover entity types and properties at runtime. Skill docs in `skills/elemental-api/` (run `npm install` if empty). Lovelace MCP servers may also be configured (see `api` rule) but are optional — check your tool list before assuming they're available.
+**Data:** The Query Server (Elemental API) is the primary data source -- entities, news, filings, sentiment, relationships, events. Use `useElementalClient()` from `@yottagraph-app/elemental-api/client`. Do NOT call external APIs for data the platform provides. Discovery-first: use `getSchema()` to discover entity types and properties at runtime. Skill docs: `skills/elemental-api/` (API endpoints) and `skills/data-model/` (Lovelace entity types, properties, relationships, YAML schemas per fetch source; `SKILL.md` first). Run `npm install` if those directories are empty. Lovelace MCP servers may also be configured (see `api` rule) but are optional — check your tool list before assuming they're available.
 
 **Storage:** KV (Upstash Redis) for preferences and lightweight state via `Pref<T>` from `usePrefsStore()`. Supabase for relational data if connected (check `.env`).
 

package/rules/api.mdc

@@ -16,21 +16,16 @@ regularly — use the discovery-first pattern to find what's available.
 
 ## Skill Documentation
 
-For full endpoint documentation, read the **elemental-api skill** in
-`skills/elemental-api/`. Start with `SKILL.md`, then `overview.md`.
-These files are copied from `@yottagraph-app/elemental-api-skill` during
-`npm install` (postinstall step) — if the directory is empty, run
-`npm install` first. The skill docs contain detailed response shapes and
-edge cases that go beyond this rule's quick reference — **run `npm install`
-early** to make them available during initial exploration.
-
-Key files:
-- `entities.md` — entity search, details, and properties
-- `find.md` — expression language for searching by type, property, and relationships
-- `schema.md` — entity types (flavors), properties (PIDs), and schema endpoints
-- `relationships.md` — entity connections
-- `events.md` — events involving entities
-- `articles.md` — news mentions and article content
+For endpoint reference, response shapes, and edge cases, **read the
+elemental-api skill** in `skills/elemental-api/` (start with `SKILL.md` and
+follow the skill’s own structure). Files are copied from
+`@yottagraph-app/elemental-api-skill` during `npm install` (see
+`skill-packages.json`); if the directory is empty, run `npm install` first —
+**run it early** during initial exploration so the skill is available.
+
+## Data model skill
+
+For Lovelace **entity types, properties, relationships, and per-source schemas** (EDGAR, FRED, FDIC, etc.), read the **data-model skill** in `skills/data-model/`. Start with `SKILL.md`, then `overview.md` and the source-specific folders. These files are copied from `@yottagraph-app/data-model-skill` during `npm install` (same postinstall; both skills are listed in `skill-packages.json`).
 
 ## Client Usage