Why Droids?

Two things sold me on Droids over Claude Code and Codex. Better orchestration out of the box and model agnostic. They're already optimized for developers and come built-in with capabilities such as:

This is the normal LLM coding workflow.

Skills

Skills are markdown files that tell the Droid how to do something. Think of it as predefined tool calls. You don't have to manually call them. Droid looks at your task and pulls in whatever skills seem relevant based on the name and description.

The skills get reused across different tasks. Build a frontend feature? The Droid pulls in Design Engineer for component structure, Animation for interactions, and QA to verify everything works. Fix a layout bug? It grabs Design Engineer and QA, skipping Animation since it's not needed.

My Workflow

With skills combined, each part of your workflow gets its own specialist. This is exactly how my design engineering agent currently works.

Writing Better Skills

The key is reducing ambiguity. Make everything as deterministic as possible. I think of LLMs as repetition machines. They're really good at copying patterns. So give them patterns or hardcoded values to copy.

Yes! Hardcode the actual values.

Don't tell the Droid "follow the design system." Tell it exactly what the design system is. Put the actual hex codes, the actual spacing values, the actual class names right in the skill file.

My globals.css skill doesn't say "use consistent colors." It says something like:

Background: #0a0a0a
Text primary: #ffffff at 90% opacity
Text secondary: #ffffff at 60% opacity  
Borders: #ffffff at 20% opacity

My component skill doesn't say "match existing patterns." It lists the actual patterns, something like:

Cards: border border-white/20 p-4 rounded-sm
Buttons: px-4 py-2 rounded-md font-medium
Labels: text-xs uppercase tracking-wide text-white/40

When the Droid builds something, it's not guessing what "looks right." It's copying values I've already decided on. No interpretation. No hallucination. Just the exact styles I want, every time.

I believe this is how you should build a custom Agentic system around your daily workflow. It won't matter how good or bad the next model is. Your system keeps working the way you want and helps ship code much faster.

Magic Zone

I've also noticed that somewhere between Deterministic and Non-deterministic workflows, there are moments where the model comes up with insane output that I could have never expected. I call this the Magic Zone.

Examples

Here's what this workflow looks like in practice.

I first built this component. Then I copied all the CSS values and created a skill.md with those values.

Later I tried to trigger that skill and asked it to generate a scatterplot and later a bar chart. It built these two in a single prompt:

Sure, they're not perfect and need further work. The text labels are cut off, there's no tooltip. But the creativity of adding the dashed grid lines and maintaining the same color scale is so much better than if you had just prompted "build me a scatterplot" or "build me a bar chart."

This playlist card was another spinoff from the same skill. It took around 12-15 prompts to get it to this state:

December

2025

untitledBlaxian