Art & Design

Buffer API integration with managed authentication. Schedule and manage social media posts across multiple platforms. Use this skill when users want to schedule posts, manage channels, view organizations, or create content ideas in Buffer. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).

Claude Code plugin: plays a random droid-style chatter whenever Claude finishes a turn

Configure and deploy Astro sites with zephyr-astro-integration; use when adding withZephyr to astro.config integrations, deciding whether an Astro app's output can be published, wiring ZE_PUBLIC_* runtime values or deployment hooks, publishing a TAP package, or diagnosing why an Astro build did not publish.

Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support. Use when you need help with astro.

The Astro marketing site in site/ — URL/SEO contract (build.format preserve, .html canonicals, sitemap serialize), 5-locale i18n structure, GitHub Pages deploy workflow, and how to verify Astro major-version bumps. Use when touching anything under site/, reviewing dependabot bumps of astro or its integrations, debugging Pages deploys, or auditing SEO output (canonical, hreflang, sitemap).

EmDash is an open-source, full-stack TypeScript CMS built on Astro and Cloudflare, designed as a spiritual successor to WordPress. It features sandboxed plugins, structured content via Portable Text, a built-in MCP server for AI agents, and runs on Cloudflare Workers, D1, and R2 or any Node.js server with SQLite.

AmputatorBot migration plan v7 — locked decisions, milestones M1–M6, API contract, schema, port notes. Load when working on AmputatorBot architecture, the rewrite, or M6 deployment.

Use when building a new marketing or consultancy website that needs speed, bilingual content, SEO/AEO, a WordPress-backed blog, accessibility, WordPress-handled forms, and Calendly booking. Also use when the user mentions "new website", "site framework", "Astro starter", "headless WordPress", "bilingual site", or "llms.txt". Delivers a sprint-by-sprint build plan, not a code dump.

Load automatically when user asks to learn Astro framework development (e.g., "teach me how to build with Astro", "guide me through Astro", "I want to learn Astro", "quiero aprender Astro", "how do I get started with Astro"). Interactive guided tutorial where Claude acts as a co-pilot, guiding the user through building a real personal blog with Astro step-by-step. Trigger this skill whenever the user expresses interest in learning Astro from scratch, even if they don't say "tutorial" explicitly.

Astro framework patterns, islands architecture, content collections, rendering strategies, and deployment. Use for: astro, islands architecture, content collections, astro cloudflare, view transitions, partial hydration, astrojs, SSG, SSR, hybrid rendering, astro adapter.

Deploys the myanmardev.com project to Cloudflare Pages (frontend) and Cloudflare Workers (API proxy), running build, secrets check, and deploy in one flow.

AI coding agent skill for building with EmDash, the full-stack TypeScript CMS built on Astro and Cloudflare

GEO+SEO audit of asdlc.io — analyzes the codebase for Generative Engine Optimization across AI citability, technical infrastructure, content quality, schema markup, and knowledge base discoverability. Produces a composite GEO Score (0-100) with prioritized action plan.

Deploy, configure, troubleshoot, and verify the socai marketing/download website on Vercel. Use for socai.io deployments, Vercel project settings, domain/redirect checks, Git preview setup, /download and /github redirect validation, and deployment runbooks for the site/ Astro app.

Convert a plain static Astro template into a WordPress theme using the astro-wordpress adapter — install the adapter, configure astro.config.mjs, add the theme style.css, convert pages to .php.astro, optionally run WordPress itself via Docker Compose. Use when asked to "add astro-wordpress", "turn this Astro site into a WP theme", "integrate with WordPress", "wire up the WordPress adapter", or "run WordPress in Docker for this Astro project". For making content inside that theme editable from the WP backoffice via ACF, see the astro-wordpress-acf skill instead — this skill only covers the base adapter setup.

Compare a baseline URL against a dev or Storybook URL by taking Playwright screenshots at multiple breakpoints, running a pixel-level image diff, and reporting results to guide style and HTML corrections. Use when replicating an existing page or component, verifying visual accuracy, or checking responsive fidelity.

Google Stitch design-to-code workflow with design system management. Trigger when user mentions Stitch, design-to-code, UI design, visual comparison, design.md, design system, ShadCN conversion, redesign from screenshot, or wants to pull designs from Stitch into local code. Also trigger when user says '做个页面', 'build a landing page', '用 Stitch 设计', 'convert design', 'export from Stitch', '设计系统', or uploads wireframes/screenshots for UI generation.

Extracts all container image references (registry, image, tag) from the microsoft/aspire source code and produces a JSON data file for the aspire.dev Astro site. USE FOR: update container images JSON, refresh container image data, list all aspire container images, sync container image versions, generate container-images.json. DO NOT USE FOR: updating the container image versions in aspire source code itself (that's a product repo change), NuGet package data (use the integrations skill), or Dockerfile-based images for dev containers. INVOKES: bash, file read/write. FOR SINGLE OPERATIONS: Use grep/find to quickly check a single image tag.

Build, serve, and drive the built pardonned site to verify UI changes at the browser surface.

Astro Web Framework workflow skill. Use this skill when the user needs Build content-focused websites with Astro \u2014 zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

Upgrade a Lumos for Astro site to the latest version of the framework (not Lumos for Webflow). Use when the user asks to upgrade Lumos, update the framework, pull in the newest components, or migrate a site to current conventions. Moves the site onto the latest names, placements and props while keeping every customization the user made.

description: Configure Jetson AI Lab model pages — frontmatter for the Model Details sidebar (parameters, modalities, context length, license, precision pills), the Run on Jetson serve/call/one-shot UI, the three "block" levers (hide_run_button, matrix_modules_disabled, per-engine modules_supported), and the join to src/data/benchmarks.json (benchmark_key, benchmark_series, OOM vs DNR vs null). Use when adding or editing model pages, inference engines, serve/run commands, one-shot blocks, the details sidebar, benchmark wiring, or deciding whether to mark a Jetson module as OOM, blocked, or simply untested.

>- Connects a coding agent to Google Stitch through the stitch-mcp CLI and MCP proxy, so the agent can read a screen's HTML and screenshot and rebuild it in the project's own framework. Use when a user says "implement this Stitch screen", "hook Stitch up to Claude Code / Cursor / Codex", "add the Stitch MCP server", "turn my Stitch project into a site", "preview my Stitch screens locally", or when Stitch tools fail with authentication or permission errors. Covers choosing API key or OAuth, proxy or direct HTTP, per-client configuration, the non-interactive flags an agent can run, the tool inputs and outputs, and how to diagnose a broken setup.

Sets up GitHub Actions CI/CD workflows for Astro sites — `astro check` (TypeScript + content schema), ESLint, Prettier, build verification, Vitest testing, Lighthouse CI, link checking, npm audit, and automated deployment to GitHub Pages, Cloudflare Pages, Netlify, or Vercel. ALWAYS use this skill when a user wants to create, add, set up, or configure GitHub Actions, CI/CD, automated checks, or deployment workflows for an Astro site — even if they don't use the exact phrase "GitHub Actions". This includes any request to: add automated type-checking or linting to an Astro repo; set up `astro check` in CI; add Lighthouse or accessibility checks to PRs; configure Vitest in CI for an Astro project; auto-deploy an Astro site to GitHub Pages, Cloudflare Pages, Netlify, or Vercel from GitHub; add link checking or broken-link detection; add security scanning to an Astro pipeline; or generally "add CI", "add automated checks", "set up workflows", or "automate" anything related to an Astro site's GitHub repository. ...