Several issues with wireframes created in office-hours
- Dominant language
- TypeScript
- Stars
- 133k
- Forks
- 19.9k
- Avg merge
- 18h 46m
- Merged PRs (30d)
- 26
Description
I've come across 3 issues related to wireframe generation in the office-hours skill. They're interrelated but I've broken out into 3 issues here for clarity
**1. wireframes never make it to plan-design-review**
Even though office-hours claims the wireframe "can be referenced by downstream skills," the instructions for plan-design-review and design-review don't actually tell the agent to look for it
plan-design-review focuses on rating the "dimensions" of the written plan (0-10). It doesn't have a phase where it is required to "View the wireframe at /tmp/gstack-sketch.png and compare it to the plan."
**2. wireframes often deleted**
Because a wireframe is created in /tmp which is an ephermeral location, they can and are deleted. In my situation they're definitely removed and I had to go and rescue a png file before deletion so I can see it.
3. Appears to require a non-headless setup
I'm on a headless setup and the step
```
Step 4: Present and iterate
Show the screenshot to the user. Ask: “Does this feel right? Want to iterate on the layout?”
If they want changes, regenerate the HTML with their feedback and re-render. If they approve or say “good enough,” proceed.
```
never ran which means that the design docs wasn't created that referenced the screenshot.
Suggestions:
1. Recommend these wireframe assets be saved in $HOME/.gstack/projects/ directory with other assets/
2. Have the "present and iterate" step be more resilient
Contributor guide
Assessment
This issue has not been assessed yet.