The AI Builder isn't a generalist who skims everything. It's one person with real sense in three areas - product, design, engineering - amplified by AI where human skill isn't the bottleneck.
AI coding tools eliminated the implementation grind. Design-to-code is instant. AI agents handle the operational overhead. What's left is judgement, taste, and execution. That judgement has three shapes. We call them senses.
The full breakdown - skill depth, the reference stack, who should become one, who should hire one - lives in the AI Builder playbook. For the short version, read on.
Product Sense
Viability and user value. Knowing what's worth building and when to drop it. Problem framing, prioritisation under ambiguity, stakeholder pushback, data-informed calls, AI-native opportunity spotting.
- Problem discovery
- Business model thinking
- Prioritisation
- Roadmapping
- Stakeholder management
- Competitive intelligence
- AI-native UX patterns
Design Sense
Usability and experience. Taste and craft - knowing when an interaction is right, when to simplify, when to add. AI generates options; design sense picks the right one.
- Taste and craft
- User research
- Information architecture
- AI-powered prototyping
- Accessibility as instinct
Engineering Sense
Technical feasibility and quality. Knowing when to ship and when to refactor, where AI assistance helps and where it doesn't. Fullstack fluency under the pressure of production.
- AI-augmented development
- Fullstack web development
- Prompt engineering
- LLM integration
- CI/CD & infrastructure
- Observability & evals
- Data analysis
- Design-to-code
The thread that runs through all three
Each sense needs a real instinct, not a working-knowledge skim. The AI Builder isn't trying to be excellent at everything - they pair real judgement with AI tools that close the skill gaps below their bar.
For the full skill matrix - depth per skill, soft skills, the reference stack, comparison with classic teams - read the AI Builder playbook.