website-development_skill

This skill helps you implement website development patterns using Astro 5, Tailwind, and Starlight to build responsive, accessible UI.
  • Go

10

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill lookatitude/beluga-ai --skill website-development

  • SKILL.md4.4 KB

Overview

This skill provides patterns and actionable guidance for building, styling, and adjusting website components, layouts, and interactive elements for the Beluga AI v2 documentation site. It focuses on Astro + Starlight, Tailwind-driven styling, component structure, and build configuration to deliver accessible, performant docs UI. Use this skill for implementation work only — not for writing documentation content.

How this skill works

I inspect the site structure, component conventions, and config files to recommend or produce Astro components (.astro) and client-side React only when interactivity is required. I provide Tailwind-based styling, custom plugin placement, Starlight overrides, responsive and accessible markup, and build adjustments (Vite/Tailwind/TypeScript) to meet performance and theming goals. I also outline where to place config (sidebar, theme, locales) and how to wire overrides into astro.config.mjs.

When to use it

  • Creating or modifying page layouts, headers, footers, or sidebars
  • Building interactive UI patterns (tabs, accordions, search, theme switcher) that need client behavior
  • Customizing or overriding Starlight components with minimal replacement
  • Implementing Tailwind utilities, custom plugins, or global styles
  • Optimizing images, view transitions, or build performance (Vite/Sharp)

Best practices

  • Use Astro components by default; only use React with client:* directives for interactive widgets
  • Keep overrides minimal — extend Starlight components instead of full replacements
  • Import using path aliases (@/ or ~/) to keep imports consistent across the codebase
  • Organize styles in src/styles/ and use Tailwind utilities; put project utilities in src/tailwind-plugin/
  • Respect dark/light variants and accessibility (keyboard focus, ARIA, semantic HTML)
  • Avoid client-side JS when server-rendered Astro is sufficient to reduce bundle size

Example use cases

  • Add a responsive hero section using an Astro component and Tailwind utilities
  • Create a theme switcher that persists user preference using a small client-side React component
  • Override Starlight’s NavLink to inject custom analytics attributes while preserving original behavior
  • Add a custom Tailwind plugin for the docs grid and include it in the Tailwind config
  • Optimize docs images with Sharp and configure view transitions via astro-vtbot

FAQ

No. This skill only handles site components, styling, and build work. Delegate Markdown content to the documentation writer role.

When should I choose React over Astro?

Choose React only for functionality that requires client:* lifecycle or complex interactivity. For static or server-rendered UI prefer Astro to keep bundles small.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
website-development skill by lookatitude/beluga-ai | VeilStrat