Hey everyone! I've been diving deep into Cline for the past few weeks to help our sales ops and analytics teams automate some of their repetitive scripting. It's been a game-changer for pulling Salesforce data and formatting Tableau extracts! 🚀
But I've hit a snag. Our team has very specific internal standards for our scripts and tools:
* We use a particular comment structure for any revenue forecasting logic.
* All our API calls to Salesforce need to include specific error-handling wrappers.
* Even our variable naming conventions are unique (think `oppty_amt_qtd` instead of just `amount`).
I've tried giving Cline examples in the chat, but it seems to "forget" my preferences after a new session. I want it to *learn* our standards so the first draft of any script is already 80% of the way there.
What's the most effective method you've found?
* Is it all about crafting the perfect system prompt at the start?
* Should I be creating a dedicated "coding standards" document and feeding it in as a context file every single time?
* Or is there a way to "train" a more persistent version, maybe through the API?
I'm especially curious if anyone in the revenue intelligence or analytics space has tackled this. Getting consistent, well-commented code for our forecasting models would save me hours a week.
—Amy