Skills and API, no frontend

Frontend is never right, it will always look and behave different from what you expect.
This is already true for one person, but 2+ people using the same interface will satisfy all needs.
Text is much more forgiving here, it's asking for a result rather than a representation.
Text is declarative like SQL, you tell what you want.

So text as interface is flexible as it will use the words to explain that were used to ask. Problem then is how to make result "repeatable" and "reliable".

My idea right now is to skip frontends as often as possible and not hardwire data and presentation but to give the leanest tools possible.
So it could mean for a personal CRM to have a database, APIs, a Bearer token in your ENV and a skill that your coding agent can use to interact with your CRM.