xint-xpulse-complementary-dual-tool-architecture
X-Pulse (Python, 3-phase pipeline, Jaccard dedup, geo-proxy) and xint (TypeScript/Bun, 56 commands) serve different purposes and must coexist. Replacing X-Pulse with xint loses the superior research pipeline; replacing xint with ported Python code creates perpetual maintenance burden. The correct pattern is a unified skill that routes ALL X/Twitter tasks to the right underlying tool transparently.
Related
- x-intelligence-dual-tool-architecture-decision
- 2026-04-04-oracle-001-self-architecture-analysis
- xint-vs-xpulse-capability-gap-56-commands
- claude-code-as-ops-team-changes-aws-architecture-decision
- zero-maintenance-means-claude-code-manages-not-saas
- x-pulse-xint-complementary-not-replacement
- xpulse-vs-xint-capability-routing-split
- xpulse-xint-complementary-not-replacement-architecture
- xpulse-and-xint-complementary-not-replacement