chore: add cursor command to generate paragon integration docs #2973
+207
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
LagunaElectric
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added a cursor command to generate docs for paragon integrations using it's cs-docs JSON.
Also added
.cursor/tmp/to the gitignore as a common place for AI working files or outputs that aren't necessary for the repo.This new command is a workflow that ensures all necessary changes are made to the docs to add a new paragon integration including adding it to the sidebar, the datasources page (README), and a new doc in
connect_data/references/. It will run vale linter as a final step and iterate until it passes. You will need to manually go over the doc it generates for a final editing pass before submitting a PR.Pull request type
Check the appropriate box:
*