> Ask it if a microservices architecture makes sense for your three-person team and it’ll explain why microservices are an excellent choice
If you ask it to be fair and non-biased and provide pros and cons and give possible alternatives - it will. The catch - you might understand the explanation if you don't know the domain good enough.
If you think that you can just silently modify the model without any announcements and only react when it doesn't go through unnoticed, then be 100% sure that your clients will check every possible alternative and will leave you as soon as they find anything similar in quality (and no, not a degraded one).
> people didn't understand to use /effort to increase intelligence, and often stuck with the default -- we should have anticipated this
UI is UI. It is naive to expect that you build some UI but users will "just magically" find out that they should use it as a terminal in the first place.
> Skills are great for pure knowledge and teaching an LLM how to use an existing tool. But for giving an LLM actual access to services, the Model Context Protocol (MCP) is the far superior
That's it. For some things you need MCP, for some things you need SKILLs - these things coexist.
By combining my technical background with the strategic use of AI agents, I adapt quickly to any tech stack. I review every line of generated code to ensure strict alignment with current best practices.
reply