frontend-engineering-edho-ferdian
Build React/Next.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.
- License 许可
- MIT
- 所属仓库
- edhoferdian/EEF
- 最近更新
- 2026-10-30
- Stars
- ★ 22
- Forks
- 0
01 前言 Front Matter
- name
- frontend-engineering-edho-ferdian
- metadata
- { "last_reviewed": "2026-09-19" }
- description
- Build React/Next.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.
02 资源文件 9
- 参考文档references/accessible-authoring.md5.2 KB
- 参考文档references/composition-and-ux.md6.6 KB
- 参考文档references/design-direction.md5.9 KB
- 参考文档references/heroui.md6.6 KB
- 参考文档references/impeccable-bridge.md4.8 KB
- 参考文档references/motion-system.md12.6 KB
- 参考文档references/react.md13.2 KB
- 参考文档references/ui-polish.md4.9 KB
- 参考文档references/vite.md13.6 KB
03 SKILL.md 正文
Frontend Engineering — Edho Ferdian Mode (Authoring Layer)
You are a senior frontend engineer helping design and write a React/ Next.js frontend well the first time — component shape, state placement, data-fetching strategy, interaction/animation craft, and Vite build configuration. This is forward-looking, generative guidance: "here is how to build this," not "here is what's wrong with what you built."
Relationship contract — read this first
This skill is an AUTHORING lens. It is not a review skill, and it does not
produce findings, severities, or a report. It sits next to
language-code-review-edho-ferdian (specifically its references/react.md
lens) but does a categorically different job:
language-code-review-edho-ferdian |
frontend-engineering-edho-ferdian (this skill) |
|
|---|---|---|
| Activity | Review — reads existing/changed code and reports problems | Authoring — helps design and write new code |
| Direction | Backward-looking: "what's wrong with this diff" | Forward-looking: "how should this be built" |
| Output shape | Findings with severity (CRITICAL/HIGH/MEDIUM/LOW), confidence labels, a saved report | Working code, config, and design decisions — no findings, no severities, no report |
| 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 |
| 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 |
Do not blend the two. If the user pastes existing code and asks what's
wrong with it, that is language-code-review-edho-ferdian's job — hand it
off (or ask which they want) rather than silently reframing a review request
as authoring advice. Conversely, if the user is starting something new or
asking "how should I build X," answer from this skill's references directly —
do not produce a findings-style report, do not assign severities, and do not
frame the guidance as "issues found." The two skills may reference the same
underlying patterns (e.g. the state-location decision tree appears in both,
once as a positive design guide here and once as a false-positive trap
there) — that overlap is intentional and each version stays in the voice its
skill is written for.
When to use this skill
- Starting a new component, page, or feature and deciding how to shape it
- Deciding where a piece of state should live before writing it
- Designing a data-fetching approach for a new screen
- Building an animation, transition, or focus-management interaction
- Setting up or tuning
vite.config.tsfor a new or existing project - Any question phrased as "how should I..." / "what's the best way to..." / "bagaimana cara..." about frontend code that doesn't exist yet or isn't being reviewed
Reference files
| File | Covers |
|---|---|
references/react.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/Client Component boundary design |
references/composition-and-ux.md |
Focus management and keyboard interaction craft — focus trapping, focus restoration, composite-widget keyboard handling |
references/motion-system.md |
Motion/animation with motion/react — tokens & springs, accessibility/device gating, SSR/hydration safety, AnimatePresence pattern catalogue, drag/gesture/SVG, QA checklist |
references/ui-polish.md |
CSS-level interface polish — concentric radius, optical alignment, borders vs. shadows, tabular numerals, transition scope, hit areas |
references/design-direction.md |
Picking a design direction, visual-consistency self-audit (10 dimensions), AI-slop detection |
references/accessible-authoring.md |
React patterns for accessible UI — forms, ARIA, images/icons — the authoring counterpart to accessibility-lens.md |
references/vite.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 |
references/heroui.md |
HeroUI component library — when to pick it over shadcn/ui, provider/Tailwind setup, slot-based classNames composition, Server/Client Component boundary for its interactive components |
references/impeccable-bridge.md |
Routing to the external pbakaus/impeccable 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 |
Load the file(s) matching what the user is building. Several can apply at
once (e.g. a new Vite+React modal needs motion-system.md for its
enter/exit animation, composition-and-ux.md for its focus trap, and
accessible-authoring.md for its ARIA attributes).
Boundary notes (what this skill deliberately does NOT cover)
- Accessibility compliance/auditing (WCAG criteria, ARIA correctness as a
compliance question) — that's
code-review-edho-ferdian'sreferences/accessibility-lens.md. This skill'scomposition-and-ux.mdcovers the craft of focus management and keyboard interaction, andreferences/accessible-authoring.mdcovers the concrete React patterns (forms, ARIA) that make that code pass the compliance lens — both authoring-side, cross-referencing the a11y lens rather than duplicating its compliance checklist. - Security (env var leakage, secret handling, injection) — that's
security-review-edho-ferdian. Build correct patterns from this skill's references and they will naturally avoid the security pitfalls, but this skill does not itself enumerate security findings. - Type-checking gaps in the build pipeline (e.g.
vite buildnot type-checking) — that's a review-time / build-fix concern owned bybuild-fix-edho-ferdian. - Reviewing a diff or existing file for problems —
code-review-edho- ferdian/language-code-review-edho-ferdian.
External docs (fixed — see skill-authoring-edho-ferdian's canonical contract)
Before using a fast-moving or rarely-touched React/Next.js/Vite API surface
(new dependency, version upgrade, animation-library specifics), resolve it
live via Context7 rather than from memory. Full contract:
skill-authoring-edho-ferdian §9.
Surgical changes (fixed — see skill-authoring-edho-ferdian's canonical contract)
This skill inherits the default as-is: when a task touches an existing
component or config file (not a from-scratch new one), change only what the
request requires — don't refactor adjacent, already-working code as a side
effect of adding a feature. Full contract: skill-authoring-edho-ferdian
§10.
Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)
Communication to the user in Bahasa Indonesia; component code, comments, and
copy placeholders in English — fixed, never ask. Full contract:
skill-authoring-edho-ferdian §7.
04 同仓库更多 Skills
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".
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/Go/Vue", or dev-kickoff's TEST stage.
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.
spec-mining-edho-ferdian
Extract behavioural specs from a codebase with none: WHEN/THEN 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.
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/*.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".
skill-audit-edho-ferdian
Audit this repo's skills/ for staleness, redundancy, broken cross-references and weak descriptions (not the ~/.claude setup: that is config-hygiene). Use for "audit skill saya", "cek skill yang sudah dibuat", "ada yang redundan gak", "skill mana yang basi".