updated skills

plugins/document-navigator/docs/ui/forms/form-builder/README.md

@@ -125,4 +125,3 @@ await submit({
 ## License
 
 MIT.
-

plugins/document-navigator/docs/ui/forms/form-builder/src/otel/instruments/instruments.md

@@ -12,7 +12,7 @@ instruments emitted across the package: three counters
 `form_builder.submission.total`) and two histograms
 (`form_builder.validation.duration_ms`, `form_builder.submission.duration_ms`).
 Lazy resolution lets test environments install a custom `MeterProvider`
-via `metrics.setGlobalMeterProvider` *after* the module is imported and
+via `metrics.setGlobalMeterProvider` _after_ the module is imported and
 still observe production emissions.
 
 A test-only `_resetInstrumentsForTests` is exported so the lazy cache can

plugins/document-navigator/docs/ui/forms/form-builder/src/serialise/serialise/serialise.md

@@ -62,7 +62,7 @@ try {
 The envelope wraps the schema rather than annotating it inline because that
 keeps the schema body untouched and lets the version discriminator be a
 plain object key rather than a magic field embedded in the schema. The
-implementation deliberately performs the version check *before* delegating
+implementation deliberately performs the version check _before_ delegating
 to `parseFormSchema`, so callers see a clear "wrong version" error rather
 than a flood of Zod-issue noise when the inner shape is for a future
 release.

plugins/document-navigator/docs/ui/forms/form-builder/src/zod-schema/zod-schema/zod-schema.md

@@ -54,7 +54,7 @@ import { toZodSchema } from "@suaveplan/form-builder";
 Every field is wrapped in `.optional()` so the generated schema accepts
 partially-filled drafts; the `superRefine` step is the canonical layer
 that decides whether a value is structurally required. This means the
-schema validates against the *current* values being parsed, which is what
+schema validates against the _current_ values being parsed, which is what
 `react-hook-form` consumers expect for conditional UIs. We deliberately
 avoid `z.discriminatedUnion` over field types because field types are an
 attribute of the schema, not the value space.