astro-demo

Scaffold Astro demo components and MDX docs for grid features.

48|4|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/OysteinAmundsen/toolbox --skill astro-demo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: astro-demo
Source: https://github.com/OysteinAmundsen/toolbox/tree/main/.github/skills/astro-demo
Command: npx skills add https://github.com/OysteinAmundsen/toolbox --skill astro-demo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of ready-to-run Astro demo components and MDX documentation for grid features and plugins, streamlining development and documentation workflows.

Core Features & Use Cases

  • Demo scaffolding: Generate a ready-to-use .astro demo component for a grid feature or plugin.
  • MDX integration: Wire the demo into the Markdown/MDX documentation pages as described in the project conventions.
  • Templates & conventions: Provide and reuse standard templates for core feature demos or plugin demos, with consistent file paths and imports.
  • Wiring and maintenance: Ensure demos reference the grid package via @toolbox-web/grid and follow naming conventions for easy discovery and reuse.

Quick Start

Create your first Astro demo following the project's conventions and wire it into an accompanying MDX page.

Frequently Asked Questions about astro-demo

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

FAQPage Schema
How do I scaffold an Astro demo component for a grid plugin?

Scaffolding an Astro demo component involves generating a ready-to-use `.astro` file using standard template structures, specific import paths, and `@toolbox-web/grid` references to illustrate grid features or plugins.

How do I wire a demo component into an MDX documentation page?

Wiring a demo into MDX documentation involves importing the generated `.astro` component into the MDX page, wrapping it with ShowSource, and ensuring unique container IDs for proper rendering.

What is the best way to automate Astro documentation for grid features?

Automating Astro documentation for grid features is best handled by generating both the `.astro` demo component and the accompanying MDX documentation page simultaneously using standard templates and consistent file paths.

Do I need unique container IDs for Astro grid demos?

Yes, you need unique container IDs for Astro grid demos to prevent rendering conflicts when multiple demos are displayed on the same MDX page. The scaffolding process ensures these unique identifiers are properly implemented.

Does the demo scaffolding support optional DemoControls in Astro?

Yes, the demo scaffolding supports optional DemoControls in Astro. You can implement interactive controls within the generated `.astro` component template to allow users to manipulate and visualize grid plugin behavior dynamically.

Why use standard templates for core feature demos versus plugin demos?

Using separate standard templates for core feature demos versus plugin demos ensures consistent file locations, import paths, and structural conventions, which streamlines maintenance and makes grid documentation easier to discover and reuse.