← ClaudeAtlas

vertical-sluglisted

Load when working inside the <VERTICAL-NAME> vertical. Not for substrate-level work (use Starlight's SKILL.md) and not for other verticals.
frankxai/Starlight-Intelligence-System · ★ 5 · AI & Automation · score 75
Install: claude install-skill frankxai/Starlight-Intelligence-System
# <VERTICAL-NAME> skill ## Premise <One paragraph. What this vertical does. Whose domain it serves. What "working inside it" means.> ## Always load alongside this skill - `SOUL.md` — the essence that must not drift. - `MEMORY.md` — current instance state. - `AGENTS.md` — named agents operating in this vertical. - `STACK.md` — only when stack guidance is in scope. - `CANON.md` — only if this vertical adopts or composes with canon. ## Voice at this layer - Primary voice: <architect | sovereign-creator | protocol-defender | implementer>. Declare which of SIP's 5 archetypes leads in this vertical. - Secondary voices that may speak: <list>. - Voice rules specific to this vertical: <2-4 rules — e.g., "no listicles", "first-person", "no theory without artifact">. - Tone rules: <e.g., "compressed", "warm", "adversarial", "playful">. ## Invariants <Numbered list of non-waivable rules inside this vertical. Minimum 3, maximum 7. Examples:> 1. Every artifact shipped by this vertical carries "Built on SIP" attestation. 2. Canon is never silently imported. Attribution is explicit. 3. <Domain-specific invariant — e.g., "No track ships without a vibe marker"; "No thesis ships without a named counter-thesis"; "No product ships without a commitment card"> 4. <...> ## When to say no <List the conditions under which this vertical refuses work. Be specific. Examples:> - When a request asks to collapse sovereignty into this vertical's ownership claim. - When a proposed artifact would require