helderberto/agent-skills

frontend-ui-engineering

Front-load UI construction decisions — component boundary and prop API, state placement, required states, responsiveness, accessibility.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/helderberto/agent-skills --skill frontend-ui-engineering

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Frontend UI Engineering

Decide how to structure a UI unit before writing it, so the choices audits would catch late (accessibility, i18n, bundle cost, missing states) are made up front. Frontend counterpart to codebase-design: a component is a deep module — a lot of behaviour behind a small prop surface. This skill decides; tdd/build implement; the audit skills verify. Framework-agnostic.

1. Classify the unit

KindEmphasis
Design-system primitive (Button, Input)prop API, variants via props, tokens, a11y contract
Composite componentcomposition, state placement, required states
Page / routedata-fetching boundary, layout, loading/error at the route
Refactor of existing UIshrink prop surface, extract states, remove magic values

2. Decision pass — state each choice before coding

  1. Boundary & prop API. Smallest surface that serves callers. Prefer composition (children/slots) over configuration. A growing set of boolean flags (isPrimary, isSmall, isLoading…) is a smell — three booleans is eight states, most untested; reach for a variant/size union or composition.
  2. Where state lives. The lowest owner that still works: local → lifted → server state → URL. No derived state stored twice; compute from source.
  3. Data & async. Decide the fetch boundary (route/loader vs. inside the component) and who owns caching. Keep rendering components separate from fetching ones where practical.
  4. Required UI states. Enumerate and design loading, empty, error, disabled (and partial/optimistic where relevant) now. Happy-path-only is unfinished.
  5. Styling. Design-system tokens, no magic colors/spacing. Variants through props, not one-off overrides.
  6. Responsive. Mobile-first; intentional breakpoints; no fixed widths that break small screens.
  7. Accessibility by construction. Semantic HTML first, ARIA last; keyboard + focus order; a label for every control; visible focus. Full WCAG pass belongs to a11y-audit.
  8. User-facing strings. Through the project's i18n path from the start. Coverage check belongs to i18n.

3. Build and hand off

Apply the decisions. Call the Skill tool with tdd for non-trivial logic and its tests, then with visual-review in UI mode for before/after in a real browser. /hb:review then runs the audits as the QA pass before /hb:to-pr.

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
helderberto
Comunidade

codebase-design

Shared vocabulary for designing deep modules. Use when designing or improving a module's interface, placing a seam, making code more testable, or when another skill needs it. Don't use for codebase-wide audits (/architecture-audit) or UI components (/frontend-ui-engineering).

Instalações / 1h
1
GitHub Stars
17
Atualizado
19 de out.
helderberto
Comunidade

debug

Disciplined diagnosis loop for hard bugs and performance regressions. Use when user says "diagnose" or "debug this", or reports something broken, throwing, failing, or slow. Don't use to build a feature or fix an understood bug test-first (/tdd).

Instalações / 1h
1
GitHub Stars
17
Atualizado
19 de out.
helderberto
Comunidade

deps-audit

Check dependencies for known vulnerabilities and staleness. Use when asked to "audit dependencies", "check for vulnerabilities", or check dependency health. Don't use for code quality review.

Instalações / 1h
1
GitHub Stars
17
Atualizado
19 de out.
helderberto
Comunidade

harden

Harden code where untrusted input enters the system. Use when implementing auth, handling user input, storing sensitive data, integrating external APIs, adding file uploads or LLM features, or crossing any trust boundary. Don't use for secret scanning (/safe-repo) or dependency CVEs (/deps-audit).

Instalações / 1h
1
GitHub Stars
17
Atualizado
19 de out.