ai tips
Cost saving
Using ai models with APIs can be expensive and cost you > 300€/month, if you are not careful.
- Switch models while coding.
- Use smaller prompts.
- Cancel subscriptions.
- Consolidate to on LLM router service.
Prompts
- To have faster responses and lower token usage, add urgency in your prompt for models having the “thinking” feature.
- ⚠️ Might not work on all models, e.g. Groq.
Your response is time critical, get to an answer as quickly as possible. Think as little as possible. If you keep getting the same answer while thinking, stop thinking and provide the final answer. {your_prompt}
- Ask the LLM if it has questions to better clarify the project.
- Use some framework to build the agent , e.g. Pocket Flow.
Convention
Some example:
# Coding pattern preference
- Always prefer simple solution.
- Avoid duplication of code whenever possible, which means checking for other areas of the codebase that might already have similar code and functionality.
- Write code that takes into account the different environments: dev, test and prod.
- You are careful to only make changes that are requested or you are confident you understood well to the topics related to the change being requested.
- When fixing an issue or bug, do not introduce a new pattern or technology without first exhausting all options for the existing implementation. And if you finally do this, make sure to remove the old implementation afterwards so we don't have duplicate logic.
- Keep the codebase very clean and organized.
- Avoid writing scripts in files if possible, especially if the script is likely only to be run once.
- Avoid having files over 200-300 lines of code. Refactor at that point.
- Mocking data is only needed for tests, never mock data for dev or prod.
- Never add stubbing or fake data patterns to code that affects the dev or prod environments.
- Never overwrite my .env file without first asking and confirming.
# Coding workflow preferences
- Focus on the areas of code relevant to the task.
- Do not touch code that is unreleated to the task
- Write through tests for all major functionality.
- Avoid making major changes to the patterns and architecture of how a feature works, after it has shown to work well, unless explicitly instructed.
- Always think about what other methods and areas of code might be affected by code changes.