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

forma-validation

/forma-validation

Sprawdza zadania, dostępność, renderowanie, stany i wierność projektu, z proporcjonalnymi dowodami i powtarzalnymi wynikami.

Repozytorium
forma ↗
Licencja
MIT
Ostatnia zmiana repozytorium
11.11.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
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 11.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 robi i kiedy

Sprawdza zadania, dostępność, renderowanie, stany i wierność projektu, z proporcjonalnymi dowodami i powtarzalnymi wynikami.

Oryginalny opis (EN)

Validate tasks, accessibility, rendering, states, and fidelity with proportionate evidence and reproducible findings. Use for QA and confirmation after changes; not to certify inaccessible areas or treat isolated builds/tests as visual proof.

Jak działa

  1. When to use
  2. Inputs
  3. Procedure
  4. Output and stopping condition
  5. Coordination and execution boundaries
Sekcje z nagłówków SKILL.md, w oryginale · 50 linii, 680 słów
Podgląd SKILL.md
---
name: forma-validation
description: "Validate tasks, accessibility, rendering, states, and fidelity with proportionate evidence and reproducible findings. Use for QA and confirmation after changes; not to certify inaccessible areas or treat isolated builds/tests as visual proof."
metadata:
  version: 1.36.0
---

# Validation and quality

## When to use

- Use for audits, acceptance, regression, accessibility, rendered comparison, and confirmation of integrated capabilities.
- Do not invent scores, declare full compliance from automation, or expand an audit into unauthorized edits.

This module must be read by the agent; it does not trigger tests, fixes, or other modules by itself.
Preserve scope, brand, and stack. Distinguish verified, inferred, untested, and not applicable, with a reason.

For a relevant saved capability, use [reuse by capability](../../references/capability-reuse.md): search by the task, not the source project, and bind the mechanism to the destination's own identity and state owners. Read only the matching contract; do not expand a local fix into a redesign. Source names and exact profiles remain provenance or explicit fidelity targets.

## Inputs

- Artifact/route, revision actually loaded, task, acceptance criteria, and supported states/devices.
- A baseline for comparisons, data/fixtures, and tools/environments that are actually available.

## Procedure

1. Build a matrix proportionate to the risk and request before judging the result.
   Read [verification](../../references/verification.md); select dimensions and minimum proof without requiring every dimension for a small fix.
   When consuming agent/renderer gates, check [coverage and receipts](../../references/verification.md#verifier-coverage-and-receipts): a pass without measurements, zero assessed items, or an old revision does not approve the current delivery.
2. Confirm execution identity and follow the task through input, action, success, and recovery.
   Use [rendered validation](../../references/rendered-validation.md); verify persistence after reopening if promised, and distinguish an in-memory prototype from real operation.
3. For access, read [accessibility](../../references/accessibility.md) and exercise the relevant keyboard, focus, semantics, zoom, and alternative paths.
   Inspect computed accessible names for inputs presented with icons or placeholders; descriptions explain a field but do not replace its label.
   If layout/color is affected, use [spatial contracts](../../references/layout-spatial-contracts.md) and [color refinement](../../references/color-refinement.md).
   For a new surface or broad visual refinement, inspect the [coordinated foundation](../../references/verification.md#coordinated-foundation-review) in representative consumers and supported modes. Isolated token or contrast checks do not establish a coherent composition.
4. For reference work or reuse, test the operation that distinguishes the requested mechanism from an approximation.
   Consult reuse in [playbooks](../../references/playbooks.md) and [fidelity](../../references/reference-fidelity.md); observe the primary path, fallback, and relevant states separately. The [component lab](../../references/reusable-components.md#run-the-lab) exposes actual renderer and state diagnostics; counters and geometry tests still need rendered inspection, Save/reload, error recovery, unmount/remount and BFCache checks in the consumer.
   When frozen reference values exist, run the [fidelity verifier](../../references/fidelity-contracts.md) against consumer measurements. Missing fields, NaN, omitted points, or different revisions cannot pass through averaging. A passing numerical fixture does not prove that the browser loaded the revision or that the contract covers everything; confirm those facts separately.
5. Record failures with reproduction steps, effects, severity, and the smallest correction; fix only within existing authorization.
   Recheck affected states and critical paths, preserving before/after captures. Additional tests must address a remaining concern.
6. When changing Forma itself, use [plugin operation](../../references/plugin-operation.md) and the [evaluation protocol](../../evals/routing-scenarios.md#compare-versions-without-confusing-evidence).
   Package integrity, host discovery, agent decisions, and consumer operation have separate acceptance criteria. Apply [release validation](../../references/release-validation.md) when the request concerns a revision, independent trials, reusable components, or observed retrieval: freeze inputs/submissions, keep post-review corrections separate, and record each browser/input/motion/WebGL/cost gate as passed, failed, unverified, or inapplicable with a reason. Two Chromium shells are not two engines; narrow width is not touch, and CPU render time is not GPU cost.

## Output and stopping condition

Deliver results by criterion, evidence/environment, actionable findings, and coverage limits.
Helper scripts verify their input contracts; passing them does not replace observation in the product.
Stop when relevant criteria have evidence and no material blocker remains, or conclude the audit with clearly open failures.
Without runtime access, state what static analysis confirms and what remains untested; do not treat a limitation as approval.

## Coordination and execution boundaries

Consult the relevant Forma domain specialist to interpret evidence. Browser, accessibility and end-to-end checks remain this module's responsibility, using the available runner and existing project tests.
The coordinator selects additional modules; do not recursively dispatch between specialists. Use the available tools according to [capabilities](../../references/integrations.md); a tool name does not prove connection or execution.
Do not create suites that merely mirror the implementation. Test evidence, visual inspection, and task validation answer different questions.
Pliki w paczce (2)
  • SKILL.md 6 KB
  • agents/openai.yaml 1 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · figueirego/forma100MIT
figueirego/forma100MIT

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

  • 90forma-product
    Doprecyzowuje niejasne prośby projektowe w briefy i gotowe polecenia, bada zadania użytkowników i projektuje przepływy produktu z proporcjonalnym researchem.
  • 90forma-product
    Doprecyzowuje niejasne prośby projektowe w briefy i gotowe polecenia, bada zadania użytkowników i projektuje przepływy produktu z proporcjonalnym researchem.
  • 100forma
    Konfiguruje narzędzie Forma, które renderuje projekty z plików JSON i tokenów do PNG, i tworzy grafiki zgodne z marką.
  • 100forma
    Czyta i edytuje tablice badawcze Forma, czyli foldery z plikami board.json, mediami i komponentami, w tym obrazy, notatki i linki.
  • 100forma-templating
    Pakuje bieżący projekt Forma jako instalowalny szablon pod nazwą podaną przez człowieka, tylko na jego wyraźne żądanie.
  • 100trove-design-review
    Ocenia wdrożenie interfejsu UI i UX względem specyfikacji projektu, sprawdzając wierność wizualną i zgodność z systemem.

Uwagi i zgłoszenia

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