[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C8XD148H2AA04P54FCMVAS":3,"skill-same:01M7C8XD148H2AA04P54FCMVAS":74},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7C8XD148H2AA04P54FCMVAS","data-layer-patterns-edho-ferdian",null,"Design and set up the data layer: Postgres schemas, Prisma, Redis caching and queues, and safe expand-contract migrations. Use for \"desain schema untuk X\", \"setup Prisma\u002FRedis\", \"strategi migration yang aman\", \"cache invalidation strategy\".","edhoferdian\u002FEEF","edhoferdian","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64404158?v=4","01M7C8538ZVVZWZEN1AW2MQXCV","Edho F","01M7C8539NS56BMJ4GXN8A47TQ",22,"MIT","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fdata-layer-patterns-edho-ferdian\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: data-layer-patterns-edho-ferdian\ndescription: >-\n  Design and set up the data layer: Postgres schemas, Prisma, Redis caching\n  and queues, and safe expand-contract migrations. Use for \"desain schema\n  untuk X\", \"setup Prisma\u002FRedis\", \"strategi migration yang aman\", \"cache\n  invalidation strategy\".\nmetadata:\n  last_reviewed: \"2026-10-27\"\n---\n\n# Data Layer Patterns — Edho Ferdian Mode (Skill Edition)\n\nYou are helping **design and set up** a data layer — schema, ORM, cache, and\nmigration strategy — before code exists to review. You think like an\nengineer sketching the shape of the system on a whiteboard: what tables,\nwhat access patterns, what will this look like at 10x the current data\nvolume, and what will break first.\n\n## Boundary — read this before doing anything else\n\n**This skill is authoring\u002Fdesign-time. It is not a review lens.**\n\n`code-review-edho-ferdian`'s `references\u002Fdatabase-lens.md` is a **review**\nlens: it runs against code\u002FSQL\u002Fmigrations that already exist, and finds\nproblems in them — missing indexes confirmed via `EXPLAIN ANALYZE`, RLS\npolicy mistakes, `SELECT *` in a diff. It activates automatically during a\ncode review when the scope touches `*.sql`, `migrations\u002F`, or an ORM schema.\n\nThis skill runs the opposite direction in time: it helps **decide what to\nbuild** before it exists — which columns, which indexes up front, which\ncaching strategy, which migration sequence — so that `database-lens` finds\nless to flag later. Concretely:\n\n- \"Review this migration for safety\" \u002F \"is this query slow\" \u002F \"audit my\n  schema\" → that's `database-lens` territory (via `code-review-edho-ferdian`\n  or `security-review-edho-ferdian` for the RLS\u002Fprivilege half). Point the\n  user there.\n- \"Help me design a schema for X\" \u002F \"how should I set up Prisma\u002FRedis\" \u002F\n  \"what's a safe migration strategy for adding this column\" \u002F \"how should I\n  invalidate this cache\" → that's this skill.\n\nIf a user asks you to review code that already exists, don't run this\nskill's content against it — hand off to `code-review-edho-ferdian`\n(database lens) or `security-review-edho-ferdian` instead. If they ask how\nto build something that doesn't exist yet, this skill is the right one, even\nif the conversation started from a review.\n\n## Scope map\n\n| Topic | Reference file |\n|---|---|\n| Postgres schema design decisions made at setup time | `references\u002Fpostgres.md` |\n| MySQL\u002FMariaDB schema, indexing, transaction, and replication design | `references\u002Fmysql.md` |\n| Prisma-specific setup, pooling, N+1, migration workflow | `references\u002Fprisma.md` |\n| Redis caching\u002Fqueue\u002Finvalidation strategy, anti-patterns | `references\u002Fredis.md` |\n| Cross-ORM migration strategy, expand-contract, reversibility | `references\u002Fmigrations.md` |\n| JPA\u002FJava persistence — entity design, fetch strategy, transactions, pagination, indexing, HikariCP pooling | `references\u002Fjpa.md` |\n\n`references\u002Fpostgres.md` is intentionally thin — most Postgres depth\nalready lives in `database-lens.md` as review criteria. Read that file's\nnote at the top before assuming something is missing here.\n\n`references\u002Fmysql.md` is a separate engine, not a Postgres reskin — InnoDB\nlocking, `utf8mb4` defaults, `ON DUPLICATE KEY UPDATE`, and replica-lag\nmechanics all diverge from Postgres. Use it whenever the target is MySQL or\nMariaDB rather than assuming `postgres.md` transfers; it starts with an\nexplicit statement of what's different and why.\n\n## Workflow\n\n1. **Identify what's being designed.** Schema for a new feature? A cache\n   layer for an existing hot path? A migration for a breaking schema change?\n   Route to the relevant reference file(s) — a real task often touches more\n   than one (e.g. \"add a new required column\" touches both\n   `prisma.md`\u002F`postgres.md` for the schema shape and `migrations.md` for\n   how to roll it out safely).\n2. **State the access pattern before the schema.** Don't design tables in\n   the abstract — ask (or infer from context) how the data will be read and\n   written: point lookups vs. range scans, read-heavy vs. write-heavy,\n   expected row-count order of magnitude. The right schema\u002Findex\u002Fcache\n   choice depends on this, and guessing wrong here is expensive to unwind\n   later.\n3. **Prefer the boring, provably-safe migration path.** When a schema\n   change could lock a large table or lose data if done in one step, default\n   to expand-contract (`references\u002Fmigrations.md`) rather than a single\n   destructive migration — even if the team is impatient. Say why, briefly.\n4. **Hand off setup output that `database-lens` will approve of.** Since\n   this skill and the review lens are two ends of the same pipeline, a\n   schema this skill helps design should not trip its own review findings\n   later (e.g. don't emit `int` PKs, `timestamp` without timezone, or\n   missing FK indexes — `postgres.md` and `database-lens.md` agree on these\n   defaults).\n\n## Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nCommunication to the user in Bahasa Indonesia; schema names, code, comments,\nand any generated files in English — fixed, never ask. Full contract:\n`skill-authoring-edho-ferdian` §7.\n\n## Global rules\n\n1. **Design-time, not review-time.** Never present this skill's output as a\n   review finding, and never run it against code presented for audit — hand\n   that to `code-review-edho-ferdian` \u002F `security-review-edho-ferdian`.\n2. **Access pattern first.** A schema or cache decision without a stated\n   access pattern is a guess — say so if one wasn't given.\n3. **Default to reversible, staged changes** for anything that touches a\n   table already holding data — see `references\u002Fmigrations.md`.\n4. **Don't duplicate `database-lens.md`.** If a review-time query\u002Findex\n   check applies, point there instead of re-deriving it here.\n5. **Security-sensitive schema decisions** (RLS, privilege, `GRANT`) belong\n   to `security-review-edho-ferdian` — this skill covers structure and\n   access patterns, not authorization design.\n","# Data Layer Patterns — Edho Ferdian Mode (Skill Edition)\n\nYou are helping **design and set up** a data layer — schema, ORM, cache, and\nmigration strategy — before code exists to review. You think like an\nengineer sketching the shape of the system on a whiteboard: what tables,\nwhat access patterns, what will this look like at 10x the current data\nvolume, and what will break first.\n\n## Boundary — read this before doing anything else\n\n**This skill is authoring\u002Fdesign-time. It is not a review lens.**\n\n`code-review-edho-ferdian`'s `references\u002Fdatabase-lens.md` is a **review**\nlens: it runs against code\u002FSQL\u002Fmigrations that already exist, and finds\nproblems in them — missing indexes confirmed via `EXPLAIN ANALYZE`, RLS\npolicy mistakes, `SELECT *` in a diff. It activates automatically during a\ncode review when the scope touches `*.sql`, `migrations\u002F`, or an ORM schema.\n\nThis skill runs the opposite direction in time: it helps **decide what to\nbuild** before it exists — which columns, which indexes up front, which\ncaching strategy, which migration sequence — so that `database-lens` finds\nless to flag later. Concretely:\n\n- \"Review this migration for safety\" \u002F \"is this query slow\" \u002F \"audit my\n  schema\" → that's `database-lens` territory (via `code-review-edho-ferdian`\n  or `security-review-edho-ferdian` for the RLS\u002Fprivilege half). Point the\n  user there.\n- \"Help me design a schema for X\" \u002F \"how should I set up Prisma\u002FRedis\" \u002F\n  \"what's a safe migration strategy for adding this column\" \u002F \"how should I\n  invalidate this cache\" → that's this skill.\n\nIf a user asks you to review code that already exists, don't run this\nskill's content against it — hand off to `code-review-edho-ferdian`\n(database lens) or `security-review-edho-ferdian` instead. If they ask how\nto build something that doesn't exist yet, this skill is the right one, even\nif the conversation started from a review.\n\n## Scope map\n\n| Topic | Reference file |\n|---|---|\n| Postgres schema design decisions made at setup time | `references\u002Fpostgres.md` |\n| MySQL\u002FMariaDB schema, indexing, transaction, and replication design | `references\u002Fmysql.md` |\n| Prisma-specific setup, pooling, N+1, migration workflow | `references\u002Fprisma.md` |\n| Redis caching\u002Fqueue\u002Finvalidation strategy, anti-patterns | `references\u002Fredis.md` |\n| Cross-ORM migration strategy, expand-contract, reversibility | `references\u002Fmigrations.md` |\n| JPA\u002FJava persistence — entity design, fetch strategy, transactions, pagination, indexing, HikariCP pooling | `references\u002Fjpa.md` |\n\n`references\u002Fpostgres.md` is intentionally thin — most Postgres depth\nalready lives in `database-lens.md` as review criteria. Read that file's\nnote at the top before assuming something is missing here.\n\n`references\u002Fmysql.md` is a separate engine, not a Postgres reskin — InnoDB\nlocking, `utf8mb4` defaults, `ON DUPLICATE KEY UPDATE`, and replica-lag\nmechanics all diverge from Postgres. Use it whenever the target is MySQL or\nMariaDB rather than assuming `postgres.md` transfers; it starts with an\nexplicit statement of what's different and why.\n\n## Workflow\n\n1. **Identify what's being designed.** Schema for a new feature? A cache\n   layer for an existing hot path? A migration for a breaking schema change?\n   Route to the relevant reference file(s) — a real task often touches more\n   than one (e.g. \"add a new required column\" touches both\n   `prisma.md`\u002F`postgres.md` for the schema shape and `migrations.md` for\n   how to roll it out safely).\n2. **State the access pattern before the schema.** Don't design tables in\n   the abstract — ask (or infer from context) how the data will be read and\n   written: point lookups vs. range scans, read-heavy vs. write-heavy,\n   expected row-count order of magnitude. The right schema\u002Findex\u002Fcache\n   choice depends on this, and guessing wrong here is expensive to unwind\n   later.\n3. **Prefer the boring, provably-safe migration path.** When a schema\n   change could lock a large table or lose data if done in one step, default\n   to expand-contract (`references\u002Fmigrations.md`) rather than a single\n   destructive migration — even if the team is impatient. Say why, briefly.\n4. **Hand off setup output that `database-lens` will approve of.** Since\n   this skill and the review lens are two ends of the same pipeline, a\n   schema this skill helps design should not trip its own review findings\n   later (e.g. don't emit `int` PKs, `timestamp` without timezone, or\n   missing FK indexes — `postgres.md` and `database-lens.md` agree on these\n   defaults).\n\n## Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nCommunication to the user in Bahasa Indonesia; schema names, code, comments,\nand any generated files in English — fixed, never ask. Full contract:\n`skill-authoring-edho-ferdian` §7.\n\n## Global rules\n\n1. **Design-time, not review-time.** Never present this skill's output as a\n   review finding, and never run it against code presented for audit — hand\n   that to `code-review-edho-ferdian` \u002F `security-review-edho-ferdian`.\n2. **Access pattern first.** A schema or cache decision without a stated\n   access pattern is a guess — say so if one wasn't given.\n3. **Default to reversible, staged changes** for anything that touches a\n   table already holding data — see `references\u002Fmigrations.md`.\n4. **Don't duplicate `database-lens.md`.** If a review-time query\u002Findex\n   check applies, point there instead of re-deriving it here.\n5. **Security-sensitive schema decisions** (RLS, privilege, `GRANT`) belong\n   to `security-review-edho-ferdian` — this skill covers structure and\n   access patterns, not authorization design.\n",{"name":5,"metadata":24,"description":7},{"last_reviewed":25},"2026-10-27","main","533d32ad55c92d40fbabe93cbe21fe048598fe5a",".kiro\u002Fskills\u002Fdata-layer-patterns-edho-ferdian",0,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF","https:\u002F\u002Fgithub.com\u002Fedhoferdian","Elevating ideas through AI, rising from humble beginnings to mastering the frontiers of the web. Every line of code is open-sourced on GitHub, inviting you to f","2026-10-30 03:34:17",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add edhoferdian\u002FEEF --skill data-layer-patterns-edho-ferdian",{"tool":40,"command":41},"bunx","bunx skills add edhoferdian\u002FEEF --skill data-layer-patterns-edho-ferdian",{"tool":43,"command":44},"pnpm","pnpm dlx skills add edhoferdian\u002FEEF --skill data-layer-patterns-edho-ferdian","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fdata-layer-patterns-edho-ferdian\u002FSKILL.md",true,[48,54,58,62,66,70],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fjpa.md","REFERENCE","参考文档",10089,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fdata-layer-patterns-edho-ferdian\u002Freferences\u002Fjpa.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fmigrations.md",9293,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fdata-layer-patterns-edho-ferdian\u002Freferences\u002Fmigrations.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fmysql.md",13698,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fdata-layer-patterns-edho-ferdian\u002Freferences\u002Fmysql.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fpostgres.md",5543,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fdata-layer-patterns-edho-ferdian\u002Freferences\u002Fpostgres.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fprisma.md",8820,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fdata-layer-patterns-edho-ferdian\u002Freferences\u002Fprisma.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fredis.md",8427,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fdata-layer-patterns-edho-ferdian\u002Freferences\u002Fredis.md",[75,82,89,96,103,110],{"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},"01M7C9FY2EWE5NB7M3YW0KJX62","video-style-edho-ferdian","Measure a reference video's look and pacing (colour grade as a 3D LUT, cut rhythm, overlays) and reproduce it: grade, cut and composite new footage, verify numerically, hand off an NLE timeline. Use for \"tiru look video ini\", \"samakan grading\", \"bikin video dengan gaya referensi\", \"LUT dari referensi\", \"cut rhythm\".","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-style-edho-ferdian\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},"01M7C9FT74P7JXGQ73116B9WS1","test-authoring-edho-ferdian","Write unit and component tests well: React Testing Library, pytest, Go and Vue, plus regression-test patterns. Use for \"tulis test untuk component ini\", \"bagaimana test hook ini\", \"test yang bagus untuk fitur X\", \"tulis test pytest\u002FGo\u002FVue\", or dev-kickoff's TEST stage.","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Ftest-authoring-edho-ferdian\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},"01M7C9FMPE9W76FS7S8ZZ48ARE","system-design-edho-ferdian","Mid-project architecture decisions: ADRs, trade-off analysis, non-functional requirements, scaling tiers and blast radius. Use for \"desain arsitektur\", \"keputusan teknis besar\", \"bikin ADR\", \"trade-off antara X dan Y\", \"microservices atau monolith\", \"apa yang rusak kalau X diubah\", or a capacity question.","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fsystem-design-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7C9FETATAHKG5WKPT4AP1A2","spec-mining-edho-ferdian","Extract behavioural specs from a codebase with none: WHEN\u002FTHEN requirements and invariants, each anchored to the code that enforces it, unclear behaviour recorded as uncertainty. Use for \"ekstrak spec\", \"buat spec dari kode\", \"reverse-engineer the spec\", \"repo ini tidak ada dokumentasi\", or a missing BEHAVIOR_SPEC in dev-kickoff.","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fspec-mining-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7C9F93YCXFCVRDG4S5QFAH4","skill-authoring-edho-ferdian","Create and govern this ecosystem's skills: search before building, a quality bar, compliance checks, promoting repeated principles to rules, and packaging dist\u002F*.skill. Use for \"bikin skill baru\", \"ada skill buat X gak\", \"fork skill ini\", \"skill gue kepake gak sih\", \"package skill ini\", \"buatkan .skill-nya\".","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring-edho-ferdian\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7C9F4XZJ59R0GS4YEP4E1RD","skill-audit-edho-ferdian","Audit this repo's skills\u002F for staleness, redundancy, broken cross-references and weak descriptions (not the ~\u002F.claude setup: that is config-hygiene). Use for \"audit skill saya\", \"cek skill yang sudah dibuat\", \"ada yang redundan gak\", \"skill mana yang basi\".","https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002Fskills\u002Fskill-audit-edho-ferdian\u002FSKILL.md",[],[]]