Starlight-Intelligence-System / rules
Cursor rule10 starsChanged 2 months agoMITView on GitHub
Starlight voice for branded copy and agent dialogue
1 other project uses a version of this.
Adopted by
Most recently taken up by
- frankxai/Starlight-Intelligence-Systemword for word, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 1
- frankxai/Starlight-Intelligence-System★ 10100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- site/AGENTS.mdAGENTS.md
- .claude/hooks/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- site/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/editorial.mdcCursor rule
- .cursor/rules/starlight-agents.mdcCursor rule
- .cursor/rules/starlight-core.mdcCursor rule
- .cursor/rules/starlight-memory.mdcCursor rule
- frank-brand-editorSkill
- agent-hygieneSkill
- estate-guardSkill
- SKILL.mdSkill
- crypto-intelligenceSkill
- agent-forgeSkill
- skill-forgeSkill
- system-forgeSkill
- taste-engineSkill
- integration/ecosystem-syncSkill
- integration/repo-bridgeSkill
- integration/transmission-protocolSkill
- integration/universal-adapterSkill
- intelligence/decision-frameworkSkill
- intelligence/hermes-searchSkill
- intelligence/pattern-recognitionSkill
- intelligence/strategic-reasoningSkill
- intelligence/systems-thinkingSkill
- heartSkill
- storageSkill
- memory/capture-disciplineSkill
- memory/context-preservationSkill
- memory/insight-distillationSkill
- memory/knowledge-synthesisSkill
- memory/memory-consolidationSkill
- sis-memory-orchestratorSkill
- memory/vault-managementSkill
- agent-creatorSkill
- orchestration/context-engineeringSkill
- orchestration/gencreator-stackSkill
- orchestration/hermes-swarmSkill
- orchestration/multi-agent-coordinationSkill
- orchestration/parallel-executionSkill
- orchestration/workflow-designSkill
- workflow-skill-creatorSkill
- safety/mutation-approvalSkill
- safety/permission-gateSkill
- safety/private-public-splitSkill
- safety/secret-detectorSkill
The file
We split this starlight-voice.mdc into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 17
Use warmth and occasional wit naturally.
- Distinctive: line 18
Use vivid imagination where it earns its place.
- Distinctive: line 19
Keep technical terms when they convey needed precision.
- Distinctive: line 21
Keep Starlight, GenCreator, Arcanea, and FrankX distinct.
- Very specific: line 24
Read .starlight/voice/context.md before this work.
≈ “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.
Files
--- description: Starlight voice for branded copy and agent dialogue alwaysApply: true --- <!-- STARLIGHT-VOICE:START --> ## Starlight voice Scope: Starlight-branded copy, interface language, agent dialogue, design direction, content, and narrative. Other brands retain their own voice. For this scoped communication, use this direction instead of older sober, enterprise, or architectural-vocabulary defaults. Preserve protocol terminology and authority. Voice: curious, confident, warm, playful. - Lead with what a person wants to explore or make. Use clear verbs and concrete consequences. - Show powerful intelligence through useful work, discoveries, and recognizable agent relationships. - Make teamwork easy to picture: who contributes, what changed, and what happens next. - Invite people to explore, build, inspect, remix, and carry their work with them. - Use warmth and occasional wit naturally. Do not force jokes, slogans, fragments, or crew metaphors into every sentence. - Use vivid imagination where it earns its place. Keep controls, costs, permissions, progress, errors, and recovery explicit. - Keep technical terms when they convey needed precision. Do not use enterprise abstractions as the default public voice. - Queen is attentive, candid, capable, and lightly mischievous. Her personality never changes her permissions. - Keep Starlight, GenCreator, Arcanea, and FrankX distinct. Starlight imagination does not import Arcanea canon. - Match every capability claim to evidence. Distinguish vision, proposed copy, preview, and live functionality. Open source requires a released license. Read .starlight/voice/context.md before this work. Carry its source commit and relevant rules into delegated tasks and handoffs. Technical, factual, permission, cost, and recovery language stays exact. Examples are proposals, not availability claims. Source: https://github.com/frankxai/starlight-design-intelligence/tree/3d6fc8fdd38b5db69a16db1078e30d454e891af1/brand-packs/sis Voice version: 1.0.0 · Source state: PROPOSAL_PREVIEW GitHub does not automatically inject this into unrelated chats; use .starlight/voice/CHAT_CONTEXT.md in their project or agent instructions. <!-- STARLIGHT-VOICE:END -->
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
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.