Structured code review through the shared OpenClaw agent-skills installation.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 22, 2026
openclaw-marketing-pages
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.
The English summary is being prepared. Showing the original description.
See how to installFiles included (2)
- SKILL.md1.7 KB
- references/page-patterns.md1.4 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
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.
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 22, 2026
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.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 22, 2026
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.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 22, 2026
Route OpenClaw design work to canonical brand, Carapace product-interface, marketing-page, or design-audit guidance. Use when a task touches OpenClaw visual identity, shared CSS tokens, product UI, public web pages, or Carapace compliance.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 22, 2026
Audit OpenClaw frontend code and rendered interfaces for Carapace 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.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 22, 2026