That part sounds like “libraries”, commonly handled by GitHub repos, so copilot and others working nicely with GitHub would be a starting point (at least for me).
The way I write (as of end 2024) the code:
Now, I’m about to dump Tabnine (less and less compatible with copilot on the same IDE, too invasive with updates, and copilot now in 2025 got most of the features I used Tabnine for).
Also, see myself more and more use
- the linked process to create one or two classes (well commented),
- then use them as examples in ChatGPT UI (4.1/3o) and simply explain what is the next class to do, features, pitfalls, focus points, etc.
- Then just hit the enter and get almost production ready output instantly.
- Then polish the results and feed them back to chat for reference (improve next iteration quality)
- Then keep asking for next classes (similar types/patterns)
Weirdly, I don’t use enough codex/cursor and other ai IDEs , I’m a PHP guy mostly, and possibly with too weird/uncommon logic, so those tools generally produce crap for me and waste me more time then they save. OR it’s the way they break down tasks under the hood that is not compatible with the way I code?.. Who knows.
Hope that helps .