Ran Prototype Creator on RHAISTRAT-1267

[beaumorley]

Ran /prototype-create against strat https://redhat.atlassian.net/browse/RHAISTRAT-1267 with fidelity=medium and mode=decide.

Here is the first screen. I think we need to put restrictions around the IA for the suggestions. We could tie this into some kind of IA and navigation guidelines so that it is not giving options that violate our design system.

cc @ymanor2404

[beaumorley]

[beaumorley]

Here is an HTML prototype for the non cluster admin user. This was what was generated based on the input I gave from decision kit. It is in an artifacts directory. I am not sure what the workflow should be for including this in the STRAT. Should we write the files back to the Jira?

[andybraren]

Thank you for testing it @beaumorley!

Note that the --workspace flag lets you specify an existing repo to build the prototype from, rather than building entirely from scratch.

In our case, passing it --workspace=https://gitlab.cee.redhat.com/uxd/prototypes/rhoai/-/tree/3.5 will make it pull down our current prototype and use that instead.

I think we need to put restrictions around the IA for the suggestions. We could tie this into some kind of IA and navigation guidelines so that it is not giving options that violate our design system.

I agree. 👍

I don't know where to make this change yet, but having the agent check the prototype's .design folder (if it exists) for relevant design & consistency guidelines to inform its suggestions would definitely be good here.

I am not sure what the workflow should be for including this in the STRAT. Should we write the files back to the Jira?

I think ideally this tool would automatically push/host the prototype somewhere (GitLab? Maybe an MR?) and then add a link to that live prototype to the Jira issue that was passed in initially. Wiring that up and working around some of our GitLab challenges is definitely something we need to figure out.

[beaumorley]

I do not see much reference to the workspace flag in the readme. I will try what you suggest and check against the readme again for recommended updates.

Would you see anyone using our prototype in this way? Even if not a UX person running /prototype-create? If so, we should explore this as a use case and make sure we can support it with our workflow and repo.

[jnemargut]

I think we need to put restrictions around the IA for the suggestions. We could tie this into some kind of IA and navigation guidelines so that it is not giving options that violate our design system.

The PatternFly MCP is pretty good for this when used along decision kit. One possible way to approach this is to have the instruction prompt check for Patternfly MCP and even without patternfly MCP say "follow the rules in pattern 6 (or whatever version)".

Decision Kit is really completely agnostic to any design library at all but bases its decisions off whatever instruction prompts or code base is within the repo the agent is pointing to. So if the repo is empty and the instruction prompt is empty it will just make its best judgment in general around decisions and be pretty abstract. If the prototype repo is already pulled down locally and the instruction prompt says to follow patternfly it will stay pretty close to that.

Some of this stuff could even be baked in and good without the --decide flag as well.

[andybraren]

I do not see much reference to the workspace flag in the readme.

@beaumorley Oh good catch, updated! 👍

Would you see anyone using our prototype in this way? Even if not a UX person running /prototype-create?

I suspect so. Prototyping new ideas atop "brownfield" code will likely be one of the most common scenarios. Right now /prototype-create does ask the user whether there's an existing repo that the agent should use:

Do you have an existing prototype or codebase you'd like me to build on top of?

• Yes, I have an existing repo — I'll add the new feature directly into your code, matching your existing style, components, and tech stack. Just share the local folder path or a git URL (like a GitLab link to a branch).
• No, start from scratch — I'll create a standalone HTML prototype you can open in any browser. No setup or dependencies needed.

Either way works great — building on an existing repo gives more realistic results, but standalone is faster and simpler to share.

So that should work. 👍

[andybraren]

@jnemargut That approach makes sense to me! I added similar logic to Prototype Creator so that if it pulls down a repo it'll check for any relevant agent-oriented documentation before continuing. That should hopefully keep "brownfield" prototypes a bit more consistent with whatever already exists. 👍