When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Guides solutions pages focused on business outcomes. Industry-first is the B2B norm (Salesforce, HubSpot). Answer "what outcome do I get for my industry/team/size?" rather than "what does it do?" Distinct from features (capabilities) and use cases (scenarios); solutions emphasize measurable value by segment.
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, outcomes, and proof points.
Identify:
| Section | Purpose |
|---|---|
| Headline | Outcome-led; "Achieve X with [Product]" |
| Challenge | Business problem, context |
| Solution | How product delivers the outcome |
| Proof | Metrics, case study, ROI |
| Features used | Link to relevant features |
| CTA | Book demo, start trial, see case study |
| Related | Other solutions, use cases (as sub-applications) |
| Dimension | Priority | Examples |
|---|---|---|
| By Industry | Primary | Healthcare, Retail, Manufacturing, Financial Services |
| By Company Size | Secondary | SMB, Mid-Market, Enterprise |
| By Team | Secondary | Marketing, Sales, Service, Operations |
| By Outcome | Alternative | Scale support, Reduce churn, Accelerate sales |
Automotive, Communications, Consumer Goods, Consumer Services, Construction & Real Estate, Education, Energy & Utilities, Financial Services, Government, Healthcare & Life Sciences, Manufacturing, Media, Nonprofit, Professional Services, Retail, Technology, Travel & Hospitality.
| Size | Typical | Focus |
|---|---|---|
| Startup | <50 | Speed, agility |
| SMB | 50–500 | Ease of use, affordability |
| Mid-Market | 500–5000 | Scalability |
| Enterprise | 5000+ | Customization, compliance, integration |
| Page | Answers | Primary Organization |
|---|---|---|
| Features | What does it do? | Capabilities |
| Use cases | When would I use it? | By scenario, persona, business goal |
| Solutions | What outcome do I get? | By industry, company size, team |
Hierarchy: Solutions (industry/segment) can contain Use Cases as sub-applications. Example: /solutions/healthcare → use cases: patient scheduling, telemedicine.
| Need | Use |
|---|---|
| By industry (Healthcare, Retail) | Solutions |
| By company size (SMB, Enterprise) | Solutions |
| By team (Marketing, Sales) | Solutions |
| By outcome (Scale support) | Solutions |
| By scenario (Event marketing) | Use Cases |
| By persona (For Realtors, For CMOs) | Use Cases |
| By business goal (Acquisition, Retention) | Use Cases |
| Industry-specific application | Use Cases (as Solutions sub-page) |
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.