Skip to content
Agentmart
Submit a tool

ui-react-engineering

React and Next.js engineering guidance for frontend UI implementation.

Skill by hersti

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/hersti-ui-react-engineering

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

React and Next.js engineering guidance for frontend UI implementation. Use when substantial UI work affects data fetching, server/client boundaries, rendering, rerenders, bundle size, hydration, or performance. Do not invoke for framework-agnostic styling-only work.

Use cases: design, frontend, backend, data

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/ui-react-engineering

What's inside

Skill name
ui-react-engineering
Description
React and Next.js engineering guidance for frontend UI implementation. Use when substantial UI work affects data fetching, server/client boundaries, rendering, rerenders, bundle size, hydration, or performance. Do not invoke for framework-agnostic styling-only work.
License
MIT
Instructions
18 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# React / Next UI Engineering

Optimize architecture where it materially affects user experience; do not turn every UI task into speculative micro-optimization.

Prioritize in this order:
1. eliminate avoidable async waterfalls and serialize less work;
2. keep unnecessary code out of the client bundle;
3. respect Server/Client Component boundaries and avoid broad client islands;
4. avoid duplicate client fetching/listeners and redundant subscriptions;
5. fix rerender causes before adding memoization;
6. preserve hydration correctness and responsive rendering behavior;
7. optimize hot JavaScript paths only when they are real bottlenecks.

Prefer parallel independent work, direct imports where barrel imports materially inflate bundles, lazy-load genuinely heavy optional UI, and pass the smallest serializable data surface to client components.

Do not add `memo`, `useMemo`, `useCallback`, caching, or dynamic imports as ceremony. Keep component APIs clear and composable; performance complexity must have a reason.

From hersti/ui-engineering, MIT.

More from hersti/ui-engineering

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 27, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/hersti/ui-engineering
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from hersti

Cite this page

ui-react-engineering skill. Agent Mart. https://agentmart.dev/skills/hersti-ui-react-engineering (last updated 2026-10-24)