← Back

amkrMWkekMTpVBgmObjj7e1997:2

wicked websites internal

https://www.figma.com/design/amkrMWkekMTpVBgmObjj7e/Wicked-Websites-Internal?node-id=1997-2&t=ZvKA4YKOpudH9yMo-11

not-readyneeds-fixesrender: coded

Preflight

Frame needs design cleanup before demo generation or dev handoff.

Design gate fix-first

Blocked because score 68 is below the demo threshold 85; status is not-ready, but demo generation requires ready-to-go.

Demo verdict: blocked

The frame still needs too much cleanup before it can be trusted as a clean demo.

Score

68/100

Checked

4/16/2026, 1:44:36 PM

Recommended action

Request fixes

Demo verdict

Blocked

Demo eligibility

Blocked by strict gate

Override history

0

Structural absolutes

0

Decorative absolutes

0

Fixed width blocks

0

Fixed height blocks

0

Design review lanes

Layout2 issues
Root frame is composed from many loose groups, text layers, and shapes instead of section frames.warning

Fix: Wrap major sections into named frames/components before handoff so the page has durable structure instead of artboard-level placement.

Targets
  • 'PORTFOLIO INSIDE ' > Group 114 [1997:3]
  • 'PORTFOLIO INSIDE ' > Group 3 [1997:7]
  • 'PORTFOLIO INSIDE ' > Rectangle 37 [1997:13]
  • 'PORTFOLIO INSIDE ' > Group 4 [1997:14]
  • 'PORTFOLIO INSIDE ' > Rectangle 93 [1997:17]
  • 'PORTFOLIO INSIDE ' > Group 171 [1997:18]
Frame relies heavily on GROUP containers, which weakens responsive and handoff structure.warning

Fix: Convert structural groups into named Auto Layout frames/components, especially at section, card, and control boundaries.

Targets
  • 'PORTFOLIO INSIDE ' > Group 114 [1997:3]
  • 'PORTFOLIO INSIDE ' > Group 3 [1997:7]
  • 'PORTFOLIO INSIDE ' > Group 3 > Group 2 [1997:10]
  • 'PORTFOLIO INSIDE ' > Group 38 [1997:53]
  • 'PORTFOLIO INSIDE ' > Group 38 > Group 33 [1997:54]
  • 'PORTFOLIO INSIDE ' > Group 143 [1997:1156]
Responsiveness1 issue
No wrapping Auto Layout groups detected.info

Fix: Add wrap or a mobile stacking rule to these multi-item rows before handoff.

Score breakdown

Start 92 → end 68. Demo threshold 85; ready-to-go threshold 85.

Layout
FREEFORM_ROOT_COMPOSITION-12

The root frame has too many loose top-level layers (76 freeform vs 1 section frames).

GROUP_HEAVY_STRUCTURE-8

Structural grouping is too heavy (44 GROUP layers), which usually means weaker responsive structure.

Responsiveness
NO_WRAP_LAYOUTS-4

No wrapping groups were detected, which increases responsive layout risk.

Issues

Root frame is composed from many loose groups, text layers, and shapes instead of section frames.warning

Wrap major sections into named frames/components before handoff so the page has durable structure instead of artboard-level placement.

Evidence: 'PORTFOLIO INSIDE ' > Group 114 [1997:3], 'PORTFOLIO INSIDE ' > Group 3 [1997:7], 'PORTFOLIO INSIDE ' > Rectangle 37 [1997:13], 'PORTFOLIO INSIDE ' > Group 4 [1997:14], 'PORTFOLIO INSIDE ' > Rectangle 93 [1997:17], 'PORTFOLIO INSIDE ' > Group 171 [1997:18]

Frame relies heavily on GROUP containers, which weakens responsive and handoff structure.warning

Convert structural groups into named Auto Layout frames/components, especially at section, card, and control boundaries.

Evidence: 'PORTFOLIO INSIDE ' > Group 114 [1997:3], 'PORTFOLIO INSIDE ' > Group 3 [1997:7], 'PORTFOLIO INSIDE ' > Group 3 > Group 2 [1997:10], 'PORTFOLIO INSIDE ' > Group 38 [1997:53], 'PORTFOLIO INSIDE ' > Group 38 > Group 33 [1997:54], 'PORTFOLIO INSIDE ' > Group 143 [1997:1156]

No wrapping Auto Layout groups detected.info

Add wrap or a mobile stacking rule to these multi-item rows before handoff.

Actions

Strict gate first. Parser, scene cache, and operator actions should stay visible here, not hidden behind API trivia.

Scene cache present

/app/data/scenes/wicked-websites-internal-1997-2.txt

65,537 bytes • updated 4/16/2026, 1:44:36 PM

Fix-first mode

This frame should stay in correction mode until the blocking design issues are fixed.

Demo verdict: blocked

The frame still needs too much cleanup before it can be trusted as a clean demo.

Reference export

Standard publish stays locked until the frame clears the strict readiness gate.

Discord handoff block

Copy this directly into Discord or a dev handoff thread.

Links

Reference export

/diagnostic/wicked-websites-internal-1997-2

Generated preview

Not generated yet.

/generic/wicked-websites-internal-1997-2

/ai-preview/wicked-websites-internal-1997-2

/compare/wicked-websites-internal-1997-2

Published

Not published yet.

Artifacts

/data/openclaw/workspace-personal-assistant/reports/figma/amkrmwkekmtpvbgmobjj7e-1997-2.md

/data/openclaw/workspace-personal-assistant/reports/figma/amkrmwkekmtpvbgmobjj7e-1997-2.json

Scene cache

/app/data/scenes/wicked-websites-internal-1997-2.txt

Present • updated 4/16/2026, 1:44:36 PM

Discord flow

Target commands: check https://www.figma.com/design/amkrMWkekMTpVBgmObjj7e/Wicked-Websites-Internal?node-id=1997-2&t=ZvKA4YKOpudH9yMo-11, recheck, go, publish, status.

Current rule: go/generate should open the standard preview route for a registered demo. If no dedicated implementation exists yet, preview uses the exact-frame path. Publish still requires the stricter gate and a dedicated implementation.