Intent engineering is how product teams turn judgment under evidence into specs precise enough for AI agents to execute — and verify. Here's the complete guide: what it is, why it matters, and how to practice it.
Product teams struggled to create intent. AI let them think they could skip it.
Teams struggled to produce intent. AI let them think they could skip it.
Intent-Based Architecture and Their Risks - Paradigm
Paradigm is a frontier technology investment firm that builds and invests in crypto, AI, robotics, and across new frontiers from the earliest stages.
Cognitive engineering
Cognitive engineering is an interdisciplinary field that applies principles from cognitive psychology, cognitive neuroscience, and human factors to design and develop engineering systems that effectively support or enhance human cognitive processes.[1][2] The field emerged in the 1980s when Donald Norman and others recognized the need to better understand how humans interact with complex technological systems.[3]
The intent pipeline: why most prompt guides miss how people actually use AI
Most prompt guides assume that people interact with AI by carefully authoring prompts. In practice, that is rarely how AI is used. Most…
Laws of Software Engineering
A collection of principles and patterns that shape software systems, teams, and decisions.
X : What are you interested in? Me : Wow, that varies constantly. Right now? There are a number of topics that I'm actively pursuing … a) When we talk about software engineering we typically think… | Simon Wardley
X : What are you interested in? Me : Wow, that varies constantly. Right now? There are a number of topics that I'm actively pursuing … a) When we talk about software engineering we typically think about the active part of creating code but software development is currently practised as a craft not an engineering discipline. The only engineering discipline in software engineering is testing. This creates a flaw in the comparison with using AI to code because development itself has never been optimised. If all we have to do is write code and we can automate that part then we can just replace those expensive typists with LLMs but development should be, and has the capability to become an engineering discipline. It's just not that for now. https://lnkd.in/eSRprhbf b) Most people talking digital sovereignty are doing so with good intentions but they literally have no idea what they are talking about. This is not because they are daft or foolish but because they cannot see the environment they are talking about. They are like generals talking about territorial sovereignty with no idea of what territory is or how you represent it. https://lnkd.in/eku2X_Ea c) Architectural decisions are made in code and not in the diagrams we create. Those architectural diagrams are more like prompts, wishes and beliefs of what a system should be but rarely reflect the actual system. This creates additional problems when the real architectural decisions are made by coders but coding itself is a craft not an engineering discipline. d) The current crop of LLMs / LMMs are driving us towards a new theocracy. We can counter this through diversity, critical thinking and open approaches but that does mean we have to get to the point of all symbolic instructions being open. That includes the training data. Copyright is a distraction from the real issue that we don't know what the systems are being trained on. Guardrails are a post event kludge. https://lnkd.in/exJVmNvD e) The medium we use in conversational programming environments such as cursor and lovable (or what we call vibe coding when not looking at the code or Software Engineering + AI when looking at the code) appear to be flawed. We are focused on text not images. The change of medium changes the conversation, the corollary is the conversation we have around the screen and the one we have around the whiteboard. Same problem, different medium, different discussion. https://lnkd.in/e_W6b6z3 f) "Value" in consulting land is mostly theatre rather than something meaningful. There are many forms of value but often we fail to identify this, quantify it or even measure it. https://lnkd.in/eeNbR_VY g) Rewilding Software Engineering. To change software development into an engineering practice, we need to introduce two wolves - one that software engineering is a decision making process and secondly that we need to build tools for problems we are facing - https://lnkd.in/epyUnqgh
Prompts I use - Agentic Engineering Patterns
Prompts I use - Agentic Engineering Patterns
Context Engineering Guide – Nextra
A Comprehensive Overview of Prompt Engineering
The New Science of Designing for Humans (SSIR)
The rise of behavioral science and impact evaluation has created a new way for engineering programs and human interactions. <meta property=
Effective context engineering for AI agents
Anthropic is an AI safety and research company that's working to build reliable, interpretable, and steerable AI systems.
Prompt Engineering Guide – Nextra
A Comprehensive Overview of Prompt Engineering
Agent experience: How to design products that agents can actually use — WorkOS
What engineers and founders need to know about designing APIs, tools, and interfaces for agent-driven workflows
Small models, big results: Achieving superior intent extraction through decomposition
We present a novel approach to tackle the task of understanding user intents from UI interaction trajectories using small models, which shows better results than significantly larger models.
feynon/intent-router-blueprint
A hybrid LLM intent routing system for secure agent orchestration.
Agentic manual testing - Agentic Engineering Patterns
Agentic manual testing - Agentic Engineering Patterns
I've been thinking a lot lately about how lexicon authors could help app developers understand intent. #atproto trezy.codes/blog/what-if-lexicons-knew-ho…
What If Lexicons Knew How to Look? - A Thought Experiment About Display Intents on the Atmosphere
trezy.codes
winter
has anyone thought about the multi repo feed yet or are we still in the era of "this is a <app.bsky.*> viewer" and "this is a <site.standard.*> viewer"
