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

lynx-openui

/lynx-openui

Generuje poprawne programy OpenUI Lang v0.5 dla renderera Lynx OpenUI na podstawie opisu interfejsu w języku naturalnym, w tym stan, przepływy Query i Mutation oraz plany akcji.

Repozytorium
skills ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
26.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
6
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

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

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Generuje poprawne programy OpenUI Lang v0.5 dla renderera Lynx OpenUI na podstawie opisu interfejsu w języku naturalnym, w tym stan, przepływy Query i Mutation oraz plany akcji.

Oryginalny opis (EN)

Generate valid OpenUI Lang v0.5 functional-notation programs for the Lynx OpenUI renderer. Use when Codex must turn a natural-language UI request into raw OpenUI DSL for OpenUiRenderer, including static mobile UI, $state, Query/Mutation tool flows, Action plans, streaming-friendly output, or catalog-constrained revisions. Do not use for JSX, HTML, CSS, A2UI JSON, or implementing new ReactLynx components.

Jak działa

  1. Read The References
  2. Workflow
  3. Output Contract
  4. Syntax Rules
  5. Data And Interaction Rules
  6. Lynx UI Rules
  7. Final Verification
Sekcje z nagłówków SKILL.md, w oryginale · 149 linii, 1 066 słów
Podgląd SKILL.md
---
name: lynx-openui
description: Generate valid OpenUI Lang v0.5 functional-notation programs for the Lynx OpenUI renderer. Use when Codex must turn a natural-language UI request into raw OpenUI DSL for OpenUiRenderer, including static mobile UI, $state, Query/Mutation tool flows, Action plans, streaming-friendly output, or catalog-constrained revisions. Do not use for JSX, HTML, CSS, A2UI JSON, or implementing new ReactLynx components.
---

# Generate Lynx OpenUI Programs

Generate valid OpenUI Lang v0.5 consumed by
`<OpenUiRenderer response={...}>`. Produce declarative DSL, not application
code.

## Read The References

- Always read [components.md](references/components.md) before generating a
  program. Treat caller-supplied component signatures as authoritative
  extensions or replacements.
- Read [runtime.md](references/runtime.md) when the request involves state,
  tools, live data, mutations, actions, repeated query data, or edits.
- Read [examples.md](references/examples.md) for a non-trivial layout or tool
  workflow. Adapt patterns; do not copy irrelevant content.

## Workflow

1. Identify the requested UI, exact active component catalog, configured root
   component, available tool schemas, host-supplied prefetched Query keys,
   media URLs, and whether the host supports full programs or
   `mergeStatements` patches.
2. Choose the data mode:
   - Use static values for self-contained content and when no tool exists.
   - Use `Query` only for an actual read tool supplied by the caller or host.
   - Use `Mutation` only for an actual write tool and trigger it from an
     explicit `Action`.
3. Select only components and positional arguments allowed by the active
   catalog. Treat an explicitly reduced catalog as the complete vocabulary:
   built-ins omitted from it are unavailable. Use the host's explicit root
   override when present; otherwise use the Library's default `Stack` root.
4. Write a streaming-friendly graph. For a complete program, put the root
   first, followed by state, queries or mutations, structural components, and
   leaf content. For an edit-mode patch, return only changed statements.
5. Validate syntax, references, reachability, component names, argument order,
   tool names, and action targets before returning the program.

## Output Contract

- Return only OpenUI Lang. Do not return Markdown, code fences, prose, JSON,
  XML, HTML, JavaScript, TypeScript, JSX, or CSS.
- Put one assignment statement on each line.
- For a complete program, make the first non-empty line assign `root` to a call
  of the host's explicit root override, for example `root = Shell(...)`.
  Otherwise use the Library's default `root = Stack(...)`.
- Return a complete program by default. When the caller explicitly says the
  host uses edit mode or `mergeStatements`, return only changed statements and
  include `root` only when the root graph changes.
- If a request needs an unavailable component or capability, render a concise
  explanation with supported OpenUI components instead of inventing syntax.

## Syntax Rules

- Use `identifier = Expression` for ordinary declarations and
  `$identifier = defaultValue` for mutable state.
- Pass component arguments positionally. Never use named arguments such as
  `gap: "m"`.
- Omit optional arguments only from the end. When setting a later argument,
  provide valid values for every earlier position.
- Use double-quoted strings and escape embedded quotes and backslashes.
- Use references or inline components. Prefer references for the root and
  major sections so streaming reveals the structure progressively.
- Ensure every referenced identifier is defined. Ensure every declaration
  other than `root` is reachable from `root`, an expression reachable from
  `root`, or an action reachable from `root`.
- Use only documented operators, built-ins, components, and action steps.

Correct positional layout using the default `Stack` root:

```text
root = Stack([header, content], "column", false, "l", "stretch", "start")
```

Incorrect positional layout:

```text
root = Stack([header, content], "column", "l", "stretch")
```

The incorrect form passes a string into `wrap` and shifts every later prop.

## Data And Interaction Rules

- Do not invent tool names. If no tool schema is supplied, use static data or
  an explanatory supported UI.
- Give every `Query` a representative default result matching the real tool
  shape so the UI renders in the first synchronous render after the response
  stabilizes and before the request resolves.
- When the host supplies prefetched Query results, preserve the corresponding
  Query assignment names. They are statement IDs and prefetch keys, not tool
  names. See [runtime.md](references/runtime.md#query).
- Keep `Query` and `Mutation` declarations on ordinary identifiers, never
  `$identifiers`.
- Use `@Each` for query-backed repeated UI. Keep its loop-dependent component
  inline inside `@Each`.
- Trigger write operations only from an explicit submit or confirmation action
  on an active-catalog component. With the default catalog, use `Button`. Do not
  attach a mutation to an input's change action.
- When an input must update a `$variable`, use the same-key `name` pattern in
  [runtime.md](references/runtime.md). Do not invent an event-value variable.
- Execute multi-step actions in deliberate order. Remember that a failed
  mutation stops the remaining steps.
- Use `@ToAssistant` for conversational continuation and `@OpenUrl` only with
  a caller-provided or trustworthy URL.
- Use caller-provided media URLs. Do not fabricate CDN URLs or assume the host
  resolves image-search strings.

## Lynx UI Rules

- Prefer compact, mobile-first layouts with a shallow component tree.
- Apply component-specific preferences only when those components exist in the
  active catalog; otherwise follow the supplied custom signatures.
- With the default catalog, use `Stack` or `Column` for ordinary vertical
  structure, `Row` for small horizontal groups, and `List` for grouped or
  repeated content.
- When `Image` exists, prefer explicit variants so the Lynx renderer has
  concrete sizing.
- With the default catalog, keep readable text in `Text` or `TextContent`; do
  not emit raw Lynx elements.
- When available, use `Tabs` for alternate views and `Modal` for tap-to-open
  details. Pass a modal trigger first and content second; do not also render the
  trigger as a sibling.

## Final Verification

Before returning, verify all of the following:

- A complete program assigns `root` to the host's explicit root override when
  present, or to the Library's default `Stack` root otherwise. An edit-mode
  patch omits `root` unless the root graph changes. The response contains only
  OpenUI Lang.
- Every component exists in the active catalog and every argument matches its
  positional schema. A reduced catalog contains no implicit built-ins, and the
  root call uses its configured root component.
- No `Form`, `Input`, `Select`, `SelectItem`, `FormControl`, table, or chart is
  used unless the caller supplied that custom component.
- Every reference resolves and no declaration is orphaned.
- Every `Query` or `Mutation` uses a real supplied tool and is referenced by
  visible UI or a visible action.
- Every intended prefetched Query uses its exact host-supplied key as the
  assignment name, and every Query still has a shape-correct default.
- Every `$variable` participates in visible UI, a query argument, or an action.
- Every `@Each` loop variable stays inside its inline template expression.
- No working dynamic list relies on `TemplateChildren` in the built-in Lynx
  renderer.
- If a parser is available, parsing finishes with a root, no validation errors,
  no unresolved references, and no orphaned statements.
Pliki w paczce (6)
  • LICENSE 11 KB
  • SKILL.md 8 KB
  • agents/openai.yaml 1 KB
  • references/components.md 7 KB
  • references/examples.md 4 KB
  • references/runtime.md 8 KB

Wersje

W bazie nie ma innych skilli o nazwie lynx-openui.

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

  • 96openui-forge-zh
    Buduje aplikacje z generatywnym UI w OpenUI: integracja z dowolnym dostawcą LLM i backendem, scaffolding oraz walidacja.
  • 100lynx-check-css-support
    Sprawdza w danych compat_data pakietu @lynx-js/css-defines, które właściwości CSS i wartości obsługuje Lynx w danym backendzie i wersji, oraz czy dostępna jest nowsza wersja zbioru.
  • 100add-component
    Dodaje komponent lub właściwość do biblioteki austere-axi OpenUI, tylko dla opiekuna repozytorium.
  • 100lynx-tasm-codec
    Zamienia szablony JSON na binarne tasm i z powrotem przez agent-lynx tasm, także przy innej wersji @lynx-js/tasm.
  • 100aurora-generative
    Pomaga modelowi generować interfejs Aurora w czasie działania: prompt w openui-lang, specyfikację i pliki statyczne.
  • 100lynx-miniapp
    Tworzy, migruje i sprawdza strony miniaplikacji Douyin renderowane przez Lynx, z kontrolą zgodności TTML i TTSS.

Uwagi i zgłoszenia

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