Direct answer
Product design decides how software behaves before it decides how it looks: what a person is trying to do, the steps between them and doing it, and what the interface has to make obvious. UI and UX design, wireframing and usability testing are the practices that answer those questions.
UI and UX design
User interface design covers what a person sees and operates. User experience design covers the sequence they move through and whether it matches the task they actually have. The two are usually done together and are not interchangeable terms.
What the work covers
Design at CodeDTX is attached to software being built rather than delivered as artefacts on their own.
Interaction and flow
The path through a task, the states along it, and what happens when something goes wrong partway.
Interface design
Layout, hierarchy, type and colour, applied consistently enough that people can learn the product once.
Wireframing and prototyping
Enough of an interface to test a decision before it is built.
Usability testing
Watching people use it and changing the design in response, rather than defending it.
Design systems
Shared components and tokens, so the product stays coherent as more people work on it.
Accessibility
Contrast, focus order, keyboard operation and screen-reader structure treated as part of the design.
Designing for systems that act
Agentic software creates interface problems ordinary applications do not have. A person has to see what an agent proposes, understand the evidence behind it, approve or reject it with a reason, and later reconstruct why something happened. Those screens are design work, and they decide whether the governance is real or theatre.
Frequently asked
This is the practice the AI work is built on
We still take this work on. If the system you are describing should also be making decisions on its own, start with the AI side.