원클릭으로 Manus에서 모든 스킬 실행

openclaw-marketing-pages

스타9,141

포크1,423

업데이트2026년 7월 9일 18:05

Create or update OpenClaw public-page composition for websites, landing pages, content pages, ecosystem pages, and campaigns. Use for page structure, navigation, responsive layout, media, SEO presentation, or public-site visual polish.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

openclaw

openclaw/clawhub

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

OpenClaw Marketing Pages

Build the real public experience first. Do not replace it with a generic landing-page template or an explanatory feature tour.

Workflow

Read page-patterns.md.
Inspect the consumer's existing header, footer, sections, and page primitives.
Reuse local public-site patterns before adding another composition.
Use the canonical tokens and typography contract.
Make the brand, product, place, or object visible in the first viewport.
Keep a hint of the next section visible at common desktop and mobile heights.
Validate navigation, content hierarchy, media, light/dark themes, and responsive behavior in a browser.

Rules

Use the literal brand, product, place, person, or offer as the primary headline.
Put value propositions in supporting copy rather than an abstract headline.
Use relevant product or community imagery instead of atmospheric stock media.
Keep page sections unframed; use cards only for genuinely repeated items.
Avoid repetitive social-proof, feature-grid, and CTA sections without a content need.
Keep headings proportionate to their container.
Use icons for tools and familiar actions; do not use decorative icon boxes.
Preserve readable line length and clear section rhythm.
Use motion to explain state or progression, not as ambient decoration.
Preserve SEO metadata, semantic heading order, and accessible navigation.

이 저장소의 다른 Skills

같은 저장소

openclaw-design

openclaw/clawhub

Route OpenClaw design work to the canonical brand, product design-system, marketing-page, or design-audit guidance. Use when a task touches OpenClaw visual identity, shared CSS tokens, product UI, public web pages, or design-system compliance.

2026-07-129.1k

clawhub-moderation

openclaw/clawhub

Use for ClawHub staff moderation actions with the repo-local ClawHub admin tool: skills, users, org publishers, plugin packages, trusted publishers, official publishers, and guarded staff email.

2026-07-109.1k

clawhub-production-release

openclaw/clawhub

Run and verify ClawHub production deploys and stable ClawHub CLI npm releases. Use when deploying backend or frontend changes to clawhub.ai, dispatching the Deploy workflow, publishing a stable CLI tag, checking release prerequisites, or proving the exact production SHA and workflow outcome.

2026-07-109.1k

openclaw-brand

openclaw/clawhub

Apply OpenClaw visual identity to logos, typography, imagery, voice, documents, presentations, social graphics, and launch materials. Use when the task changes brand identity rather than ordinary product UI or public-page composition.

2026-07-099.1k

openclaw-design-audit

openclaw/clawhub

Audit OpenClaw frontend code and rendered interfaces for design-system drift, token misuse, primitive reimplementation, accessibility problems, responsive defects, and off-brand copy. Use for design reviews, compliance checks, or scheduled audit-and-fix workflows.

2026-07-099.1k

openclaw-design-system

openclaw/clawhub

Build or modify OpenClaw application UI using canonical semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives. Use for product interfaces, component styling, theme work, or design-token integration.

2026-07-099.1k

name	openclaw-marketing-pages
description	Create or update OpenClaw public-page composition for websites, landing pages, content pages, ecosystem pages, and campaigns. Use for page structure, navigation, responsive layout, media, SEO presentation, or public-site visual polish.

OpenClaw Marketing Pages

Build the real public experience first. Do not replace it with a generic landing-page template or an explanatory feature tour.

Workflow

Read page-patterns.md.
Inspect the consumer's existing header, footer, sections, and page primitives.
Reuse local public-site patterns before adding another composition.
Use the canonical tokens and typography contract.
Make the brand, product, place, or object visible in the first viewport.
Keep a hint of the next section visible at common desktop and mobile heights.
Validate navigation, content hierarchy, media, light/dark themes, and responsive behavior in a browser.

Rules

Use the literal brand, product, place, person, or offer as the primary headline.
Put value propositions in supporting copy rather than an abstract headline.
Use relevant product or community imagery instead of atmospheric stock media.
Keep page sections unframed; use cards only for genuinely repeated items.
Avoid repetitive social-proof, feature-grid, and CTA sections without a content need.
Keep headings proportionate to their container.
Use icons for tools and familiar actions; do not use decorative icon boxes.
Preserve readable line length and clear section rhythm.
Use motion to explain state or progression, not as ambient decoration.
Preserve SEO metadata, semantic heading order, and accessible navigation.