Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I don't know if I like treating it as an override. You lose the ability to copy markdown and work with any other LLM besides Cursor. What if the buttons move below the larger callout? |
I recon we should update the "Open in Cursor" in the And possibly we add a button next to the "edit in github" button at the bottom of the page of "view raw markdown" that opens the
Thats an option, but I still feel like will confuse people |
I can see that. Big, bold callout with |
manovotny
left a comment
There was a problem hiding this comment.
Contradicting myself and approving.
Longer story: Nick and I met and discussed what I was asking for earlier. Thing is:
- None of the other items in the Open in list are IDEs where you'd be doing coding with a custom prompt like this except for Cursor. We could look to add others like VS Code and Zed as a future feature separate from the PR.
- Further, opening that prompt into an AI client (i.e. ChatGPT) does basically nothing. The LLM says "Got it." because it's not capable of performing a coding task like the prompt guides.
Based on that, it makes sense to only render the LLM prompt or the LLM actions, not both (at least at this time).
🔎 Previews:
What does this solve?
Once https://github.com/clerk/clerk/pull/1837 is merged, users on the new docs actions locations will see the actions right above the
<LLMPrompt />component. But this creates two issues:What changed?
llmis defined in the frontmatter.We are effectively treating the llm prompt as an upgrade over the guides actions, if its defined then we want to hide the guide actions as to not cause confusion.
Checklist
This pr does not need to be merged before https://github.com/clerk/clerk/pull/1837, but it will need to be merged before the feature flag gets enabled / rolled out to 50% of people.