transparent-bg
Skill18 starsChanged 7 months agoMITView on GitHub
Produce a truly RGBA-transparent asset from a brief. Handles the #1 pain (Gemini/Imagen rendering checkerboard pixels instead of real alpha). Routes to native-RGBA providers; falls back to BiRefNet / BRIA RMBG / LayerDiffuse / difference matting.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/prompt-enhancer.mdcCursor rule
- .cursor/rules/prompt-to-asset.mdcCursor rule
- app-iconSkill
- asset-enhancerSkill
- asset-validation-debugSkill
- brand-consistencySkill
- faviconSkill
- illustrationSkill
- logoSkill
- og-imageSkill
- svg-authoringSkill
- t2i-prompt-dialectSkill
- transparent-bgSkill
- ui-mockup-promptSkill
- vectorizeSkill
- app-iconSkill
- asset-enhancerSkill
- asset-validation-debugSkill
- brand-consistencySkill
- faviconSkill
- illustrationSkill
- logoSkill
- og-imageSkill
- svg-authoringSkill
- t2i-prompt-dialectSkill
- ui-mockup-promptSkill
- vectorizeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 64
Do not ask for transparency in the prompt: Ask for pure white:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Transparent background
The problem (see research 13 + 04)
Almost every modern T2I VAE is RGB-only. Asking Imagen 3/4 or Gemini 2.5/3 Flash Image for a "transparent logo" triggers one of two failures:
- Flat background — DALL·E 3, Stable Diffusion families render a white/gray background that must be matted.
- Checkerboard as RGB pixels — Gemini/Imagen literally render the gray-and-white 8×8 tile pattern (because Photoshop screenshots in their training data show transparency that way). This is the "weird boxes" users report. It cannot be fixed by prompting.
Fix hierarchy (apply first that fits)
1. Route to a native-RGBA provider
| Provider | Mechanism |
gpt-image-1 / gpt-image-1.5 | API param background: "transparent" + output_format: "png" or "webp" |
| Ideogram 3 Turbo | Dedicated /ideogram-v3/generate-transparent endpoint; set rendering_speed: "TURBO" for Turbo tier |
| Recraft V3 | native SVG output (alpha is trivial); rasterize if raster needed |
| LayerDiffuse on SDXL / Flux | In-diffusion-loop transparency adapter; better edges than post-matte |
2. Post-process matte (for everything else)
| Matting model | License | Strength |
| BiRefNet | MIT | Default choice 2026; best soft-edge handling |
| BRIA RMBG-2.0 | CC-BY-NC-4.0 (hosted API for commercial) | Best overall quality |
| U²-Net | Apache-2.0 | Legacy fallback |
| rembg | wrapper around U²-Net / BiRefNet | Easy CLI integration |
| SAM 2 | Apache-2.0 | For complex/multi-object scenes; 2-stage (segment → matte) |
3. Difference matting (for semi-transparency: glass, hair, smoke)
- Generate the same subject on pure-white background.
- Generate again with same seed on pure-black background.
alpha = (white_version - black_version + 255) / 2in luminance.- Works for true semi-transparent objects where
rembg/BiRefNet produce hard-cutout artifacts.
4. Vectorize-and-drop (for flat marks)
- Generate raster at 1024² on white background.
- BiRefNet matte → K-means quantize to N colors →
vtracerorpotrace. - SVG has alpha trivially. Rasterize at target sizes with
@resvg/resvg-jsfor RGBA PNGs.
Validation (never ship without)
Tier-0 alpha validator (see packages/mcp-server/src/pipeline/validate.ts):
1. Check PNG/WebP header has alpha channel type (RGBA, not RGB).
2. Reject if no pixels have alpha < 255 (it's opaque).
3. Reject if >5% of pixels have alpha ∈ [0.05, 0.95] AND FFT signature shows gray-tile band frequency (Gemini fake checkerboard).
4. Alpha coverage: subject pixels (alpha > 0.5) should occupy 30–85% of frame (sanity check).
5. Premultiplied-alpha check: no RGB values where alpha==0 (cleanup artifacts).Prompt scaffold for fallback matting flow
Do not ask for transparency in the prompt. Ask for pure white:
[SUBJECT, concrete].
Centered, isolated, no surrounding context or props.
Solid pure white #FFFFFF background.
Clean silhouette with distinct outline.
No drop shadow, no ground plane, no reflection.
1:1 square, 1024x1024.Then post-process with BiRefNet / BRIA.
Never do this
"transparent background"as a prompt to Imagen or Gemini (checkerboard result).- Trust
output_format: "png"alone to produce alpha (PNG supports alpha, but the model has to emit it). - Algorithmic
#FFFFFF → alpha=0thresholding (loses anti-aliasing, creates jagged edges). - Post-resize RGBA with non-premultiplied alpha (dark fringes).
Output
transparent/
├── mark.png # RGBA, validated
├── mark@2x.png # optional high-DPI
├── mark.svg # if vector path chosen
└── meta.json # alpha_coverage, matting_method, validation_hashDoes 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
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.

