Engineering Vocabulary
Name a frontend engineering concept from a loose description. Reverse-lookup for FE technical terms — user describes a pattern informally ("supaya gak fetch ulang", "render cuma yang keliatan"), skill returns the proper name + brief definition. Use when the user uses informal language for a technical concept, or when you need the correct term to pick the right implementation.
Install
/plugin marketplace add sukirman1901/frontend-expertThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sukirman1901/frontend-expert --skill engineering-vocabularygit clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/engineering-vocabulary ~/.claude/skills/engineering-vocabularyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Engineering Vocabulary
## Overview
Bridge the gap between **casual engineering descriptions** and **precise technical terms**. When a user describes a frontend pattern loosely, look it up here to pick the right implementation approach.
## When to use
- User describes a pattern informally ("yang nge-cache itu", "biar gak nge-lag")
- You need the precise term to search docs or pick the right library
- Communicating architecture decisions clearly
## When to skip
- User already uses the correct term
- Non-frontend (backend, DevOps, database) concepts
## Lookup table
### State Management
| Description (loose) | Term | Definition |
|---------------------|------|------------|
| Share data without passing through every component | **Context / Provider pattern** | React Context or equivalent for cross-tree state |
| Data cached so it doesn't fetch again | **SWR / Stale-while-revalidate** | Return cached data, revalidate in background |
| Store that any component can read | **Global store (Zustand/Redux)** | Centralized client state container |
| State in the URL (filters, tabs) | **URL state / Search params** | Shareable, bookmarkable state via URL |
| Pass data down without prop chains | **State hoisting / Lifting state** | Move state to nearest common ancestor |
| Optimistic update before server confirms | **Optimistic UI / Optimistic mutation** | Show expected result immediately, rollback on error |Details
- Skill name
engineering-vocabulary- Repository
- sukirman1901/frontend-expert
- Path
skills/engineering-vocabulary/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Engineering Vocabulary skill do?
Name a frontend engineering concept from a loose description. Reverse-lookup for FE technical terms — user describes a pattern informally ("supaya gak fetch ulang", "render cuma yang keliatan"), skill returns the proper name + brief definition. Use when the user uses informal language for a technical concept, or when you need the correct term to pick the right implementation.
How do I install the Engineering Vocabulary skill?
Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Engineering Vocabulary popular?
It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.
Related skills
Accessibility
9sukirman1901/frontend-expert
Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.
Anti Slop Code
9sukirman1901/frontend-expert
Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.
Anti Slop Design
9sukirman1901/frontend-expert
Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.
Fidelity
9sukirman1901/frontend-expert
Spec vs implementation fidelity — Figma/Dev Mode/screenshot compare, spacing tolerance, token remap, close-enough rules. Use when matching a design file, "pixel perfect", "mirip Figma", design QA, or /design with a provided mock.
Devtools
9sukirman1901/frontend-expert
Frontend DevTools audit workflow — Lighthouse/CWV, a11y (axe), network/layout, when checks are MUST vs optional. Use for /test-ui deep passes, "audit performance", "cek Lighthouse", "axe", or verifying UI before ship with tooling evidence.
Forms
9sukirman1901/frontend-expert
Accessible forms, field/form errors, submit pending, wizards, progressive disclosure. Use when building or fixing forms, login, settings, checkout, filters, "validasi", "form error", or multi-step flows.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.