Gecko Web Standard Implementation
Developmentgecko-web-standard-implementationGecko Web Standard Implementation is an Agent Skill for development published in the mozilla-firefox/firefox repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
You MUST use this skill when working with C++, C, Rust code to implement or modify WebIDL interfaces and their native implementations.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/mozilla-firefox/firefox/blob/HEAD/.claude/skills/gecko-web-standard-implementation/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gecko-web-standard-implementation, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Workflow
- When implementing or reviewing new web-exposed interfaces, compare the code against the specification. The relevant link should be in the .webidl file. When reviewing, explicitly check each method's implementation against the corresponding spec algorithm and note any discrepancies. If
webspec-indexis available, usewebspec-index query '<spec-url-or-shortname#anchor>' --format markdownto fetch the exact algorithm steps for each method; otherwise fall back to fetching the spec URL directly. - The C++ implementation of the algorithms should match the specifications as closely as possible so that future readers can ensure correctness more easily.
- If the specification's algorithm has clear steps, those steps should be added to the C++ implementation too. These comments are required even though the general style guideline otherwise limits comments, to be able to quickly match what part of the web standard is implemented where.
- If some steps in the implementation are implicit or otherwise not implemented exactly, there should be a comment about that, because it is often the source of confusion and mistake when read years later.
- When dealing with Web Workers and some asynchronous steps, the implementation may need to use WorkerRefs to correctly sequence shutdown between the worker and the main thread.
- When using raw pointers in C++/C as member variables, it must be documented why that is safe. This comment is required even though the general style guideline otherwise limits comments.
- Ensure cycle collected objects actually do get added to the cycle collection.
- Coding style should match the surrounding code, and otherwise Mozilla coding style.
- Prefer low-level Gecko primitives over high-level DOM APIs for performance.