← Selected work

AI-assisted engineering · Personal project

Designome

Give coding agents a memory for design.

I created Designome to give coding agents a lasting design reference. This plugin for Codex and Claude Code analyzes screenshots, structures their rules into a “Design DNA,” and integrates them into the project to guide subsequent interface work.

Role
Creator · Design and development
Status
Open source project · In development
Technology
Codex and Claude Code plugin · Node.js
Repository
Code and documentation on GitHub

System overview

Designome — System overview
checked against01ScreenshotsReference UI02Extract13 analysis axes03Design DNARules + evidence04 · The only human stepReviewExplicit approval05InstallBrief and tokens06BuildNew screens07AuditRender vs. ruleschecked against01ScreenshotsReference UI02Extract13 analysis axes03Design DNARules + evidenceThe only human stepReviewExplicit approval05InstallBrief and tokens06BuildNew screens07AuditRender vs. rules

Evidence taxonomy

  1. Observed

    Directly visible in supplied evidence.

  2. Inferred

    Derived from visible patterns and relationships.

  3. Proposed

    A design decision offered for explicit acceptance.

  4. Unknown

    Not provable from static screenshots.

Keep the design coherent across screens.

A coding agent can produce a convincing first screen from a screenshot, then drift when asked to build another page. Spacing changes, components lose their character, and the hierarchy becomes harder to read.

I designed Designome around this problem: make design decisions explicit and reusable so they can guide work beyond the initial reference.

Connect each rule to what the reference shows.

Designome distinguishes what is visible in a screenshot, what can be inferred, and what is a proposal. Each observation retains its source so the resulting rules can be understood and discussed.

This distinction matters particularly for behavior: an image does not show how a menu opens, how keyboard navigation works, or how a page adapts to mobile. These aspects still need to be checked in a working interface.

Make design knowledge part of the project.

The analysis brings typography, colors, spacing, composition, and component rules together in a Design DNA. Once the user accepts it, Designome installs structured documentation that the agent can consult during future tasks.

I separated visual interpretation, handled by the agent, from file operations, handled by the program. Requests and DNA are validated before use, and references can be assigned to a specific need, such as colors or charts.

Support a project as it evolves.

The workflow saves progress through analysis, DNA acceptance, installation, and audit. It can resume after an interruption while identifying the steps that need input from the user or the agent.

Installation checks the project before writing, records changes, and supports rollback. It separates files managed by Designome from user customizations so the design can continue to evolve.

Compare the interface with the original intent.

The fidelity contract identifies the visual qualities to preserve and the criteria to check for each component. It gives the agent concrete guidance for applying the design and evaluating the result.

The audit distinguishes correct rule installation, measurable layout, visual fidelity, and browser behavior. This separation helps locate gaps and guide corrections.

Learn from what gets lost between design and code.

Reconstruction experiments showed that table density, KPI anatomy, and content meaning can get lost despite a polished finish. Detailed documentation also needs to be interpreted and applied correctly.

These observations guide the next steps: refine component rules and check their resilience to content changes. Designome remains in development; documented evaluations help explain its limits and guide improvements.

+ Engineering principles

What the system is designed to preserve.

01

Traceable sources

Find the origin of design observations and rules.

02

Explicit decisions

Distinguish what is observed, inferred, proposed, or still unknown.

03

Controlled integration

Verify changes and preserve project customizations.

04

Design continuity

Give future tasks a shared reference to consult.

Next case studyDocument AI