AI-generated web interfaces have so far often looked the same: centred heading, background gradient, three tiles, one button. Anyone who creates prototypes with prompts – i.e. natural-language instructions – knows this uniform look. The term vibecoding has become established in the scene for this: software comes into being by describing to a language model what you want instead of writing the code yourself.
A new feature in Claude's Artifacts addresses exactly this point. Artifacts are interactive results that the model outputs directly in the chat and that can be viewed and operated immediately – for example a small web application or a landing page. According to the report, Claude can now embed texts, buttons and other building blocks of a page in elaborate graphics and 3D effects. The resulting look is compared with an aesthetic reminiscent of Flash and described as bizarre – an indication that the results are striking but not automatically tasteful.
Why this is relevant for project teams
The real progress lies less in the 3D effects than in the breadth. When a model no longer merely reproduces a single standard template but offers stylistically different directions, it becomes more interesting as a tool for early project phases. Concept sketches, variant comparisons, mood boards for a relaunch: these require fast, visible results, not finished production quality.
This is particularly helpful in the coordination process with specialist departments. A clickable draft answers questions that a text concept leaves open. Whether an idea holds up can be clarified more quickly when everyone involved has the same thing in front of them – and when several drafts are placed side by side instead of just one.
Where the limits begin
Elaborate visuals are not the same as good design. Three topics remain with humans:
- Brand management: A model only knows your colour world, typography, tone and imagery to the extent that you provide them. Effects that are generically impressive can run counter to a brand that relies on calm and clarity.
- Accessibility: Contrasts, focus states for keyboard operation, meaningful document structure, understandable labels – these cannot be derived from the visuals but must be tested. Strong visual effects tend to increase the risk that readability and operability suffer.
- Technical substance: Load times, behaviour on weaker devices, display on small screens, maintainability of the generated code. A prototype may be generous here, a production system may not.
There is also the editorial level. A landing page lives from content that fits a specific offering and a specific target group. Placeholder texts from the model look plausible in the draft and rarely carry in practice.
A realistic working mode
A clear separation between the exploration phase and implementation makes sense. In exploration, the rule is: many variants, fast iterations, low hurdles. This is where tools like Artifacts play to their strengths, because the result is immediately visible and discardable.
In implementation, the usual rules apply: design system instead of individual draft, components instead of copies, testing against your own quality criteria. Anyone transferring a web interface into a content management system such as TYPO3 needs reusable building blocks that editors can fill themselves anyway – and not a one-off generated page that breaks with every content change.
A few simple guardrails have proven practical:
- Write brand specifications – colours, fonts, tone – concretely into the prompt instead of hoping for the model's taste.
- Treat generated drafts as a basis for discussion, not as an approved state.
- Before implementation, define which parts of the draft will actually be turned into components.
- Test accessibility and performance separately, regardless of how the draft was created.
- Clarify rights to content and graphics before anything is published.
The aesthetics question
That an aesthetic reminiscent of Flash of all things should appear as a counter-design to the generic AI look has a certain irony. Flash interfaces stood for design freedom – and at the same time for problems with accessibility, findability and device support that ultimately contributed to their disappearance. Anyone relying on opulent effects today should answer the same questions: Does the page work without the effects? Does a search engine understand the content? Can someone navigate it with a keyboard or screen reader?
Diversity in design is a gain. But it does not replace a decision about what suits the company and what actually helps the users.
Assessment
For web and software projects, this above all shifts the effort in the early phase: drafts are created faster and look more distinctive, which shortens coordination and makes wrong decisions visible earlier. The effort does not disappear, however; it moves downstream – into brand management, accessibility, performance and maintainable components. Anyone who deliberately limits AI tools to exploration and continues to safeguard production quality through craftsmanship gains speed without giving up control over the result.