about page generator

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," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.

The skill

# 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:
1. **Audience**: Job seekers, buyers, partners, press
2. **Key message**: Mission, values, differentiation
3. **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

How to install it

Claude Code / Claude Desktop

1. Create a folder named after the skill inside your skills directory:
   - Claude Code: `~/.claude/skills/<skill-name>/`
   - A project-local skill: `<project>/.claude/skills/<skill-name>/`
2. Save the text below as `SKILL.md` in that folder, keeping the
   `---` frontmatter block at the top — the `name` and `description`
   fields are what make the skill discoverable.
3. Restart Claude Code, or run `/skills` to confirm it is listed.

The skill loads only when its `description` matches what you are doing,
so a precise description matters more than a long body.

Did it work for you?

Where it came from

kostja94 MIT The original

2025 kostja94