Skip to content
Skills Library
Programming · Building & coding

frontend

/frontend

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.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

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.

Original author 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.

How it works

  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
Original SKILL.md headings · 78 lines, 793 words
SKILL.md preview
---
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.
Files in this package (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

Versions

RepositoryScoreLicence
This page · 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

Database snapshot: 13.11.2026 · package version 965cb9c6640c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90uds-frontend
    Use when implementing or changing frontend pages, components, forms, client state, or UI behavior within an existing application.
  • 90react-typescript
    Use when modifying a frontend that actually uses React and TypeScript, including components, hooks, routing, state, forms, and client-side tests.
  • 86ds-native
    Use when changing desktop or mobile application behavior that crosses packaging, operating-system permissions, or native lifecycle boundaries.
  • 100frontend-patterns
    Framework-neutral frontend architecture decisions - where state lives, server-state fetching and caching, loading/error/empty states, forms and validation, routing and URL state, styling approach, code splitting, client-side security. Use when planning, building or reviewing UI…
  • 100frontend-developer
    Build React components, implement responsive layouts, and handle client-side state management. Masters React 19, Next.js 15, and modern frontend architecture. Optimizes performance and ensures accessibility. Use when creating UI components or fixing frontend issues.
  • 95base44-platform-frontend
    Frontend coding standards for Base44 web and native mobile apps: code conventions, the installed packages, routing (React Router in the Vite SPA, file routes in TanStack Start, expo-router in native mobile), Tailwind or NativeWind and design tokens, styling and componentization…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.