Use after tests pass on a Nova feature — before linting or formatting — to annotate changed files with @nova-cleanup instructions for post-launch automated cleanup.
Do not add cleanup comments if the user says "skip cleanup comments".
Add @nova-cleanup comments to Firefox newtab code following Project Nova implementation strategy.
Project Nova uses a parallel development approach where classic newtab stays untouched and Nova changes live in isolated directories/conditionals. Cleanup comments serve as instructions for a future automated pass: when Nova ships, Claude will find all @nova-cleanup markers and execute the described cleanup autonomously. Write descriptions as direct, unambiguous instructions that Claude can act on without engineer input.
// @nova-cleanup(action): Instruction for Claude to execute during cleanupremove-directory - Delete entire classic directorymove-directory - Move Nova/ up one levelmerge-styles - Move styles from nova/ to component locationsremove-pref - Remove pref checkremove-conditional - Remove conditional logicnova.enabled or similarNova/ directorystyles/nova/ directory@nova-cleanup(remove-conditional) with description@nova-cleanup(remove-pref) with description@nova-cleanup(move-directory) at top of file@nova-cleanup(remove-directory) at top@nova-cleanup(merge-styles) at top// Entry point with component selection
// @nova-cleanup(remove-pref): Delete this line; replace Base with NovaBase everywhere in this file
const Base = prefs["browser.nova.enabled"] ? NovaBase : ClassicBase;// Nova/Base/Base.jsx
// @nova-cleanup(move-directory): Move this file to components/Base/Base.jsx and update all imports
export class Base extends React.Component {
// ...
}mozilla/firefox-aidev-plugins
0edd81f
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.