Przejdź do treści
Biblioteka skilli
Projektowanie i UX · Testowanie

mantis

/mantis

Otwiera działającą aplikację w przeglądarce i sprawdza ekrany w różnych rozmiarach, w jasnym i ciemnym trybie oraz językach, zanim uzna UI za gotowe.

Repozytorium
mantis ↗
Licencja
MIT
Ostatnia zmiana repozytorium
30.10.2026

Ocena i bezpieczeństwo

100/ 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ść35 / 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
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

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

Licencja

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

Co robi i kiedy

Otwiera działającą aplikację w przeglądarce i sprawdza ekrany w różnych rozmiarach, w jasnym i ciemnym trybie oraz językach, zanim uzna UI za gotowe.

Wyzwalacze z opisu

check the UIdoes it work on mobile
Oryginalny opis (EN)

Look at the UI before calling it done. Opens the running app in a real browser, checks every screen size, light and dark mode, and other languages, and reports what is actually broken: page overflow, cut-off text, overlapping controls, unreadable contrast, dark-mode leaks, tiny tap targets, console errors, broken images, layout shift. Use after any frontend change, before saying a UI task is done, when a UI, layout or screenshot check fails (a red check:ui, a failing mobile e2e test, a release blocked by one), or when the user says "check the UI", "does it work on mobile", "dark mode looks off

Jak działa

  1. 1. Get the app running
  2. 2. Look
  3. 3. Read the evidence, then look at it
  4. 4. Decide
  5. 5. Report back
  6. Limits
Sekcje z nagłówków SKILL.md, w oryginale · 103 linii, 884 słów
Podgląd SKILL.md
---
name: mantis
description: >
  Look at the UI before calling it done. Opens the running app in a real browser,
  checks every screen size, light and dark mode, and other languages, and reports
  what is actually broken: page overflow, cut-off text, overlapping controls,
  unreadable contrast, dark-mode leaks, tiny tap targets, console errors, broken
  images, layout shift. Use after any frontend change, before saying a UI task is
  done, when a UI, layout or screenshot check fails (a red check:ui, a failing
  mobile e2e test, a release blocked by one), or when the user says "check the
  UI", "does it work on mobile", "dark mode looks off", /mantis.
---

# Mantis

A mantis shrimp sees 12 color channels. People see 3. A coding agent that never
opens the browser sees 0.

**Rule:** a UI change is not done until you have looked at it rendered. "The code
looks right" is not evidence. A Mantis run with zero errors is.

## 1. Get the app running

- Use the project's own dev command (`npm run dev`, `pnpm dev`, `rails s`, …) and
  note the URL. If it is already running, reuse it.
- List the routes your change touches. Add `/` when the change is global
  (layout, theme, fonts, CSS reset).
- Pages behind a login or onboarding: pass `--storage-state <file>`, a Playwright
  storage state with the session's cookies and localStorage. Ask the user for one,
  or make it: `npx playwright@1.64.1 codegen --save-storage=.mantis/auth.json <login-url>`
  (the user signs in and closes the window), or a short Playwright script that signs
  in with a dev or seed user and calls `context.storageState({ path })`. When the
  app only checks a localStorage flag (onboarding done), write the JSON by hand.
  The file holds a live session: keep it in `.mantis/` or elsewhere out of git.
- If you can't reach a page, say so in your report instead of skipping it silently.

## 2. Look

```bash
mantis look http://localhost:3000 --routes /,/settings
```

If `mantis` isn't installed, run `npx -y @vulinh1704/mantis@0.7.1 look …` instead.
Without Node or a browser, use the Docker image (`ghcr.io/vulinh1704/mantis`, see the
README for how it reaches a dev server on the host).

- `--locales en,vi` when the app has translations. Longer languages (Vietnamese,
  German) break layouts that look fine in English.
- `--locale-strategy` when the app doesn't follow the browser language (the report
  says a locale is "not localized"). Check how the app switches language first:
  `path:/{locale}` (`/vi/settings`), `query:lang`, `cookie:NEXT_LOCALE` (next-intl)
  or `storage:i18nextLng` (i18next).
- `--locales en,pseudo` when the app has no translations yet (or one language
  only). The pseudo cell shows every string about 40% longer, accented and
  bracketed; cut or overflowing text there will break in real translations. Fix it
  the same way (let the box grow or wrap), never by shortening the pseudo text.
- `--locales en,pseudo-rtl` when the app will ship Arabic, Hebrew or Persian but
  doesn't yet: the pseudo text laid out right to left. Overflow on the left and
  controls stuck to the wrong side usually come from physical CSS (`margin-left`,
  `left:`, `text-align: left`); fix them with logical properties
  (`margin-inline-start`, `inset-inline-start`, `text-align: start`).
- `--dark-strategy class:dark` or `--dark-strategy attr:data-theme=dark` when dark
  mode is a class or attribute toggle rather than the OS setting. Check how the app
  switches themes before choosing.
- Keep the default screens (mobile 360, tablet 768, desktop 1440). Never drop
  mobile to make a report pass.
- Before you change styles, run `mantis learn <url>` (same routes) on the
  unchanged app when `.mantis/style.json` doesn't exist yet. Every later `look`
  then reports `off-style` warnings: colors, font sizes and radii that are near
  copies of the house values, and fonts the app uses nowhere else.
- Exit code: `0` no errors, `1` errors found, `2` the page could not be loaded
  (is the server up, on that port?).

## 3. Read the evidence, then look at it

1. Read `.mantis/latest/report.md`: issues grouped by type, with the selector, the
   screens where each appears, and the screenshot file. When an earlier run of the
   same URL exists, the report also compares with it: what was fixed, what is new,
   and any `cover-up` (an issue hidden instead of fixed).
2. Open the screenshots of the worst screens in `.mantis/latest/shots/`. Errors
   are boxed in red and warnings in amber, each with its issue number. Look at the
   image before deciding; a selector alone can mislead.
3. `.mantis/latest/contact-sheet.png` shows every screen at once.
4. A clean report means clean for what Mantis measures, not "nothing is wrong".
   Scan the sheet and the shots for what it can't judge: text over photos or
   gradients, a control that is missing, spacing that looks off. Say what you saw.
5. One bug can hide another: an invisible toolbar can't overlap anything. After a
   fix, look again before you call the report final.

## 4. Decide

- Errors in code you changed: fix them now with the **mantis-fix** skill, then
  look again with the same command.
- Errors that were already there before your change: tell the user what you saw.
  Don't silently rewrite unrelated code.
- Warnings: fix them when cheap and in scope; otherwise list them.

## 5. Report back

Say what Mantis checked (routes × screens × themes × languages), the error counts
before → after, and where the contact sheet is. Say plainly what you could not
check.

## Limits

- Mantis checks that the rendered page works, not whether it is beautiful. Pair it
  with a design skill for taste.
- It doesn't click through flows or test hover and focus states yet. Visit a route
  that shows the menu or dialog you changed, or say it was not checked.
- It doesn't measure animation smoothness. For load speed (LCP, blocking time,
  slow API calls, third parties), use the **mantis-perf** skill.
- Contrast on canvas apps and under transparent layers is read from the
  screenshot. Text over photos, CSS background images and gradients is not
  checked: look at those yourself.

Wersje

W bazie nie ma innych skilli o nazwie mantis.

Migawka bazy z 13.11.2026 · wersja paczki d2a62cc3edc1 (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

  • 100mantis-fix
    Naprawia u źródła problemy UI znalezione w raporcie, zamiast je ukrywać, i sprawdza ponownie, aż raport będzie czysty.
  • 100color-contrast
    Dobiera paletę kolorów i sprawdza kontrast WCAG, aby tekst był czytelny w jasnym i ciemnym motywie.
  • 90verify-ui
    Sprawdza zmianę interfejsu w przeglądarce: uruchamia serwer, robi zrzuty ekranu w telefonie i na komputerze oraz szuka błędów układu.
  • 98build-and-verify
    Buduje aplikację WinUI 3 z linii poleceń, instaluje ją i sprawdza zrzuty okien w trybie jasnym i ciemnym po każdej zmianie interfejsu.
  • 100color-mode-and-theme
    Pomaga zdecydować o trybie jasnym, ciemnym lub obu oraz o tym, kiedy warto dodać przełącznik motywu, przy definiowaniu palety bazowej.
  • 100build-and-verify
    Buduje aplikację SwiftUI na macOS z wiersza poleceń i sprawdza zrzuty okien w jasnym i ciemnym motywie.

Uwagi i zgłoszenia

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