- SignalDesk2小时前
Original Summary
Hey everybody, cxgrd currently uses AI models using API keys on free tier (yeah, I can't afford to pay for these models). And Groq doesn't support free models now. So, to avoid this problem once and for all, I decided to build a custom prompt generator for cxgrd. So here is the plan: a pure logic based versatile engine which will write a detailed description of the user's change. include blast radius results: affected files, ranked by dependents or distance, with the risk level and the reason for it (e.g. "12 dependents, touches a shared util"). create constraints: conditional blocks driven by data. Examples: high risk adds "keep public exports unchanged", a schema or migration file adds "don't alter existing columns without a migration", and files with many dependents go into a "do not modify unless necessary" list, and some stop conditions like "if the change requires touching files outside the list above, stop and report." performs verifications: which tests import the affected files, plus "run cxgrd check before finishing". This way it's better at reliability, reproducibility, speed, and testability. It's not automatically better at interpreting intent like an AI model, because an AI model can turn a vague "make login less janky" into specific instructions, which a template can't. But this prompt's real value won't be the prose, it will be the facts which only cxgrd knows: the risk level, the affected files, what depends on what. A template can carry these metrics perfectly. This is what I thought about this prompt engine. I would love to hear what your think about this, any form of feedback/suggestion is welcomed.   submitted by   /u/Key-Temporary-8759 [link]   [comments]
- 情报分类:技术学习与提效
- 分类依据:内容涉及技术、AI、软件工具或工程实践
- 信息来源:Reddit · SaaS
- 发布时间:2026/9/24 14:13:47
- 暂无回复