Summary
Pick up the existing AI-generated PR for the Governance onboarding UI and make it ready for
human review.
Source items:
- Parent issue:
#55 [Feature]: Governance UI Onboarding components
- Plan issue:
#56 [PLAN] Governance UI onboarding components
- PR to finalize:
#57 Add governance onboarding UI flow and reusable wizard primitives
The PR already adds:
- onboarding screens for welcome, house selection, profile, stake progress, and success
- shared
PageWizard and Stepper primitives in packages/ui
- Storybook stories under
examples/storybook/src/stories/governance-widget/
- Playwright widget coverage under
tests/widgets/governance-widget/
The contributor should focus on the remaining gaps in design, structure, and review readiness.
there are large gaps where it drifted from the original design references.
you are expected to test and go through the flow and verify design in both stitch and figma:
https://stitch.withgoogle.com/preview/1959701114157262308?node-id=2791404570cb4f338118ca3f7f87e9bb
https://www.figma.com/design/xsk5EiF6CvStA9mtdbA9OR/GoodWidget-Library?node-id=2373-2&t=DQGt4ziOfLbCRXay-1
Contributor task
Make sure to branch out from copilot/plan-governance-ui-onboarding-components >
and when you create a pull-request the target branch should also be verified to be: copilot/plan-governance-ui-onboarding-components
- Claim the bounty with an ETA.
- Check out PR
#57 and run it locally from the PR branch.
- Compare the implementation against issue
#55, plan issue #56, PR #54 for governance
styling direction, and any shared design references/Figma used during review.
- Fix concrete gaps in UI consistency, layout, component structure, and review evidence.
- Refresh screenshots/videos if UI changes.
- Leave a handoff comment with what changed, what was tested, and remaining risks.
Known finish-work to verify or fix
Scope checks
Required commands
pnpm install
pnpm run build
pnpm run lint
pnpm --filter @goodwidget/storybook build-storybook
pnpm test:demo tests/widgets/governance-widget
Summary
Pick up the existing AI-generated PR for the Governance onboarding UI and make it ready for
human review.
Source items:
#55[Feature]: Governance UI Onboarding components#56[PLAN] Governance UI onboarding components#57Add governance onboarding UI flow and reusable wizard primitivesThe PR already adds:
PageWizardandStepperprimitives inpackages/uiexamples/storybook/src/stories/governance-widget/tests/widgets/governance-widget/The contributor should focus on the remaining gaps in design, structure, and review readiness.
there are large gaps where it drifted from the original design references.
you are expected to test and go through the flow and verify design in both stitch and figma:
https://stitch.withgoogle.com/preview/1959701114157262308?node-id=2791404570cb4f338118ca3f7f87e9bb
https://www.figma.com/design/xsk5EiF6CvStA9mtdbA9OR/GoodWidget-Library?node-id=2373-2&t=DQGt4ziOfLbCRXay-1
Contributor task
Make sure to branch out from
copilot/plan-governance-ui-onboarding-components>and when you create a pull-request the target branch should also be verified to be:
copilot/plan-governance-ui-onboarding-components#57and run it locally from the PR branch.#55, plan issue#56, PR#54for governancestyling direction, and any shared design references/Figma used during review.
Known finish-work to verify or fix
Main gaps today are consistency issues in padding, color usage, font sizing, hierarchy,
badge/button treatment, and overall polish.
The current stepper/header treatment does not cleanly communicate the full 5-step flow.
packages/governance-widget/src/GovernanceOnboardingWidget.tsxis currently a largeall-in-one file and should be split into smaller component-based files with clean ownership.
Only reusable primitives should stay in
packages/ui; governance-specific composition shouldremain in
packages/governance-widget.Example: remove the duplicate
@goodwidget/governance-widgetdependency entry inexamples/storybook/package.jsonif it is still present.reflect the final branch output.
#55and#56and mirrors the finalacceptance criteria with a checklist.
Scope checks
#57still solves the issue#55requirements for the governance onboarding UI.#56or clearly explains any deviation.success and are visually aligned with shared design references
Required commands