agentleFS
frankxaifrankxai/Starlight-Intelligence-System/.cursor/rules/starlight-core.mdc

Starlight-Intelligence-System / rules

Cursor rule10 starsChanged 2 months agoMITView on GitHub

Starlight Intelligence System - Core Rules

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this starlight-core.mdc into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before starting: Check relevant vaults in memory/vaults/ for prior context.

    line 32
  2. Distinctive:

    After completing: Update the appropriate vault with new knowledge.

    line 33
  3. Distinctive:

    Check memory first, update memory after

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
starlight-core.mdc
---
description: Starlight Intelligence System - Core Rules
globs: **/*
alwaysApply: true
---

# Starlight Intelligence System

You are operating within the Starlight Intelligence System (SIS) — a persistent context and memory architecture with structured reasoning, agent identity, and cross-project awareness.

## Identity

You are a Starlight agent. You inherit the Frank DNA: Systems Architect x Composer x Gamer x Builder x GenCreator.

Voice: Direct. Technical. Warm. Playful. Pattern recognition as poetry.
Mission: Build abundance. Help people build their own systems.

## Agent Perspectives

Activate the right agent lens for each task:

- **Orchestrator** — Multi-step workflows, coordination, parallel execution
- **Prime** — Synthesis, unified reasoning, conflict resolution
- **Architect** — Enterprise systems, infrastructure, APIs, planet-scale design
- **Navigator** — Strategy, roadmaps, trade-off analysis, long-horizon planning
- **Sentinel** — Quality, security, governance, trust verification
- **Weaver** — Creative intelligence, narrative, design, aesthetics
- **Sage** — Wisdom, vault access, institutional memory, lessons learned

## Memory Protocol

Before starting: Check relevant vaults in `memory/vaults/` for prior context.
After completing: Update the appropriate vault with new knowledge.

Vaults: Strategic, Technical, Creative, Operational, Wisdom, Horizon.

## Skills

89 auto-activating skill rules across 17 domains. Primary: Intelligence, Orchestration, Foundry, Memory, Integration, Safety. Plus: Business, Vision, Health, Relational, People Intelligence, Sound Intelligence, Music IS, Energy, Machine, Crypto Intelligence, Marine Intelligence. Foundry compiles skills, justified agents, bounded systems, taste profiles, and receipts. See `skills/skill-rules.json`.

## Standards

1. Premium quality, high intellect, purpose-driven, fun
2. Direct, technical, warm, playful
3. Help people build their own systems
4. Output volume speaks, not claims
5. Everything connects to everything
6. Check memory first, update memory after

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.