AI Agent & Automation Workflows

Manually-triggered regenerator for this repo's docs/CATALOG.md. Rebuilds the plugin table straight from the plugin manifests — name, description, and component counts (skills/commands/agents/hooks/MCP servers) — so a missing, stale, or mis-counted row is fixed deterministically. The write-capable counterpart to marketplace-sync-check, which only reports the same local-catalog drift. Touches only the local catalog table (the surrounding prose is preserved); never the published marketplace, never commits, never opens a PR.

Read-only check of whether the current branch's changes require a marketplace-publish — a plugin added or removed, or a plugin's name/description/homepage edited (a version-only bump does not count). Run it when opening a PR to decide whether to apply the marketplace-publish label, so a needed catalog publish isn't forgotten after merge. Prints the affected plugins; exits non-zero when a publish is needed.

Use when the user says "harvest learnings", "anything worth remembering?", "what should I save?", "before I go...", or any variation of asking whether there are takeaways from the session — including when they're wrapping up a long or complex session. Runs a systematic pre-exit sweep of the current conversation for learnings worth preserving in memory: surfaces corrections, project context, preferences, and references, deduplicates against existing memory, and presents findings for the user to approve. Never auto-saves.

Use whenever the user is working with raw WebGL or GLSL — writing, debugging, optimizing, or asking about WebGL2 (or WebGL1) without a higher-level framework. Trigger on WebGLRenderingContext, WebGL2RenderingContext, getContext('webgl'|'webgl2'), vertex/fragment shaders, glFragColor, glPosition, vec2/vec3/vec4, uniform, attribute, varying, in/out in shader code, gl.createBuffer, gl.vertexAttribPointer, VBOs/VAOs/UBOs, FBOs/framebuffers, texImage2D, drawArrays/drawElements, instancing, GLSL noise/SDF/smoothstep patterns, "black canvas" debugging, getShaderInfoLog, shader compile errors, or any mention of WebGL pipeline mechanics. Load this even when the user doesn't say "WebGL" explicitly — if the code or question is about shaders, GPU rasterization, or the browser graphics pipeline beneath a framework, this is the right skill. For app-level 3D (Three.js scene graph, loaders, post-processing), defer to threejs-mastery instead.