You are in Technical Switch to Everyday AI
Skill Early access

/dxdev Skill.

Early Access

A parent skill you install once into your AI agent. After that, every DXDEV lesson renders as a visual PASS/FAIL report instead of a wall of text, and each result is saved as a persistent memory your agent can reference later.

⬛

Visual reports

Lessons that would normally return plain text instead render as a structured report: a PASS or FAIL verdict at the top, a breakdown by criteria, and a one-line fix for anything that did not pass.

⬛

Saved memory

After each lesson run, the verdict and key findings are written to a memory file your agent can consult on future tasks. You stop re-teaching the same patterns.

⬛

Sibling hub

The /dxdev skill is the entry point for the whole skill set. It wires in /brief, /lesson, and /read so they work together with shared context.

Note

You do not need this skill to use DXDEV lessons. Bare lessons work fine on their own. The /dxdev skill adds the visual layer and memory on top; it is an enhancement, not a requirement.

Related skills Install independently or together
/brief

Renders a status-page summary of current work as an HTML visual. Useful when a reply gets dense.

/lesson

Loads and runs a DXDEV lesson on demand. Returns structured criteria and a plain-text verdict.

/read

Token-efficient file reader. Greps first, reads targeted ranges second, and avoids pulling whole files into context.

Early access Limited spots

Get early access to the /dxdev skill.

The skill is in private early access while we refine the memory format and report renderer. Leave your email and we will send you the install instructions when your spot opens.

Claude, Cursor, a custom agent, etc. Helps us prioritize compatibility.

Early access spots are limited. We will follow up within a few days.

Ran a lesson and hit a wall?

You ran a lesson from the build log against your own code and it flagged a real issue, or your agent stalled on it. Send us exactly what it found. We reply with a focused, human take on that one problem, usually within a business day. No call required to start.

Language, framework, anything that matters. One line is fine.

The lesson's report, the verdict, the file:line evidence, or wherever it got stuck. The more concrete, the faster we can help.

One or two sentences. "Confirm this is a real bug", "tell me how to fix it safely", "is my whole pattern wrong", etc.

Is this a one-off, or a pattern across your codebase?

We read every request and reply within one business day with a focused take and what a fix would involve. If it turns out to be systemic, we will point you at the paid assessment instead, no pressure.