All authors

Claude Skills by alanvaa06
github.com/alanvaa066 skills0 installs0 views
- AssetsGenerate, refine and integrate all landing media via Higgsfield MCP from DESIGN.md-derived briefs — hero images, textures, background loops, product shots. Use when craft invokes the asset phase, standalone to (re)generate one slot ("/award-craft:assets hero"), or to refine a slot from feedback ("/award-craft:assets hero 'light too hard, more air on the left'"). Requires DESIGN.md with an asset-slots section.Votes: 0GitHub stars: 2
- Build RecipesBuild the landing from the approved DESIGN.md and design plan on the fixed stack (Next.js + Tailwind + GSAP + Lenis, optional R3F). Use when craft/elevate invoke it after the design-plan gate, or standalone to rebuild a section. Never use before a design plan is approved.Votes: 0GitHub stars: 2
- CraftBuild a new Awwwards-level landing page end-to-end — intake (script + brand source + interview), approved design plan gate, recipe build, Higgsfield assets, mandatory verify. Use when the user wants a new landing/marketing page built ("/award-craft:craft <brief> [@docs] [--brand <path>]"). Not for elevating an existing page (use elevate).Votes: 0GitHub stars: 2
- DirectionProduce the Pass-1 design plan for an Awwwards-level landing — tokens, motion identity, art direction, ASCII wireframe per script section, ONE signature moment, and explicit drift vs brand source. Use when craft/elevate invoke it, or standalone to (re)generate a design plan before any code. Requires PRODUCT.md (and optionally an imported brand DESIGN.md) to exist.Votes: 0GitHub stars: 2
- ElevateElevate an existing landing page toward Awwwards level — read the project, gap-analysis against the anatomy checklist, prioritized plan gate, apply approved items, mandatory verify. Use when the user wants an existing page improved ("/award-craft:elevate [path]"). Not for building from scratch (use craft).Votes: 0GitHub stars: 2
- VerifyMandatory visual verification loop for award-craft landings — screenshot desktop+mobile, critique against the quantitative checklist, fix, re-shoot until verified. Use when craft/elevate reach the verify phase, or standalone after manual edits ("/award-craft:verify"). An edit that ran without errors is NOT done — only verified_ screenshots are done.Votes: 0GitHub stars: 2