Craft AnythingGUIDES
Menu

Project file guide · v0.3.0

Find your Craft Anything project files.

Locate your app code, read the project records and keep what you need to continue. Explore the file map here without an account.

Maintained by Arthur WintersUpdated November 5, 2026

On this page
01 · FIND THE APP

Project folder or app/?

The location depends on how you started. Choose the situation that matches your project.

NEW APP / STARTING MATERIALYour generated code goes in app/.
your-project/
├── craft.json
├── app/ ← your app code
├── capture/
├── reference/
├── checks/
├── investigation.cany/
└── inbox/

Open the app inside the project

Look for the generated app’s own files and run instructions inside app/. Starting material stays beside that folder.

EDIT AN EXISTING APPYour code stays in the selected folder.
your-existing-app/
├── your app’s files ← code here
├── craft.json
├── capture/
├── reference/
├── checks/
├── investigation.cany/
└── inbox/

Use the folder you selected

When you choose to edit the existing app, the builder works in that folder. A missing app/ folder is normal in this mode.

Guide diagram based on v0.3.0. Folders appear as the relevant work runs; this is a map of their roles.
02 · OPEN THE RIGHT FOLDER

Start from the project view

The Open folder button in the official Craft Anything project view.
ArtCraft · actual control detail · Full screenshot ↗
  1. Open the project in Craft Anything and select Open folder.
  2. Find craft.json. It identifies the project records; it is not the generated app.
  3. Use the layout above to find the code. Read that app’s run instructions before starting it.
Default locationDocuments/Craft AnythingNew projects use this location unless you change it in Settings → General or choose another folder.
03 · READ WHAT YOU HAVE

What does each part contain?

Choose a part of the project to see what it tells you and what to do next.

THE THING YOU ARE BUILDING

app/ or the selected app folder

This contains the implementation. The file types depend on the language and framework requested.

Next actionRead its run instructions, open the result and test a required action. Use the movie catalogue checks as an example.
WHAT WAS REQUESTED / WHAT HAPPENED

craft.json and build-activity.log

The manifest records the request, target, status and history. The activity log records run activity; an earlier log can be kept as build-activity.old.log.

Next actionCheck the request and latest activity when an attempt stops. Preserve the relevant error in a problem note.
TWO DIFFERENT IMAGE SOURCES

capture/ and reference/

capture/ holds recorded target observations. reference/ holds pictures of the original that you add. A new website study can replace the capture.

Next actionOpen the image and confirm it shows the intended target. If it shows a blocked page, follow the reference checks.
THE COMPARISON ROUNDS

checks/

This holds comparisons against the target, organized by round. The comparison answers a different question from a working search field or game control.

Next actionRead the relevant round alongside its reference, then try the required behavior yourself.
WHAT THE STUDY LEARNED

investigation.cany/

The investigation keeps evidence, memory and a journal. It is separate from the generated app.

Next actionKeep it with the project when preserving the study. Use the tool reference if you want to understand inspection commands.
DECISIONS WAITING FOR YOU

inbox/

This holds open questions and approval requests.

Next actionReturn to the project view and read the pending question or command before choosing a response.
04 · KEEP A WORKING COPY

Keep a complete working copy

Keep the app and the context needed to continue. Before editing existing code, make a separate copy of the folder you plan to change.

0 of 4 checks complete.

Choose the next check

From a file observation to a useful action
What you foundWhat to do
Records exist, but no app codeRead the activity and pending questions. Use missing-file checks.
Code exists, but you cannot run itRead the app’s instructions and keep the exact startup error in a downloadable problem note.
The app opens, but an action failsRecord the action, expected result and actual result. Follow the focused revision checks.
File-map sources and version

File locations follow the v0.3.0 README and workspace source, checked November 5, 2026. The diagrams are made for this guide. See how the guides are prepared.