In my pursuit of trying to get the most out of my AI Agents I have spent a lot of time exploring how one can deliver requirements in such a way that they can be understood by Humans and provide the details that will make the Agent implementation successful. Knowing that there is typically a pause between when the requirements is established / captured and when the Agent starts working on it, I wanted to make sure that much of the context and details the Agent had during the planning session was captured in a way that it can be use later during implementation.
Stride Active Guidence
Stride Now Supports Four AI Assistants with Always-Active Guidance
What a day. Earlier today I rolled out Claude Code Skills for Stride. A couple of hours later I’m excited to announce that Stride now supports four popular AI coding assistants beyond Claude Code, with always-active instruction files that help developers avoid common mistakes and follow best practices when working with the Stride API.
The Challenge: Supporting Multiple AI Assistants
I know that not all developers use Claude Code. Many companies are invested in tools like Copilot, Windsurf, etc. Developers in these companies should not feel left out when it comes to Stride. Because of that need, I have just added enhanced instructions for GitHub Copilot, Cursor, Windsurf Cascade, and Continue.dev. These assistants are excellent tools, but they needed help understanding Stride’s workflow requirements, especially around:
