Architect layer
Development mode
How work on this project is carried out. The agent reads this at the start of every session — said in a chat, it would not survive the conversation.
Development steps
The mode decides one thing: whether a confirmed use case and an open step are required before work begins. Everything else — the technical laws of the project — holds in all four.
Development steps
currentThe recommended mode
This is the recommended way to build here. The mode brings its own instructions and skills: the agent plans the work before touching code, reuses the patterns this project has already grown instead of inventing them again, and — if the session breaks or the context runs out — picks the work up from the same place, without losing what was decided.
Before you choose
This is the recommended way of working with the Fractera architecture. The project is built in numbered steps, each written down before it is done — so the work survives the end of a session, and you always see where it stands.
The agent breaks the task into numbered steps with sub-steps, and works the queue. What is planned survives the end of a session, because it is written down before it is executed.
Take it when the work is longer than one conversation.
- recommended for Opus 5
What the mode never changes.
Static public pages, size limits, translations instead of inline text, settings read from config — these hold in every mode. A law that a mode could switch off would not be a law.