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

forma-handoff

/forma-handoff

Przygotowuje przekazanie projektu do wdrożenia: źródła, artefakty, tokeny, komponenty i eksport w wymaganym formacie.

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

Przygotowuje przekazanie projektu do wdrożenia: źródła, artefakty, tokeny, komponenty i eksport w wymaganym formacie.

Oryginalny opis (EN)

Prepare and verify the handoff between design and implementation: editable design sources, artifacts, tokens, components, export and consumer integration. Use to deliver the required format; not to replace requested functionality with documentation or a screenshot.

Jak działa

  1. When to use
  2. Inputs
  3. Procedure
  4. Output and stopping condition
  5. Coordination and execution boundaries
  6. Clear PDF guides
Sekcje z nagłówków SKILL.md, w oryginale · 51 linii, 640 słów
Podgląd SKILL.md
---
name: forma-handoff
description: "Prepare and verify the handoff between design and implementation: editable design sources, artifacts, tokens, components, export and consumer integration. Use to deliver the required format; not to replace requested functionality with documentation or a screenshot."
metadata:
  version: 1.36.0
---

# Artifacts, tokens and handoff

## When to use

- Use for design-source inspection, design-to-code work, editable artifacts, export, tokens or resource transfer to another project.
- Do not use to publish a library without authorization or present a full screenshot as an implemented interface.

This module instructs the agent after it is read; it does not connect services, export files or call other modules automatically.
Preserve the existing brand, stack, IDs and source of truth; deliver the format useful to the destination.

For a relevant saved capability, use [reuse by capability](../forma/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/source, destination, requested format, editing scope and content/state requirements.
- Existing components/tokens, assets/licenses, tool access and verifiable acceptance criteria.

## Procedure

1. Establish the source of truth, production route and type of delivery: specification, editable source, code or final file.
   Read [artifacts and editing](../forma/references/artifact-workflows.md); inventory actual IDs and dependencies to avoid duplication and invented links.
   For an aligned prompt or design-system document, follow [design specifications from evidence](../forma/references/design-specification.md). Compile the standalone prompt from the same [progressive brief](../forma/references/progressive-brief.md), preserve its revision and pending decisions, and check that prompt, specification and requested scope agree. Another assistant must be able to resume from project artifacts without relying on the previous chat or a host-specific tool.
2. For a connected design service, follow the [tool capability contract](../forma/references/integrations.md) and inspect its available API before using tools.
   Inspect existing context, render, components and bindings. Generated code remains a reference until adapted, integrated and verified.
3. For tokens/components, read [tokens and handoff](../forma/references/tokens-handoff.md).
   Map roles, aliases, modes, consumers and exceptions; example JSON has its own format and does not imply compliance with another pipeline.
4. When transferring a capability, follow reuse in [playbooks](../forma/references/playbooks.md).
   Connect implementation, events, state, assets and lifecycle to the consumer. BookPreset, AppearanceEditor and NeuronPassport have executable modules and integration contracts; the clean shell provides a scoped example. Preserve the approved mechanism and connect the destination's data and persistence adapters.
5. Open the editable/exported artifact or run the consumer in the destination and inspect the final result.
   Use [rendered validation](../forma/references/rendered-validation.md) and [verification](../forma/references/verification.md); validate fonts, assets, sizes, links and states for the format.
   For multiple deliverables, verify each output and its revision against the existing contract. For video, also check [duration, frames and audio](../forma/references/motion.md#films-and-rendered-sequences); preview, rendered file and confirmed delivery are distinct stages.
   For cutouts, verify [alpha and composition](../forma/references/artifact-workflows.md#transparency-and-composition) in the final file; PNG format or a checkerboard preview does not prove transparency.

## Output and stopping condition

Deliver real files/links, format, location, consumer and the minimum instructions needed for use.
Identify what is editable, exported, integrated, persisted or only specified, with corresponding evidence.
Stop when the recipient can use the artifact in the agreed format and the result has been opened/exercised.
If integration, runtime or an export tool is missing, state the limit; do not conclude a requested implementation with isolated documentation.

## Coordination and execution boundaries

Use Forma Foundations for token consistency, Forma Interface for consumer integration, and Forma Validation for rendered and exported acceptance. Use one primary production capability per artifact when sufficient.
The coordinator selects additional modules; do not recursively dispatch between specialists. Use the available tools according to [capabilities](../forma/references/integrations.md); a tool name does not prove connection or execution.
Do not install services, regenerate paid artifacts or publish by default. In-memory contracts and demos do not prove persistence or export in the consumer.

## Clear PDF guides

For clean PDF guides, follow the [clear-guide export contract](../forma/references/clear-pdf-guides.md#export-and-verification). Brand owns composition; support the actual export, page and text checks. Deliver the requested PDF and available editable source without treating an HTML specimen as a finished PDF.
Pliki w paczce (2)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · figueirego/forma100MIT
figueirego/forma100MIT

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

  • 100forma-reference
    Szuka przykładów w katalogu Forma, podaje autorów materiałów i porównuje różnice wizualne i techniczne na podstawie kodu i działania.
  • 100forma-reference
    Szuka przykładów w katalogu Forma, podaje autorów materiałów i porównuje różnice wizualne i techniczne na podstawie kodu i działania.
  • 100ui-design-system
    Dostarcza narzędzia systemu projektowego UI: tokeny projektowe, dokumentację komponentów, obliczenia responsywności i przekazanie projektu deweloperom.
  • 100forma
    Konfiguruje narzędzie Forma, które renderuje projekty z plików JSON i tokenów do PNG, i tworzy grafiki zgodne z marką.
  • 100uxd-design-handoff
    Przygotowuje specyfikację przekazania projektu do wdrożenia: mapuje elementy UI na komponenty systemu, wylicza stany i kryteria akceptacji.
  • 86d2s-handoff
    Przygotowuje przekazanie projektu dla programistów i wdraża interfejs według zatwierdzonej specyfikacji.

Uwagi i zgłoszenia

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