Tools· Design & Creative

    Fulldev UI

    Open source library of Astro-native UI components and ready-made marketing sections in the Shadcn registry format, with props-based customization instead of a React runtime or plain HTML copy-paste.

    designingexecutableOpen Source

    Description

    Strengths

    Astro-native without a React requirement
    Components and blocks are real `.astro` files with props and slots, not React components and not plain HTML markup to retype.
    Shadcn-compatible install path
    Individual building blocks can be pulled into the project through the familiar Shadcn CLI and the `@fulldev` registry namespace.
    Broad set of ready-made sections
    Around 84 blocks for heroes, features, pricing, FAQs, calls to action, articles, reviews, headers, and footers cover common marketing and content pages.
    Token-based theming
    Color, radius, spacing, and visual tone can be adjusted centrally through CSS variables instead of restyling every component individually.
    Open source under the MIT license
    The source code installs as Astro and Tailwind files directly in the project, inspectable, versionable, and customizable without an attribution requirement.

    Assessment

    AI features

    • Markdown documentation for agents Every docs page has a Markdown version, reachable by appending `.md` to the URL, as a direct entry point for AI agents without going through rendered HTML.
    • Blocks as a composition template AI agents can use existing blocks directly, or as a reference for layout, props, spacing, and component composition when building their own sections.
    • Source code meant to be safely adapted Complete sections with documented props, where source and rendered preview sit side by side, are meant, according to the provider, to be safely adaptable for developers and agents alike.

    Suitable for

    • Astro projects that need ready-made marketing sections as real parametrized components instead of plain HTML markup
    • Teams that want AI agents to assemble layouts and components from real, inspectable Astro source code
    • Content-driven websites such as docs, editorial pages, or marketing sites that need typography, price, rating, and video components alongside complete sections
    • Less suitable for Less suitable for React-based projects, where a library such as shadcn/ui fits more directly into the existing component model, and for projects that expect a highly distinctive design level from the start without reworking the tokens

    Limitations and notes

    • No React The library is deliberately built Astro-native, it is not the right choice for projects with a React requirement, though according to the provider it can be used alongside shadcn/ui when a project additionally needs interactive React components.
    • Design level needs further work Out of the box, visual quality sits in the solid, content-driven range, an eye-catching, distinctive look requires remapping the color and spacing tokens to your own brand.
    • License file uses British spelling The license file in the repository is named `LICENCE` rather than `LICENSE`, anyone searching for it automatically should account for the different spelling.
    • Registry install requires project setup The path through the Shadcn CLI needs an existing `components.json` in the project, without that configuration only manually copying the Astro files from the source remains.

    Quick start

    1. Open the documentation at ui.full.dev and pick the components or blocks you need.
    2. Set up a `components.json` for the Shadcn CLI in your own Astro project, if it does not exist yet.
    3. Install individual building blocks through `npx shadcn@latest add @fulldev/<block-name>`.
    4. Open the installed Astro and Tailwind files and adapt props and slots to your own content.
    5. Switch the color, radius, and spacing tokens over to your own brand through CSS variables.

    Tips

    • For AI-assisted layout work, link directly to the Markdown version of the documentation, that saves agents the detour through rendered HTML.
    • When theming, map the CSS variables to your own project tokens first, instead of recoloring individual Tailwind classes in the components by hand.
    • If the registry configuration is missing, copy the affected `.astro` files directly from the repository and bring the imports and props along manually.
    • Treat ready-made blocks more as a starting point for your own section structure than as a finished design, for a distinctive result it is worth adapting typography and imagery on top of the tokens.

    Access

    Last reviewed: · Pricing, plans and features are a snapshot in time. Check the provider's own page before deciding.

    In the workshop this becomes your method.

    Whoever sees this process run once wants the agent behind it next. We build that in the workshop From Process to Agent.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call