Domains¶
Per-domain hub pages. Each hub is a single-page entry point that pulls together the local skills, vendored skills, external (manual-install) skills, MCP servers, and backlog items relevant to a professional domain.
Hubs¶
| Hub | Coverage | Status |
|---|---|---|
| Finance | Banking, capital markets, equity research, wealth management, fund admin. | Populated |
| Quant Research | Quant trading, factor research, backtesting, live execution. | Populated |
| AI/ML Research | Experiment tracking, model lifecycle, fine-tuning, agent frameworks. | Populated |
| Web & Fullstack | Next.js / React / Tailwind / Supabase / Vercel / browser automation / web quality audits. | Populated |
| Knowledge Work | Sales / legal / customer support / product / marketing / data / etc. | Mostly template |
| Agent Harness | SDD frameworks + agent harnesses (the layer above skills), plus reusable control adapters. | Populated |
"Mostly template" / "Template only" hubs are honest about being mostly empty — they exist so the structure is in place when content arrives.
How to add a new domain hub¶
- Copy
docs/_snippets/domain-hub-template.mdtodocs/catalog/domains/<slug>.md. - Fill in the elevator pitch + the 4 tables (Local / Vendored / External / MCP) — leave
_none yet_for empty rows. - Add the new page to
mkdocs.ymlnav underCatalog → Domains. - Translate to
docs/catalog/domains/<slug>.zh-TW.md(every catalog page is bilingual). - Cross-link from related hubs (
See alsosection) and from any relevant reference landscape pages. - Run
make docs-build(strict mode catches missing translations and broken links).
For the workflow on adding individual entries to an existing hub (skills, MCPs, status changes), see Adding catalog entries.