Conversation
6ed4372 to
0762850
Compare
|
Hell yeah, thanks for diving in with this! love that we have an example to test against. A couple things:
Have a look at the examples repo for some thoughts on how we do this: https://github.com/PostHog/examples The examples project turns into a zip file that the MCP ingests and reflects as of note: https://github.com/PostHog/examples/tree/main/llm-prompts These are the high level prompts that drive wizard runs, stored as markdown. https://github.com/PostHog/examples/tree/main/mcp-commands These define the slash commands delivered to Claude Code, Cursor, etc Your prompt uses a ton of string interpolation, which is fine: we'd probably have a runtime-generated, thin base prompt that plugs in all the variables, then appends the bulky stuff by calling an MCP URI. Check out how |
|
The wizard workbench can get the full set of wizard > MCP > examples working together as well: |
This still needs work! We should also consider some way to detect if they have linting, formatting, etc in their project so we can hook into that and get into a validation loop with the changes the agent makes against their codebase. The migration guides can be a bit more inclusive as well.
I had this idea at lunch today, this seems like such an obvious win. Had to scratch the itch and see how easy it would be.
Arch'd it to be provider abstract so we can easily implement other SDKs migrations as well.
Tested on their example react app, it one shot converted it with no errors.
https://github.com/amplitude/ampli-examples/tree/main/browser/typescript/v2/react-app