[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SP7AZ7NGYBKXDBWEZ71J6":3,"skill-same:01M79SP7AZ7NGYBKXDBWEZ71J6":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},"01M79SP7AZ7NGYBKXDBWEZ71J6","kafka-architect",null,"Architect-level Kafka design — topic and partition strategy, key choice and ordering guarantees, replication and min-ISR, retention and compaction, consumer groups and rebalancing, and the lag and disk failures that take a cluster down. Use when Kafka (or MSK\u002FConfluent) carries event data.","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\u002Fevent-streams-architect\u002Fkafka-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: kafka-architect\ndescription: Architect-level Kafka design — topic and partition strategy, key choice and ordering guarantees, replication and min-ISR, retention and compaction, consumer groups and rebalancing, and the lag and disk failures that take a cluster down. Use when Kafka (or MSK\u002FConfluent) carries event data.\nlicense: MIT\ncompatibility: Apache Kafka, MSK, Confluent Cloud, Redpanda\nmetadata:\n  crusor-domain: data-engineering-architect\n  crusor-path: data-engineering-architect\u002Fevent-streams-architect\u002Fkafka-architect\n  crusor-origin: original\n  crusor-sources: \"kafka.apache.org\u002Fdocumentation; docs.confluent.io\u002Fplatform\u002Fcurrent; docs.aws.amazon.com\u002Fmsk\"\n  crusor-triggers: \"kafka, topic, partition, consumer group, offset, isr, retention, compaction, broker, msk, rebalance\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Kafka Architect\n\nKafka is **an ordered log per partition**. Every design decision follows from the\nkey: it decides ordering, parallelism, and hot spots simultaneously.\n\n## When to use\n\n- Event streams with multiple consumers and replay.\n- Durable buffering between producers and consumers.\n- Event sourcing or log-based integration.\n\n## When NOT to use\n\n- Simple task queues (SQS-style semantics are simpler).\n- Low volume where an HTTP call or a table would do.\n\n## Decision 1 — Topics and partitions\n\n- One topic per event type with a stable schema; not one topic for everything.\n- Partitions = target throughput ÷ per-partition throughput; more partitions mean more\n  parallelism but slower rebalances and more files.\n- Ordering is guaranteed **within a partition only** — if you need per-entity order,\n  key by entity.\n- Partition count is easy to increase and hard to decrease; start conservative and\n  leave headroom.\n\n## Decision 2 — Keys\n\n| Key | Consequence |\n|---|---|\n| entity id | per-entity order, uneven partitions if skewed |\n| none (round-robin) | even spread, no ordering |\n| tenant id | isolation and order per tenant, hot tenants |\n| composite (tenant+id) | spread with intra-entity order |\n\n- A skewed key creates a hot partition: one broker saturates while others idle.\n  Check key distribution against real data before launch.\n\n## Decision 3 — Durability\n\n- Replication factor 3, `min.insync.replicas=2`, `acks=all` for anything that must\n  not be lost.\n- `unclean.leader.election=false` — availability is not worth silent data loss.\n- Producer idempotence on; transactions only when consuming and producing atomically.\n- Retention by time and size; compacted topics for entity state (latest per key).\n\n## Decision 4 — Consumers\n\n- One consumer group per application; partitioning of work across members is\n  automatic.\n- Rebalances stop consumption — use cooperative\u002Fsticky assignment and static\n  membership for long-running consumers.\n- Commit offsets after processing, not before; at-least-once is the honest default.\n- Lag in **time**, not messages: offset lag hides a slow consumer.\n\n## Decision 5 — Operations\n\n- Monitor: under-replicated partitions, offline partitions, ISR shrinks, disk usage,\n  controller changes, consumer lag.\n- Disk is the classic outage: retention × throughput must fit with headroom; alert at\n  70%.\n- Broker upgrades and rolling restarts need a plan for the partition movement they\n  trigger.\n- Schema registry with backward-compatible evolution (`event-schema-architect`).\n\n## Failure modes at scale\n\n- Key by a low-cardinality field; one partition takes 60% of traffic.\n- Retention set to 7 days on a topic with a 10-day backlog after an incident.\n- Consumer commits before processing; an outage loses a batch.\n- Partition count increased during peak; rebalance storm for an hour.\n- Disk full on one broker because replicas are unevenly distributed.\n\n## Verification receipts\n\n1. Topic inventory: partitions, replication, retention, cleanup policy.\n2. Key-distribution analysis on real data.\n3. Failure test: broker killed, production continues, no data loss.\n4. Lag dashboard in seconds with alerting.\n5. Disk capacity model with growth projection and alert thresholds.\n","# Kafka Architect\n\nKafka is **an ordered log per partition**. Every design decision follows from the\nkey: it decides ordering, parallelism, and hot spots simultaneously.\n\n## When to use\n\n- Event streams with multiple consumers and replay.\n- Durable buffering between producers and consumers.\n- Event sourcing or log-based integration.\n\n## When NOT to use\n\n- Simple task queues (SQS-style semantics are simpler).\n- Low volume where an HTTP call or a table would do.\n\n## Decision 1 — Topics and partitions\n\n- One topic per event type with a stable schema; not one topic for everything.\n- Partitions = target throughput ÷ per-partition throughput; more partitions mean more\n  parallelism but slower rebalances and more files.\n- Ordering is guaranteed **within a partition only** — if you need per-entity order,\n  key by entity.\n- Partition count is easy to increase and hard to decrease; start conservative and\n  leave headroom.\n\n## Decision 2 — Keys\n\n| Key | Consequence |\n|---|---|\n| entity id | per-entity order, uneven partitions if skewed |\n| none (round-robin) | even spread, no ordering |\n| tenant id | isolation and order per tenant, hot tenants |\n| composite (tenant+id) | spread with intra-entity order |\n\n- A skewed key creates a hot partition: one broker saturates while others idle.\n  Check key distribution against real data before launch.\n\n## Decision 3 — Durability\n\n- Replication factor 3, `min.insync.replicas=2`, `acks=all` for anything that must\n  not be lost.\n- `unclean.leader.election=false` — availability is not worth silent data loss.\n- Producer idempotence on; transactions only when consuming and producing atomically.\n- Retention by time and size; compacted topics for entity state (latest per key).\n\n## Decision 4 — Consumers\n\n- One consumer group per application; partitioning of work across members is\n  automatic.\n- Rebalances stop consumption — use cooperative\u002Fsticky assignment and static\n  membership for long-running consumers.\n- Commit offsets after processing, not before; at-least-once is the honest default.\n- Lag in **time**, not messages: offset lag hides a slow consumer.\n\n## Decision 5 — Operations\n\n- Monitor: under-replicated partitions, offline partitions, ISR shrinks, disk usage,\n  controller changes, consumer lag.\n- Disk is the classic outage: retention × throughput must fit with headroom; alert at\n  70%.\n- Broker upgrades and rolling restarts need a plan for the partition movement they\n  trigger.\n- Schema registry with backward-compatible evolution (`event-schema-architect`).\n\n## Failure modes at scale\n\n- Key by a low-cardinality field; one partition takes 60% of traffic.\n- Retention set to 7 days on a topic with a 10-day backlog after an incident.\n- Consumer commits before processing; an outage loses a batch.\n- Partition count increased during peak; rebalance storm for an hour.\n- Disk full on one broker because replicas are unevenly distributed.\n\n## Verification receipts\n\n1. Topic inventory: partitions, replication, retention, cleanup policy.\n2. Key-distribution analysis on real data.\n3. Failure test: broker killed, production continues, no data loss.\n4. Lag dashboard in seconds with alerting.\n5. Disk capacity model with growth projection and alert thresholds.\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\u002Fevent-streams-architect\u002Fkafka-architect","data-engineering-architect","original","kafka.apache.org\u002Fdocumentation; docs.confluent.io\u002Fplatform\u002Fcurrent; docs.aws.amazon.com\u002Fmsk","kafka, topic, partition, consumer group, offset, isr, retention, compaction, broker, msk, rebalance","2026-10-30","Apache Kafka, MSK, Confluent Cloud, Redpanda","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fdata-engineering-architect\u002Fevent-streams-architect\u002Fkafka-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 kafka-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill kafka-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill kafka-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdata-engineering-architect\u002Fevent-streams-architect\u002Fkafka-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",[],[]]