No. The project model also includes logic, APIs, Storage, Content and database tables, Environment values, Scripts, Code Components, Documents, export settings, libraries, and MCP operations. Each surface has its own readiness and export behavior.
Start with the developer path.
Yes, with different roles. API files describe requests; Storage defines client-side schemas and optional loaders; Content and database tables provide typed records, views, relations, and actions; Components mount or reference those sources through logic. Authentication and generated backend execution still have documented unfinished boundaries.
Yes. Component logic connects events and lifecycle triggers to conditions, state/property changes, data actions, timelines, and other supported operations. Treat Preview as behavioral evidence, then inspect diagnostics and generated output because not every stored expression or branch combination has identical preview/export support.
Yes. A Code Component stores authored TSX, exposes a Component-like contract, and can be placed in visual Components. Misaki does not turn arbitrary source into a fully visual internal element tree; keep ownership of handwritten source explicit.
Yes through project libraries, subject to their current source/consumer model. A linked library is a dependency rather than an ordinary local folder: edit the source project, synchronize it, then verify each consumer.
Production MCP covers project selection, file and element inspection, many Component/design/data mutations, Preview and capture, diagnostics, code inspection/export, undo/redo, and generic registered operations. It does not expose every UI session gesture or every account, sync, Git, package, and publishing workflow.
Use the MCP capability reference.
Read the target, reproduce the behavior in Preview, inspect component or project diagnostics, inspect generated code when export is involved, and run the consumer's own typecheck/tests/build. A successful MCP write or clean screenshot alone is not enough.
Use the preview, test, and debug workflow.
Not as a general claim. The public backend boilerplate states that its SQL action engine is unfinished, authentication client generation has a current TODO, and sensitive Users-file export remains a boundary. Evaluate the scaffolding, but do not promise a working production backend until that exact flow passes runtime and integration tests.