菜单
Automatically configures FanHub MCP servers and installs documentation. Runs merge-mcp.js and install-docs.js directly. Triggers on: setup fanhub apm, setup fanhub, setup mcp, install documentation, configure mcp servers, fanhub setup, initialize fanhub, setup fanhub workspace.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Complete end-to-end FanHub site rebrand. Replaces all show content, seed data, and visual design for the currently focused language track only (determined by the "Active implementation" line in the project's AGENTS.md / copilot-instructions). Always driven by a universe file in /fanhubdocs/. Use when asked to "rebrand the site", "switch shows", "replace Breaking Bad with X", "do the rebrand", "implement the rebrand plan", or "run the rebrand". Follows the phased plan in /fanhubdocs/*-plan.md.
Use this skill when asked to verify, validate, fact-check, or review any data entry, lore fact, character bio, episode record, quote, or show content for accuracy against canonical project sources and the live database. Triggers on: check data, verify data, fact-check, accuracy check, data accuracy, check entry, verify entry, review accuracy, is this accurate, canon check, lore check, check this data, verify this, review this entry, check for errors, validate data, is this right, is this canon.
Use this skill when asked to add a new entity type to FanHub. Always scaffolds the complete full-stack implementation: backend model, DbContext registration, seed data, EF Core migration, REST controller (GET + POST), frontend model, homepage summary card (showing counts) + nav-card, header nav link, and a Blazor list page with an inline add form. Always include everything unless explicitly told otherwise.
FanHub ASP.NET Core backend conventions, patterns, and best practices. Use when writing or fixing C# code in dotnet/Backend/ — controllers, models, DbContext, EF Core queries, seeding, HTTP status codes, CORS, or unit tests.
FanHub Blazor Server frontend conventions, patterns, and styling. Use when writing or fixing Razor components in dotnet/Frontend/ — data loading, null safety, form design, dropdowns, FanHub brand colors, CSS patterns, or Razor gotchas.
| name | fanhub-setup |
| description | Automatically configures FanHub MCP servers and installs documentation. Runs merge-mcp.js and install-docs.js directly. Triggers on: setup fanhub apm, setup fanhub, setup mcp, install documentation, configure mcp servers, fanhub setup, initialize fanhub, setup fanhub workspace. |
Purpose: Automatically configure MCP servers and install FanHub documentation in your workspace.
What happens when triggered: The skill runs two setup scripts in sequence:
merge-mcp.js — Configures MCP servers for FanHub API and databases (dotnet, Node.js, Java, Go)install-docs.js — Installs FanHub documentation and architecture guidesFrom your project root, run:
# Step 1: Setup MCP servers
node .github/skills/fanhub-setup/scripts/merge-mcp.js
# Step 2: Install documentation
node .github/skills/fanhub-setup/scripts/install-docs.js
Done! Your workspace is now configured with MCP servers and documentation.
Script: merge-mcp.js
Safely integrates FanHub MCP servers into your .vscode/mcp.json without destroying existing configurations:
fanhub-api, fanhub-db-dotnet, fanhub-db-node, fanhub-db-java, fanhub-db-go.vscode/mcp.json doesn't exist yetScript: install-docs.js
Copies FanHub documentation from the APM package into fanhubdocs/ at repo root:
architecture-backend.md — Full API reference, models, EF Core setup, seed dataarchitecture-frontend.md — Blazor Server setup, data fetch patterns, component conventionsbreaking-bad-universe.md — Breaking Bad lore for context| Server | Purpose | Location |
|---|---|---|
fanhub-api | REST API queries | localhost:5265 (when backend running) |
fanhub-db-dotnet | SQLite database (C# backend) | dotnet/Backend/fanhub.db |
fanhub-db-node | SQLite database (Node.js backend) | node/Backend/fanhub.db |
fanhub-db-java | SQLite database (Java backend) | java/Backend/fanhub.db |
fanhub-db-go | SQLite database (Go backend) | go/Backend/fanhub.db |
Cause: APM package not installed
Fix:
apm install MSBart2/apm
node .github/skills/fanhub-setup/scripts/merge-mcp.js
.vscode/mcp.json corruptedFix:
rm .vscode/mcp.json
node .github/skills/fanhub-setup/scripts/merge-mcp.js
Possible causes: APM package not properly installed or Node.js not available
Verify and fix:
# Verify APM package is installed
ls apm_modules/MSBart2/apm/
# Try manual run
node .github/skills/fanhub-setup/scripts/install-docs.js
Documents are installed to fanhubdocs/ at the repo root but Copilot may need a reload. Try restarting VS Code or explicitly referencing the docs in your instructions.
Safe MCP merging: The merge-mcp.js script uses Object.assign() to safely merge FanHub servers into .vscode/mcp.json while preserving your pre-existing MCP configuration.
Self-contained deployment: Both scripts are part of this skill and auto-deployed to .github/skills/fanhub-setup/ when you run apm install MSBart2/apm.