[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SQ3CSTHR67M4RGP6SDPZ5":3,"skill-same:01M79SQ3CSTHR67M4RGP6SDPZ5":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79SQ3CSTHR67M4RGP6SDPZ5","cdc-architect",null,"Architect-level change data capture — log-based versus query-based capture, Debezium-style connectors, schema history, tombstones and deletes, exactly-once into a sink, snapshot-then-stream bootstrap, and the operational failure modes that silently diverge replicas. Use when a replica must track an operational database.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdata-engineering-architect\u002Fingestion-architect\u002Fcdc-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cdc-architect\ndescription: Architect-level change data capture — log-based versus query-based capture, Debezium-style connectors, schema history, tombstones and deletes, exactly-once into a sink, snapshot-then-stream bootstrap, and the operational failure modes that silently diverge replicas. Use when a replica must track an operational database.\nlicense: MIT\ncompatibility: Debezium, Kafka Connect, Postgres logical replication, DynamoDB Streams\nmetadata:\n  crusor-domain: data-engineering-architect\n  crusor-path: data-engineering-architect\u002Fingestion-architect\u002Fcdc-architect\n  crusor-origin: original\n  crusor-sources: \"debezium.io\u002Fdocumentation; postgresql.org\u002Fdocs\u002Fcurrent\u002Flogical-replication.html; docs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FStreams.html\"\n  crusor-triggers: \"cdc, change data capture, debezium, logical replication, wal, binlog, tombstones, snapshot, replica divergence\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# CDC Architect\n\nCDC is **a second copy of your database with a lag and its own failure modes**. The\narchitecture question is how divergence is detected before a human notices.\n\n## When to use\n\n- Analytics or search must track an OLTP database without querying it directly.\n- Row-level changes matter (updates and deletes, not just inserts).\n- Polling by `updated_at` cannot keep up or misses deletes.\n\n## When NOT to use\n\n- Small tables where a nightly full extract is trivial.\n- The source has no changelog and no reliable ordering column.\n\n## Decision 1 — Capture method\n\n| Method | Trade-off |\n|---|---|\n| log-based (WAL\u002Fbinlog) | complete, ordered, no query load; needs privileges and slots |\n| query-based (timestamp\u002Fwatermark) | simple; misses deletes and hard deletes between polls |\n| trigger-based | complete; adds write load to the source |\n| dual-write from app | no lag, but app now owns consistency — avoid |\n\n- Log-based is the default for correctness; the operational cost is a replication\n  slot you must monitor.\n- Query-based is acceptable only for append-mostly, soft-delete data.\n\n## Decision 2 — Bootstrap\n\n```\nconsistent snapshot → stream from that snapshot's LSN\u002Fposition → replay deltas\n```\n\n- Snapshot and stream must be bound to the same position, or rows inserted during the\n  snapshot are lost or doubled.\n- Incremental snapshots for large tables avoid a long lock window.\n- Re-snapshotting a table means a coordinated swap, not a rebuild in place.\n\n## Decision 3 — Events\n\n- Event contains: before, after, op type, source position, timestamp, schema version.\n- Deletes need tombstones or an explicit delete event — otherwise \"missing\" is\n  ambiguous downstream.\n- Keying by primary key lets downstream compact to current state.\n- Ordering is per key, not global; a consumer that assumes global order is broken.\n\n## Decision 4 — Sinks\n\n- Idempotent upserts keyed by primary key and event position.\n- Exactly-once is only within a transactional sink; otherwise design for duplicates.\n- Schema changes propagate: a new source column must not break the sink. Additive\n  safe, renames\u002Fdrops need a versioned migration.\n- DDL changes are a common outage: capture them and alert.\n\n## Decision 5 — Operations\n\n- Monitor: replication slot lag, connector lag (seconds not rows), error counts, and\n  schema-history failures.\n- A stalled connector holds WAL and can fill the source disk — the most dangerous\n  failure in this design.\n- Slot retention must be bounded and alerted; a dropped connector must release its\n  slot.\n- Reconcile periodically: row counts and checksums per table between source and sink.\n\n## Failure modes at scale\n\n- Connector down for a day; WAL fills the primary disk and takes down production.\n- Deletes never captured; the replica grows forever with dead rows.\n- Snapshot taken with concurrent writes and no position binding; silent duplicates.\n- Schema rename propagated; downstream jobs fail with confusing null columns.\n- Lag measured by offset, hiding a 40-minute real delay.\n\n## Verification receipts\n\n1. Capture method chosen with the correctness rationale.\n2. Lag dashboard in seconds with an alert threshold.\n3. Delete propagation test: row removed at source, removed downstream.\n4. Reconciliation query comparing counts\u002Fchecksums per table.\n5. Slot retention and disk-growth alarm verified.\n","# CDC Architect\n\nCDC is **a second copy of your database with a lag and its own failure modes**. The\narchitecture question is how divergence is detected before a human notices.\n\n## When to use\n\n- Analytics or search must track an OLTP database without querying it directly.\n- Row-level changes matter (updates and deletes, not just inserts).\n- Polling by `updated_at` cannot keep up or misses deletes.\n\n## When NOT to use\n\n- Small tables where a nightly full extract is trivial.\n- The source has no changelog and no reliable ordering column.\n\n## Decision 1 — Capture method\n\n| Method | Trade-off |\n|---|---|\n| log-based (WAL\u002Fbinlog) | complete, ordered, no query load; needs privileges and slots |\n| query-based (timestamp\u002Fwatermark) | simple; misses deletes and hard deletes between polls |\n| trigger-based | complete; adds write load to the source |\n| dual-write from app | no lag, but app now owns consistency — avoid |\n\n- Log-based is the default for correctness; the operational cost is a replication\n  slot you must monitor.\n- Query-based is acceptable only for append-mostly, soft-delete data.\n\n## Decision 2 — Bootstrap\n\n```\nconsistent snapshot → stream from that snapshot's LSN\u002Fposition → replay deltas\n```\n\n- Snapshot and stream must be bound to the same position, or rows inserted during the\n  snapshot are lost or doubled.\n- Incremental snapshots for large tables avoid a long lock window.\n- Re-snapshotting a table means a coordinated swap, not a rebuild in place.\n\n## Decision 3 — Events\n\n- Event contains: before, after, op type, source position, timestamp, schema version.\n- Deletes need tombstones or an explicit delete event — otherwise \"missing\" is\n  ambiguous downstream.\n- Keying by primary key lets downstream compact to current state.\n- Ordering is per key, not global; a consumer that assumes global order is broken.\n\n## Decision 4 — Sinks\n\n- Idempotent upserts keyed by primary key and event position.\n- Exactly-once is only within a transactional sink; otherwise design for duplicates.\n- Schema changes propagate: a new source column must not break the sink. Additive\n  safe, renames\u002Fdrops need a versioned migration.\n- DDL changes are a common outage: capture them and alert.\n\n## Decision 5 — Operations\n\n- Monitor: replication slot lag, connector lag (seconds not rows), error counts, and\n  schema-history failures.\n- A stalled connector holds WAL and can fill the source disk — the most dangerous\n  failure in this design.\n- Slot retention must be bounded and alerted; a dropped connector must release its\n  slot.\n- Reconcile periodically: row counts and checksums per table between source and sink.\n\n## Failure modes at scale\n\n- Connector down for a day; WAL fills the primary disk and takes down production.\n- Deletes never captured; the replica grows forever with dead rows.\n- Snapshot taken with concurrent writes and no position binding; silent duplicates.\n- Schema rename propagated; downstream jobs fail with confusing null columns.\n- Lag measured by offset, hiding a 40-minute real delay.\n\n## Verification receipts\n\n1. Capture method chosen with the correctness rationale.\n2. Lag dashboard in seconds with an alert threshold.\n3. Delete propagation test: row removed at source, removed downstream.\n4. Reconciliation query comparing counts\u002Fchecksums per table.\n5. Slot retention and disk-growth alarm verified.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"data-engineering-architect\u002Fingestion-architect\u002Fcdc-architect","data-engineering-architect","original","debezium.io\u002Fdocumentation; postgresql.org\u002Fdocs\u002Fcurrent\u002Flogical-replication.html; docs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\u002FStreams.html","cdc, change data capture, debezium, logical replication, wal, binlog, tombstones, snapshot, replica divergence","2026-10-30","Debezium, Kafka Connect, Postgres logical replication, DynamoDB Streams","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fdata-engineering-architect\u002Fingestion-architect\u002Fcdc-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill cdc-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill cdc-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill cdc-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdata-engineering-architect\u002Fingestion-architect\u002Fcdc-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]