BuildEditing files directly
Updated 4 Nov 20261 min readView as Markdown

Editing files directly

Every project is real code. Change it yourself when you prefer.

Automo Build projects are standard React, TypeScript and Tailwind. You own the code, and nothing is locked away.

When editing by hand is the better choice

Chat is faster for most changes, but direct editing wins when:

  • You want to change one exact value, such as a padding, a colour or a label.
  • You want to copy a component into another project.
  • You are comfortable in code and want to move quickly.
  • A change is easier to make than to describe.

Things to know

  • Code is the source of truth. Chat changes and hand edits land in the same place, so you can mix them.
  • Styles are centralised. Colours, spacing and fonts usually come from shared design tokens, so changing a token updates the whole app. Prefer tokens over one-off values.
  • Database changes are not file changes. To add a table or a column, ask in chat so the change is applied safely.
  • Mention your edits. If you edit a file and then ask for a big change to the same screen, say so, so the builder preserves your work.

Deleting files by hand can break the app even when the preview still looks fine. If you are not sure a file is unused, ask before removing it.

Finding your way in the code

The structure is deliberately boring: pages in one place, reusable components in another, styles together, and server code kept separate. If you have used React before, you will feel at home quickly.

Next: Images and branding.

Was this page helpful?