@yottagraph-app/aether-instructions 1.1.13 → 1.1.15

package/package.json

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

package/rules/api.mdc

@@ -17,15 +17,14 @@ regularly — use the discovery-first pattern to find what's available.
 ## Skill Documentation
 
 For endpoint reference, response shapes, and edge cases, **read the
-elemental-api skill** in `skills/elemental-api/` (start with `SKILL.md` and
+elemental-api skill** in `.cursor/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.
+`@yottagraph-app/aether-instructions` (installed during project init). If
+the directory is missing, run `/update_instructions` to install it.
 
 ## 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`).
+For Lovelace **entity types, properties, relationships, and per-source schemas** (EDGAR, FRED, FDIC, etc.), read the **data-model skill** in `.cursor/skills/data-model/`. Start with `SKILL.md`, then `overview.md` and the source-specific folders. Both skills are distributed via `@yottagraph-app/aether-instructions` and installed during project init.
 
 ## Client Usage
 

package/rules/server.mdc

@@ -69,10 +69,10 @@ Returns `null` if KV is not configured (env vars missing). Always check.
 
 ## Neon Postgres
 
-If a Neon database is connected to the project, Vercel auto-injects
-`DATABASE_URL` (pooled) and `DATABASE_URL_UNPOOLED` (direct). For local
-development, copy the connection string from Vercel project settings into
-`.env`.
+If a Neon database is connected to the project, `DATABASE_URL` (pooled) and
+`DATABASE_URL_UNPOOLED` (direct) are available. Vercel auto-injects them for
+deployed builds; for local dev they are populated in `.env` during project
+init. Check `.env` for `DATABASE_URL` — if present, Postgres is ready to use.
 
 ### Utility pattern