raster-texture-reconstruction
Skill0 starsChanged 4 months agoISCView on GitHub
Reconstruct source-specific raster texture such as grain, halftone, scanlines, RGB offset, chromatic aberration, edge erosion, distress, and banded glitch while keeping structural text and UI live. Use when a mockup-to-code manifest explicitly sets rasterTexture.required=true, or when a user explicitly asks to reproduce identity-bearing raster texture without shipping source pixels or rasterizing structural copy.
In this repository11 other files it gives its agents.
- mockup-to-codeSkill
- design-copy-structureSkill
- design-motion-sequencingSkill
- design-whitespaceSkill
- lp-interaction-qaSkill
- photo-art-directionSkill
- responsive-image-deliverySkill
- seamless-section-wavesSkill
- typographySkill
- visual-device-inventorySkill
- visual-qa-pixel-polishSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 12 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Read the parent manifest and normalize rasterTexture into a four-key raster-texture-contract/v1 snapshot: schemaVersion, required, reason, …
- Very specific: line 25
Create one target row per manifest id.
- Distinctive: line 34
Read the actual desktop/mobile QA viewports from the parent workflow.
- Distinctive: line 61
Keep CSS-owned surfaces and image-owned assets separate.
- Distinctive: line 75
Use the parent workflow's render/capture commands at the declared widths and heights.
- Distinctive: line 97
Never ship pixels copied, cropped, masked, blurred, recolored, or downscaled from the source mockup.
- Distinctive: line 99
Never rasterize structural text to obtain texture fidelity.
- Very specific: line 100
Prefer filters, masks, and pseudo-elements over duplicated text.
- Distinctive: line 103
Treat generated masks and procedural rasters as content-free: no readable words, logos, UI, faces, products, or source-identifying …
- Distinctive: line 105
Keep effect ownership local to the declared target.
- Distinctive: line 109
Keep desktop/mobile tuning explicit.
- Distinctive: line 111
Keep animation separate from static texture fidelity.
- Distinctive: line 114
Do not turn helper metrics into one synthetic pass score.
- Distinctive: line 118
Keep source/build crops and measurement evidence under the work root's report area.
- Very specific: line 124
Read schemas/raster-texture-report-v1.schema.json before creating or transforming a report.
- Very specific: line 126
Start blocked work from templates/raster-texture-report.blocked.json.
- Very specific: line 128
Use relative, traversal-free paths rooted at --root.
- Very specific: line 129
Use raster-texture-report/v1 for the specialist report and raster-texture-metrics/v1 for helper measurements.
- Distinctive: line 136
Run the focused tests and structural skill validation after changes:
≈ “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.
Files
Raster Texture Reconstruction
Rebuild raster-specific visual character as a Web-owned effect layer. Preserve semantic HTML, responsive behavior, and accessibility; use source crops only as measurement and comparison evidence.
This first version is explicit-only. Start only when the parent manifest sets
rasterTexture.required: true. If the user explicitly requests the skill,
record that decision first with reason: "user-request" and exact existing
target ids. Block when no parent manifest or resolvable target exists. Do not
auto-detect a requirement from weak background noise.
Workflow
- Read the parent manifest and normalize
rasterTextureinto a four-keyraster-texture-contract/v1snapshot:schemaVersion,required,reason, andtargetIds. Bind that snapshot in the report and copytargetIdsexactly. The report receipt can then be added to the parent manifest without creating a circular whole-manifest hash. - Create one target row per manifest id. Bind a real source crop and classify
every effect separately with its own
coordinateSpace,methods, andownership. Useglyph-local,element-local, orsection-field; one target may legitimately combine spaces. - Record only source-observed effect types. Give each effect a stable target-local id. Read references/reconstruction-methods.md before selecting CSS, SVG filter, content-free mask, or procedural-raster methods.
- Read the actual desktop/mobile QA viewports from the parent workflow. Define each state's width, height, intensity scale, and spatial scale. Keep motion static unless the parent manifest separately requires motion.
Set the report safety assertions exactly:
{ "sourcePixelsShipped": false, "contentFreeAsset": true, "structuralTextRemainsLive": true }Validate the plan before implementation:
SKILL_ROOT="${SKILL_ROOT:-${CODEX_HOME:-$HOME/.codex}/skills}" "$SKILL_ROOT/mockup-to-code/scripts/skill-pack-python" \ "$SKILL_ROOT/raster-texture-reconstruction/scripts/validate_raster_texture_report.py" \ reports/raster-texture-report.json --root . --phase pre-css --receiptA pre-CSS report uses
status: "ready"and targetimplementation.status: "planned". A fully passing completion report is also valid at this phase.- Implement the effect outside the source pixels. Structural headings, labels, CTA copy, navigation, body, and legal text remain selectable live DOM text. Keep CSS-owned surfaces and image-owned assets separate.
Measure matched source/build crops with the supplied helper. Treat the result as diagnostic evidence, not a universal quality score:
SKILL_ROOT="${SKILL_ROOT:-${CODEX_HOME:-$HOME/.codex}/skills}" "$SKILL_ROOT/mockup-to-code/scripts/skill-pack-python" \ "$SKILL_ROOT/raster-texture-reconstruction/scripts/texture_metrics.py" \ --target-id hero.heading \ --source reports/crops/hero-heading-source.png \ --build reports/crops/hero-heading-build.png \ --out reports/texture-metrics-hero-heading.json- Use the parent workflow's render/capture commands at the declared widths and
heights. Capture readable desktop and mobile crop pairs and record the
dimensions. Bind current hashes for implementation files, any content-free
assets, the metrics report, and both crop pairs. Set each target verdict and
the report status to
pass. Validate completion and copy the emitted receipt into
specialistReports.rasterTexture:SKILL_ROOT="${SKILL_ROOT:-${CODEX_HOME:-$HOME/.codex}/skills}" "$SKILL_ROOT/mockup-to-code/scripts/skill-pack-python" \ "$SKILL_ROOT/raster-texture-reconstruction/scripts/validate_raster_texture_report.py" \ reports/raster-texture-report.json --root . --phase completion --receipt- Return the crop pairs to the parent workflow's existing independent visual
reviewer. Do not create a second reviewer system inside this skill. A
specialist
passmeans the evidence contract is complete; it does not override a parent reviewer rejection.
Hard Rules
- Never ship pixels copied, cropped, masked, blurred, recolored, or downscaled from the source mockup.
- Never rasterize structural text to obtain texture fidelity.
- Prefer filters, masks, and pseudo-elements over duplicated text. If a
decorative DOM copy is unavoidable, it must be
aria-hidden="true", must not own the semantic target id, and must not replace the accessible live node. - Treat generated masks and procedural rasters as content-free: no readable words, logos, UI, faces, products, or source-identifying composition.
- Keep effect ownership local to the declared target. A glyph-local effect may not become an unbounded section overlay.
- Preserve legibility and contrast. Texture may erode edges; it may not destroy the parent workflow's content, accessibility, or CTA requirements.
- Keep desktop/mobile tuning explicit. Do not reuse desktop grain size, scanline pitch, glitch-band width, or RGB displacement blindly on mobile.
- Keep animation separate from static texture fidelity. If motion is requested, follow the parent motion contract and prove a settled static state plus reduced-motion behavior.
- Do not turn helper metrics into one synthetic pass score. Use crop pairs and the parent independent review for final visual judgment.
- Emit
blockedorneeds_workwhen evidence is unavailable. Do not fill receipts with placeholders or retrospective hashes. - Keep source/build crops and measurement evidence under the work root's report area. They may not be referenced by site code, copied into deploy assets, or included in the production bundle.
Contract
- Read schemas/raster-texture-report-v1.schema.json before creating or transforming a report.
- Start blocked work from templates/raster-texture-report.blocked.json.
- Use relative, traversal-free paths rooted at
--root. - Use
raster-texture-report/v1for the specialist report andraster-texture-metrics/v1for helper measurements. - The stable parent receipt shape is
{contract:"raster-texture-report/v1",path,sha256}.
Validation
Run the focused tests and structural skill validation after changes:
SKILL_ROOT="${SKILL_ROOT:-${CODEX_HOME:-$HOME/.codex}/skills}"
"$SKILL_ROOT/mockup-to-code/scripts/skill-pack-python" \
"$SKILL_ROOT/raster-texture-reconstruction/scripts/quick_validate.py"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
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.

