agentleFS
Sign inStart free
frankxaifrankxai/Starlight-Intelligence-System/.github/copilot-instructions.md

Starlight-Intelligence-System

Copilot instructions10 starsChanged 2 months agoMITView on GitHub

Brand: Starlight Intelligence Systems (sis) Pinned source: https://github.com/Starlight-Intelligence/starlight-design-intelligence/blob/851a11be31a0640df64baabcf2b1fc1afb9ce849/brand-packs/sis/COPY.md <!-- STARLIGHT-EDITORIAL:END --> 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…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this copilot-instructions.md into the rules it gives an agent

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read CREATOR.md before changing public or customer-facing copy.

    line 6
  2. Distinctive:

    Keep public labels in sentence case.

    line 9
  3. Distinctive:

    Run the changed-copy editorial audit before release.

    line 10
  4. Distinctive:

    Use warmth and occasional wit naturally.

    line 27
  5. Common:

    Use vivid imagination where it earns its place.

    line 28
  6. Distinctive:

    Keep technical terms when they convey needed precision.

    line 29
  7. Distinctive:

    Keep Starlight, GenCreator, Arcanea, and FrankX distinct.

    line 31
  8. Very specific:

    Read .starlight/voice/context.md before this work.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions 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
copilot-instructions.md
<!-- STARLIGHT-EDITORIAL:START -->

Editorial contract

Brand: Starlight Intelligence Systems (sis)

  • Read CREATOR.md before changing public or customer-facing copy.
  • Apply the registered brand voice and the shared editorial gate.
  • Reject generated prestige language, rhetorical contrast formulas, invented claims, and abstract labels that hide simple facts.
  • Keep public labels in sentence case.
  • Run the changed-copy editorial audit before release.

Pinned source: https://github.com/Starlight-Intelligence/starlight-design-intelligence/blob/851a11be31a0640df64baabcf2b1fc1afb9ce849/brand-packs/sis/COPY.md

<!-- STARLIGHT-EDITORIAL:END --><!-- 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 -->

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.

Check your setup, free