OpenTDX Engineering

Scope

Use this skill for finance data infrastructure work, not trading decisions. It covers opentdx parser architecture, binary protocol reverse engineering, MCP tool behavior, TypeScript parser alignment, and viewer/gateway integration.

If the user asks for market analysis, use evf-stock-skill instead. If the user asks why a quote/K-line/tool/parser is wrong, times out, returns null, serializes badly, or disagrees with another implementation, use this skill.

Routing

For opentdx architecture, bitmap presets, unified interface design, client adaptation, or known parser bugs, read:

• references/legacy-opentdx-architecture.md
• references/trading-system-stack.md
• references/tdx-board-symbols.md

For binary protocol reverse engineering, unknown bitmap bits, msg_id mapping, or cross-market field discovery, read:

• references/legacy-protocol-reverse-engineering.md
• references/msg-id-registry.md

For TypeScript parser parity, test alignment, or parser audit tasks, read:

• references/ts-parser-alignment-checklist.md
• references/ts-parser-audit-2026-05-17.md
• references/ts-project-structure.md

For web viewer, FastAPI gateway, URLSearchParams, polling, or frontend integration, read:

• references/trading-system-stack.md
• references/opentdx-viewer-integration.md

Engineering Rules

Prefer reproducing with the smallest parser, msg_id, and market/code pair that shows the mismatch.

When comparing Python and TypeScript parsers, verify request byte length, msg_id, customize fields, compression flag, response frame layout, and final decoded field offsets before renaming fields.

Do not assume a quote server failure is a parser bug. Separate network timeout, server incompatibility, empty-market response, serialization failure, and true decode mismatch.

When a live quote call is unstable, preserve the raw request, raw response length, hex preview, parser name, market, code, server, and timestamp. These become regression fixtures.

For MCP serialization bugs, document both the user-facing tool parameters and the underlying TdxClient call. Many failures come from int/string coercion, list schema shape, or batch mode instability.

Output

Lead with a diagnosis:

问题类型: parser / transport / MCP serialization / server data / test expectation
复现: command or tool call
证据: raw bytes, field offset, error text, comparison result
修复: minimal code or test change
回归: exact test or fixture to add

Keep trading recommendations out of this skill. When infrastructure work changes data semantics used by trading workflows, update the trading skill references afterward.