Builds practical marketing websites using reusable sections, design data, site cloning, customisation, and image-generation workflows. This is the closest public equivalent to a full Website OS build skill.

↳ brief → structure → visual direction → sections → publish-ready site.

Turns design intent into accessible, responsive, maintainable front-end implementation. Useful once a website concept or layout exists and needs to become real React/Next.js/Tailwind code.

↳ implementation and final engineering polish.

This is the app that can consume this catalogue. The source repository is private, so this public catalogue anchor is the safe GitHub link to expose inside the app unless the app source is intentionally made public.

↳ customer-facing interface and skills marketplace/library.

Extracts website design systems with tokens, responsive behaviour, accessibility findings, CSS health, DTCG tokens, Tailwind output, Figma variables, shadcn/ui patterns, and platform emitters.

↳ reference collection, reverse engineering, and source material for DESIGN.md.

Open Design is a local-first design workbench with a large skills/design-system catalogue. The frontend-design skill is useful for turning a vague design goal into specific visual direction.

↳ early design direction and design generation.

Provides practical website design rules and guidelines. Useful as a critique layer before shipping any generated page.

↳ quality control for web design.

A collection of DESIGN.md files inspired by well-known brand systems. Good for quickly choosing a design direction before building.

↳ design reference selection and prompt context.

A broad design-intelligence skill for professional UI/UX. Useful when the site needs stronger layout, hierarchy, colours, type, landing-page conventions, and interaction design.

↳ design critique and high-level UI/UX improvement.

High-agency front-end guidance that helps agents avoid bland UI and make stronger aesthetic decisions.

↳ taste pass after the first design draft.

A focused skill for making interfaces feel premium rather than merely functional.

↳ late-stage UX and visual polish.

A set of critique and improvement skills for layout, type, animation, colour, responsiveness, and visual anti-patterns. Use it like a senior design-review pass.

↳ design QA and refinement before handoff.

Useful for APAC/Chinese-market design inspiration, high-fidelity prototypes, animated web concepts, and polished HTML deliverables.

↳ high-fidelity design generation and visual exploration.

Adds WebGPU, Three.js, shader, particle and post-processing capability for interactive websites. Optional, but useful for premium hero sections and immersive experiences.

↳ advanced visual effects.

Creates hand-drawn architecture diagrams, wireframes, user flows and explanatory diagrams. Useful before building a site or funnel because it makes the structure visible.

↳ planning, diagrams and wireframes.

Covers funnel types such as SaaS, webinar, VSL, ecommerce and high-ticket funnels. This should sit directly beside Website OS because many websites are really funnels.

↳ funnel strategy and conversion architecture.

Use when the design is fine but the page does not clearly communicate value. Especially useful for hero sections, service pages, landing pages, and offer pages.

↳ messaging and conversion copy.

Turns a website or funnel lead capture into a follow-up system. Useful when Website OS creates a landing page that needs an automated email journey.

↳ post-conversion nurture and lifecycle automation.

Uses lead intelligence to create specific, human-sounding email openers. Useful for campaigns that drive traffic to new offers or websites.

↳ outbound copy and lead activation.

Creates case study narratives and presentations from notes, transcripts, results and client data. Useful for agency websites and landing pages that need credibility.

↳ proof, authority and sales collateral.

Creates professional infographics for websites, lead magnets, social proof, blog posts and funnel assets.

↳ content visuals and supporting assets.

Use before launch and after launch. Website OS should be able to send every generated site through SEO checks before handoff.

↳ SEO strategy, implementation and post-launch audits.

Validates rendered pages, browser errors, accessibility behaviour, responsive layouts, routing and UI regressions.

↳ browser QA before delivery.

Self-healing browser control for agents. Useful for website inspection, screenshots, scraping, testing and real browser validation.

↳ automation and visual/runtime QA.

Useful when Website OS needs repeatable QA checks or automated screenshots for generated websites.

↳ repeatable QA and screenshot automation.

Audits Google, Meta, LinkedIn, TikTok and Microsoft Ads. Useful when a client already has traffic and the website/funnel must match or improve campaign performance.

↳ acquisition audit and traffic-source alignment.

Covers platform selection, campaign architecture, budget planning, creative strategy, and phased implementation roadmaps.

↳ acquisition planning for a new site or funnel.

Analyses competitor ad copy, creative strategy, keyword targeting, spend estimates and competitive gaps.

↳ competitor intelligence and positioning.

Evaluates ad copy, video, image, format diversity and brand consistency across platforms.

↳ creative QA and production planning.

Includes scripts for landing-page analysis, fetching pages and screenshots. Useful to connect ad strategy back to the website/funnel experience.

↳ paid-traffic landing page QA.

Researches leads and companies before outreach, personalisation or funnel strategy.

↳ lead research and campaign context.

Qualifies leads against a defined ICP so campaigns focus on the best-fit prospects.

↳ ICP filtering and campaign targeting.

Mines CRM stages such as Lost, No Show, Churned and Stalled to find high-value prospects worth re-engaging.

↳ reactivation campaigns and pipeline recovery.

The local `gstack-main` contains multiple skills around design consultation, deployment setup, guardrails, design review and agent collaboration. Good bridge between website build, launch and GoHighLevel implementation.

↳ build/review/deploy workflow glue.

Machine-readable selector reference for GHL forms. Useful when generated websites need embedded forms that actually match the design system.

↳ GHL lead capture styling.

Reference for calendar-widget selectors and theme variables. Useful when a landing page uses a booking calendar and must stay on-brand.

↳ GHL booking/calendar styling.