Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

docs-sync

Estrelas0

Forks0

Atualizado10 de julho de 2026 às 13:46

When a feature lands or behavior changes, update every documentation artifact it touches — driven by a change-type → checklist table, ended by the docs-drift tripwire. Use after merging any user-visible change (new hook, widget, grammar/directive change, behavior change, perf change).

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

yanivkalfa

yanivkalfa/ReactiveUI-Unreal

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	docs-sync
description	When a feature lands or behavior changes, update every documentation artifact it touches — driven by a change-type → checklist table, ended by the docs-drift tripwire. Use after merging any user-visible change (new hook, widget, grammar/directive change, behavior change, perf change).

Docs sync

Input: the merged change (PR title/diff or plan phase). Look it up in the table; do every cell; finish with the tripwire. Haiku-class-executable: table lookup + templated edits + one command.

Change-type → artifact checklist

Change	Update ALL of
New hook	docs hooks reference page (from `templates/hook_doc.template.tsx`) · README hook-count line (if claimed) · docs-site hooks table · `new-component` skill's hook list
New widget wrapper (`RUI::*`)	prop-map schema entry (single source — the LSP + docs both read it) · docs elements page regenerates · README widget-count line (if claimed)
New style key	style-keys docs section · the widget's prop-map entry
Grammar / directive change	`.uetkx` syntax docs page · `new-component` skill · LSP schema/vocabulary note · cross-repo byte-compat: corpus case landed per `grammar-contract` (and siblings notified)
Behavior change	README "Notes & limitations" · docs page of the affected subsystem · store-listing template if user-facing (`templates/fab-listing.template.md`)
Perf change	README/docs perf claims ONLY with the measured numbers from `plans/BENCH_BASELINES.md` (never unmeasured — MASTER_PLAN §6 DO-NOT-CLAIM)
New diagnostic code	the Diagnostics catalog source (docs page generates from it)
New CVar / console command	Debugging docs page · CLAUDE.md conventions block

The tripwire (always the last step)

node scripts/docs-drift.mjs

The wiring rule: any PR that introduces a user-facing COUNT claim ("N hooks", "M widgets") must add a matching check to scripts/docs-drift.mjs's CHECKS in the same PR — a claim without a tripwire is how READMEs rot.

Scar tissue (why these steps exist)

The sibling repo's README once claimed "MVP / 10 elements / 6 hooks" while shipping ~60 elements and 23 hooks — months stale, found by accident. The tripwire + this table are the automated version of "never again".
Counts are claimed in ONE place per artifact and always tripwired — duplicated counts drifted independently.
Grammar changes notify siblings — a "small" directive tweak that skipped the corpus once cost a cross-repo divergence hunt; the corpus case IS the notification.

Mais deste repositório

mesmo repositório

engine-catchup

yanivkalfa/ReactiveUI-Unreal

The runbook for supporting a NEW Unreal Engine version (5.7, 5.8, …) — run the header-diff automation, classify what changed in Slate/UMG, and walk the implementation checklist (widgets, schema, docs version manifest, CI matrix, per-engine packaging). Ported from the Unity sibling's add-unity-version process. Use whenever Epic releases an engine version the plugin should support.

2026-07-250

dev-process

yanivkalfa/ReactiveUI-Unreal

The house development methodology for ReactiveUI-Unreal — the research→develop→test→bughunt→fix→commit loop, the UE gate ladder (compile → suites → boot check → demo), branch/PR model, changelog/version tables, and the laws that never bend. Use for any code change in this repo.

2026-07-180

grammar-contract

yanivkalfa/ReactiveUI-Unreal

How the .uetkx grammar stays byte-compatible with the family (.uitkx Unity — the origin; .guitkx Godot) and how the two in-repo implementations (C++ compiler, TS language server) stay in lockstep — corpus cases, goldens, the .pending divergence protocol, and cross-repo sync. Use for ANY lexer/parser/formatter change, and at release time for the sibling drift check.

2026-07-170

new-component

yanivkalfa/ReactiveUI-Unreal

Author a .uetkx component for ReactiveUI-Unreal — file placement, declaration kinds and companion-file layout, props/hooks/events/directives/styling syntax, what the compiler generates, and the done-checklist. Use when writing or reviewing .uetkx markup. (Toolchain lands in Phase 3 — until then this is the authoring contract.)

2026-07-170

release-process

yanivkalfa/ReactiveUI-Unreal

The ReactiveUI-Unreal release runbook — draining the pending changelog, version bumps, the two-lane changelog system, packaging per engine version, the merge→fast-forward→Publish flow, and the manual Fab checklist with its compliance items. Use when preparing, staging, or publishing a release of any artifact.

2026-07-160

test-run

yanivkalfa/ReactiveUI-Unreal

The exact incantations to build and run this repo's test suites headlessly — UE's CLI is arcane and these commands are load-bearing, in this order. Use whenever building or running ReactiveUI.* automation suites, benches, or the markup drift gate.

2026-07-140

name	docs-sync
description	When a feature lands or behavior changes, update every documentation artifact it touches — driven by a change-type → checklist table, ended by the docs-drift tripwire. Use after merging any user-visible change (new hook, widget, grammar/directive change, behavior change, perf change).

Docs sync

Input: the merged change (PR title/diff or plan phase). Look it up in the table; do every cell; finish with the tripwire. Haiku-class-executable: table lookup + templated edits + one command.

Change-type → artifact checklist

Change	Update ALL of
New hook	docs hooks reference page (from `templates/hook_doc.template.tsx`) · README hook-count line (if claimed) · docs-site hooks table · `new-component` skill's hook list
New widget wrapper (`RUI::*`)	prop-map schema entry (single source — the LSP + docs both read it) · docs elements page regenerates · README widget-count line (if claimed)
New style key	style-keys docs section · the widget's prop-map entry
Grammar / directive change	`.uetkx` syntax docs page · `new-component` skill · LSP schema/vocabulary note · cross-repo byte-compat: corpus case landed per `grammar-contract` (and siblings notified)
Behavior change	README "Notes & limitations" · docs page of the affected subsystem · store-listing template if user-facing (`templates/fab-listing.template.md`)
Perf change	README/docs perf claims ONLY with the measured numbers from `plans/BENCH_BASELINES.md` (never unmeasured — MASTER_PLAN §6 DO-NOT-CLAIM)
New diagnostic code	the Diagnostics catalog source (docs page generates from it)
New CVar / console command	Debugging docs page · CLAUDE.md conventions block

The tripwire (always the last step)

node scripts/docs-drift.mjs

Scar tissue (why these steps exist)

The sibling repo's README once claimed "MVP / 10 elements / 6 hooks" while shipping ~60 elements and 23 hooks — months stale, found by accident. The tripwire + this table are the automated version of "never again".
Counts are claimed in ONE place per artifact and always tripwired — duplicated counts drifted independently.
Grammar changes notify siblings — a "small" directive tweak that skipped the corpus once cost a cross-repo divergence hunt; the corpus case IS the notification.