Openclaw marketing pages
Canonical web design tokens, styles, and agent guidance for OpenClaw
npx -y skills add openclaw/carapace --skill openclaw-marketing-pagesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.7 KB, as published. Nobody here has run it
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.