Tencentcloud Lighthouse Website

---
name: tencentcloud-lighthouse-website
kind: tool
version: 1.0.0
tags:
  - domain: tools
  - subtype: tencentcloud-lighthouse-website
  - level: expert
description: 腾讯云轻量服务器建站：购买、配置宝塔、部署网站。Use when building websites on Tencent Cloud, setting up WordPress, or getting started with cloud. Triggers: '轻量服务器', 'Lighthouse', '建站', '腾讯云'. Works with: Claude Code, Codex, OpenCode, Cursor, Cline, OpenClaw, Kimi.
license: MIT
metadata:
  author: theNeoAI <lucas_hsueh@hotmail.com>
---

# Tencent Lighthouse Website Expert

## Decision Framework

| Requirement | Instance Spec |
|-------------|---------------|
| 个人博客 | 2核2G |
| 企业官网 | 4核4G |
| 电商网站 | 4核8G+ |
| 学习测试 | 1核1G |

---

## § 2 · What This Skill Does

1. **服务器购买** — 轻量应用服务器
2. **环境配置** — 宝塔面板安装
3. **网站部署** — WordPress/商城

---

## § 3 · Steps

```
1. 购买轻量应用服务器
2. 登录控制台 → 远程登录
3. 安装宝塔面板
4. 部署网站 → 绑定域名
5. 配置SSL
```

---

## § 4 · Platform Support

**[URL]:** `https://raw.githubusercontent.com/theneoai/awesome-skills/main/skills/tools/cn-cloud/tencent/tencentcloud-lighthouse-website.md`

---

## § 5 · Pricing

| 配置 | 价格 |
|-----|------|
| 2核2G | ¥24/月 |
| 4核4G | ¥50/月 |
| 8核8G | ¥100/月 |

---

## § 6 · Installation Guide

### 6.1 购买后配置

1. 登录腾讯云控制台
2. 选择轻量应用服务器
3. 点击"登录" → 选择"一键登录"
4. 记录密码信息

### 6.2 宝塔安装

```bash
# CentOS
yum install -y wget && wget -O install.sh https://download.bt.cn/install/install_6.0.sh && sh install.sh

# Ubuntu
wget -O install.sh https://download.bt.cn/install/install-ubuntu_6.0.sh && sudo bash install.sh
```

---

## § 7 · Common Applications

| 应用 | 环境 | 特点 |
|------|------|------|
| WordPress | LNMP | 博客/CMS |
| Discuz! | LAMP | 论坛 |
| ECShop | LNMP | 电商 |
| Typecho | LNMP | 轻量博客 |

---

## 8.1 常用操作

| 任务 | 操作路径 |
|------|----------|
| 创建站点 | 网站 → 添加站点 |
| 安装SSL | 网站 → 设置 → SSL |
| 数据库 | 数据库 → phpMyAdmin |
| 备份 | 计划任务 |

### 8.2 WordPress部署

1. 软件商店 → 一键部署
2. 填写域名信息
3. 自动创建数据库
4. 访问域名完成安装向导

---


## § 8 · Workflow

### Phase 1: Discovery & Assessment

| **Done** | Phase completed |
| **Fail** | Criteria not met |

**Objective:** Fully understand the problem context and requirements.

| **Done** | All tasks completed |
| **Fail** | Tasks incomplete |

**Key Activities:**
1. **Context Gathering** — Collect relevant background information and data
2. **Stakeholder Mapping** — Identify all affected parties and their needs
3. **Requirements Definition** — Document explicit and implicit requirements
4. **Constraint Analysis** — Identify limitations, boundaries, and dependencies

**✓ Done Criteria:**
- [✓] Problem statement clearly defined and documented
- [✓] All stakeholders identified and engaged
- [✓] Success metrics established and agreed upon
- [✓] Constraints documented and acknowledged

**✗ Fail Criteria:**
- [✗] Requirements remain ambiguous or undefined
- [✗] Critical stakeholders excluded from process
- [✗] Success criteria not measurable
- [✗] Constraints ignored or violated

### Phase 2: Analysis & Strategy

| **Done** | Phase completed |
| **Fail** | Criteria not met |

**Objective:** Develop a comprehensive solution strategy.

| **Done** | All tasks completed |
| **Fail** | Tasks incomplete |

**Key Activities:**
1. **Root Cause Analysis** — Identify underlying issues (5 Whys, Fishbone)
2. **Option Generation** — Develop multiple solution alternatives
3. **Risk Assessment** — Evaluate potential risks and mitigation strategies
4. **Resource Planning** — Define required resources, timeline, and budget

**✓ Done Criteria:**
- [✓] Root causes identified and validated
- [✓] At least 3 solution options evaluated with trade-offs
- [✓] Risks assessed with mitigation plans
- [✓] Resources and timeline committed

**✗ Fail Criteria:**
- [✗] Addressing symptoms, not root causes
- [✗] Only one solution considered
- [✗] Risks ignored or underestimated
- [✗] Insufficient resources allocated

### Phase 3: Implementation & Execution

| **Done** | Phase completed |
| **Fail** | Criteria not met |

**Objective:** Execute the chosen solution with quality and efficiency.

| **Done** | All tasks completed |
| **Fail** | Tasks incomplete |

**Key Activities:**
1. **Detailed Planning** — Create actionable implementation plan
2. **Progress Tracking** — Monitor milestones and deliverables
3. **Quality Assurance** — Validate outputs meet standards
4. **Communication** — Keep stakeholders informed

**✓ Done Criteria:**
- [✓] All planned activities completed
- [✓] Stakeholders informed at each milestone
- [✓] Quality checkpoints passed
- [✓] Documentation current and complete

**✗ Fail Criteria:**
- [✗] Activities rushed or skipped
- [✗] Stakeholders surprised by changes
- [✗] Quality issues discovered late
- [✗] Documentation missing or outdated

### Phase 4: Review & Optimization

| **Done** | Phase completed |
| **Fail** | Criteria not met |

**Objective:** Validate results and capture learnings.

| **Done** | All tasks completed |
| **Fail** | Tasks incomplete |

**Key Activities:**
1. **Outcome Evaluation** — Measure against success criteria
2. **Feedback Collection** — Gather stakeholder input
3. **Lessons Learned** — Document insights and improvements
4. **Knowledge Transfer** — Share findings with organization

**✓ Done Criteria:**
- [✓] Success metrics achieved or understood
- [✓] Feedback incorporated for future work
- [✓] Lessons documented and shared
- [✓] Knowledge artifacts created

**✗ Fail Criteria:**
- [✗] Success criteria not measured
- [✗] Feedback ignored or dismissed
- [✗] Same mistakes likely to recur
- [✗] Knowledge lost or siloed

---

## § 9 · Scenario Examples

### Scenario 1: Initial Consultation

**Context:**
A new client or stakeholder needs expert guidance on a tencentcloud lighthouse website matter.

**User Input:**
"I'm new to this area and need help understanding [specific problem]. Where should I start?"

**Expert Response:**
Welcome! I'm here to help you navigate this tencentcloud lighthouse website challenge effectively. Let me start by understanding your situation better.

**1. Assessment Questions:**
- What is your current level of experience with this topic?
- What are your immediate goals or deadlines?
- Do you have any specific constraints (budget, resources, timeline)?
- Who else is involved in this project?

**2. Initial Guidance:**
Based on typical patterns, I recommend we start with:
- **Phase 1: Assessment** — Clearly define what success looks like
- **Phase 2: Strategy** — Develop a tailored approach
- **Phase 3: Execution** — Implement with proper checkpoints

**3. Next Steps:**
Please share more details about your specific situation, and I'll provide targeted recommendations.

---

### Scenario 2: Complex Problem Solving

**Context:**
An urgent, complex tencentcloud lighthouse website issue requires immediate expert intervention.

**User Input:**
"We have a critical situation: [describe urgent problem]. We need a solution within [timeframe]."

**Expert Response:**
I understand the urgency. Let's work through this systematically to ensure we don't miss critical elements.

**1. Triage (First 5 minutes):**
```
[Urgency Assessment]
- Impact Level: [Critical/High/Medium/Low]
- Time Critical: [Yes/No]
- Reversibility: [Reversible/Irreversible]
```

**2. Immediate Stabilization:**
If this is a "bleeding" situation, immediate actions:
- [Stabilization action 1]
- [Stabilization action 2]
- [Communication to stakeholders]

**3. Root Cause Analysis:**
Once stabilized, let's understand what caused this:
```
[5 Whys Analysis]
Why did this happen? → [Answer]
  Why did [Answer]? → [Answer]
    Continue until root cause identified...
```

**4. Solution Development:**
Based on root cause, here are 3 options:
| Option | Approach | Risk | Effort | Timeline |
|--------|----------|------|--------|----------|
| A | Quick fix | High | Low | 1 day |
| B | Balanced | Medium | Medium | 1 week |
| C | Complete | Low | High | 1 month |

**Recommendation:** [Specific recommendation with rationale]

---

### Scenario 3: Strategic Planning

**Context:**
Long-term tencentcloud lighthouse website strategy development for sustained excellence.

**User Input:**
"We want to build world-class capability in tencentcloud lighthouse website. What's our roadmap?"

**Expert Response:**
Building world-class capability is a journey. Here's a strategic framework:

**Phase 1: Foundation (Months 1-3)**
```
Goals:
- Establish baseline assessment
- Define capability maturity model
- Identify quick wins

Key Activities:
□ Comprehensive assessment
□ Best practice research
□ Team skill mapping
□ Quick win identification

Milestone: Foundation Report + Quick Win Implementation
```

**Phase 2: Acceleration (Months 4-9)**
```
Goals:
- Implement core systems
- Upskill team members
- Establish metrics and KPIs

Key Activities:
□ System implementation
□ Training programs
□ Process standardization
□ Performance tracking

Milestone: Operational Excellence Framework
```

**Phase 3: Optimization (Months 10-18)**
```
Goals:
- Continuous improvement culture
- Advanced methodology adoption
- Innovation integration

Key Activities:
□ Maturity assessment
□ Advanced techniques
□ Innovation pipeline
□ Knowledge management

Milestone: World-Class Capability Certification
```

**Success Metrics:**
| Dimension | Baseline | 6 Months | 12 Months | 18 Months |
|-----------|----------|----------|-----------|-----------|
| Efficiency | X% | +20% | +40% | +60% |
| Quality | X defects | -30% | -50% | -70% |
| Speed | X days | -25% | -40% | -50% |
| Innovation | 0/year | 2/year | 5/year | 10/year |

**Investment Required:**
- Human Capital: [FTE estimates]
- Financial: [Budget ranges]
- Timeline: [Phased commitment]

**Risk Mitigation:**
🔴 **High Risk:** [Risk] → Mitigation: [Action]
🟡 **Medium Risk:** [Risk] → Mitigation: [Action]
🟢 **Low Risk:** [Risk] → Mitigation: [Action]

---

### Scenario 4: Quality Assurance & Review

**Context:**
Project or deliverable requires quality verification and optimization.

**User Input:**
"Can you review our [deliverable] and help us improve quality before final delivery?"

**Expert Response:**
Absolutely. Let me conduct a comprehensive quality review using established frameworks.

**1. Quality Checklist:**
- [ ] Requirements alignment verified
- [ ] Standards compliance confirmed
- [ ] Best practices applied
- [ ] Edge cases considered
- [ ] Documentation complete

**2. Gap Analysis:**
| Aspect | Current | Target | Gap | Priority |
|--------|---------|--------|-----|----------|
| Completeness | 80% | 100% | 20% | High |
| Accuracy | 90% | 100% | 10% | High |
| Usability | 70% | 95% | 25% | Medium |

**3. Improvement Plan:**
- **Immediate fixes** (Today): [List]
- **Short-term** (This week): [List]
- **Long-term** (Next month): [List]

**4. Final Validation:**
Before sign-off, ensure:
- ✓ All acceptance criteria met
- ✓ Stakeholder approval obtained
- ✓ Handover documentation ready

---

## § 10 · Professional Toolkit

| 工具 | 用途 |
|------|------|
| 宝塔面板 | 服务器管理 |
| Lighthouse控制台 | 云资源管理 |
| phpMyAdmin | 数据库管理 |

---

## 11.1 个人博客搭建

**User:** "搭建WordPress博客"

**Expert:**
> 1. 购买Lighthouse 2核2G（约¥24/月）
> 2. 安装宝塔面板
> 3. 一键部署WordPress
> 4. 访问临时域名开始配置
> 5. 绑定自定义域名
> 6. 申请免费SSL
> 7. 完成！预估成本：¥30-50/月

### 11.2 SSL配置

**User:** "开启HTTPS"

**Expert:**
> 1. 宝塔 → 网站 → 设置 → SSL
> 2. 选择"Let's Encrypt"
> 3. 勾选域名 → 申请
> 4. 开启"强制HTTPS"
> 5. 自动续期生效

### 11.3 性能优化

**User:** "网站打开很慢"

**Expert:**
> 1. 开启PHP缓存：软件商店 → PHP设置 → 缓存
> 2. 安装Redis：软件商店 → Redis
> 3. 开启Gzip：软件设置 → 性能优化
> 4. 优化图片：使用WebP格式

---

## § 12 · Edge Cases

| 问题 | 解决方案 |
|------|----------|
| 面板无法访问 | 检查安全组8888端口 |
| 网站502错误 | 检查PHP版本/进程 |
| 磁盘满 | 清理日志/升级磁盘 |
| 远程连接失败 | 检查密码/密钥 |

---

## § 13 · Basic Security

| 措施 | 说明 |
|------|------|
| 修改面板端口 | 默认8888 |
| 禁用root登录 | 创建普通用户 |
| 定期更新 | 系统和软件 |
| 防火墙 | 仅开放必要端口 |

---

## § 14 · Scope & Limitations

**In Scope:**
- Lighthouse server setup
- Baota panel installation
- WordPress deployment

**Out of Scope:**
- Advanced server configuration
- Complex application deployment

---

## § 15 · How to Use

```bash
# OpenCode
/skill load tencentcloud-lighthouse-website
```

**Trigger Words:**
- "轻量服务器", "Lighthouse", "建站", "腾讯云"

---

## § 16 · Quality Verification, Version History & License

**Quality Verification:**
- [ ] Can purchase Lighthouse server
- [ ] Can install Baota panel
- [ ] Can deploy WordPress

**Version History:**
| Version | Date | Changes |
|---------|------|---------|
| 3.0.0 | 2026-03-15 | Full rewrite |
| 1.0.0 | 2026-02-16 | Initial release |

MIT with Attribution — See [../../LICENSE](../../LICENSE)
## Anti-Patterns

| Pattern | Avoid | Instead |
|---------|-------|---------|
| Generic | Vague claims | Specific data |
| Skipping | Missing validations | Full verification |