Skip to content

docs(blueprints): loading, empty and error wireframes for Studio screens S07, S08, S11, S12 (#36) - #163

Merged
TOMOKI977 merged 2 commits into
mainfrom
docs/36-studio-state-wireframes
Oct 13, 2026
Merged

TOMOKI977 merged 2 commits into
mainfrom
docs/36-studio-state-wireframes

Conversation

@XxHugheadxX

Copy link
Copy Markdown
Contributor

Refs #36

Summary

This PR covers the first half of TOMOKI's remaining point on #36: the Studio images showed only the success state, while the other states were described only in tables. It adds 22 wireframes (1440 and 390), in the style of the S11/S12 ones from #161. It also links every state from the screen's state table, the way S02 and S03 already do.

Screen Loading Empty Error Success
S07-studio new: skeleton form while a draft loads new: blank form, "7 fields to complete", Deploy disabled new: the app's own ManifestProblem messages under the name, instructions and price fields (from studio_form_check.dart) existing
S08-deploy-sheet existing (stepper waiting for the signature) does not apply: the sheet opens only with a valid manifest new: "The signature was declined", Try again from that step, failed step marked in the stepper new: "Agent deployed" with agent id, agent wallet, registration tx, Open agent, View on explorer
S11-playground new: Running…, input locked, output skeleton new: 0 / 8,000, Run disabled, "free and limited per day" new: AgentExecutionFailed banner with Try again, runs left existing (#161)
S12-my-agents new: skeleton rows under Drafts and Live new: "No agents yet", Create your first agent new: "Could not load your agents", Retry existing (#161)

docs/blueprints/screens.md: the state tables of S07, S08, S11 and S12 gain a Wireframe column that links both viewports for each state. No spec text changed.

Acceptance criteria (#36)

Verification evidence

Notes for reviewers

  • On S11, the error image shows AgentExecutionFailed, the most common case. TestQuotaExceeded and an input over inputMaxChars stay described in the table.
  • The S07 and S08 wireframes from docs(blueprints): screen specs, wireframes and component inventory #146 are app screenshots. The new state images are drawn wireframes with the same layout, theme colors and copy.

…screens S07, S08, S11, S12

#36 asked for every Studio screen in both viewports with its 4 states;
the images covered only the success state. Add 22 PNGs (1440 and 390) in
the style of the S11/S12 ones:

- S07-studio: loading (draft skeleton), empty (blank form, 7 fields to
  complete, Deploy disabled), error (the app's ManifestProblem messages
  under name, instructions and price).
- S08-deploy-sheet: error (signature declined, Try again from that step)
  and success (Agent deployed with agent id, wallet, registration tx). Its
  loading state is the existing stepper image; empty does not apply.
- S11-playground: loading (Running..., input locked), empty (0 / 8,000,
  Run disabled), error (AgentExecutionFailed banner with Try again).
- S12-my-agents: loading (skeleton rows under Drafts and Live), empty
  (No agents yet, Create your first agent), error (Could not load your
  agents, Retry).

The state tables of the four screens gain a Wireframe column that links
each state, as S02 and S03 do.

Refs #36
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Deploying puls3 with  Cloudflare Pages  Cloudflare Pages

Latest commit: c6610ed
Status: ✅  Deploy successful!
Preview URL: https://5f1acd26.puls3-4lw.pages.dev
Branch Preview URL: https://docs-36-studio-state-wirefra.puls3-4lw.pages.dev

View logs

@TOMOKI977

Copy link
Copy Markdown
Contributor

The remaining #36 acceptance item is the frontend owner’s explicit confirmation that these specs are buildable. Please add or link that confirmation and request review before merge.

@TOMOKI977 TOMOKI977 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. The new loading, empty and error wireframes for S07, S08, S11 and S12 match the state tables, and the success rows point at the wireframes that were already in the spec.

CI is green on this head. The branch is behind main, so I will update it and merge once the refreshed checks pass.

@TOMOKI977
TOMOKI977 merged commit 4b78904 into main Oct 13, 2026
10 checks passed
@TOMOKI977
TOMOKI977 deleted the docs/36-studio-state-wireframes branch October 13, 2026 22:00
XxHugheadxX added a commit that referenced this pull request Oct 14, 2026
…-rejected copy (#36)

The S08 error wireframes (#163) said "The signature was declined", "Nothing
was registered on Stellar…", "Declined in the wallet" and "Back to
Studio". The deploy sheet shows the DeployErrorKind.signatureRejected copy
from deploy_copy.dart instead: "Signature rejected" / "The deployment was
cancelled in your wallet.", the failed step's own description ("Approve it
in your wallet"), and Try again / Cancel (deploy_error_panel.dart).

Both images (1440 and 390) are rendered again with the same wireframe
tool and fonts. The S08 Error row in screens.md now names Cancel and the
declined-signature copy.

Refs #36
TOMOKI977 added a commit that referenced this pull request Oct 14, 2026
…-rejected copy (#36) (#178)

The S08 error wireframes (#163) said "The signature was declined", "Nothing
was registered on Stellar…", "Declined in the wallet" and "Back to
Studio". The deploy sheet shows the DeployErrorKind.signatureRejected copy
from deploy_copy.dart instead: "Signature rejected" / "The deployment was
cancelled in your wallet.", the failed step's own description ("Approve it
in your wallet"), and Try again / Cancel (deploy_error_panel.dart).

Both images (1440 and 390) are rendered again with the same wireframe
tool and fonts. The S08 Error row in screens.md now names Cancel and the
declined-signature copy.

Refs #36

Co-authored-by: Julio Cesar Severiche Orellana <39506930+TOMOKI977@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants