Daniela Buitrago
ES
← Selected work

Design Systems · 2026

Design skill.

Design for everyone

A design skill for Claude that helps PMs, developers and anyone at the company create with good design decisions and produce real deliverables, following the ADS and UX Writing rules.

Role
Product Designer · Skill co-creator
Client
Healthatom · Internal use
Year
2026
Tools
Claude Code, Atom Design System, Figma, GitHub
  • 01For PMs, devs and Design, each in their own tone
  • 02Substance before form
  • 03Real usage data before designing

The idea

At Healthatom, not everything that gets designed goes through Design: PMs, developers and others also create screens and flows. I wanted any of them to be able to create with good design decisions, without needing a designer on every screen, and to end up with a real deliverable.

That’s how the design skill was born, co-created with Andrea Iruretagoyena, Head of Product: a Claude skill that knows the Atom Design System rules and the UX Writing guide, and walks people from understanding the problem to building the screen. I’ve been working on AI features for two years, and this project is where AI stopped taking away my creative space and started multiplying it.

How it works

The design skill flow

The skill itself works in Spanish.

  • It adapts to whoever uses it. It detects from their job title whether the person is in Design, Product or Engineering, and changes its tone and questions. Design rules decide the form; PMs and developers decide the substance.
  • It looks at data before designing. It connects real screen usage, customer feedback and user profiles. If a source is missing, anything that depends on it is flagged as an assumption to confirm.
  • It asks one thing at a time, with options and a mockup, recommending one.
  • It builds the deliverable: the screen on a branch and a test environment, with a mobile review.
  • It has safety rules: nothing happens without an OK, no personal data is used, work stays in test environments, and business logic isn’t touched without asking.

Alongside the skill, I built an audit that compares Atomlink 3.0’s code against ADS and reports, app by app and screen by screen, what doesn’t follow the system.

Key decisions

Substance before form

I ruled out starting from components or the screen.

Why the problem, the people and the flow define everything else. Components come after, from the ADS rules.

One question at a time, with options

I ruled out bundling every question into a single screen, like other skills do.

Why each answer changes the next question, which makes it possible to show options with their mockup. For someone outside Design, deciding one thing at a time is much easier.

If a rule is missing, don’t make it up

I ruled out letting the skill improvise when ADS doesn’t have the answer.

Why the question goes to the ADS team to decide. Meanwhile the design keeps moving, but the decision is flagged as provisional, so the system stays one system.

Where it is today

The skill is on version 0.8, and Andrea and I maintain it together. Its v2 is in testing and, once approved, it moves into the Atomlink repository so it reaches the whole team along with the code.

Next project Casa Healthatom.