One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
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.
BrowserWorksAGENTS.mdBrowserWorks/waterfox/AGENTS.md
Do not remove existing comments unless they are directly related to what you are changing. If you see a good first bug that isn't directly related to your work, don't…
1 project uses a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/accessibility-frontend-review/SKILL.md
Performs an accessibility code review of a local diff or Phabricator revision in the style of the Firefox accessibility team. Use this skill whenever the user asks to review a Phabricator patch or revision for accessibility issues, mentions a D-number (like D284142) in the context of accessibility review, asks "does this patch have any a11y issues", or wants to check a diff against accessibility guidelines. Also use it when the user says things like "can you review this for a11y", "check this patch", or "give me an accessibility review of D[number]". Invoke proactively when the user pastes a phabricator.services.mozilla.com URL or shares a revision ID alongside any accessibility concern. Invoke when questions about the following topics are raised: aria properties, aria roles, high contrast mode, forced colors, prefers contrast, focus order, screen readers, assistive technology.
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/android-new-module/SKILL.md
Guide for creating new Android gradle modules in the android-components project.
3 projects use a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/android/SKILL.md
Workflow guide when working with Android builds or the mobile/ directory.
9 projects use a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/bug-filing/SKILL.md
File a Bugzilla bug for Firefox/Gecko work, or draft a bug summary and description. Use when the user asks to file a bug, wants a bug summary/description for a change, or needs to report a defect/enhancement/task. Determines the product and component with `mach file-info`, drafts the summary and description, and opens a prefilled enter_bug.cgi form in the browser for the user to submit.
Steady3 mentions in 2 weeks
3 projects use a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/documentation/SKILL.md
Use this skill when working with Firefox documentation,
101 projects use a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/file-good-first-bug/SKILL.md
Use this skill when the user wants to file good-first-bugs in Bugzilla for Firefox. A good-first-bug is a narrow, self-contained, low-risk task scoped so a first-time contributor can land it without deep context. Sources include lint warnings, small typos, dead-code removal, mechanical refactors, docs conversions, or any other small task the user points at. Produces prefilled `enter_bug.cgi` URLs the user clicks to submit. Trigger on phrases like "file a good first bug", "open good first bugs for X", "create a good-first-bug from this".
3 projects use a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/firefox-desktop-frontend/SKILL.md
You MUST use this skill when working with HTML, JS, CSS and other front-end code.
3 projects use a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/gecko-web-standard-implementation/SKILL.md
You MUST use this skill when working with C++, C, Rust code to implement or modify WebIDL interfaces and their native implementations.
3 projects use a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/jj-split/SKILL.md
Steps to reliably split a commit/change using the jj (jujutsu) VCS
1 project uses a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/js-perf-investigation/SKILL.md
Structured performance opportunity investigation for SpiderMonkey (the Firefox JavaScript engine). Use this skill when the user wants to investigate JS engine performance, profile SpiderMonkey, find optimization opportunities, write performance patches, or evaluate benchmark regressions. Trigger on mentions of: profiling JS, SpiderMonkey performance, JIT optimization, benchmark regression analysis, shell benchmarking, or any request to make JS workloads faster.
3 projects use a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/mozlint/SKILL.md
You MUST use this skill when working with Firefox's linting infrastructure (mozlint), adding new linters, modifying existing linters, running linters, or dealing with linting issues.
3 projects use a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/profiler-analysis/SKILL.md
Analyze Firefox performance profiles using the profiler-cli CLI tool. Trigger when given a profiler.firefox.com or share.firefox.dev link, a local profile path, or when the user wants to investigate an issue in a Firefox profile. Always use this skill instead of WebFetch for Firefox profiler URLs; WebFetch only retrieves the profiler UI's HTML shell and cannot access profile data, whereas profiler-cli downloads and parses the actual profile into a local daemon that supports structured queries over stacks, markers, threads, and samples.
3 projects use a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/reorganize-patches-for-review/SKILL.md
Analyze a range of local commits, and reorganize them to minimize latency and friction in the review and landing process. To achieve this, commits can be split, reordered, squashed / grouped, or even rewritten. In the final commit series / "patch stack", the codebase should build, lint, and test cleanly after every commit, and each individual commit should stand on its own.
Steady3 mentions in 2 weeks
1 project uses a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/specmap/SKILL.md
Map relationships between a web spec section, its Firefox implementation code, and Web Platform Tests. Use when starting work on a spec feature, checking implementation coverage, or finding which WPTs to enable.
3 projects use a version of this
BrowserWorksReads credentialsSkillBrowserWorks/waterfox/.agents/skills/stmo/SKILL.md
Manage Redash queries and dashboards on Mozilla's STMO (sql.telemetry.mozilla.org) using stmo-cli. Use when the user wants to explore telemetry data on STMO, write, deploy, or execute Redash queries, manage dashboards, or discover data sources. Also trigger on mentions of STMO, Redash, sql.telemetry.mozilla.org, or when the user wants to query Mozilla telemetry data (as opposed to probe/metric discovery, which is mozdata territory).
3 projects use a version of this
BrowserWorksSkillBrowserWorks/waterfox/.agents/skills/webspec-index/SKILL.md
Use webspec-index to query WHATWG, W3C, IETF and TC39 web specifications from the command line
Steady3 mentions in 2 weeks
3 projects use a version of this
BrowserWorksCLAUDE.mdBrowserWorks/waterfox/CLAUDE.md
No summary in the file. Open it to read it.
152 projects use a version of this
BrowserWorksAGENTS.mdBrowserWorks/waterfox/js/AGENTS.md
This directory is SpiderMonkey, the JavaScript engine inside the Firefox/Gecko monorepo in the parent directly. Project-wide instructions live in ../AGENTS.md (referenced from ../CLAUDE.md). Notes below cover what is specific to…
1 project uses a version of this
BrowserWorksAGENTS.mdBrowserWorks/waterfox-android/AGENTS.md
Do not remove existing comments unless they are directly related to what you are changing. If you see a good first bug that isn't directly related to your work, don't…
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.
