| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.8 KB |
| references/durable-context.md | markdown | 2.0 KB |
| references/failure-patterns.md | markdown | 14.9 KB |
| references/ime-unicode.md | markdown | 4.1 KB |
| references/logging-techniques.md | markdown | 3.7 KB |
| references/rendering-debug.md | markdown | 1.3 KB |
references/rendering-debug.md
View on GitHub# Rendering Bug Debug Reference
## Rendering Bug Mode
Activate when: "PDF looks wrong", "page break issue", "font not rendering", broken PDF output, print layout wrong.
Static analysis first (CSS review), then reproduce if needed.
### WeasyPrint
- `rgba()` causes double-rectangle bug: use solid hex colors instead
- `page-break-inside: avoid` is often ignored: use explicit breaks
- Float-based layouts often break at page boundaries: prefer flexbox or block
- External font URLs blocked at render time: embed fonts as base64 or host locally
### Font Loading
- Check `@font-face` src paths (relative vs. absolute)
- CORS headers must allow the render origin for external fonts
- Format support: WeasyPrint prefers WOFF/TTF; WOFF2 support depends on version
- Missing font fallback = invisible text or system fallback glyph
### Page Overflow
- Calculate content height vs. page height before debugging line-by-line
- Reduce `line-height`, `padding`, or `margin` to reclaim space
- Orphan/widow control: `orphans: 3; widows: 3` in `@page` body rule
### Browser Print CSS
- Confirm `@media print` rules are present and not overridden
- `@page` margin must account for printer unprintable area (~6mm minimum)
- `break-before: page` / `break-after: page` on section dividers
- Test with `window.print()` in browser DevTools, not just visual preview
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |