Desktop behavior comes before web-like convenience.
Vincent needs real windows, local files, pointer input, keyboard shortcuts, and a UI layer close to C++ painting code.
A curated working archive for technical documents, playable experiments, solution stories, and reusable visual material from iisacc.

Route-ready framework docs are organized as a navigable studio reference instead of a flat file dump.
Color Workbench handles HEX, RGB, HSL, contrast, gradients, and framework color code entirely inside the browser.
A canvas-first tool connects the game and solution material in this archive.
Development context, design judgment, and the practical reason the tool exists.
A place for new directions, collaborations, and solution-line changes.
These notes stay inside Contents because they are reference material, not a separate brand section. They explain the pressure behind the technical choices so solution pages can stay focused on what shipped.
Vincent needs real windows, local files, pointer input, keyboard shortcuts, and a UI layer close to C++ painting code.
Vincent is presented as a cross-platform desktop app so packaging, installation, and daily testing can be described without implying a single-platform direction.
Brush softness, layer behavior, undo boundaries, and export quality need solution-owned rendering work instead of a generic document model.
Screenshots, sketches, rough notes, and private drafts should begin on the user's machine and leave only when the user chooses.
iisacc treats content as production material: notes for judgment, assets for iteration, and small interactive experiments that keep the page alive.

A playable constant-scroll corridor with layered scenery, block patterns, spikes, and altitude control.
Hold click or press Space/Arrow Up to thrust. Enter restarts the run after a crash.
The asset page collects the mini game's source graphics with previews, direct downloads, and context for reuse.