ZviBaratz

Run automated EGO (extensions.gnome.org) compliance checks on a GNOME Shell extension. Validates metadata.json, GSettings schema, import segregation, console.log usage, deprecated modules, web APIs, binary files, CSS scoping, ESLint with gnome config, and package contents. Use when checking extension code quality, preparing for EGO submission, or when linting, validation, or GNOME extension compliance is mentioned.

Perform a manual code review of a GNOME Shell extension simulating what an EGO reviewer checks. Analyzes lifecycle correctness, signal disconnection, resource cleanup, async safety, security patterns, and code quality. Use before EGO submission, when reviewing GNOME extension code, or for pre-submission review.

Simulate an EGO review submission — produces a readiness report based on published review criteria. Triages the extension in reviewer order, applies a 23-reason rejection taxonomy with weighted scoring, and generates a structured report with a pass/fail verdict. Use before EGO submission to assess review readiness.

Run automated field tests across all registered GNOME extensions, diff against baselines, classify findings, and produce regression reports.

Complete pre-submission validation for EGO (extensions.gnome.org). Runs automated lint, performs manual code review, validates packaging, and produces a submission readiness report. Use as the final check before uploading to extensions.gnome.org.

Create a new GNOME Shell extension project with correct structure, lifecycle boilerplate, eslint-config-gnome, and EGO-compliant metadata. Generates extension.js, prefs.js, metadata.json, schema, stylesheet, and tooling. Use when creating a new extension, scaffolding a project, or starting fresh.

Use when building any terminal / ASCII / ANSI animation — a splash screen, a loader or spinner, a generative background, a game-of-life-style sim, a typewriter or reveal, plasma, a starfield, digital rain, a "mesmerizing" or "jaw-dropping" terminal effect, or any moving terminal graphic — and when deciding whether such an animation belongs in fresco or stands on its own.

Use when adding, authoring, or contributing a new fresco splash *variant* — a new generative field for the roster (rain/tunnel/ripple/galaxy-style) — inside the fresco repo (github.com/ZviBaratz/fresco), or when retuning, re-art-directing or fixing the look of a shipped one. Triggers: "add a variant", "new fresco field/animation", writing a splashPointFn, the propose-a-new-variant issue, building an aurora/plasma/flow/nebula-style field, or "rain/tunnel/ripple/galaxy looks flat / dead / washed out / too uniform — make it read better".