一键在 Manus 中运行任何 Skill

website-branding-preferences

星标1,793

分支330

更新时间2026年7月7日 16:00

Apply the user's default website branding preferences. Use when building, editing, redesigning, cloning, recreating, or implementing a website, landing page, ecommerce UI, frontend app, or brand-bearing web experience, especially when a logo, brand name, header, navbar, hero, favicon, or site identity is involved.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

itswadesh

itswadesh/svelte-commerce

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Rules

Do not use exact real logos, copied logo marks, or lookalike logo artwork for website builds unless the user explicitly provides permission and assets.
Replace logo marks with the website name itself as a text wordmark in the UI.
Rename the brand/site name to Website-$1 by default, preserving $1 as the user-provided or inferred original brand/site identifier.
If the source brand name is ambiguous, choose a simple descriptive suffix for $1 from the user's request or the project context.
Apply the text wordmark consistently in navbars, headers, footers, favicons where practical, metadata, page titles, mock data, and visible copy touched by the task.
Keep the result visually polished: treat Website-$1 as the brand, not as a placeholder label.
Make every generated website mobile responsive across common viewport widths.
Ensure pages do not create a horizontal scrollbar; fix overflowing layouts, images, grids, absolute elements, and long text instead of hiding unresolved overflow.

Examples

A Shopify-inspired storefront for "Acme" should display Website-Acme as text instead of an Acme logo.
A redesign based on an existing site should replace copied logo imagery with a styled Website-[source-name] wordmark.

同仓库更多 Skills

同仓库

storefront-originality

itswadesh/svelte-commerce

Build or reskin production-grade ecommerce storefronts while avoiding copyright, plagiarism, copied branding, dead links, weak UX, and incomplete flows. Use when creating a new theme, cloning or adapting a reference storefront, applying a static-site design, building a demo ecommerce site, or auditing a storefront for originality and completeness.

2026-07-071.8k

adapt

itswadesh/svelte-commerce

Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.

2026-07-071.8k

animate

itswadesh/svelte-commerce

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.

2026-07-071.8k

audit

itswadesh/svelte-commerce

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.

2026-07-071.8k

bolder

itswadesh/svelte-commerce

Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.

2026-07-071.8k

clarify

itswadesh/svelte-commerce

Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.

2026-07-071.8k

name	website-branding-preferences
description	Apply the user's default website branding preferences. Use when building, editing, redesigning, cloning, recreating, or implementing a website, landing page, ecommerce UI, frontend app, or brand-bearing web experience, especially when a logo, brand name, header, navbar, hero, favicon, or site identity is involved.
version	1.0.0
user-invocable	true
argument-hint	[source brand or site]

Rules

Do not use exact real logos, copied logo marks, or lookalike logo artwork for website builds unless the user explicitly provides permission and assets.
Replace logo marks with the website name itself as a text wordmark in the UI.
Rename the brand/site name to Website-$1 by default, preserving $1 as the user-provided or inferred original brand/site identifier.
If the source brand name is ambiguous, choose a simple descriptive suffix for $1 from the user's request or the project context.
Apply the text wordmark consistently in navbars, headers, footers, favicons where practical, metadata, page titles, mock data, and visible copy touched by the task.
Keep the result visually polished: treat Website-$1 as the brand, not as a placeholder label.
Make every generated website mobile responsive across common viewport widths.
Ensure pages do not create a horizontal scrollbar; fix overflowing layouts, images, grids, absolute elements, and long text instead of hiding unresolved overflow.

Examples

A Shopify-inspired storefront for "Acme" should display Website-Acme as text instead of an Acme logo.
A redesign based on an existing site should replace copied logo imagery with a styled Website-[source-name] wordmark.