Skip to main content

website-homepage-design

Use when the task is to design a branded homepage, 官网首页, company website, startup homepage, product website, or corporate front page. Focus on brand hierarchy, hero composition, proof sequencing, section rhythm, and clear conversion paths.

설치로 이동

소스 정보

저장소
Mr-Q526/TeamCC-Platform
최근 소스 활동
2026년 4월 15일 03:16
감지된 SKILL.md 언어
영어
스타
7
포크
1

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
4 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
schemaVersion
2026-04-11T00:00:00.000Z
skillId
frontend/website-homepage-design
name
website-homepage-design
displayName
Website Homepage Design
description
Use when the task is to design a branded homepage, 官网首页, company website, startup homepage, product website, or corporate front page. Focus on brand hierarchy, hero composition, proof sequencing, section rhythm, and clear conversion paths.
aliases
["website-homepage-design","Website Homepage Design","websitehomepagedesign","官网首页","品牌首页","企业官网","产品官网","官网","website","首页","主页","homepage","企业官网首页","产品官网首页","homepage design"]
version
0.1.0
sourceHash
sha256:f4e8366bdec59c6430819340ef2eabbdc2f6abf34adf25f5286c965af00a0d96
domain
frontend
departmentTags
["frontend-platform"]
sceneTags
["design"]
# Website Homepage Design Use this skill for branded homepages where first impression, positioning, and trust are the main jobs. Goal: make the brand memorable in one screen, explain the offer quickly, and guide visitors into the right next step. ## Homepage model Default sequence: 1. Hero: brand, value proposition, CTA, dominant visual 2. Credibility: proof, customers, metrics, or press 3. Capabilities: what the product or company does best 4. Product or service depth: workflow, differentiators, or featured work 5. Trust block: testimonial, case study, security, or social proof 6. Final CTA: contact, start, book, or explore ## Hero rules - The brand or product name must be unmistakable. - Use one visual anchor only: image, scene, device render, or typographic composition. - Keep headline length short enough to scan in one glance. - CTA should appear as soon as the value proposition lands. - Avoid a dashboard collage unless the product itself is the visual story. ## Section rules - Each section gets one message and one visual idea. - Put proof before detailed explanation when trust is the blocker. - Use featured examples or use cases instead of generic feature grids when possible. - Keep page rhythm varied: full-bleed section, compressed proof band, narrative detail block. - Footer should close with action, orientation, and essential navigation only. ## Navigation and responsive behavior - Global nav should reflect the real information architecture, not every possible link. - Sticky headers must not steal too much viewport from the hero. - On mobile, collapse complexity fast and keep the first CTA reachable. - Do not let decorative media push the headline or CTA below the fold. ## Reject these failures - Hero cards, stat strips, and logo clouds all fighting in the first viewport - Brand buried under oversized headline copy - Generic SaaS sections repeated without narrative progress - Placeholder stock imagery that weakens credibility - Multiple accent colors with no brand logic ## Final checks - Is the brand unmistakable in the first viewport? - Can a first-time visitor explain what the company does after one scroll? - Does the homepage move from promise to proof to action cleanly?
GitHub에서 보기