Update Joyride user scriprs project instructions

[PEZ]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• My contribution adds a new instruction, prompt, or chat mode file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, or chat mode with GitHub Copilot.
• I have run node update-readme.js and verified that README.md is up to date.

---

Description

Updates Joyride User Project instructions, with more workflow patterns and new Joyride fearures

---

Type of Contribution

• New instruction file.
• New prompt file.
• New chat mode file.
• Other (please specify): An update to existing instructions

---

Additional Notes

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[Copilot]

Pull Request Overview

This PR updates the Joyride User Project instructions to include more comprehensive workflow patterns and newly added Joyride features. The update enhances the guidance for interactive ClojureScript programming and VS Code automation in user space.

Key changes:

• Enhanced API coverage with detailed patterns for async operations, extension interactions, and WebView creation
• Added comprehensive Joyride Flares documentation for creating visual interfaces
• Improved namespace targeting guidelines and REPL usage patterns

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
instructions/joyride-user-project.instructions.md	Significantly expanded content with new APIs, patterns, and workflow guidance while fixing minor typos
README.prompts.md	Fixed spelling error in categorization
README.instructions.md	Updated title to match the instructions file

[Copilot]

The tool names have been changed from specific function names (joyride_basics_for_agents, joyride_assisting_users_guide) to generic descriptions. This could make it unclear which specific tools should be invoked. Consider keeping the actual tool/function names for clarity.

Suggested change

	- **Joyride agent guide** - Technical guide for LLM agents using Joyride evaluation capabilities
	- **Joyride user guide** - Complete user assistance guide with project structure, patterns, examples, and troubleshooting
	- `joyride_basics_for_agents` - Technical guide for LLM agents using Joyride evaluation capabilities
	- `joyride_assisting_users_guide` - Complete user assistance guide with project structure, patterns, examples, and troubleshooting

[PEZ]

This is on purpose, following the example of VS Code built-in tools like the Todo List. The specific function names are not visible to the user. They are purely agent facing