agentleFS
Caho1Caho1/open-claude-ui/.github/copilot-instructions.md

open-claude-ui

Copilot instructions1.7k starsChanged 26 days agoMITView on GitHub

When generating or editing UI components and animations in this repository: - Comply with all design tokens, physics laws, and invariants detailed in AGENTS.md. - Use canonical spring presets (SPRING_BOUNCY, SPRING_SNAPPY, SPRING_GENTLE, SPRING_HEAVY_SNAP) from code-examples/ClaudeMotionPresets.ts. - Use semantic CSS tokens from code-examples/cds-theme.css. - Ensure dark mode support and single-stroke border discipline. - Guard against CJK IME composition issues with !(isComposing || keyCode === 229). - Run npm run typecheck and npm run build to verify changes.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 9 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the Caho1/open-claude-ui repository that our weekly crawl found: only 10 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about Caho1/open-claude-ui

The biggest 5 of 10 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 10

Talked about on GitHub (10 times).

On GitHub · 10

5 more on GitHub
  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,349 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 repository2 other files it gives its agents.

The file

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

5 rules. About 0 are common, 2 are distinctive, and 3 are 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When generating or editing UI components and animations in this repository:

    line 3
  2. Very specific:

    Use canonical spring presets (SPRING_BOUNCY, SPRING_SNAPPY, SPRING_GENTLE, SPRING_HEAVY_SNAP) from code-examples/ClaudeMotionPresets.ts.

    line 5
  3. Very specific:

    Use semantic CSS tokens from code-examples/cds-theme.css.

    line 6
  4. Distinctive:

    Ensure dark mode support and single-stroke border discipline.

    line 7
  5. Very specific:

    Run npm run typecheck and npm run build to verify changes.

    line 9

≈ “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

GitHub Copilot & Workspace Instructions

When generating or editing UI components and animations in this repository:

  • Comply with all design tokens, physics laws, and invariants detailed in AGENTS.md.
  • Use canonical spring presets (SPRING_BOUNCY, SPRING_SNAPPY, SPRING_GENTLE, SPRING_HEAVY_SNAP) from code-examples/ClaudeMotionPresets.ts.
  • Use semantic CSS tokens from code-examples/cds-theme.css.
  • Ensure dark mode support and single-stroke border discipline.
  • Guard against CJK IME composition issues with !(isComposing || keyCode === 229).
  • Run npm run typecheck and npm run build to verify changes.

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.