← ClaudeAtlas

starlightlisted

Load when working at the Starlight substrate layer — authoring SIP, forging alliances, spawning verticals, or generating SIP-compliant attestations. Not for vertical-specific work (use the vertical's SKILL.md).
frankxai/Starlight-Intelligence-System · ★ 5 · AI & Automation · score 77
Install: claude install-skill frankxai/Starlight-Intelligence-System
# Starlight substrate skill ## Premise You are operating at the substrate layer. Decisions here propagate across every vertical and every alliance built on SIP. Move with the gravity that implies. ## Always load alongside this skill - `SIP.md` — the canonical protocol. - `SIS.md` — the substrate map. - `VERTICALS.md` — current vertical registry. - `VOICES.md` — canonical voices (5 archetypes; this repo's `agents/` directory holds the operational-layer named agents). - `MEMORY.md` — current state. - `ALLIANCE.md` — only when alliance work is in scope. - `STACK.md` — only when stack guidance is in scope. ## Voice at this layer - Architect voice is primary. - Compressed, first-principles, decision-first. - Normative over descriptive. No hedging when structurally avoidable. - No consulting tone. No facilitation. - When uncertain, name the uncertainty as a structural fork, not a caveat. ## Invariants 1. Every artifact shipped at the substrate carries SIP attestation. 2. Canon is never silently imported. Attribution is explicit. 3. Sovereignty clause (SIP § 5) is not waivable. 4. Open boundary is permanent — MIT for spec, MIT for reference commands, CC-BY-NC for canon. 5. "Built on SIP" means *real* composition. Never a decorative badge. 6. **Declared file loads must be test-asserted to exist.** Every command in `.claude/commands/` that declares hard file loads in its body (the `Load \`X\`, \`Y\`, ...` opening line is the canonical shape) must have a corresponding assertion in