Capture visible states
Record pages at several widths, visible text, layout measurements and open controls to specify what the new project needs to do.
Craft Anything
Craft Anything collects evidence from software you are allowed to study, passes a brief to a coding agent, and compares the new implementation against the reference.
Turn three viewport captures into a prototype brief
Bring authorized screenshots and a short description of the interaction. Use Craft Anything’s evidence and comparison model to turn what you observed into checks the builder can run.
Name the page, supported viewport widths, and key states such as an open menu or error.
Copy the request into a new Floatboat conversation and provide the required material.
Download FloatboatYour request for Floatboat
Preview and copy the request. It is not sent automatically from this page.
Reference: Craft Anything https://github.com/storytold/craft-anything Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding. My task: Study Craft Anything’s clean-room and comparison workflow. Use my desktop, tablet and phone screenshots of our pricing page to write a replacement brief. List observable behavior, specify our own assets, and create checks for the open menu and monthly/yearly toggle. Separate assumptions from evidence. Expected deliverable: A responsive prototype brief with an evidence list, asset boundaries, and a state-by-state test matrix.
From software observation to a testable rebuild
A screenshot captures one moment. It leaves out mobile layouts, open menus and the behavior that makes a prototype useful. Craft Anything is an early-alpha Rust project that records observations and puts them alongside a new implementation and its comparison results. The desktop app, CLI and MCP interface expose the same underlying engine.
The default clean-room mode studies visible behavior, such as text, screenshots, spacing and menu states. Deep mode can inspect internals such as files or code when you are authorized to examine them. The mode does not isolate the operating system, and a coding agent still acts with its own permissions.
The useful pattern for a Floatboat workflow is to turn observable evidence into a brief and a set of acceptance checks. Choose assets and interactions you have permission to reuse, keep references separate from generated files, and record differences you want to fix or keep.
How Craft Anything connects evidence and implementation
The project folder separates the capture, new implementation, and comparison results. Those artifacts make it possible to revisit one mismatch without reopening every design choice.
Delegate the build
Give an installed coding agent a brief and target stack. Upstream documents Claude Code as the first supported builder.
Compare the result
Review viewport checks and remaining mismatches against the source evidence, then decide which differences need another pass.
Craft Anything use cases
Choose a target you can examine and a small set of behaviors worth reproducing. The handoff should identify what was observed, where the brief leaves room for judgment, and how to evaluate the result.
Replace an internal page with a responsive prototype
Capture the current layout at desktop, tablet and phone widths, including a collapsed navigation state. Ask the builder to use your own copy and assets, then check overflow, element order and menu behavior at all three widths.
Document the behavior of a retiring desktop tool
Work from a permitted copy and record how the window changes after an import, an empty file or a failed action. Turn the observations into acceptance cases for a replacement and list any behavior you could not reproduce.
Rebuild a game mechanic as a small experiment
Choose a mechanic you may study, such as a movement or scoring loop, and describe it using your own art and level design. Treat a runnable demo and a repeatable gameplay check as the handoff, with unresolved differences listed separately.
Separate regressions from approved design changes
After reviewing a comparison, approve the intentional differences in writing and turn the rest into small fix requests. Rerun the affected checks so later reviewers can tell a deliberate redesign from an unresolved mismatch.
What to prepare before a Craft Anything run
Start with a target you are authorized to inspect and a separate project folder. Confirm your platform’s release and your coding agent before committing to a larger rebuild.
A reference you may study
Define what can be captured and what assets, copy or branding require separate permission.
A build agent for implementation
Check the supported backend in the upstream status notes. Claude Code uses its own local installation and sign-in.
A testable project scope
Pick representative screens or states and write down how you will compare them. Early-alpha support varies by target and tool.
Related Software Projects
Compare the workflows, operating requirements, and source licenses of these projects.
Craft Anything FAQ
What can the default clean-room mode see?
It uses visible evidence such as screenshots, text and measured layout. Deep mode is separate and may inspect internals where you have permission.
Does clean-room mode sandbox the builder?
The mode controls what Craft Anything offers for inspection. The operating system and coding agent keep their own permission boundaries.
Is Craft Anything ready for production migration?
Upstream labels it early alpha. Pilot with a bounded target and verify the particular platform, agent and comparison tools you intend to rely on.
Can I inspect a project without starting a build?
Yes. The upstream app provides an inspection-only path in Deep mode, and the CLI and MCP interfaces expose inspection tools.
Can I use Codex as the builder?
Upstream documents a Codex adapter but says it has not verified it on a real installation. Check the current status before depending on it.
Does the source license cover the target’s assets?
Craft Anything is offered under MIT or Apache-2.0. A target's logos, text, images and other materials keep their own rights.