Craft Apps Guide

Your first Craft Anything project

Use a small website you own for your first Craft Anything project. The app's official README defines four stages: Study, Build, Check and Ready. A bounded sample lets you compare actual pages, navigation and files instead of treating a similarity number as proof that a new site works.

Set a task with a clear boundary

Choose a two-page site that you created or are authorized to examine: a home page, an information page and one navigation action between them. Keep the original URL or files, a copy of any assets you own, and a short list of observable behavior. Record the home page and second page at desktop, tablet and phone widths. Include the actual target width for each screenshot so the later comparison uses the same viewport.

Building requires a coding agent on your computer. The official README names Claude Code as its first supported builder. Sign in to that agent under your own account before starting. The same README labels Craft Anything early alpha, and its Codex adapter as not yet verified on a real installation; this first-project walkthrough uses the documented Claude Code path.

Before you startRecord or prepare
Original siteURL or local folder, ownership/permission and two pages to compare.
Allowed assetsFiles and text you own or have permission to reuse.
Target behaviorNavigation result, visible content and one interaction to check.
Local setupCraft Anything build, operating system and signed-in coding agent.
OutputA new project folder separate from the original.

Follow the four stages

  1. Study. Point Craft Anything at your site, describe the two-page scope and let it inspect the visible layout and behavior. The default clean-room mode works from what visitors can see; it does not read the target's hidden code or files. Keep the evidence it records for each page and width.
  2. Build. Ask for a new two-page implementation with the same navigation and responsive behavior. State which of your own images or text it may reuse. Do not add unrelated features or copyrighted assets from a third-party site.
  3. Check. Compare the new result with the original at the same three widths. Open both pages and activate the navigation. Review the generated project files. The app's comparison is evidence to inspect, not a substitute for opening the result.
  4. Ready. Open the new project, list differences that remain and request a focused correction. Keep the original and new folders separate until you have checked the result.

Use a simple record instead of a vague “looks close” judgment:

CheckOriginalNew projectDifference to fix
Home at desktop/tablet/phoneRecord layout and widthRecord layout at the same widthName the changed element.
Second-page navigationRecord destination and labelClick and record destinationNote missing or wrong route.
One interactionRecord input and visible resultRepeat the same inputNote behavior difference.
Output filesKeep original files untouchedOpen the new project folderNote missing or unexpected files.

When to stop and inspect

Craft Anything runs a coding agent under your own account and permissions. Its README says clean-room mode is a product rule, not an operating-system sandbox. Read a dependency-install or out-of-scope approval request before accepting it. The status section describes website checking at three widths and identifies current alpha limits. This guide does not claim a particular generated site passed those checks.

For the app's purpose and official downloads, use the Craft Anything application guide. Reverse Engineer Anything is a separate project, not this app's earlier name.

Sources