about-page-generator
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page", "about us", "company story" or "our team". For sitewide page planning, use website-structure.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 12
- Forks
- 0
01 前言 Front Matter
- name
- about-page-generator
- metadata
- { "version": "1.0.1" }
- description
- When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page", "about us", "company story" or "our team". For sitewide page planning, use website-structure.
03 SKILL.md 正文
Pages: About
Guides About page content, structure, and trust-building for company websites.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for company story, values, and differentiation. See branding for full brand strategy framework (purpose, values, storytelling).
Identify:
- Audience: Job seekers, buyers, partners, press
- Key message: Mission, values, differentiation
- Proof points: Awards, metrics, testimonials
Best Practices
Essential Elements
| Element | Purpose |
|---|---|
| Company overview | Who, what, where, when, why, how |
| Origin story | Journey, founding, milestones |
| Team | Key people, photos, roles |
| Mission and values | What you stand for |
| Visuals | Photos, videos, office/culture |
| Social proof | Testimonials, awards, certifications |
| Contact | Easy way to reach you |
Strategic Approach
- Tell a story: Convey who you are and why you're different—not just facts. See branding for origin story, hero's journey, narrative arc.
- Customer-focused: Frame around what you solve for customers, not self-promotion
- Build trust: Social links, testimonials, contact details, certifications
- Visible placement: About in main nav, not buried in footer
Schema (AboutPage, Not Organization)
- AboutPage schema: Use on About page—describes page content (headline, description, author, about). Helps search engines understand this page's purpose.
- Organization schema: Place on homepage or root layout, not About. Organization is entity-level (brand that owns the site); AboutPage is page-level. See schema-markup for placement.
Why It Matters
- One of the most-visited pages
- 58% of customers buy based on company values
- 60% of job candidates choose employers based on values
- Entry point for branded search; impacts conversions
Output Format
- Structure outline (sections)
- Story narrative and key messages
- Team section approach
- SEO metadata (title, description, H1)
- Trust elements checklist
Related Skills
- branding: Brand strategy, storytelling, purpose, values; About page implements brand story
- homepage-generator: About often linked from homepage
- contact-page-generator: Contact info on About
- customer-stories-page-generator: Social proof complements About
- title-tag, meta-description, page-metadata: About page metadata
- schema-markup: AboutPage schema for About; Organization goes on homepage/root layout
- brand-protection: Official domain and identity declaration; helps users distinguish from impersonation sites
04 同仓库更多 Skills
youtube
Download YouTube video transcripts when user provides a YouTube URL or asks to download/get/fetch a transcript from YouTube. Also use when user wants to transcribe or get captions/subtitles from a YouTube video.
write-plan
Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY/SOLID/YAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs /plan-eng-review as an independent double-check before execution.
worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
web-perf
Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.
verify
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
validate-idea
Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.