agentleFS
Sign inStart free
gesh75gesh75/claude-mastery-hub/.github/copilot-instructions.md

claude-mastery-hub

Copilot instructions0 starsChanged 3 months agoMITView on GitHub

Interactive single-page guide to mastering Claude - the app, Claude Code, the API, MCP, skills, subagents, and hooks. Ships as one self-contained index.html, published to GitHub Pages. Stack. Hand-authored HTML + vanilla JavaScript. No Python, no build step, no framework. Playwright for E2E, @axe-core/playwright for accessibility. Layout. index.html is the whole site. tests/e2e/*.spec.js, docs/ - Small, focused edits. index.html is large; change only the section you are working on. - Keep the page self-contained: no external CDN scripts, stylesheets, fonts,…

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Keep the page self-contained: no external CDN scripts, stylesheets, fonts, or images.

    line 22
  2. Very specific:

    Run npx playwright test before pushing - the suite includes axe-core checks, so a contrast or ARIA regression fails CI.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 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

claude-mastery-hub

Interactive single-page guide to mastering Claude - the app, Claude Code, the API, MCP, skills, subagents, and hooks. Ships as one self-contained index.html, published to GitHub Pages.

Stack. Hand-authored HTML + vanilla JavaScript. No Python, no build step, no framework. Playwright for E2E, @axe-core/playwright for accessibility.

Layout. index.html is the whole site. tests/e2e/*.spec.js, docs/

Build and test

npm ci
npx playwright install --with-deps chromium
npx playwright test

Conventions

  • Small, focused edits. index.html is large; change only the section you are working on.
  • Keep the page self-contained: no external CDN scripts, stylesheets, fonts, or images.
  • Vanilla JS only. Do not introduce a framework, bundler, or build step.
  • Handle errors explicitly; never leave a silent failure in interactive code.
  • Conventional Commits: feat:, fix:, docs:, test:, chore:, perf:, ci:. Imperative mood, lower case, no trailing period. No Co-authored-by trailers.

Single-file site - specific gotchas

  • Anchor SVG edits on a unique aria-label, never on a shared viewBox. Several diagrams reuse the same viewBox, so a viewBox-based selector silently edits the wrong graphic.
  • Never combine a gradient fill with a clip-path on text. It renders as solid black boxes when the page is exported to PDF. Use a solid fill.
  • Run npx playwright test before pushing - the suite includes axe-core checks, so a contrast or ARIA regression fails CI.
  • Content sections carry dates ("What's New"). Keep them accurate; do not invent release dates or model names - verify against primary sources first.

Pull requests

  • Title in Conventional Commits form.
  • Body covers: what changed, why, and how you verified it renders correctly.

Download now (ZIP)

  • 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,297 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 repositoryOne other file it gives its agents.

Does it work?

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

Reviews can't be read right now.

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