WebGL Standards Skill: Dormant Conventions for Rebuilds

Where this fits

When a WebGL scroll-film was retired and replaced with a static site, the team kept the hard-won conventions, version pins, and architectural patterns in a dormant skill for a future rebuild. If you're about to spin up a new GL surface on an existing codebase, this skill jumps you straight to verified decisions instead of rediscovering them.

Why agents benefit

• Agents get the exact version pins for WebGL libraries, so they don't waste time guessing compatible releases.
• The skill documents the playhead/scroll-rig, VAT, Gerstner wave, and post-processing chain patterns that were validated in production.
• Budget rules and gate + semantic-layer machinery are captured, letting agents enforce performance and review standards without hunting through git history.
• The dormant flag (ADR-0017) tells agents not to apply it to the current static site, preventing accidental misapplication.
• Because it's preserved verbatim, agents can diff against the retired implementation to see what changed and why.

Practical scenarios

Rebuilding a scroll-driven hero after a design pivot

Your team decides to bring back the cinematic scroll-film effect. Instead of reconstructing the rig from scratch, the agent loads this skill, reads the playhead/scroll-rig pattern, and applies the documented budget constraints (e.g., draw calls, texture memory) directly to the new implementation.

Auditing a WebGL codebase against historical standards

A reviewer agent uses the skill as a checklist. It verifies that the new code follows the version pins, post-chain order, and gate review rules, catching drift before it reaches production.

Planning a phased WebGL migration in a static site

When the static site needs to introduce a single GL canvas (for a product viewer), the agent consults the skill's "semantic-layer machinery" to see how the previous team bridged GL state with app logic, avoiding known pitfalls.

Add it to your agent workflow

Install the skill with:

npx skills add saeedkolivand/ai-job-hunter-app --skill webgl-standards

Then reference it in your agent's instructions: "When starting any WebGL work on apps/landing, first load the webgl-standards skill to retrieve the preserved conventions. Note that it is dormant; the current static site routes to project-steward."

Compare before adopting

Before you make this a permanent part of your workflow, weigh it against other WebGL skills or your own internal docs. Look at how fresh the version pins are, whether the patterns match the libraries you'll actually use, and whether the dormant status means the content is stale. Also check if the repository is actively maintained (48 stars, single author) and whether you need that level of rigor.

Why it is worth tracking

This skill is a rare example of a well-documented architectural decision that survives a pivot. The ADR-0017 note, the preserved test patterns, and the explicit "do not load for current work" flag show a disciplined team that values institutional memory. Even though it's dormant, it's a quality reference for any future WebGL rebuild—especially if you're considering a similar rollback. Keep it on your radar and re-evaluate if the repository shows new commits or the author lifts the dormant flag. For more context, see the OpenAgentSkill listing.