openclicky-build-preview

name	openclicky-build-preview
description	Build, modify, launch, preview, and iterate websites, web apps, dashboards, landing pages, HTML files, React/Next apps, and frontend UI. Use when the user wants a visible working thing, not only code.

OpenClicky compatibility guardrails

• Follow ../_shared/OpenClickySkillCompatibilityPolicy.md before acting.
• Verify required local commands, tools, keys, or bridge endpoints before promising execution.
• Treat sends, publishes, deploys, deletes, moves, merges, playlist/library changes, cloud writes, and app-control clicks as external writes unless this skill narrows them further.
• Stop and report the exact missing setup step for unavailable tools, auth, or macOS permissions; do not loop or silently switch to browser automation.

OpenClicky Build Preview

Build the thing, launch it when appropriate, show or report where it is, and iterate. This workflow absorbs frontend design, polish, and animation guidance without exposing those raw skills separately.

Use When

• The user asks to build a website, app, dashboard, landing page, HTML file, frontend component, or local preview.
• The user asks to open, preview, or revise a generated site/app.
• The request includes UI polish, animation, responsiveness, or visual design fixes.

Do Not Use When

• The task is primarily GitHub/PR/CI/repo workflow; use openclicky-repo-operator.
• The task is primarily localhost/toolchain failure; use openclicky-dev-setup-doctor.
• The task is only finding/opening an existing generated file; use openclicky-artifacts.

Primary Path

1. Detect the stack and package manager.
2. Make scoped code changes using existing project patterns.
3. Use high-quality frontend rules: strong hierarchy, responsive layout, accessible controls, tasteful motion, no generic filler.