Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

frontend

/frontend

Pisze lub poprawia kod po stronie klienta w aplikacjach webowych, mobilnych i desktopowych: ekrany, komponenty, stan, ładowanie danych i błędy w UI.

Licencja
MIT
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
5
Skrypty
0
Komentarze HTML
1
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

Co robi i kiedy

Pisze lub poprawia kod po stronie klienta w aplikacjach webowych, mobilnych i desktopowych: ekrany, komponenty, stan, ładowanie danych i błędy w UI.

Oryginalny opis (EN)

Use when writing or changing client code for web, mobile or desktop: a screen or component, its state and data loading, or a bug in the UI.

Jak działa

  1. Client stack — resolve it before the first line, in this order; stop at the first answer
  2. Architecture
  3. State & data
  4. State-complete UI (design it from the start)
  5. i18n & accessibility (default, not decoration)
  6. Visual & UX quality
  7. Responsive & performance
  8. Verify at runtime (contract)
  9. DoD (this skill's contribution)
  10. Constraints
Sekcje z nagłówków SKILL.md, w oryginale · 78 linii, 793 słów
Podgląd SKILL.md
---
name: frontend
description: |
  Use when writing or changing client code for web, mobile or desktop: a screen or component,
  its state and data loading, or a bug in the UI.
---

# Frontend Discipline (stack-agnostic)

<!-- routing-eval reads the next line; why it sits in the body: AGENT_TEMPLATE.md -->
Trigger phrases: "in the frontend", "frontend code", "frontend'de", "screen size", "component", "page", "the UI", "UI component", "UI bug", "state management", "interface"

Web, mobile (native iOS/Android, Flutter, React Native, .NET MAUI, KMP) or desktop — shared principles.
The stack-specific "how" (native bridge, router choice, etc.) lives in the relevant project skill; this skill applies to all of them.

## Client stack — resolve it before the first line, in this order; stop at the first answer
There is no default client stack, and none is suggested: the user chooses. **Model discipline, not a gate.**
1. **The request says it.** "Add a Flutter screen" is an answer. Use it; record it if `## Stack` was empty.
2. **`CLAUDE.md ## Stack` → `Client:` says it.** A filled line is a decision: follow it.
3. **The repo says it** — manifests at the root and one level down (`app/`, `mobile/`, `web/`, `client/`, `apps/*`):

   | Manifest | Client |
   |:--|:--|
   | `package.json` | web (framework from its dependencies); React Native/Expo if it depends on `react-native` or `expo` |
   | `pubspec.yaml` | Flutter |
   | `*.xcodeproj` / `Package.swift` | native iOS (Swift / SwiftUI) |
   | `build.gradle(.kts)` with the Android plugin | native Android (Kotlin / Compose); KMP if it applies `kotlin("multiplatform")` |
   | `*.csproj` with `<UseMaui>` | .NET MAUI |
4. **Still open (a new project) → ask, once.** A few questions at most (which platforms · which client stack), the
   options listed plainly — **no option marked recommended and no "Decide for me"**: the stack is the user's call.
   This is the one decision where the discipline's "give a clear recommendation" does NOT apply: state each option's
   trade-off and stop there. That Crewforth ships layers for two stacks (`frontend-rn-expo`, `frontend-flutter`) is
   not a reason to favour either (measured: the first version of this step still got "React Native + Expo (recommended)", because of it).
   No one to ask (headless) → write the questions as text and stop; do not start client code on a guessed stack.

**Record it** in the `Client:` line of `CLAUDE.md ## Stack`, plus an ADR (`adr` skill). **Never ask twice** — a
recorded client stack changes only when the user asks. Then apply this skill on that stack; an RN/Expo project
also applies `frontend-rn-expo`, a Flutter project `frontend-flutter`.

## Architecture
- **Presentation / logic separation:** component/view is pure and thin; business logic lives in the hook/composable/service layer.
- **Reusability:** repeated UI is factored out; the prop contract is clear and typed.
- **Folder:** feature-based (`features/<name>/`) — view, logic, and test together.

## State & data
- **Local state first** (`useState`/signal); if global is needed, the project's choice (store/context) — nothing imposed.
- **Data fetching:** cache + error + loading states are considered; race/abort are handled.

## State-complete UI (design it from the start)
Every data-bound view covers **four states**: **loading · empty · error · full**.
Don't code only the "full" case; empty/error/loading are part of the experience. "Full" means the worst realistic
data too (a long unbreakable name, 0, 1 and 1000 items, extreme numbers, RTL): `references/worst-data.md`.

## i18n & accessibility (default, not decoration)
- User-visible text comes from the language file (project languages); no hard-coded strings (`i18n-integrity`).
- Meaningful labels/roles, sufficient contrast, keyboard/screen-reader access, appropriate touch/click target.

## Visual & UX quality
This skill covers *structure*; the **visual/UX design layer** — hierarchy, spacing rhythm, typographic scale, a
restrained color system, and polished states — lives in **`frontend-design`**. Apply it when the work is about how the
interface *looks and feels*, not just how it's wired. Building from a design file or a mock ("match this design",
a Figma link): `references/from-design.md`. A page others will find or share (title, description, canonical, Open
Graph, structured data): `references/page-metadata.md`.

## Responsive & performance
- Works across the target screen/device matrix (responsive/adaptive).
- Unnecessary renders (memo/callback), bundle size, lazy loading, virtualization for long lists.

## Verify at runtime (contract)
Prove a change works by **observing the running UI**, structured — not by interpreting a screenshot. Have components
emit `data-verify-*` state attributes, register verifiable units with fixtures + invariants (≥1 adversarial `probe`
each), expose `window.__verify`, and adopt the `PASS/FAIL/BLOCKED/SKIP` taxonomy (when in doubt, FAIL). Then drive
the browser to check it. The full convention: **`references/verify-contract.md`**.

## DoD (this skill's contribution)
- `/simplify`; no dead styles/unused props.
- The four states are covered; `i18n-integrity` clean; accessibility passes the baseline matrix.
- `crew-review-agent` clean.

## Constraints
- Surgical change; follow existing conventions, do not impose a stack/preference.
- Do not present data the platform does not provide as if it existed; do not promise a capability that isn't there.
- §4 applies: no AI trace or vendor template name in code/comments/strings.
Pliki w paczce (5)
  • SKILL.md 5 KB
  • references/from-design.md 1 KB
  • references/page-metadata.md 1 KB
  • references/verify-contract.md 4 KB
  • references/worst-data.md 2 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · byerlikaya/claude-starter-kit90MIT
speakeasy-api/gram100AGPL-3.0
kriscard/Skills100MIT
tlkppm/ModelBridge100MIT
Tristan578/project-forge100Apache-2.0
muon-m2/magento2-tools100MIT
Tyler-R-Kendrick/agent-skills100MIT
matteocervelli/llms100MIT

Migawka bazy z 13.11.2026 · wersja paczki 965cb9c6640c (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90uds-frontend
    Wdraża lub zmienia strony, komponenty, formularze i stan po stronie klienta w istniejącej aplikacji frontendowej.
  • 90react-typescript
    Modyfikuje frontend w React i TypeScript: komponenty, hooki, routing, stan, formularze i testy po stronie klienta.
  • 86ds-native
    Prowadzi zmiany w aplikacjach desktopowych i mobilnych, które dotykają pakowania, uprawnień systemu i cyklu życia.
  • 100frontend-patterns
    Podejmuje decyzje architektury frontendu niezależne od frameworka: gdzie leży stan, pobieranie danych, formularze, routing i bezpieczeństwo po stronie klienta.
  • 100frontend-developer
    Buduje komponenty React, układy responsywne i stan po stronie klienta, z naciskiem na wydajność i dostępność w React 19 i Next.js 15.
  • 95base44-platform-frontend
    Ustala standardy frontendu dla aplikacji Base44 webowych i mobilnych: routing, Tailwind lub NativeWind, tokeny projektowe i komponenty.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.