dev_agent

Translate brand strategy and design tokens into Astro + Tailwind UI implementations.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/David-Melo/astro-base --skill dev-agent-david-melo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev_agent
Source: https://github.com/David-Melo/astro-base/tree/main/.claude/skills/dev_agent
Command: npx skills add https://github.com/David-Melo/astro-base --skill dev-agent-david-melo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Developer Agent helps teams convert strategic briefs, component standards, and design tokens into production-ready Astro + Tailwind UI code, reducing lead time and ensuring consistency across pages and features.

Core Features & Use Cases

  • Strategic-to-UI Translation: Converts brand strategy, typography, color rules, and the approved component registry into implementation-ready UI blocks.
  • MDX-Driven Content Wiring: Coordinates loading content from src/content and mapping it to components in src/components via Astro pages and Layouts.
  • Automation & Guardrails: Enforces accessibility, performance, and semantic HTML while aligning with the strategy blueprint.

Quick Start

Describe the page to build and this agent will generate production-ready Astro/Tailwind code wired to the project's content and components.

Frequently Asked Questions about dev_agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate brand strategy and design tokens into Astro and Tailwind UI components?

To translate brand strategy into Astro and Tailwind UI, you provide a strategic brief and design tokens to generate production-ready components. This process maps typography and color rules directly into implementation-ready UI blocks.

Can I wire MDX content from src/content to Astro components automatically?

Yes, you can wire MDX content by loading files from src/content and mapping them to components in src/components via Astro pages and Layouts. This MDX-driven content wiring ensures structured content matches the approved component registry.

What's the best way to build accessible marketing site pages with Tailwind and Astro?

The best way to build accessible marketing pages with Tailwind and Astro is to enforce semantic HTML, accessibility guardrails, and typography tokens during component generation. This ensures hero sections, CTAs, and content blocks meet performance standards.

Does this Astro UI generation approach work with a specific component registry?

Yes, this Astro UI generation approach works with an approved component registry, using it as the source of truth. It aligns generated layouts and UI blocks with the established component standards and brand strategy blueprint.

Do I need Yarn-based tooling to generate production-ready Astro frontend code?

Yes, you need Yarn-based tooling to generate production-ready Astro frontend code in this workflow. The automation enforces Yarn-based tooling while loading content and applying the approved component registry to build the UI.

Why use Preline with Astro and Tailwind for component-driven layouts?

Use Preline with Astro and Tailwind to accelerate building component-driven layouts by leveraging pre-styled UI blocks. This aligns with the component registry to ensure consistency across marketing-site pages and content blocks.