extension-manifest-change
Skill2 starsChanged 27 days agoMITView on GitHub
Changes what an extension manifest may contain: validator in electron/extensions/manifest.cjs, then the mirrored src/extensions/types.ts, then the probe fixture and contract-coverage tests, in that order. Use for any request to add, rename, narrow or remove a manifest field, or make the validator accept or reject something.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- author-and-verify-extensionSkill
- autoreviewSkill
- cut-releaseSkill
- deslopSkill
- figma-to-codeSkill
- ship-prSkill
- sushiai-taskSkill
- sushiai-testingSkill
- sushiai-uiSkill
- ui-evidenceSkill
The file
Files
Extension manifest contract change
Four steps, always in this order. Skipping the last two is how the validator and the type system drift silently mid-session.
- Edit the validator in
electron/extensions/manifest.cjs. The closed sets a manifest may draw from (hosts, placements, icons, field types, ...) are collected once in theCONTRACTobject at the bottom of the file — add a new closed set there too, not just inline in the validator function. Known shape constraints worth checking against:MAX_VIEWS = 1(the renderer only ever drawsviews[0]), contributionids must be unique per-manifest per-kind (surfaces, navigation, actions, commands), labels onnavigation/actionsmust be unique too,commands[].surfaceIdis required (never make it optional again). - Sync
src/extensions/types.tsto match. The validator and the type file are two independent copies of the same contract; nothing fails automatically if only one changes. - Update the tests:
tests/extension-manifest.test.cjs(validator behavior — accepted and rejected shapes) andtests/extension-contract-coverage.test.cjs(which asserts, among other things, that every value inCONTRACTis exercised bytests/fixtures/extensions/probe/manifest.json, and thattypes.tslists the same values as the validator for the sets it mirrors). Widening the contract without touching the probe fixture fails this test on purpose — widen the fixture too. - Run
npm run check:conventions, then the fullnpm run cibefore calling the change done.
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
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.

