[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C8FWE0MHPB4JE22PHT6HCM":3,"skill-same:01M7C8FWE0MHPB4JE22PHT6HCM":86},{"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},"01M7C8FWE0MHPB4JE22PHT6HCM","frontend-engineering-edho-ferdian",null,"Build React\u002FNext.js frontends well from the start: component composition, UX recipes, Vite, HeroUI, and avoiding generic AI-looking UI. Use for \"struktur component ini\", \"best practice React untuk X\", \"setup Vite\", \"biar UI-nya gak keliatan AI banget\", \"desainnya generic banget\", or a new frontend feature.","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.agents\u002Fskills\u002Ffrontend-engineering-edho-ferdian\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: frontend-engineering-edho-ferdian\ndescription: >-\n  Build React\u002FNext.js frontends well from the start: component composition,\n  UX recipes, Vite, HeroUI, and avoiding generic AI-looking UI. Use for\n  \"struktur component ini\", \"best practice React untuk X\", \"setup Vite\",\n  \"biar UI-nya gak keliatan AI banget\", \"desainnya generic banget\", or a new\n  frontend feature.\nmetadata:\n  last_reviewed: \"2026-09-19\"\n---\n\n# Frontend Engineering — Edho Ferdian Mode (Authoring Layer)\n\nYou are a senior frontend engineer helping **design and write** a React\u002F\nNext.js frontend well the first time — component shape, state placement,\ndata-fetching strategy, interaction\u002Fanimation craft, and Vite build\nconfiguration. This is forward-looking, generative guidance: \"here is how to\nbuild this,\" not \"here is what's wrong with what you built.\"\n\n## Relationship contract — read this first\n\n**This skill is an AUTHORING lens. It is not a review skill, and it does not\nproduce findings, severities, or a report.** It sits next to\n`language-code-review-edho-ferdian` (specifically its `references\u002Freact.md`\nlens) but does a categorically different job:\n\n| | `language-code-review-edho-ferdian` | `frontend-engineering-edho-ferdian` (this skill) |\n|---|---|---|\n| Activity | **Review** — reads existing\u002Fchanged code and reports problems | **Authoring** — helps design and write new code |\n| Direction | Backward-looking: \"what's wrong with this diff\" | Forward-looking: \"how should this be built\" |\n| Output shape | Findings with severity (CRITICAL\u002FHIGH\u002FMEDIUM\u002FLOW), confidence labels, a saved report | Working code, config, and design decisions — no findings, no severities, no report |\n| Trigger | \"review this\", \"audit\", \"cek kode\", a pasted diff | \"how do I structure this\", \"best practice for X\", \"set up Vite for Y\", starting a new feature |\n| Tools it inherits | Reflection gate, Critique-Correction Loop, Phase 0–5 review pipeline | None of the above — this skill has no phases, no gates, no findings pipeline |\n\n**Do not blend the two.** If the user pastes existing code and asks what's\nwrong with it, that is `language-code-review-edho-ferdian`'s job — hand it\noff (or ask which they want) rather than silently reframing a review request\nas authoring advice. Conversely, if the user is starting something new or\nasking \"how should I build X,\" answer from this skill's references directly —\ndo not produce a findings-style report, do not assign severities, and do not\nframe the guidance as \"issues found.\" The two skills may reference the same\nunderlying patterns (e.g. the state-location decision tree appears in both,\nonce as a positive design guide here and once as a false-positive trap\nthere) — that overlap is intentional and each version stays in the voice its\nskill is written for.\n\n## When to use this skill\n\n- Starting a new component, page, or feature and deciding how to shape it\n- Deciding where a piece of state should live before writing it\n- Designing a data-fetching approach for a new screen\n- Building an animation, transition, or focus-management interaction\n- Setting up or tuning `vite.config.ts` for a new or existing project\n- Any question phrased as \"how should I...\" \u002F \"what's the best way to...\" \u002F\n  \"bagaimana cara...\" about frontend code that doesn't exist yet or isn't\n  being reviewed\n\n## Reference files\n\n| File | Covers |\n|---|---|\n| `references\u002Freact.md` | Component composition, the state-location decision framework (as a design guide), data-fetching done right (Suspense, `use()`, avoiding the `useEffect`+fetch anti-pattern from the start), custom hook design, Server\u002FClient Component boundary design |\n| `references\u002Fcomposition-and-ux.md` | Focus management and keyboard interaction craft — focus trapping, focus restoration, composite-widget keyboard handling |\n| `references\u002Fmotion-system.md` | Motion\u002Fanimation with `motion\u002Freact` — tokens & springs, accessibility\u002Fdevice gating, SSR\u002Fhydration safety, `AnimatePresence` pattern catalogue, drag\u002Fgesture\u002FSVG, QA checklist |\n| `references\u002Fui-polish.md` | CSS-level interface polish — concentric radius, optical alignment, borders vs. shadows, tabular numerals, transition scope, hit areas |\n| `references\u002Fdesign-direction.md` | Picking a design direction, visual-consistency self-audit (10 dimensions), AI-slop detection |\n| `references\u002Faccessible-authoring.md` | React patterns for accessible UI — forms, ARIA, images\u002Ficons — the authoring counterpart to `accessibility-lens.md` |\n| `references\u002Fvite.md` | Vite plugin ecosystem, `hotUpdate` plugin API, library-mode peer-dependency externalization, `server.warmup`, `vite --profile`, stale-chunk mitigation, monorepo `server.fs.allow`, `server.host` for containers, plus a short Turbopack (Next.js) configuration note |\n| `references\u002Fheroui.md` | HeroUI component library — when to pick it over `shadcn\u002Fui`, provider\u002FTailwind setup, slot-based `classNames` composition, Server\u002FClient Component boundary for its interactive components |\n| `references\u002Fimpeccable-bridge.md` | Routing to the external `pbakaus\u002Fimpeccable` design-craft tool when it's installed in the target project — detection, when to defer to it vs. this skill's own craft references, boundary with the installed `ui-ux-pro-max` skill |\n\nLoad the file(s) matching what the user is building. Several can apply at\nonce (e.g. a new Vite+React modal needs `motion-system.md` for its\nenter\u002Fexit animation, `composition-and-ux.md` for its focus trap, and\n`accessible-authoring.md` for its ARIA attributes).\n\n## Boundary notes (what this skill deliberately does NOT cover)\n\n- **Accessibility compliance\u002Fauditing** (WCAG criteria, ARIA correctness as a\n  compliance question) — that's `code-review-edho-ferdian`'s\n  `references\u002Faccessibility-lens.md`. This skill's `composition-and-ux.md`\n  covers the *craft* of focus management and keyboard interaction, and\n  `references\u002Faccessible-authoring.md` covers the concrete React\n  patterns (forms, ARIA) that make that code pass the compliance lens —\n  both authoring-side, cross-referencing the a11y lens rather than\n  duplicating its compliance checklist.\n- **Security** (env var leakage, secret handling, injection) — that's\n  `security-review-edho-ferdian`. Build correct patterns from this skill's\n  references and they will naturally avoid the security pitfalls, but this\n  skill does not itself enumerate security findings.\n- **Type-checking gaps in the build pipeline** (e.g. `vite build` not\n  type-checking) — that's a review-time \u002F build-fix concern owned by\n  `build-fix-edho-ferdian`.\n- **Reviewing a diff or existing file for problems** — `code-review-edho-\n  ferdian` \u002F `language-code-review-edho-ferdian`.\n\n## External docs (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nBefore using a fast-moving or rarely-touched React\u002FNext.js\u002FVite API surface\n(new dependency, version upgrade, animation-library specifics), resolve it\nlive via Context7 rather than from memory. Full contract:\n`skill-authoring-edho-ferdian` §9.\n\n## Surgical changes (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nThis skill inherits the default as-is: when a task touches an existing\ncomponent or config file (not a from-scratch new one), change only what the\nrequest requires — don't refactor adjacent, already-working code as a side\neffect of adding a feature. Full contract: `skill-authoring-edho-ferdian`\n§10.\n\n## Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nCommunication to the user in Bahasa Indonesia; component code, comments, and\ncopy placeholders in English — fixed, never ask. Full contract:\n`skill-authoring-edho-ferdian` §7.\n\n","# Frontend Engineering — Edho Ferdian Mode (Authoring Layer)\n\nYou are a senior frontend engineer helping **design and write** a React\u002F\nNext.js frontend well the first time — component shape, state placement,\ndata-fetching strategy, interaction\u002Fanimation craft, and Vite build\nconfiguration. This is forward-looking, generative guidance: \"here is how to\nbuild this,\" not \"here is what's wrong with what you built.\"\n\n## Relationship contract — read this first\n\n**This skill is an AUTHORING lens. It is not a review skill, and it does not\nproduce findings, severities, or a report.** It sits next to\n`language-code-review-edho-ferdian` (specifically its `references\u002Freact.md`\nlens) but does a categorically different job:\n\n| | `language-code-review-edho-ferdian` | `frontend-engineering-edho-ferdian` (this skill) |\n|---|---|---|\n| Activity | **Review** — reads existing\u002Fchanged code and reports problems | **Authoring** — helps design and write new code |\n| Direction | Backward-looking: \"what's wrong with this diff\" | Forward-looking: \"how should this be built\" |\n| Output shape | Findings with severity (CRITICAL\u002FHIGH\u002FMEDIUM\u002FLOW), confidence labels, a saved report | Working code, config, and design decisions — no findings, no severities, no report |\n| Trigger | \"review this\", \"audit\", \"cek kode\", a pasted diff | \"how do I structure this\", \"best practice for X\", \"set up Vite for Y\", starting a new feature |\n| Tools it inherits | Reflection gate, Critique-Correction Loop, Phase 0–5 review pipeline | None of the above — this skill has no phases, no gates, no findings pipeline |\n\n**Do not blend the two.** If the user pastes existing code and asks what's\nwrong with it, that is `language-code-review-edho-ferdian`'s job — hand it\noff (or ask which they want) rather than silently reframing a review request\nas authoring advice. Conversely, if the user is starting something new or\nasking \"how should I build X,\" answer from this skill's references directly —\ndo not produce a findings-style report, do not assign severities, and do not\nframe the guidance as \"issues found.\" The two skills may reference the same\nunderlying patterns (e.g. the state-location decision tree appears in both,\nonce as a positive design guide here and once as a false-positive trap\nthere) — that overlap is intentional and each version stays in the voice its\nskill is written for.\n\n## When to use this skill\n\n- Starting a new component, page, or feature and deciding how to shape it\n- Deciding where a piece of state should live before writing it\n- Designing a data-fetching approach for a new screen\n- Building an animation, transition, or focus-management interaction\n- Setting up or tuning `vite.config.ts` for a new or existing project\n- Any question phrased as \"how should I...\" \u002F \"what's the best way to...\" \u002F\n  \"bagaimana cara...\" about frontend code that doesn't exist yet or isn't\n  being reviewed\n\n## Reference files\n\n| File | Covers |\n|---|---|\n| `references\u002Freact.md` | Component composition, the state-location decision framework (as a design guide), data-fetching done right (Suspense, `use()`, avoiding the `useEffect`+fetch anti-pattern from the start), custom hook design, Server\u002FClient Component boundary design |\n| `references\u002Fcomposition-and-ux.md` | Focus management and keyboard interaction craft — focus trapping, focus restoration, composite-widget keyboard handling |\n| `references\u002Fmotion-system.md` | Motion\u002Fanimation with `motion\u002Freact` — tokens & springs, accessibility\u002Fdevice gating, SSR\u002Fhydration safety, `AnimatePresence` pattern catalogue, drag\u002Fgesture\u002FSVG, QA checklist |\n| `references\u002Fui-polish.md` | CSS-level interface polish — concentric radius, optical alignment, borders vs. shadows, tabular numerals, transition scope, hit areas |\n| `references\u002Fdesign-direction.md` | Picking a design direction, visual-consistency self-audit (10 dimensions), AI-slop detection |\n| `references\u002Faccessible-authoring.md` | React patterns for accessible UI — forms, ARIA, images\u002Ficons — the authoring counterpart to `accessibility-lens.md` |\n| `references\u002Fvite.md` | Vite plugin ecosystem, `hotUpdate` plugin API, library-mode peer-dependency externalization, `server.warmup`, `vite --profile`, stale-chunk mitigation, monorepo `server.fs.allow`, `server.host` for containers, plus a short Turbopack (Next.js) configuration note |\n| `references\u002Fheroui.md` | HeroUI component library — when to pick it over `shadcn\u002Fui`, provider\u002FTailwind setup, slot-based `classNames` composition, Server\u002FClient Component boundary for its interactive components |\n| `references\u002Fimpeccable-bridge.md` | Routing to the external `pbakaus\u002Fimpeccable` design-craft tool when it's installed in the target project — detection, when to defer to it vs. this skill's own craft references, boundary with the installed `ui-ux-pro-max` skill |\n\nLoad the file(s) matching what the user is building. Several can apply at\nonce (e.g. a new Vite+React modal needs `motion-system.md` for its\nenter\u002Fexit animation, `composition-and-ux.md` for its focus trap, and\n`accessible-authoring.md` for its ARIA attributes).\n\n## Boundary notes (what this skill deliberately does NOT cover)\n\n- **Accessibility compliance\u002Fauditing** (WCAG criteria, ARIA correctness as a\n  compliance question) — that's `code-review-edho-ferdian`'s\n  `references\u002Faccessibility-lens.md`. This skill's `composition-and-ux.md`\n  covers the *craft* of focus management and keyboard interaction, and\n  `references\u002Faccessible-authoring.md` covers the concrete React\n  patterns (forms, ARIA) that make that code pass the compliance lens —\n  both authoring-side, cross-referencing the a11y lens rather than\n  duplicating its compliance checklist.\n- **Security** (env var leakage, secret handling, injection) — that's\n  `security-review-edho-ferdian`. Build correct patterns from this skill's\n  references and they will naturally avoid the security pitfalls, but this\n  skill does not itself enumerate security findings.\n- **Type-checking gaps in the build pipeline** (e.g. `vite build` not\n  type-checking) — that's a review-time \u002F build-fix concern owned by\n  `build-fix-edho-ferdian`.\n- **Reviewing a diff or existing file for problems** — `code-review-edho-\n  ferdian` \u002F `language-code-review-edho-ferdian`.\n\n## External docs (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nBefore using a fast-moving or rarely-touched React\u002FNext.js\u002FVite API surface\n(new dependency, version upgrade, animation-library specifics), resolve it\nlive via Context7 rather than from memory. Full contract:\n`skill-authoring-edho-ferdian` §9.\n\n## Surgical changes (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nThis skill inherits the default as-is: when a task touches an existing\ncomponent or config file (not a from-scratch new one), change only what the\nrequest requires — don't refactor adjacent, already-working code as a side\neffect of adding a feature. Full contract: `skill-authoring-edho-ferdian`\n§10.\n\n## Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)\n\nCommunication to the user in Bahasa Indonesia; component code, comments, and\ncopy placeholders in English — fixed, never ask. Full contract:\n`skill-authoring-edho-ferdian` §7.\n\n",{"name":5,"metadata":24,"description":7},{"last_reviewed":25},"2026-09-19","main","533d32ad55c92d40fbabe93cbe21fe048598fe5a",".agents\u002Fskills\u002Ffrontend-engineering-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 frontend-engineering-edho-ferdian",{"tool":40,"command":41},"bunx","bunx skills add edhoferdian\u002FEEF --skill frontend-engineering-edho-ferdian",{"tool":43,"command":44},"pnpm","pnpm dlx skills add edhoferdian\u002FEEF --skill frontend-engineering-edho-ferdian","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-engineering-edho-ferdian\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Faccessible-authoring.md","REFERENCE","参考文档",5321,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-engineering-edho-ferdian\u002Freferences\u002Faccessible-authoring.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fcomposition-and-ux.md",6798,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-engineering-edho-ferdian\u002Freferences\u002Fcomposition-and-ux.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fdesign-direction.md",6041,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-engineering-edho-ferdian\u002Freferences\u002Fdesign-direction.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fheroui.md",6712,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-engineering-edho-ferdian\u002Freferences\u002Fheroui.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fimpeccable-bridge.md",4955,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-engineering-edho-ferdian\u002Freferences\u002Fimpeccable-bridge.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fmotion-system.md",12903,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-engineering-edho-ferdian\u002Freferences\u002Fmotion-system.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Freact.md",13555,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-engineering-edho-ferdian\u002Freferences\u002Freact.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fui-polish.md",5007,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-engineering-edho-ferdian\u002Freferences\u002Fui-polish.md",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fvite.md",13948,"https:\u002F\u002Fgithub.com\u002Fedhoferdian\u002FEEF\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend-engineering-edho-ferdian\u002Freferences\u002Fvite.md",[87,94,101,108,115,122],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"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",[],[]]