ccg-workflow 1.8.2 → 2.0.0

package/templates/skills/impeccable/quieter/SKILL.md

@@ -0,0 +1,102 @@
+---
+name: quieter
+description: "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic."
+argument-hint: "[target]"
+user-invocable: true
+---
+
+Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness.
+
+## MANDATORY PREPARATION
+
+Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first.
+
+---
+
+## Assess Current State
+
+Analyze what makes the design feel too intense:
+
+1. **Identify intensity sources**:
+   - **Color saturation**: Overly bright or saturated colors
+   - **Contrast extremes**: Too much high-contrast juxtaposition
+   - **Visual weight**: Too many bold, heavy elements competing
+   - **Animation excess**: Too much motion or overly dramatic effects
+   - **Complexity**: Too many visual elements, patterns, or decorations
+   - **Scale**: Everything is large and loud with no hierarchy
+
+2. **Understand the context**:
+   - What's the purpose? (Marketing vs tool vs reading experience)
+   - Who's the audience? (Some contexts need energy)
+   - What's working? (Don't throw away good ideas)
+   - What's the core message? (Preserve what matters)
+
+If any of these are unclear from the codebase, Ask the user using AskUserQuestion.
+
+**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness.
+
+## Plan Refinement
+
+Create a strategy to reduce intensity while maintaining impact:
+
+- **Color approach**: Desaturate or shift to more sophisticated tones?
+- **Hierarchy approach**: Which elements should stay bold (very few), which should recede?
+- **Simplification approach**: What can be removed entirely?
+- **Sophistication approach**: How can we signal quality through restraint?
+
+**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision.
+
+## Refine the Design
+
+Systematically reduce intensity across these dimensions:
+
+### Color Refinement
+- **Reduce saturation**: Shift from fully saturated to 70-85% saturation
+- **Soften palette**: Replace bright colors with muted, sophisticated tones
+- **Reduce color variety**: Use fewer colors more thoughtfully
+- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule)
+- **Gentler contrasts**: High contrast only where it matters most
+- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness
+- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead
+
+### Visual Weight Reduction
+- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate
+- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness
+- **White space**: Increase breathing room, reduce density
+- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely
+
+### Simplification
+- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose
+- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes
+- **Reduce layering**: Flatten visual hierarchy where possible
+- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows
+
+### Motion Reduction
+- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing
+- **Remove decorative animations**: Keep functional motion, remove flourishes
+- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback
+- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic
+- **Remove animations entirely** if they're not serving a clear purpose
+
+### Composition Refinement
+- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling
+- **Align to grid**: Bring rogue elements back into systematic alignment
+- **Even out spacing**: Replace extreme spacing variations with consistent rhythm
+
+**NEVER**:
+- Make everything the same size/weight (hierarchy still matters)
+- Remove all color (quiet ≠ grayscale)
+- Eliminate all personality (maintain character through refinement)
+- Sacrifice usability for aesthetics (functional elements still need clear affordances)
+- Make everything small and light (some anchors needed)
+
+## Verify Quality
+
+Ensure refinement maintains quality:
+
+- **Still functional**: Can users still accomplish tasks easily?
+- **Still distinctive**: Does it have character, or is it generic now?
+- **Better reading**: Is text easier to read for extended periods?
+- **Sophistication**: Does it feel more refined and premium?
+
+Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality.

package/templates/skills/impeccable/teach-impeccable/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: teach-impeccable
+description: One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
+user-invocable: true
+---
+
+Gather design context for this project, then persist it for all future sessions.
+
+## Step 1: Explore the Codebase
+
+Before asking questions, thoroughly scan the project to discover what you can:
+
+- **README and docs**: Project purpose, target audience, any stated goals
+- **Package.json / config files**: Tech stack, dependencies, existing design libraries
+- **Existing components**: Current design patterns, spacing, typography in use
+- **Brand assets**: Logos, favicons, color values already defined
+- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales
+- **Any style guides or brand documentation**
+
+Note what you've learned and what remains unclear.
+
+## Step 2: Ask UX-Focused Questions
+
+Ask the user using AskUserQuestion. Focus only on what you couldn't infer from the codebase:
+
+### Users & Purpose
+- Who uses this? What's their context when using it?
+- What job are they trying to get done?
+- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)
+
+### Brand & Personality
+- How would you describe the brand personality in 3 words?
+- Any reference sites or apps that capture the right feel? What specifically about them?
+- What should this explicitly NOT look like? Any anti-references?
+
+### Aesthetic Preferences
+- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.)
+- Light mode, dark mode, or both?
+- Any colors that must be used or avoided?
+
+### Accessibility & Inclusion
+- Specific accessibility requirements? (WCAG level, known user needs)
+- Considerations for reduced motion, color blindness, or other accommodations?
+
+Skip questions where the answer is already clear from the codebase exploration.
+
+## Step 3: Write Design Context
+
+Synthesize your findings and the user's answers into a `## Design Context` section:
+
+```markdown
+## Design Context
+
+### Users
+[Who they are, their context, the job to be done]
+
+### Brand Personality
+[Voice, tone, 3-word personality, emotional goals]
+
+### Aesthetic Direction
+[Visual tone, references, anti-references, theme]
+
+### Design Principles
+[3-5 principles derived from the conversation that should guide all design decisions]
+```
+
+Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place.
+
+Then Ask the user using AskUserQuestion. whether they'd also like the Design Context appended to CLAUDE.md. If yes, append or update the section there as well.
+
+Confirm completion and summarize the key design principles that will now guide all future work.

package/templates/skills/impeccable/typeset/SKILL.md

@@ -0,0 +1,115 @@
+---
+name: typeset
+description: "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography."
+argument-hint: "[target]"
+user-invocable: true
+---
+
+Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type.
+
+## MANDATORY PREPARATION
+
+Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first.
+
+---
+
+## Assess Current Typography
+
+Analyze what's weak or generic about the current type:
+
+1. **Font choices**:
+   - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults)
+   - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface)
+   - Are there too many font families? (More than 2-3 is almost always a mess)
+
+2. **Hierarchy**:
+   - Can you tell headings from body from captions at a glance?
+   - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy)
+   - Are weight contrasts strong enough? (Medium vs Regular is barely visible)
+
+3. **Sizing & scale**:
+   - Is there a consistent type scale, or are sizes arbitrary?
+   - Does body text meet minimum readability? (16px+)
+   - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings)
+
+4. **Readability**:
+   - Are line lengths comfortable? (45-75 characters ideal)
+   - Is line-height appropriate for the font and context?
+   - Is there enough contrast between text and background?
+
+5. **Consistency**:
+   - Are the same elements styled the same way throughout?
+   - Are font weights used consistently? (Not bold in one section, semibold in another for the same role)
+   - Is letter-spacing intentional or default everywhere?
+
+**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting.
+
+## Plan Typography Improvements
+
+Consult the [typography reference](reference/typography.md) from the frontend-design skill for detailed guidance on scales, pairing, and loading strategies.
+
+Create a systematic plan:
+
+- **Font selection**: Do fonts need replacing? What fits the brand/context?
+- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy
+- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits)
+- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements
+
+## Improve Typography Systematically
+
+### Font Selection
+
+If fonts need replacing:
+- Choose fonts that reflect the brand personality
+- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights
+- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks)
+
+### Establish Hierarchy
+
+Build a clear type scale:
+- **5 sizes cover most needs**: caption, secondary, body, subheading, heading
+- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5)
+- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone
+- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need
+- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed
+
+### Fix Readability
+
+- Set `max-width` on text containers using `ch` units (`max-width: 65ch`)
+- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7)
+- Increase line-height slightly for light-on-dark text
+- Ensure body text is at least 16px / 1rem
+
+### Refine Details
+
+- Use `tabular-nums` for data tables and numbers that should align
+- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text
+- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`)
+- Set `font-kerning: normal` and consider OpenType features where appropriate
+
+### Weight Consistency
+
+- Define clear roles for each weight and stick to them
+- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty)
+- Load only the weights you actually use (each weight adds to page load)
+
+**NEVER**:
+- Use more than 2-3 font families
+- Pick sizes arbitrarily — commit to a scale
+- Set body text below 16px
+- Use decorative/display fonts for body text
+- Disable browser zoom (`user-scalable=no`)
+- Use `px` for font sizes — use `rem` to respect user settings
+- Default to Inter/Roboto/Open Sans when personality matters
+- Pair fonts that are similar but not identical (two geometric sans-serifs)
+
+## Verify Typography Improvements
+
+- **Hierarchy**: Can you identify heading vs body vs caption instantly?
+- **Readability**: Is body text comfortable to read in long passages?
+- **Consistency**: Are same-role elements styled identically throughout?
+- **Personality**: Does the typography reflect the brand?
+- **Performance**: Are web fonts loading efficiently without layout shift?
+- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%?
+
+Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make.

package/templates/skills/orchestration/multi-agent/SKILL.md

@@ -113,6 +113,46 @@ disable-model-invocation: false
 
 ---
 
+## 企业级角色扩展（`/ccg:team` 专用）
+
+`/ccg:team` 命令在蚁群基础角色之上，增加 3 个大厂级专业角色，对应 Agent Teams 真实 teammates：
+
+| 角色 | Agent 名 | 道语 | 职责 | 工具权限 | 模型 |
+|------|----------|------|------|----------|------|
+| 🏗 架构师 (Architect) | `team-architect` | 天罗军师 | 代码库扫描、架构蓝图、文件分配矩阵 | Read/Glob/Grep（只读） | Sonnet |
+| 🧪 QA 工程师 (QA) | `team-qa` | 天罗验毒 | 写测试、跑测试、lint、typecheck | Read/Write/Edit/Bash/Glob/Grep | Sonnet |
+| 🔬 审查员 (Reviewer) | `team-reviewer` | 天罗护法 | 综合 Codex/Gemini 审查、分级判决 | Read/Glob/Grep（只读） | Sonnet |
+
+### 8 阶段流水线
+
+```
+Phase 0: PRE-FLIGHT    → 环境检测 + 参数解析
+Phase 1: REQUIREMENT   → Lead 需求增强 → mini-PRD
+Phase 2: ARCHITECTURE  → Codex∥Gemini 外援 + Architect teammate 出蓝图
+Phase 3: PLANNING      → Lead 拆任务 → 零决策并行计划
+Phase 4: DEVELOPMENT   → Dev×N teammates 并行编码（文件隔离）
+Phase 5: TESTING       → QA teammate 写测试 + 跑全量验证
+Phase 6: REVIEW        → Codex∥Gemini 外援 + Reviewer teammate 综合审查
+Phase 7: FIX           → Dev teammate(s) 修复 Critical（最多 2 轮）
+Phase 8: INTEGRATION   → Lead 全量验证 + 报告 + 清理
+```
+
+### 角色生命周期
+
+```
+TeamCreate ─── Phase 2: spawn Architect → shutdown
+            ├─ Phase 4: spawn Dev×N → shutdown
+            ├─ Phase 5: spawn QA → shutdown
+            ├─ Phase 6: spawn Reviewer → shutdown
+            ├─ Phase 7: spawn Fix-Dev(s) → shutdown
+            └─ Phase 8: TeamDelete
+```
+
+**推荐入口**：`/ccg:team <需求描述>` — 一键跑完 8 阶段。
+**分步入口**（兼容）：`/ccg:team-research` → `/ccg:team-plan` → `/ccg:team-exec` → `/ccg:team-review`
+
+---
+
 ## 信息素系统（Stigmergy）
 
 蚁群通过信息素间接通信，而非直接对话。在 Claude Code 中，用 **TaskCreate metadata** 模拟信息素：

package/templates/skills/scrapling/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: scrapling
+description: "使用 scrapling 进行网页抓取和数据提取。自动选择 Fetcher，支持 Cloudflare/WAF 绕过、Session 登录、HTML 解析。当用户提到 scrape/crawl/fetch page/extract data/爬取/抓取/绕过Cloudflare/解析HTML/批量采集 时触发。"
+user-invocable: true
+allowed-tools: Read, Bash
+argument-hint: "[URL or scraping task description]"
+license: MIT
+---
+
+# Scrapling 网页抓取 Skill
+
+## 步骤 0：检查版本
+
+```bash
+pip show scrapling
+```
+
+- 未安装 → 执行 `pip install "scrapling[fetchers]"` + `scrapling install`
+- 有新版 → 执行 `pip install --upgrade "scrapling[fetchers]"` → 查 changelog 告知用户
+- 已最新 → 继续
+
+## 步骤 1：选择 Fetcher
+
+```
+目标网站 →
+│
+├─ 已有 HTML 字符串/文件，只需解析?
+│   → Selector（纯解析，无网络请求）
+│   → 模板: templates/parse_only.py
+│
+├─ 静态页面，无 JS 渲染，无反爬?
+│   → Fetcher（最快，基于 curl_cffi）
+│   → 模板: templates/basic_fetch.py
+│
+├─ 需要登录（HTTP 表单，非 JS 登录）?
+│   → FetcherSession（保持会话 cookie）
+│   → 模板: templates/session_login.py
+│
+├─ 有 Cloudflare / WAF 保护?
+│   → StealthyFetcher（Camoufox 浏览器，自动过 CF）
+│   → 模板: templates/stealth_cloudflare.py
+│
+├─ SPA 应用（React/Vue），需要 JS 渲染?
+│   → DynamicFetcher（Playwright 浏览器）
+│   → 基于模板即时生成
+│
+└─ 不确定?
+    → 先用 Fetcher 试，403/空内容 → 升级到 StealthyFetcher
+```
+
+## 步骤 2：执行工作流
+
+```
+1. 检查版本（步骤 0）
+2. 查阅 references/site-patterns.md — 匹配已有模式则直接复用
+3. 无匹配 → 用决策树选择 Fetcher
+4. 读取对应模板 → 替换参数 → 生成完整脚本
+5. 执行脚本 → 返回结果
+6. **沉淀经验（必做）**:
+   - 新站点 → 追加到 site-patterns.md
+   - 新 cookie / 用户提供了 cookie → 保存到 cookie-vault.md
+   - **完成抓取后必须检查**：是否有新的 cookie 或 site pattern 需要保存
+```
+
+## Cookie 格式速查
+
+| Fetcher 类型 | Cookie 格式 | 示例 |
+|-------------|-------------|------|
+| Fetcher / FetcherSession | `dict` | `{'name': 'value', 'token': 'abc'}` |
+| StealthyFetcher / DynamicFetcher | `list[dict]` | `[{'name': 'n', 'value': 'v', 'domain': '.site.com', 'path': '/'}]` |
+
+**浏览器 Fetcher cookie 必填字段**: `name`, `value`, `domain`, `path`
+
+## 超时单位速查
+
+| Fetcher 类型 | 超时单位 | 示例 |
+|-------------|---------|------|
+| Fetcher / FetcherSession | 秒 | `timeout=30` |
+| StealthyFetcher / DynamicFetcher | 毫秒 | `timeout=60000` |
+
+## 模板索引
+
+| 模板 | 文件 | 何时读取 |
+|------|------|---------|
+| 基础 HTTP 抓取 | `templates/basic_fetch.py` | 目标为静态页面，无反爬 |
+| Cloudflare 绕过 | `templates/stealth_cloudflare.py` | 目标有 CF/WAF 保护 |
+| Session 登录 | `templates/session_login.py` | 需 HTTP 表单登录后抓取 |
+| 纯 HTML 解析 | `templates/parse_only.py` | 已有 HTML 字符串，只需提取数据 |
+
+## References 索引
+
+| 文件 | 何时读取 |
+|------|---------|
+| `references/site-patterns.md` | **每次抓取前先查阅** — 检查目标站点是否有已记录的模式 |
+| `references/api-quick-ref.md` | 生成脚本时查阅 — Fetcher/Selector 方法签名和参数 |
+| `references/troubleshooting.md` | 执行报错时查阅 — 按错误信息查找原因和解决方案 |
+| `references/cookie-vault.md` | 需要登录 cookie 时查阅 — 检查是否有历史记录可复用 |
+| `references/maintenance.md` | 安装/升级/依赖问题时查阅 — 安装层级和验证命令 |

package/templates/skills/scrapling/references/api-quick-ref.md

@@ -0,0 +1,127 @@
+# Scrapling API 速查卡
+
+## Fetcher（基于 curl_cffi，最快）
+
+```python
+from scrapling.fetchers import Fetcher
+
+# GET 请求
+page = Fetcher.get(url, impersonate='chrome', timeout=30, headers=None, cookies=None)
+
+# POST 请求
+page = Fetcher.post(url, data=None, json=None, impersonate='chrome', timeout=30)
+```
+
+**Cookie 格式**: `dict` — `{'name': 'value'}`
+**超时单位**: 秒
+
+## FetcherSession（保持会话 cookie）
+
+```python
+from scrapling.fetchers import FetcherSession
+
+with FetcherSession(impersonate='chrome') as s:
+    s.post(login_url, data={'user': '...', 'pass': '...'})
+    page = s.get(target_url)
+```
+
+## StealthyFetcher（Camoufox，绕过反爬）
+
+```python
+from scrapling.fetchers import StealthyFetcher
+
+page = StealthyFetcher.fetch(
+    url,
+    headless=True,           # 无头模式
+    solve_cloudflare=True,   # 自动过 Cloudflare
+    cookies=None,            # list[dict] 格式
+    timeout=60000,           # 毫秒
+    network_idle=True,       # 等待网络空闲
+    hide_canvas=True,        # 隐藏 canvas 指纹
+    block_webrtc=True,       # 阻止 WebRTC 泄露 IP
+    disable_resources=False, # 禁用图片/字体加速
+)
+```
+
+**Cookie 格式**: `list[dict]` — `[{'name': 'n', 'value': 'v', 'domain': '.site.com', 'path': '/'}]`
+**超时单位**: 毫秒
+
+## DynamicFetcher（Playwright，JS 渲染）
+
+```python
+from scrapling.fetchers import DynamicFetcher
+
+page = DynamicFetcher.fetch(
+    url,
+    headless=True,
+    cookies=None,            # list[dict] 格式
+    timeout=30000,           # 毫秒
+    network_idle=True,       # 等待网络空闲
+    wait_selector=None,      # 等待特定元素出现
+    disable_resources=True,  # 跳过图片/字体/CSS 加速
+)
+```
+
+**Cookie 格式**: `list[dict]`
+**超时单位**: 毫秒
+
+## Selector（纯 HTML 解析，无网络请求）
+
+```python
+from scrapling.parser import Selector
+
+page = Selector(html_string, url='https://base-url.com')
+```
+
+## Response 常用属性
+
+```python
+page.status          # HTTP 状态码 (int)
+page.text            # 原始 HTML/文本内容 (str)
+page.url             # 最终 URL（可能经过重定向）
+page.cookies         # 响应 cookie
+page.headers         # 响应头
+```
+
+## 选择器方法
+
+```python
+# CSS 选择器
+page.css('div.content')              # 返回元素列表
+page.css_first('h1')                 # 返回第一个匹配元素
+
+# XPath 选择器
+page.xpath('//div[@class="content"]')
+
+# 文本提取伪元素
+page.css('h1::text')                 # 提取文本内容
+page.css('a::attr(href)')            # 提取属性值
+
+# 获取所有匹配结果的文本
+results = page.css('h1::text').getall()  # list[str]
+
+# 获取第一个匹配结果的文本
+result = page.css('h1::text').get()      # str | None
+```
+
+## 元素方法
+
+```python
+element = page.css_first('div.post')
+
+element.text                          # 直接子文本
+element.get_all_text(strip=True)      # 递归获取所有文本
+element.attrib                        # 属性字典
+element.attrib.get('href')            # 获取单个属性
+element.css('span.author::text')      # 在子树中继续选择
+element.parent                        # 父元素
+element.children                      # 子元素列表
+```
+
+## 正则提取
+
+```python
+# 从文本中提取匹配
+page.re(r'price: \$(\d+\.\d+)')      # list[str] — 所有匹配
+page.re_first(r'price: \$(\d+\.\d+)')  # str | None — 第一个匹配
+```

package/templates/skills/scrapling/references/cookie-vault.md

@@ -0,0 +1,56 @@
+# Cookie 保险库
+
+按站点分区记录历史 cookie，供抓取时快速查找使用。
+
+> **安全提示**: 此文件存储敏感 cookie 值，请勿提交到版本控制或分享给他人。
+> 实际使用时，请将此文件复制为 `cookie-vault.local.md` 并填入真实值。
+
+---
+
+## 示例站点 (example.com)
+
+**最后更新**: YYYY-MM-DD
+**状态**: 有效 / 可能已过期
+**登录 cookie 字段**: `session_id`, `auth_token`
+**Fetcher 类型**: StealthyFetcher
+
+### Playwright 格式（StealthyFetcher/DynamicFetcher 用）
+
+```python
+cookies = [
+    {'name': 'session_id', 'value': '<YOUR_SESSION_ID>', 'domain': '.example.com', 'path': '/'},
+    {'name': 'auth_token', 'value': '<YOUR_AUTH_TOKEN>', 'domain': '.example.com', 'path': '/'},
+]
+```
+
+### 备注
+
+- 从浏览器 DevTools > Application > Cookies 获取真实值
+- cookie 有效期取决于站点设置，过期后需重新获取
+
+---
+
+## 模板：添加新站点
+
+复制以下模板，替换具体内容后追加到此文件：
+
+```markdown
+## 站点名称 (域名)
+
+**最后更新**: YYYY-MM-DD
+**状态**: 有效 / 可能已过期
+**登录 cookie 字段**: `field1`, `field2`
+**Fetcher 类型**: Fetcher / StealthyFetcher / DynamicFetcher
+
+### Playwright 格式
+
+\```python
+cookies = [
+    {'name': 'field1', 'value': '...', 'domain': '.example.com', 'path': '/'},
+]
+\```
+
+### 备注
+
+- 相关注意事项
+```