DEV Community: qingwancong

Treat AI Relight as a Photometric Hypothesis, Not a New Portrait

qingwancong — Mon, 07 Sep 2026 06:14:01 +0000

The 23 August DEV post was about splitting a prompt into change versus preserve. This one is narrower: light is a physical claim.

If a model "relights" a portrait, it is asserting a new key, a new fill, and a new set of shadows on the same objects. That is closer to a renderer than to a filter. It can be useful. It can also mint a different evening, a different room, or a different person while still looking like photography.

I tested the current MendTrue relight preset on the public synthetic night-interior sample — not a customer photo.

Input: dual sources are already visible — cool window on one side, warm lamp on the other. Synthetic site sample.

The extra instruction was a single photometric request:

Add a soft key light from camera left. Keep identity, pose, clothing, background geometry, crop and time of day.

Official site after sample for the relight preset (same synthetic scene as the input). Treat new highlights as a hypothesis until catchlights and wall geometry agree with the source. AI photometric edit, not a reshoot.

Invariants that are cheaper to name than to repair

A relight job fails in a different way than a prompt-contract job. The face can remain "the same" while the physics rot.

I write the invariants down before generating:

identity and expression;
hair volume and clothing edges;
window, lamp, table, plant, picture frame — count and placement;
camera height and crop;
outdoor time of day (blue hour stays blue hour);
number of practical lights in the room.

Then the change set is allowed to include only: intensity, softness, and direction of light on surfaces that already exist.

If the window grows, the lamp shade changes species, or a third sconce appears, the hypothesis is already false. Pretty skin will not save it.

Three tests that do not need a lab

These are the checks I actually run at 100% zoom.

Catchlights. Eyes pick up the lights that exist. If the source had a window and a lamp, a result with a studio octabox and no window reflection is a different shoot.
Shadow direction. Nose, collar, and table legs should agree with each other. Mixed shadows from imaginary overheads are a tell.
Contact with the room. The lamp still sits on the same table. The plant still occupies the same corner. Relight is not set dressing.

Only after those three do I look at whether the new key is actually softer or merely brighter.

Failure modes I would log like bugs

Symptom	Likely broken invariant	Next retry
Face looks younger or smoother	identity / skin texture	Relight only; forbid retouch words
Window view becomes a different city	background geometry	Name the window as frozen
Warm lamp turns into daylight	time of day	State "keep blue hour + practical lamp"
Crop recenters the subject	camera	Repeat with explicit crop lock
Noise vanishes into plastic	material	Relight ≠ denoise; do not combine yet

I generated denoise as a separate 1-credit run on the same source file, on purpose. Mixing both in one request would hide which tool invented the smoothness.

What I store with the result

For a lighting experiment that might be reused in a product shot or a profile crop:

the untouched source;
the exact relight sentence;
the approved output under a filename that says relight;
a note that outdoor twilight was an input fact, not a style LUT.

You can run the same photometric loop in the MendTrue relight workspace. Approve the room and the catchlights before you approve the mood.

A Change-and-Preserve Prompt Pattern for Safer AI Photo Editing

qingwancong — Sun, 23 Aug 2026 08:14:47 +0000

AI photo editing is easy to demo and surprisingly hard to trust.

A request such as “make this photo better” sounds harmless, but it gives a generative model permission to reinterpret almost everything: facial features, clothing, objects, background geometry, light direction, crop, and even the number of people.

While designing the MendTrue Photo Workspace, I found a more reliable pattern: treat every edit as a small contract with three parts — change, preserve, review.

Synthetic source image used for this workflow test.

The result improves existing clarity, exposure, and color while keeping the same person, clothing, skyline, and crop.

1. Change: ask for one visible outcome

Start with the smallest edit that would make the image useful.

Good first requests include:

improve mild exposure and white balance;
reduce a reflection;
remove one distracting person;
recover moderate blur;
restore faded color.

A focused edit is easier to evaluate than a prompt that changes the weather, background, wardrobe, and face at the same time. It also gives a retry a clear target.

2. Preserve: make invariants explicit

The second half of the prompt should name what must not move. For a portrait, that usually means identity, expression, pose, clothing, important objects, light direction, framing, and aspect ratio.

I use a prompt shape like this:

Change: improve mild exposure and white balance.

Preserve: the same face, expression, denim jacket, skyline,
sunlight direction, composition, crop, and aspect ratio.

Do not add or remove people, objects, text, or logos.

This is not magic syntax. Its value is separation: the model receives one transformation goal and a readable list of invariants instead of an ambiguous aesthetic wish.

3. Match settings to risk

Not every photo should get the same amount of generative freedom.

For recognizable people, I start conservatively. A damaged historical scan may justify more reconstruction, but a modern portrait usually needs less. If a reference image is supplied, its role must be explicit: for example, “use the second burst-frame image only as evidence for the open eyes.”

A reference without a declared role can quietly introduce the wrong expression, pose, or crop.

4. Review locally and globally

The review loop matters as much as the prompt.

At 100%, inspect:

eyes, teeth, and hands;
hair boundaries and jewelry;
text and logos;
edges around the requested change.

Then return to normal viewing size and compare:

identity and expression;
subject and object count;
body proportions and pose;
perspective, horizon, and light direction;
the complete crop.

A technically crisp local patch can still fail if the full image feels like a different moment or a different person.

5. Retry by changing one variable

If the result is faithful but slightly too warm, revise only the color instruction. If an untouched region changed, repeat the preservation rule and narrow the requested edit. Do not fix drift by adding five new aesthetic goals.

This one-variable loop makes failures diagnosable and keeps each generation comparable with the previous one.

A useful product boundary

Generative repair is not forensic recovery. A model can create plausible detail where the source contains weak evidence. For important family or historical photos, keep the untouched source, exact instruction, and approved output as separate files, and describe generated reconstruction honestly.

You can try the change-and-preserve workflow in the MendTrue Photo Workspace, or read the complete prompt-based photo editing guide.

87 87 月牙抱橡果龙猫：九板分区拼豆接缝检查法

qingwancong — Sun, 02 Aug 2026 13:27:24 +0000

把一只蜷在月牙里、双手抱橡果的龙猫做成 87×87 拼豆图纸，最大的难点不是配色，而是把整张图拆成可铺、可校对的小块，并在熨烫前发现接缝错位。这篇按九板分区的思路，讲清楚备料、铺板顺序和边界校对三个环节。

先看清参考原画

这张是配色与造型参考原画，PDF 里标注为 AI artwork reference，对应 87×87、9 块 29×29 板、16 色、3,360 颗的图纸。需要说明：它只是配色和造型的参考，不是已经制作完成的实体拼豆作品，准确的颗粒摆放以下方编号图为准。

九块板的命名与铺板顺序

87×87 的画布切成三行三列，每块 29×29，按 A1–C3 命名：

第一行：A1（左上）、B1（中上）、C1（右上）
第二行：A2（左中）、B2（正中）、C2（右中）
第三行：A3（左下）、B3（中下）、C3（右下）

铺板顺序建议从左上往右上逐行推进：A1 → B1 → C1 → A2 → B2 → C2 → A3 → B3 → C3。这样每铺完一块，右手边的相邻列永远是下一块要对接的边界，方便即时比对。

备料与分装

16 色里有两色用量很大，务必提前分装，避免铺到一半才发现不够：

色号	颜色	颗数	含余量袋数
80-19057	Cheddar	1,306	2
80-19092	Dark Grey	1,048	2
80-15249	Honey	265	1
80-19056	Pastel Yellow	179	1
80-19021	Light Brown	163	1
80-19012	Brown	81	1
80-15239	Mocha	65	1
80-19018	Black	50	1
80-15274	Rich Butter	47	1
80-15207	Charcoal	46	1
80-19035	Tan	32	1
80-19004	Orange	30	1
80-15250	Gingerbread	22	1
80-15260	Stone	11	1
80-15220	Olive	8	1
80-15268	Sunflower	7	1

Cheddar 1,306 颗和深灰 1,048 颗各备两袋，先按每块板的用量预估分到小盒里，铺板时就不必反复回到大袋数数，也降低溢洒风险。

编号图怎么读

这张是同一图案的完整编号摆放图。格子里的小数字对应上方 16 色色表，橙色粗线划分九块 29×29 板的边界。铺每一块时，先定位三个锚点：龙猫的耳尖、月牙的内缘弧线、橡果帽的轮廓——这三个位置一旦坐准，周围的填色就有了参照。

三个接缝校对技巧

每完成一块板，沿橙色粗线把相邻的两列或两行再数一次，确认边缘色块对齐；熨烫前用主色（Cheddar 或深灰）在废板上做一小块小样，试好温度和时长再正式熨；如果发现接缝处颜色对不上，回到编号图核对该坐标，多数情况是相邻板之间错了一格而非颜色选错。

按这个流程，一只月牙抱橡果的龙猫就能分九块稳定地拼出来。更多图纸和材料清单可以在 Toonbead 图纸库查看。

How to Plan an 87x87 Umbrella Totoro Fuse Bead Pattern Across Nine Boards

qingwancong — Thu, 30 Jul 2026 10:12:36 +0000

Large fuse-bead patterns usually fail quietly. A single misplaced bead near the middle of one board may look harmless, but the error can shift a face, break an umbrella rib, or leave two finished boards one cell out of alignment.

This 87×87 umbrella Totoro pattern is a useful example because it combines three very different structures: a wide geometric canopy, a mostly solid dark body, and small rain details separated by empty space. The right workflow is not simply “start at the top and keep going.” It is to prepare the materials, name the boards, establish anchors, and protect every seam before any heat is applied.

What the PDF contains

The printable file has three A4 pages:

a complete numbered placement map;
the artwork used as a shape and color reference;
a counted material list with Perler color codes.

The pattern is 87×87 cells, divided into nine 29×29 board regions. It uses 16 colors and 2,766 beads.

Artwork reference for the umbrella character and color relationships. This is not a photograph or simulation of a finished physical bead piece; use the numbered map below for exact placement.

Complete numbered placement map. Each cell number points to the color key, while the thicker amber lines mark the 29×29 board boundaries.

Sort by job, not only by color

The shopping list immediately shows which colors deserve their own large trays:

Dark Grey: 1,053 beads, so the 8% spare estimate requires two 1,000-bead bags;
Honey: 435;
Creme: 432;
Cheddar: 253;
Mist: 136;
Light Brown: 120.

The remaining ten colors total only 337 beads, but several of them carry important information. Black and Charcoal define facial and outline details. Robin’s Egg and Mist separate the rain and puddle from the warmer umbrella. Olive, Slate Blue, and Stone appear only in small quantities, so losing one symbol in a large grey field is easy.

I would therefore use two material groups:

large open trays for colors 1–6;
small labelled cups for colors 7–16.

Keep the printed color key beside the small cups. Similar dark neutrals are much easier to confuse when their names are remembered but their numbers are not.

Give every board a permanent address

Name the boards before placing the first bead:

A1  A2  A3
B1  B2  B3
C1  C2  C3

Write the same address on a removable note under each physical board. The complete map retains the original 87×87 coordinates, with thicker lines after columns 29 and 58 and rows 29 and 58. Those lines are not decorative; they are the hand-off points between boards.

For each shared edge, copy a four-cell-wide inspection strip onto scrap paper. For example, the A2/B2 seam check should include the final two rows of A2 and the first two rows of B2. A four-row strip catches more mistakes than comparing only the two touching rows because it preserves the direction of diagonals and umbrella ribs.

Build anchors before filling large areas

This design has broad regions of Dark Grey, Honey, and Creme. Filling those blocks first feels efficient, but it removes the landmarks that make counting reliable.

Use this order instead:

place the umbrella’s outer curve and the main rib intersections;
mark the eyes, nose, belly symbols, feet, and umbrella handle;
place the isolated raindrops and the ends of the puddle;
complete the character’s outer contour;
fill the large Dark Grey, Honey, and Creme regions last.

The isolated rain marks are especially useful anchors. Because they sit in empty cells, a one-column error is obvious there but can disappear inside the body.

Work in short runs of five or ten cells and stop at a symbol change. Do not count a continuous row of grey as one long task. Resetting the count at each contour change prevents an early mistake from moving the rest of the row.

Treat each seam as a small independent pattern

Before moving from one board to the next, perform three checks:

compare the last two rows or columns with the numbered map;
verify that every contour crossing reaches the same coordinate on both boards;
check that empty cells remain empty, particularly around the umbrella and raindrops.

The wide canopy crosses both vertical board boundaries, so its curved edge is the best seam indicator in the top row of boards. The character body and belly cross the lower boundaries. If those outlines meet correctly, the large interior fills are unlikely to drift.

Photograph each finished, unheated board from directly above. The photo is not proof that the full assembly is correct, but it gives you a stable reference if a bead is knocked loose while another board is being checked.

Test heat before committing nine boards

Dark and pale beads can appear equally placed but react differently under the same heat and pressure. Make a small test swatch containing Dark Grey, Honey, Creme, Cheddar, Mist, and Light Brown. Use the same iron, paper, surface, temperature, and pressing time intended for the final piece.

Look for three things:

hole closure is similar across light and dark colors;
the swatch stays flat after cooling under weight;
edge beads remain joined without spreading so far that board alignment becomes difficult.

Do not heat a board just because it is complete. First dry-align all nine unheated boards, inspect every shared edge, and confirm the outer silhouette from a few steps away. If the final method involves heating separate sections, test that exact seam method on spare beads before applying it to the pattern.

A compact build checklist

Before placement:

print the PDF at 100% scale;
label all nine boards;
sort colors by number;
reserve two bags of Dark Grey;
prepare seam strips and a row counter.

Before heating:

verify the facial anchors and umbrella ribs;
compare all twelve shared board edges;
confirm isolated raindrops against their coordinates;
dry-align the full 3×3 layout;
complete a heat swatch with both dark and pale colors.

The same board-first method works for any large printable fuse-bead pattern. The important idea is to move uncertainty forward: materials, coordinates, seams, and heat behavior should all be settled before the piece becomes difficult to correct.

The matching PDF workflow and other printable designs are collected in the Toonbead printable pattern library.

A board-by-board method for building an 87 87 white cat bead pattern

qingwancong — Tue, 28 Jul 2026 15:56:33 +0000

PDF page 2: the artwork reference for the subject and color balance. It is not a photograph of a finished fuse bead piece.

PDF page 1: the complete numbered placement map. Use this page for exact bead positions and 29 × 29 board boundaries.

A mostly white bead pattern looks forgiving until you start placing it. The silhouette is easy to recognize, but three pale colors can collapse into one under warm room light. The mistakes are rarely dramatic; they are usually a row of White placed where Toasted Marshmallow should have carried the shadow.

This white cat and camellia pattern is 87×87 cells. It spans nine 29×29 square boards, uses 16 colors, and contains 3,155 beads. The printable pack is three pages: a full view, a numbered placement map, and a material key. Here is the workflow I would use before touching the first peg.

Sort by code, not by color name

The four largest groups are:

White: 1,782 beads
Toasted Marshmallow: 735
Tomato: 152
Tan: 115

White and Toasted Marshmallow account for almost four fifths of the project. Put them in separate opaque trays and label each tray with both the symbol from the PDF and the color code. Do not rely on visual memory after sunset; pale beads change surprisingly much under yellow light.

The material list includes an 8% allowance. White needs two bags at that margin, while each of the other major colors fits into one. I still keep a small “unknown” cup beside the board. If a bead rolls away and I cannot identify it immediately, it goes there instead of being guessed back into the pattern.

Place the anchors before the white field

Do not begin by filling the largest empty-looking area. Start with the eyes, nose, ear edges, the red camellia, and the dark outline around the flower. These high-contrast landmarks make it obvious if the design has shifted by one column.

Once the anchors line up with the numbered map, fill the pale regions outward from them. A wrong white bead inside a large white area is hard to notice. A wrong bead beside a black eye or red petal is obvious immediately.

Give the nine boards names

Label the 3×3 board layout A1–A3, B1–B3, and C1–C3. Add the same labels to a printed copy of the map. When one board is finished, check only two things before moving on:

Compare the final two rows on every shared edge.
Take one overhead photo in the same orientation as the PDF.

That photo is not for social media. It is a cheap checkpoint. If the next session begins two days later, it tells you which board was finished and whether it was accidentally rotated.

Treat the PDF pages as different tools

The full image is for checking the cat’s pose and balance. The numbered map is for placement. The material table is for shopping and refilling trays. Trying to use the attractive preview as the placement guide is what makes a large project feel harder than it is.

Small isolated cells deserve a manual check, especially around eyes, whisker roots, and flower edges. In a face, a cluster of three dark beads may carry more identity than a patch of fifty white beads.

Test the iron before the cat

Make a tiny test patch from spare beads. Start with a dry iron at medium heat, always use ironing paper, and move the heat evenly without pressing hard. If the center holes close immediately, reduce the temperature. For a nine-board piece, uneven heat at the outer edges is more dangerous than taking an extra minute.

Let the piece cool before lifting the paper slowly. If children are involved, the ironing step belongs to an adult.

The useful part of a large pattern is not the thumbnail. It is the combination of a readable map, board boundaries, exact counts, and a material key. The cat pattern library and its printable workflow are available in the Toonbead printable pattern library.

Designing a Roblox Player Companion Around Verifiable Information

qingwancong — Fri, 24 Jul 2026 16:12:59 +0000

Player guides for a fast-moving Roblox game have a reliability problem: a useful page can become wrong as soon as an update lands.

I built Merge a Black Hole Companion, an independent, unofficial resource for players of XAF Games’ Merge a Black Hole. The project is deliberately scoped around information a guide can stand behind: current game status, codes with a source/verification label, beginner and raid routes, update notes, and small planning tools.

The central product decision was to separate facts from assumptions.

A live status surface uses the Roblox Games and Votes APIs rather than copying a number into a page.
Codes and update notes are labelled by source and verification state instead of being presented as permanent truth.
The upgrade tools run privately in the browser. They help a player reason about ROI or compare two upgrade paths without requiring an account.
Pages avoid publishing unverified progression tables, exploits, or fake “community” activity.
Every important route keeps the unofficial fan-site disclaimer close to the relevant player action and points people back to official links.

That sounds conservative, but it is a better fit for a game whose meta changes often. A companion does not need to pretend it knows every number; it needs to make its evidence clear and help players make a decision with the information currently available.

The implementation is a small Cloudflare Worker app with server-rendered, indexable guides, JSON-LD, a sitemap, and an Open Graph asset. The hard part is not the framework. It is maintaining the boundary between a useful player tool and an authoritative-looking page with no evidence behind it.

The project is available at https://mergeablackhole.net/

Why I Built a Free Printable Bead Pattern Library Instead of a Gallery

qingwancong — Tue, 21 Jul 2026 16:58:23 +0000

A usable craft template needs more than a pretty preview

A lot of digital craft resources stop at the image. They give you a small preview, perhaps a color approximation, and then leave the difficult translation to the person at the pegboard.

That is fine for inspiration. It is not enough for a pattern someone can actually start, pause, and finish.

The update I have been working on is a free printable pattern library for Toonbead. Each entry begins as original Toonbead Studio artwork and becomes a deliberately constrained 29 × 29 fuse-bead project. The point is not to generate a large collection of decorative thumbnails. The point is to publish templates with the missing handoff details included.

Treat the placement map as the source of truth

A finished-looking pattern image is helpful for seeing the result, but it is a weak build instruction. Small colors merge, visual counting is error-prone, and two similar shades can become indistinguishable once the image is printed.

Each library pattern therefore has a complete numbered placement map. Every colored cell uses the same symbol that appears in the printable PDF and in the material key. That lets the builder work from an unambiguous grid rather than trying to reverse-engineer a scaled-down preview.

The initial collection deliberately stays at one 29 × 29 board. That constraint is part of the product design: it keeps the project approachable, makes the page honest about the required footprint, and avoids presenting a multi-board undertaking as a quick afternoon craft.

Material counts should be measured, not guessed

The next gap in many free patterns is materials. “Use some blue and brown beads” is enough for an illustration, but not enough for someone preparing a project.

A pattern page should tell the person how many beads it contains, which real palette it maps to, and how to retrieve an exact color-by-color list. In the library, each template includes counted materials and a downloadable CSV with a small spare-bead allowance. The printable PDF is a four-page build document rather than a single poster: overview, board map, symbol key, and material information have different jobs.

This also creates a useful standard for future templates. A visual has not earned the label “free pattern” merely because it exists as a picture. It should be possible to check the grid, gather materials, and begin without inventing missing instructions.

Keep the origin of the artwork clear

The library templates are original Toonbead Studio digital artwork. They are not user submissions, and they are not photographs of completed physical pieces. That disclosure matters because a source artwork and a real-world build are different kinds of evidence.

Showing the source alongside the bead pattern makes the transformation understandable without pretending that the physical craft has already been completed. It also protects the library from drifting into an opaque feed of generated images with no clue how they became buildable.

A template should be a starting point, not a dead end

A useful free template does not need an account, an AI generation, or a credit balance to load. But a builder may still want to change the colors, alter the size, inspect another bead brand, or export the result again.

That is why the final link in the workflow matters: opening a library template in the Maker transfers a real pattern into a local editing context. Loading, recoloring, resizing, and exporting the public template remain local operations. Optional AI remains separate and requires an explicit choice later; it is not silently attached to a free pattern.

The result is a smaller promise than “unlimited AI art,” but it is more useful to a maker. A person can select a recognisable project, see the exact work involved, print it, and still adapt it for their own materials.

The first free library templates, including owl, butterfly, dinosaur, hedgehog, watermelon, cupcake, ghost, flower, star, heart, crown, and alphabet patterns, are available in Toonbead’s Pattern Library: https://toonbead.com/patterns

Designing an Own-Voice Consent Flow for an API-First TTS Product

qingwancong — Sat, 18 Jul 2026 16:03:26 +0000

Voice cloning is a product-design problem before it is a model problem

It is tempting to describe voice cloning as a simple pipeline: collect a sample, create a voice, synthesize some text. That description is technically tidy, but it skips the part that determines whether the workflow deserves trust.

A voice is not merely another media asset. It is recognisable, personal, and easy to mistake for identity. So the interface has to make the boundaries of the system legible before anyone reaches the satisfying moment of pressing “generate.”

This is the set of constraints I use when designing an own-voice text-to-speech workflow.

Put consent inside the action, not after it

A generic terms checkbox at account creation is weak context. The meaningful decision happens when a person uploads or records the sample that will become a reusable voice.

The flow should therefore make three things concrete at that point:

The user is supplying their own voice, or has the authority to use it.
The sample is being used to create a synthetic voice for the requested purpose.
The user understands that generated speech is a new output, not a recording of something they said.

A short spoken verification phrase is useful here. It makes the experience more intentional than a silent upload, and it gives the product a natural place to explain the boundary. The goal is not to pretend that one phrase solves every identity question. It is to avoid an interface that treats the source voice as an anonymous file.

Separate the clone from the script

There are two different decisions in this category of tool. The first is whether a voice should be created. The second is what text that voice should say.

Keeping those stages separate improves both the user experience and the auditability of the product. A creation step can focus on sample quality, consent, and what is retained. A synthesis step can focus on pronunciation, pacing, language, and the actual script. Combining them in one opaque button makes it harder for a user to understand what happened and harder for the product team to set responsible defaults.

This distinction also makes errors easier to communicate. “We could not create the voice from this sample” and “we could not synthesize this script” are different failures. They should not collapse into a vague loading state or, worse, a plausible-looking fake result.

Make failure honest

Generative products are often judged by their happy path, but trust is built in the unhappy path. If the voice provider is unavailable, the product should return a clear temporary error. If a sample is too short or unusable, explain the next useful action. If the request cannot meet the product's consent rules, stop before generation.

That may feel less magical than silently substituting a generic voice, but it respects the user. A workflow that creates media should always make the origin of its output clear.

Privacy is part of the interface

People reasonably want to know what happens to a sample after upload. The answer cannot live only in a policy page. The UI should say, in plain language, what the current action sends, what is processed remotely, and what the user can expect to keep locally.

For small creator tools, clarity has another benefit: it prevents product scope from drifting toward “clone any voice” as a growth shortcut. A focused own-voice workflow is not just a safer message; it gives the interface a coherent job to do.

The best use case is often continuity

The most grounded use cases are practical: recording accessible narration in a familiar voice, drafting a corrected pickup after a recording session, or turning a prepared script into an audio version without losing the creator's identity.

Those are not reasons to remove safeguards. They are reasons to build safeguards into the workflow people actually use. When a tool asks for explicit intent, separates creation from synthesis, and reports failure honestly, it feels less like a trick and more like a piece of creator infrastructure.

I am applying these constraints in ClonaTuVoz, a Spanish-first own-voice cloning workspace: https://clonatuvoz.com/

ChatWorkSkin: a free Codex skin builder with automatic macOS and Windows installers

qingwancong — Fri, 17 Jul 2026 18:29:34 +0000

ChatWorkSkin is now focused on one simple workflow: build a free Codex skin in the browser, download a layered .dreamskin package, and install it with a guided macOS or Windows path.

The current homepage positions it around these keywords: free Codex skin, ChatGPT skin for coding, Codex desktop theme, AI coding workspace theme, and automatic Codex skin installer.

What the page offers

A local visual builder for layered .dreamskin themes
Built-in original artwork presets for Codex desktop customization
A live Codex-style preview before installing
Automatic installer guidance for macOS and Windows
A restore path that keeps native Codex controls and app files intact

The key point is that the skin is not a fake screenshot overlay. It is built for a coding workspace where the sidebar, project picker, tasks, menus, and composer still need to work normally.

Try it here: https://chatworkskin.com/

Correction: ChatWorkSkin 1.2.2 latest UI uses the new fine-tune panel

qingwancong — Fri, 17 Jul 2026 07:23:07 +0000

I reposted ChatWorkSkin with the correct latest UI screenshot.

The current 1.2.2 build is about layered .dreamskin themes and native Codex controls, but the visual detail that matters is the new fine-tune panel. It shows optional foreground layers, theme name, theme copy, colors, and focal point controls in the current studio UI.

This replaces the older workbench screenshot I shared earlier.

Current product page: https://chatworkskin.com/

Search-intent mirror: https://chatgptskin.org/

Keywords: Codex skin, Codex theme, Codex desktop customization, AI coding workspace theme, dreamskin theme package.

ChatWorkSkin update: a visual Codex skin studio with layered .dreamskin packages

qingwancong — Fri, 17 Jul 2026 06:45:38 +0000

I pushed a new visual update for ChatWorkSkin / Codex Dream Skin. The project is still focused on one narrow job: make a Codex desktop workspace feel personal without breaking native controls.

The latest version is no longer just a background swap. It is a small local studio for Codex skins:

choose original artwork
preview the Codex desktop theme before installing
export a verifiable layered .dreamskin package
install on macOS or Windows with a prefilled Codex task
keep the native sidebar, task list, input box, and restore path intact

The product angle is for people searching for a Codex skin, Codex theme, Codex desktop customization, or an AI coding workspace theme.

Try it here: https://chatworkskin.com/

Search-intent mirror: https://chatgptskin.org/

The implementation deliberately avoids modifying the official app package. The skin package and install flow stay reversible so the desktop workspace can be customized without turning the app into a fragile fork.

Building a free Codex skin installer without touching the official app package

qingwancong — Thu, 16 Jul 2026 16:12:58 +0000

I shipped a small tool for a very specific search intent: people looking for a ChatGPT skin or a free Codex skin for their coding workspace.

The result is Codex Dream Skin: a free Codex desktop theme with original artwork, a local preview, and an automatic installer for macOS and Windows.

The important constraint was not visual. It was safety.

A theme tool for a coding assistant should not ask users to replace the official app, patch an app bundle, edit app.asar, or take ownership of protected Windows app files. That kind of shortcut may work once, but it is brittle across updates and hard to restore.

So I built the workflow around a different rule:

Change the mood around Codex, but keep Codex itself intact.

What the site does

The public page is built around the keywords already used on the website: Codex skin, Codex theme, free Codex skin, automatic Codex skin installer, Codex desktop customization, ChatGPT coding theme, Codex macOS, and Codex Windows.

The flow is deliberately simple:

Choose one of the bundled original themes.
Preview the Codex skin in the browser.
Prepare the one-command installer.
Paste it into Terminal or PowerShell.
Restore the original Codex appearance whenever needed.

The tool also supports a custom-image path on macOS, so users can turn their own artwork into a Codex desktop theme.

Why native controls matter

A lot of visual demos can fake a full app with a screenshot. That is not useful for daily work.

Codex Dream Skin keeps the real Codex controls in place:

sidebar
task list
project picker
menus
composer
restore path

The theme changes the surrounding visual layer and background treatment. It does not replace the workflow with a static mockup.

The safety boundary

The installer is designed around a local loopback session and a reversible restore step.

It does not modify:

the official Codex app package
app.asar
WindowsApps files
code signatures
conversation data
login state
API keys or model-provider configuration

That last point matters. A skin should stay separate from credentials and model routing.

Why I also use ChatWorkSkin

The search-domain angle is chatgptskin.org: it is for people typing things like “ChatGPT skin”, “free ChatGPT skin”, or “free Codex skin”.

The brand/workspace angle is chatworkskin.com: it frames the same project as AI coding workspace theme and Codex desktop customization.

Same product, two discovery angles.

Current state

Free to use
No account required
macOS and Windows installers
Built-in original themes
Custom image workflow on macOS
One-command install
One-click restore
Unofficial, not affiliated with OpenAI

If you use Codex Desktop and want the workspace to feel less default, the early version is here:

https://chatgptskin.org/