This is fair feedback—we're so early in building an ecosystem here that the prompts we've shared as starting points are relatively general. But already we've se

This is fair feedback—we're so early in building an ecosystem here that the prompts we've shared as starting points are relatively general. But already we've seen people start to build much more carefully-crafted and specific assistants. These are some examples that we've used internally and found to be super useful: - https://hub.continue.dev/continuedev/playwright-e2e-test https://hub.continue.dev/continuedev/playwright-e2e-test - https://hub.continue.dev/continuedev/vscode https://hub.continue.dev/continuedev/vscode - https://hub.continue.dev/continuedev/service-test-prompt https://hub.continue.dev/continuedev/service-test-prompt Importantly, you don't have to pay to use custom assistants! You can think of hub.continue.dev like the NPM registry: it's just a medium for people to create, share, and pull the assistants they want to use. It's always possible to bring your own API key and we provide a Models Add-On mostly for convenience of not needing to keep track of API keys Value prop of MCP is definitely early, but I would recommend giving Agent mode (https://docs.continue.dev/agent/how-to-use-it https://docs.continue.dev/agent/how-to-use-it) a try if you haven't had the chance—there's something compelling about having the model take the obvious actions for you (though you can of course require approval first!)