Machine-readable reference
Find the cause and correction among 107 canonical rules. Filter by ID, principle, severity, and automation level. This full catalog includes manual checks; it is not the list of checks the plugin runs automatically.
identity.missing-stable-identityImportant transferable elements, including decorative and asset roots, must have a stable identity: a stable layer name or an identity-bearing fallback tag value.
Use an English kebab-case layer name when Figma metadata provides the type. Boolean `[decor]` and `[asset]` are visual-intent/policy flags and are not enough by themselves to identify a poorly named layer.
identity.duplicate-identityTwo elements inside the same declared audit context—such as one page breakpoint/view or one selected-section variant—must not share one stable design identity.
Prefer semantic fixture keys that survive reordering, such as `product-card-sku-blue`; use positional indexes such as `product-card-1` only as a design-fixture fallback. Never treat a positional suffix as a runtime data key.
identity.same-identity-different-typeThe same identity must not resolve to different logical element types across comparable declared responsive contexts, including explicitly selected variants of one section.
Keep the Figma node/component type stable across the declared contexts or model a separate entity. Do not invent page or breakpoint tags on a selected section.
identity.breakpoint-specific-idOptional DFC Bridge identity values must describe logical elements, not responsive breakpoints. A value such as `[control=button-reviews-box-375]` inside a `[bp=375]` root is invalid when the suffix matches the current breakpoint.
Remove the breakpoint suffix from the optional id. For ordinary buttons/controls, remove the optional id completely and use `Отзывы мобилка [action=modal:marketplaces-modal]`.
identity.repeated-item-no-indexAuthored repeated list or grid occurrences need distinct stable design-instance anchors. `[item=...]` only classifies their shared repeated role or type; it is not an instance identity.
Give each occurrence a meaningful stable layer or design-instance key, such as `product-card-oak-chair` and `product-card-wool-lamp`, while both may use `[item=product-card]`. Use numeric fixture suffixes only as a fallback, never as runtime-data identity.
identity.multiple-identity-tagsOne layer must not declare multiple competing identity tags such as `[section=...]` and `[modal=...]`.
Keep the one tag that represents the layer's logical identity. Express behavior and visual intent with non-identity tags such as `[href=...]`, `[action=...]`, `[decor]`, or `[asset]`.
syntax.decor-asset-value-not-kebab-caseBoolean `[decor]` and `[asset]` are valid without values. If a fallback value is present in `[decor=...]` or `[asset=...]`, it must be English kebab-case.
Prefer a stable layer identity plus boolean flags, for example `sneg [decor] [asset]`. Use value form only for poor/default layer names, for example `Frame 182 [decor=snow-bg]`.
syntax.identity-value-not-kebab-caseAuthored identity-like tag values, anchors, and views should use stable English kebab-case so validators and adapters can compare them deterministically.
Replace spaces, localized words, uppercase characters, and punctuation with a stable English kebab-case value such as `product-card-1`, `contact-modal`, `faq`, or `not-found`.
identity.decor-asset-flags-not-identities`[decor]` and `[asset]` are visual-intent/policy flags and must not be counted as identity tags or as multiple identities when they appear together.
Resolve identity from the stable layer name such as `sneg`; keep `[decor]` and `[asset]` as flags. Use `[decor=...]` or `[asset=...]` only as fallback for poor/default layer names.
syntax.duplicate-tagA layer must not repeat the same DFC Bridge tag key.
Keep one canonical value for the key. If two values describe different concerns, model them with the appropriate distinct tags or split the logical entities.
syntax.figma-metadata-tag-invalidTags derived from native Figma metadata, including `[text]`, `[image]`, `[icon]`, `[container]`, `[layout]`, `[abs]`, and `[component]`, must not be authored in layer names.
Remove the metadata tag and express the property through the native Figma node type, component source, layout mode, positioning, fills, or export settings.
section.role-prefix-in-nameSection layer names should not repeat the role with prefixes such as `Section /` or `Секция /`.
Keep the human label concise. Resolve the section from the `Page Sections` source component when possible, or use `[section=...]` only for frame sections, generic components, or explicit overrides.
section.identity-as-human-headingA section key should describe the reusable section component, not copy the page-specific heading.
Use the layer name for the contextual heading. Resolve the stable section key from `Page Sections` or use `[section=...]` only when an explicit fallback/override is needed.
section.component-source-unclassifiedA page-level section component instance should come from the `Page Sections` library page, or the layer should declare an explicit `[section=...]` fallback.
Move the source component to `Page Sections`, register it as a section component, or add `[section=...]` only when the layer is a frame section, a generic component, or an explicit override.
section.redundant-instance-section-tagInstances of components from `Page Sections` should not repeat `[section=...]` on the page layer.
Remove the redundant page-layer `[section=...]`; resolve section id from the source component or component set name.
component.ui-kit-used-as-sectionComponents from `UI Kit` are ordinary interface components and should not be inferred as page sections.
Use a component from `Page Sections` for a page-level section, or add `[section=...]` only for a deliberate frame section or override.
naming.default-layer-nameDefault names such as `Frame 53` or `Group 271` usually hide missing structure or intent.
Rename the layer with a stable English kebab-case identity; add DFC Bridge intent tags only where needed.
layout.missing-roleEvery layer must be classifiable from Figma metadata or DFC Bridge intent tags.
Fix the Figma structure/metadata first; add DFC Bridge tags only for product or transfer intent such as `[section=...]`, `[href=...]`, `[link]`, `[action=...]`, `[control]`, `[field=...]`, `[decor]`, `[asset]`, `[modal=...]`, or `[state=...]`.
layout.page-root-missing-auto-layoutEvery DFC Bridge page root must use native Figma Auto Layout, even when it has zero or one child. A page root is a responsive content container, not primitive or leaf geometry, and cannot mark itself `[asset]` to bypass the rule.
Enable vertical, horizontal, or grid Auto Layout on the page root and define its padding, gap, alignment, and wrapping in Figma. `[asset]`, `[decor]`, absolute positioning, and an exception tag on the page root do not suppress this blocking finding.
layout.page-root-cannot-be-assetA DFC Bridge page root must not carry `[asset]`. A page is a live responsive content contract, never one opaque exported visual; root-level `[asset]` does not create an opaque boundary and descendants must still be validated.
Remove `[asset]` from the page root, keep native Auto Layout on the root, and apply `[asset]` only to genuine descendant visuals transferred as opaque units. Report the Auto Layout finding separately when the same page root also has layout mode NONE.
layout.section-missing-auto-layoutEvery editable non-page FRAME or COMPONENT carrying `[section]` that is encountered in a declared audit tree—either a page tree or a selected-section subtree—must use native Figma Auto Layout, even with zero or one child, unless that exact node is a legitimate opaque whole-visual `[asset]` with no live content flow. For selected-section entry, `[asset]` must be on that exact section root; a section below a different non-page-root opaque asset ancestor is a blocked scope precondition, not an inherited exemption. An invalid page-root `[asset]` never creates opacity. A placed INSTANCE is atomic and excluded from this rule; source-tool checks do not resolve or inspect its source component.
Enable Auto Layout on the encountered `[section]` FRAME or COMPONENT. Audit a placed instance's editable source component separately; do not flatten or detach the instance as a workaround. `[decor]` and exception tags do not waive the section layout contract; use `[asset]` only on a genuinely opaque whole-visual section root, and move a live section outside any ancestor asset boundary.
layout.container-missing-auto-layoutAn Auto Layout-capable content container outside an `[asset]` subtree with at least two visible meaningful direct children participating in content flow must use native Figma Auto Layout. Primitive and leaf geometry are exempt.
Enable native Auto Layout and express direction, padding, gap, alignment, wrapping, and sizing in Figma. Intended absolute visual children may remain absolute inside that parent, but `[decor]` and exception tags do not turn the parent into a manual-layout container or suppress this finding.
layout.group-outside-assetA Figma GROUP outside an `[asset]` subtree is invalid because it encodes geometry without a transferable layout contract. `[decor]` alone is not an exemption, and `[bridge-exception=manual-layout] [reason=...]` records a proposed deviation without suppressing this blocking finding.
Replace the GROUP with a frame or component using native Auto Layout. If the whole subtree is transferred as one opaque visual, mark its root `[asset]` and add `[decor]` only when it is ornamental. When conversion is genuinely impossible, record manual-layout and a specific reason on that GROUP, then process the still-reported finding through the separate deviation-acceptance gate.
layout.positioned-without-intentAn absolutely positioned, visually detached, or overlapping element outside an `[asset]` subtree must have clear intent on that exact node. `[decor]` is valid only for the intended absolute visual layer and does not exempt a parent or freeform subtree from Auto Layout and GROUP rules.
Keep geometry in native Figma positioning. Mark an intended absolute ornament `[decor]`, a whole opaque visual `[asset]`, or use an appropriate modal/state target. For an intentional overlay that cannot be modeled otherwise, use `[bridge-exception=overlay] [reason=...]`; never put `[decor]` on a container merely to silence layout errors.
layout.one-child-wrapper-without-roleA one-child wrapper without a structural reason is likely unnecessary noise.
Remove the wrapper or make its Figma purpose clear through structure, naming, clipping, shared surface, target scope, or asset grouping.
layout.wrapper-chain-too-deepDeep wrapper chains often make responsive mapping fragile.
Flatten structure or ensure each wrapper has a real Figma purpose.
layout.overlap-without-overlay-roleOverlapping bounds require clear overlay, absolute decor, whole-asset, target, or explicit exception intent on the overlapping node.
Declare `[decor]` only on the intended absolute visual layer, use `[asset]` for an opaque visual subtree, add the appropriate target tag, or record `[bridge-exception=overlay] [reason=...]`. Positioning still comes from Figma metadata.
layout.z-index-ambiguousLayer order is visually important but not declared as overlay/stacking intent.
Declare overlay scope or stacking behavior.
responsive.missing-breakpoint-rootResponsive root frames must declare `[bp=...]`.
Add explicit breakpoint tags to root frames.
responsive.view-missing-required-breakpointEvery declared page view must have a root for each required breakpoint in that page contract.
Add the missing `[page=...] [view=...] [bp=...]` root, or remove the breakpoint/view from the declared page contract when it is not actually required.
responsive.identity-missing-in-required-breakpointAn important identity exists in one required comparable responsive context but is missing from another explicitly declared context for the same page/view or selected section.
Keep the same identity in the same parent and change responsive visibility instead of deleting it, or model a separate state, variant, collection rule, or structural exception. An unrequested section variant is not a missing context.
responsive.tree-cardinality-changedComparable responsive roots for the same page/view or explicitly selected section variants do not preserve the same logical element tree/cardinality.
Keep the same transferable identities across the declared responsive contexts, or model the difference as a collection rule, state, variant, or structural exception.
responsive.parent-changed-across-breakpointsA transferable identity changes parent identity across comparable declared responsive contexts, including explicitly selected variants of one section.
Preserve parent-child topology across the declared contexts, use shared wrappers, or declare an explicit structural exception.
responsive.order-changed-without-reasonSibling order changed across breakpoints without an order strategy.
Preserve semantic order or declare an order strategy.
responsive.visual-intent-driftThe same identity has different visual-intent/policy tags across comparable declared responsive contexts, for example `sneg [decor] [asset]` in one selected variant and plain `sneg` in another.
Keep visual-intent flags stable across the declared contexts, or model the difference as an explicit state, variant, target-specific rule, or DFC Bridge exception.
content.text-changed-between-breakpointsThe same product text identity has different content across comparable declared responsive contexts, including explicitly selected variants of one section. Text inside decorative or root asset visuals is excluded from product-content drift checks.
Keep responsive product text identical. Model locale, experiment, or product variants outside responsive variants. For decorative or root asset visuals, preserve the root identity and visual-intent tags instead of comparing inner text as product content.
content.decorative-asset-text-excluded-from-product-driftText inside `[decor]` layers or root `[asset]` visuals is not product content and should not be reported as product-content drift.
Skip inner text product-drift comparison for decorative/root asset visuals, but still validate root identity coverage and visual-intent stability across breakpoints.
content.manual-line-break-in-dynamic-textDynamic text must not rely on forced line breaks or <br> to fit the layout.
Let text wrap by its container using hug/min-height, max-width, and explicit overflow/truncation rules. Use `[bridge-exception=manual-line-break] [reason=...]` only for semantic or approved brand-lockup breaks.
content.manual-line-break-exception-without-reasonA manual line break exception must explain why the break is semantic or brand-required.
Pair `[bridge-exception=manual-line-break]` with `[reason=...]`, for example `[reason=brand-lockup]` or `[reason=postal-address-format]`.
content.strict-content-driftStrict content such as price, legal copy, or CTA changed across breakpoints.
Synchronize strict content or document an approved variant.
interaction.clickable-without-actionA visually clickable element has no known interaction marker: no `[href=...]`, `[action=...]`, `[link]`, or `[control]`.
Add `[href=...]` for known navigation, `[action=...]` for known non-navigation behavior, `[link]` for an unknown draft destination, or `[control]` for an unknown draft action.
interaction.control-without-actionBoolean `[control]` or advanced `[control=...]` without `[action=...]` is a valid draft marker for an unknown action, not a syntax error. Final handoff should resolve it.
If the action is known, replace the draft marker with `[action=modal:...]`, `[action=state:...]`, `[action=submit:...]`, `[action=reset:...]`, or `[action=none]`. Keep `[control=...]` only as an optional advanced id when a stable machine id is needed.
interaction.link-without-hrefBoolean `[link]` or advanced `[link=...]` without `[href=...]` is a valid draft marker for an unknown destination, not a syntax error. Final handoff should resolve it.
If the destination is known, use `[href=...]`. Keep `[link=...]` only as an optional advanced id when a stable machine id is needed. Do not use `[href=#]` as a placeholder.
interaction.link-has-second-destinationLinks must not declare a second destination such as `[to=...]` or `[action=link:...]` alongside `[href=...]`.
Keep only `[href=...]` for navigation destination. `[href=...]` is already enough to classify the layer as a link.
interaction.href-placeholder-invalid`[href=#]` is not a valid unknown href placeholder. `#faq` is a real same-page anchor; `#` alone does not declare a destination.
Use `[link]` while the destination is unknown, or replace `#` with a real href such as `[href=#faq]` or `[href=/contacts]`.
interaction.optional-id-value-invalidAdvanced optional ids in `[link=...]` and `[control=...]` must be English kebab-case and must not include breakpoint names or width suffixes when a value is present.
Prefer no optional id for ordinary links/buttons: use `[href=...]`, `[link]`, `[action=...]`, or `[control]`. If an id is required, use a breakpoint-neutral kebab-case value.
interaction.href-invalidAn `[href=...]` value must be a supported real destination: an internal path, same-page anchor, `http`/`https` URL, `mailto:` URL, or `tel:` URL.
Correct the destination syntax. If the destination is not known yet, remove `[href=...]` and use the boolean draft marker `[link]`.
interaction.action-invalidAn `[action=...]` value must use a supported action grammar: `modal:target-id`, `state:target-id`, `submit:form-id`, `reset:target-id`, or `none`.
Correct the action value and use a breakpoint-neutral kebab-case target id. If the action is not known yet, remove `[action=...]` and use the boolean draft marker `[control]`.
interaction.control-action-duplicateOne control must not declare more than one `[action=...]` value.
Keep one canonical action. Model alternative behavior as an explicit state, variant, or separate control.
interaction.modal-target-missingA modal action must point to an existing modal target.
Create `[modal=target-id]` target or change the action.
interaction.state-target-missingA state action must point to an existing state target.
Create `[state=target-id]` target or change the action.
interaction.form-target-missingA submit action must point to an existing form target in the same page contract.
Create `[form=target-id]` or change `[action=submit:...]` to the correct form id.
interaction.reset-target-missingA reset action should point to an existing state, form, or other declared reset target in the same page contract.
Create the declared target or change `[action=reset:...]` to the identity that owns the resettable state.
interaction.modal-missing-closeModal targets need close behavior.
Add close button/action and define backdrop/escape behavior.
interaction.form-field-missing-labelForm fields need labels or accessible names.
Add label text and field identity.
interaction.form-missing-submit-actionForms need a submit action or declared endpoint/handler.
Add `[action=submit:...]` to the submit control or form.
state.required-state-missingInteractive or dynamic components often need empty, loading, error, disabled, hover, or focus states.
Add required states or declare why they are not needed.
height.fixed-height-without-reasonFixed height must be intentional.
Use hug/min-height or add `[height=fixed] [reason=...]`.
overflow.text-clipping-riskText appears likely to clip due to fixed height or insufficient bounds.
Use hug height, min-height, or truncation policy.
asset.raster-text-without-reasonText-like content should not be exported as a raster asset without reason.
Use native text or add asset exception reason.
asset.image-missing-focal-pointResponsive images need a crop/focal strategy.
Declare focal point, fit mode, or crop policy.
asset.media-missing-fallbackVideo/Lottie/complex media should define fallback behavior.
Add poster, fallback asset, controls, and autoplay policy.
design-system.token-missingColor, typography, radius, or spacing values appear detached from tokens.
Use design tokens or declare an exception.
accessibility.touch-target-too-smallInteractive target is smaller than recommended touch size.
Increase hit area or declare target-specific exception.
accessibility.contrast-riskText/background contrast may be insufficient.
Adjust colors or document intentional exception.
accessibility.decorative-layer-exposedA `[decor]` layer should not be exposed as product content in the accessibility tree.
Treat the transferred decorative layer as `aria-hidden` or otherwise exclude it from accessibility/content semantics.
component.page-instance-declares-component-tagPage instances should not duplicate Figma component source with `[component=...]` tags.
Remove `[component=...]` from page instance names and rely on Figma/UI Kit metadata.
component.required-state-missingUI Kit component source is missing required states for its component family.
Add states to the UI Kit component set instead of drawing them on a page.
routing.page-route-missingA page root without `[route=...]` or `[route-pattern=...]` is a Draft TODO when the production route is not known yet, not a hard error.
Do not invent fake routes. Add `[route=/path]` or `[route-pattern=/path/:param]` only when the real production route is known.
routing.page-root-requiredPage preflight requires at least one root frame with a stable `[page=...]` identity. A root may be a direct child of the Figma page or reached only through native Figma SECTION canvas organizers.
Add `[page=page-id]` to every responsive root frame that belongs to the page. Keep each root directly on the Figma page or under native Figma SECTION organizers; do not wrap it in an ordinary FRAME/GROUP, then run preflight for that page identity.
routing.default-view-missingEvery page identity should declare a `view=default` root for its normal product state.
Add `[view=default]` to the normal page roots, or create the default view before modeling empty, loading, error, or permission-specific views.
routing.route-not-production-urlWhen `[route=...]` or `[route-pattern=...]` is present, it must be a real production URL/path or route template, not a fake placeholder.
Remove the route while unknown, or replace it with the real production route such as `[route=/contacts]` or `[route-pattern=/catalog/:slug]`.
routing.duplicate-routeTwo concrete pages must not declare the same route unless intentionally modeled as views of one page.
Use one `[page=...]` with multiple `[view=...]` states, or change the duplicate route.
routing.href-internal-route-missingInternal href points to a route that is not declared in the known route contract.
Add a page with the matching real `[route=...]` when known, correct the href, or leave route resolution as a draft TODO if page routes are not known yet.
routing.href-anchor-missingInternal href points to an anchor that is not declared on the target page.
Add `[anchor=...]` to the target section or correct the href fragment.
routing.page-view-route-driftViews or breakpoints of one page identity must not use different known production routes.
Keep one known `[route=...]` across all `[view=...]` and `[bp=...]` variants of the page. If the route is unknown, omit it consistently until it is known.
variation.breakpoint-content-driftProduct content changed across breakpoints without a non-responsive variation axis. Decorative and root asset text is not product content drift.
Keep breakpoint product content identical, or model the change with `[view=...]`, `[locale=...]`, `[experiment=...]`, or another explicit axis. Preserve decorative/asset root identities and tags across breakpoints.
variation.theme-content-driftTheme variants must not change text content.
Keep content identical across themes; theme should change visual tokens only.
variation.axis-overloadOne variation axis appears to hide a different reason for variation.
Use the correct axis: breakpoint for layout, view for data state, locale for translation, experiment for A/B, role-view for permissions.
adapter.unsupported-featureThe selected target adapter does not support a declared feature.
Change the design, add asset fallback, or choose another adapter.
data.source-contract-missingA runtime data display must declare its source or owner, refresh behavior, and the policy for stale or unavailable data.
Add the source dataset or service owner, refresh cadence, freshness threshold, and fallback behavior to the structured data contract.
data.schema-contract-incompleteA data display must declare stable field, dimension, measure, row, and relationship semantics instead of relying on sample values.
Document stable keys, value types, nullability, identifiers, relationships, cardinality, and aggregation semantics in the structured data contract.
data.format-contract-missingData values with locale, time, currency, unit, precision, rounding, or missing-value semantics need an explicit format contract.
Declare locale and time-zone behavior, currency or unit, notation, precision, rounding, and distinct missing or suppressed value markers.
data.required-state-contract-missingA runtime data display must define all applicable loading, empty, error, partial, stale, offline, and unauthorized states and recovery behavior.
Add every applicable data state, its message and retained content, recovery action, announcement behavior, and transition back to usable data.
data.accessible-equivalent-missingA chart, map, canvas, or other complex visual data display must provide an accessible equivalent that exposes the same values and conclusion.
Reference a semantic table, list, description, or downloadable dataset and preserve names, relationships, keyboard operation, and the principal finding.
responsive.transformation-mapping-incompleteA declared responsive structural transformation must map every source identity and meaning to its target composition without silent content or action loss.
Record source identities, target composition, activation range, field and action mapping, semantic and focus order, state preservation, and accessible parity.
interaction.reaction-guard-ambiguousA conditional reaction must define mutually understandable guards, priority, and fallback so the same event cannot resolve ambiguously.
Declare each guard from observable state or data, define precedence for overlapping conditions, and add an explicit default or impossible-case rule.
interaction.reaction-effect-incompleteA reaction must declare every product effect, target, state mutation, navigation, announcement, persistence, and rollback consequence.
Complete the ordered effect list and name stable targets, resulting state, user feedback, persisted values, and rollback or compensating behavior.
accessibility.reaction-focus-effect-missingA reaction that opens, closes, removes, inserts, navigates, or reports content must declare its focus and announcement effects.
Specify initial and restored focus, focus order after mutation, live announcement behavior, and how keyboard users reach the resulting content.
interaction.async-outcome-missingAn asynchronous reaction must define pending, success, empty, failure, retry, cancellation, timeout, duplicate input, and stale-response behavior where applicable.
Model the asynchronous states and transitions, disabled or optimistic controls, retry and cancellation rules, timeout handling, and stale-response suppression.
motion.driver-missingA motion sequence must identify the time, event, scroll, view, media, data, or system driver that deterministically controls it.
Declare the driver type and source, start condition, progress mapping or trigger, repeat policy, and the state reached when the driver ends.
motion.range-or-timing-missingA motion track must define its input range or timing, affected properties, values and units, sequencing, easing, and interruption behavior.
Record start and end values, units, duration or driver range, delays, easing, iterations, dependencies, coordinate space, cancel, reverse, and re-entry behavior.
motion.reduced-motion-strategy-missingEvery nontrivial motion sequence must define a reduced-motion strategy that preserves content, actions, state, focus, and task completion.
Declare which movement is removed or replaced and specify the stable reduced-motion composition, timing, controls, completion state, and focus behavior.
motion.fallback-missingEssential content and actions in motion or long-scroll experiences must remain available without the preferred script, API, sticky, or animation mechanism.
Provide a normal-flow or static fallback, preserve document and action order, and define initialization for unsupported APIs, deep links, resize, and script failure.
motion.essential-content-animation-dependentEssential content, actions, or required product state must not exist only during animation or depend on animation completion events.
Represent meaningful still states in the document, keep required controls reachable, and complete product state independently of animation events or playback.
accessibility.page-profile-missingEach page or major view must declare its accessibility profile, including language, landmarks, heading outline, reading order, focus flow, and announcement regions.
Add the page accessibility profile and review landmarks, one meaningful heading hierarchy, DOM and reading order, skip paths, focus entry, and live regions.
accessibility.component-profile-missingA reusable interactive component must declare semantic role, accessible name and description sources, keyboard model, focus behavior, states, and errors.
Add a component accessibility profile covering native semantics, name computation, keyboard commands, focus visibility and movement, disabled/loading states, and errors.
delivery.required-evidence-missingA delivery gate must include traceable evidence for every required contract, review, automated check, supported target, and acceptance decision.
Attach versioned artifacts, check outputs, review owners and dates, target results, unresolved risks, and the final acceptance record to the delivery manifest.
delivery.deviation-undeclaredAny accepted deviation from the DFC Bridge contract must be declared with scope, reason, risk, owner, expiry or review date, mitigation, and evidence.
Create a delivery deviation record, link affected identities and targets, assign an accountable owner, set review or expiry, and document mitigation and approval.
capability.essential-experience-missingEach delivery target profile must identify the content, actions, data, media, and task outcomes that remain essential under constrained conditions.
List the essential DFC Bridge identities and outcomes for the target, including low bandwidth, offline, data-saver, and low-power conditions where applicable.
capability.unsupported-feature-fallback-missingA required capability that is unsupported by a target must have an explicit fallback and accountable owner without removing essential experience.
Record the unsupported capability, map a semantically equivalent fallback, assign an owner, and verify that essential content, actions, state, and accessibility remain available.
capability.asset-delivery-policy-missingMedia and large visual assets must declare target-aware dimensions, formats, art direction, loading priority, poster or fallback, and quality policy where applicable.
Add an asset delivery profile per relevant target and condition; reference the stable element and define dimensions, formats, quality, crop or art direction, priority, and fallback.
capability.data-scale-strategy-missingA potentially large data surface must declare expected and maximum scale plus pagination, windowing, virtualization, aggregation, or degradation strategy.
Record expected and maximum item counts, choose a deterministic scale strategy, preserve accessibility and selection semantics, and include representative scale evidence.
delivery.performance-budget-evidence-missingA declared performance budget must name the metric, numeric limit, accountable owner, measurement context, and delivery evidence from the target implementation.
Add each metric and limit with units, owner, device or runtime and percentile context, then link reproducible measurement evidence to the delivery lifecycle.
contract.open-question-untrackedEvery unresolved unknown that can affect implementation must be tracked as a scoped open question with owner, blocking status, review timing, and fallback.
Move TODO, TBD, unknown, and unsupported decisions into `bridge.openQuestions`; reference the affected scope, assign an owner, set due or review timing, and define a fallback when blocking.
No rules match these filters.