agentleFS
thoughtfulllcthoughtfulllc/gridland/.claude/skills/audit-render/SKILL.md

audit-render

Skill363 starsChanged 7 months agoMITView on GitHub

Audit the browser rendering pipeline for scissor/clipping bypass bugs. Use when touching browser-buffer.ts, canvas-painter.ts, or adding new visual features.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Wait for it to complete.

    line 10
  2. Distinctive:

    If issues are found, suggest the fix pattern:

    line 17
  3. Very specific:

    Add clipRect? field to the data type

    line 18
  4. Distinctive:

    Add tests for: capture, skip, paint-clip, no-clip-when-absent

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audit the rendering pipeline to ensure every canvas-level drawing path respects the scissor (overflow:hidden) system.

  1. Spawn the render-pipeline-audit agent as a background agent.
  2. Wait for it to complete.
  3. Present findings:
    • Must Fix: Any buffer→painter channel missing scissor capture or painter clipping
    • Should Fix: Channels with bounds-checking but no scissor clipping (low risk)
    • OK: Channels that are safe (cell-grid bounded or fully scissor-aware)
  4. If issues are found, suggest the fix pattern:
    • Add clipRect? field to the data type
    • Capture scissorStack[top] at write time, skip if fully outside
    • Apply ctx.save() / ctx.rect(clipRect) / ctx.clip() / ctx.restore() in the painter
    • Add tests for: capture, skip, paint-clip, no-clip-when-absent

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.