setup-mac-dev
macOS Development Setup
Perform setup directly with tools. Do not offload commands to the user unless a GUI prompt or privileged approval is required.
Use non-interactive flags wherever supported (-y, --yes, NONINTERACTIVE=1).
Before starting, tell the user:
"Setting up this Mac for development now. This may require command-line tools installation and admin approval prompts."
Then execute each step and report concise progress updates.
Step 1: Preflight checks
Run checks first and record results.
More from fwfutures/vibe-a-thon
humanizer
|
12setup-windows-dev
Sets up a new Windows machine for Node.js development by running all install commands directly. Use this skill whenever the user wants to configure a fresh Windows PC for web or Node development, install Node.js, fix PATH issues, set up npm/npx/git, scaffold a Vite or React project, or resolve common Windows dev environment problems like missing VC++ redistributables, PowerShell execution policy errors, or tools not found after install.
12gcp-deploy
Deploy containerised applications to Google Cloud Run from source using gcloud CLI. Use when the user asks to "deploy to GCP", "deploy to Cloud Run", "ship to Google Cloud", "gcloud run deploy", or needs to set up, redeploy, configure env vars/secrets, view logs, or troubleshoot a Cloud Run service.
11find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
10frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
10agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
10