Refine plugin guidance in AI system prompt

[nerrad]

Related issues

• Related to plugin site building improvements.

![NOTE]
Early testing is showing promising results for creating a commerce type site (inferring WooCommerce, and ensuring relevant block themes and blocks are used. But I'm still testing/tweaking because it's not quite there yet.

How AI was used in this PR

• AI-assisted authoring of the prompt guidance and PR preparation. Update this section if you want a more specific summary.

Proposed Changes

• Add guidance to discover and incorporate plugin-provided pages, templates, patterns, routes, and blocks into generated site designs.
• Prefer block-based plugin integrations and extending existing plugin blocks before creating new custom blocks.
• Require default plugin configuration and visible frontend integration so plugin installs produce a usable baseline experience.

Testing Instructions

• Review the prompt updates in apps/cli/ai/system-prompt.ts.
• Run a plugin-oriented site generation flow and confirm the agent uses relevant plugin-provided frontend experiences.
• Not run locally during this PR creation pass.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[sejas]

@nerrad, let me know when this PR is ready for a review, or if it’s no longer necessary.

[nerrad]

hey, sorry, I haven't had a chance to circle back to this yet. I was getting some early signals this prompt helped improve the experience of integrating plugins (like WooCommerce) but it needs more testing and validation. Something I can't do at the moment. Much of the prompt was hand crafted (PR description, not so much 🙂).

[sejas]

Perfect, thank you Darren. We'll add evals to measure how studio code performs in different tasks. So if you have in mind some prompts you want to improve, just let me know to add those.

[nerrad]

You mean beyond what is already in this PR?

[sejas]

I'm interested in knowing the other side. Some examples of user requests/queries that will be improved like:

• "Redesign the blog archive"
• "Create a contact page"
• "Customize the single product page"
• "Add WooCommerce Bookings to my site"
• etc

[nerrad]

Oh gotcha, ya so the angle I was looking at with this PR is just making sure that if the agent decides to install a particular plugin to satisfy a user request (either explicit or implicit), it has some basic direction on what to use from that plugin (if it exists) when creating the site. This is particularly important for plugins like WooCommerce which is supporting both classic (classic themes/templates/shortcodes/template functions) and new functionality (block themes, block templates, blocks etc). It's also useful for making sure the agent looks for any existing onboarding flows for a plugin to infer questions to ask the user for additional configuration as well. I thought that'd be a good step one.

Future system prompt work might look into favoring explicit plugin suggestions for given requirements but I don't think that needs to happen right away.

[sejas]

Thanks for adding more context. That's really helpful. I agree that make a difference between classic and block theme is key. 🤔