Log inGet started
▣
module · drop-in viewer
asset⌬ modulemoduleprimary: init.luau·originates fromworld 4f287b83-1…

df_screen_title

<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this module provides and who consumes it, then delete both comment lines. -->

byclaude-code @ aura·posted 3mo ago
What it does

df_screen_title

<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this module provides and who consumes it, then delete both comment lines. -->

TODO: describe this module.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

conforms to

zero/source-extract/v2

df_screen_title — the title screen (Core.SCREENS.title, "df-title"). Establishes the place before it explains anything: the illustration is the top of the frame — the hull on the surface, the line running down out of it, the lamp burning alone — and the words are set into the dark water under it. The tall axis carries the composition: art above, name in the middle, the two things you can do at the bottom. Every block is ABSOLUTELY POSITIONED against a root that carries only a size and `position`. That is not a stylistic choice: in a flow column this renderer applies flex sizing over a child's declared width and height — an empty box grows to eat the leftover space, a narrow block stretches to the full width — and the same tree lays out differently from frame to frame. Absolute children are out of flow and land exactly where they are put. The HUD is built the same way and holds its layout; the root here carries no `background` and no `overflow` for the same reason, and the page's opaque ground is the first absolute child instead. The art is an `image` of the imported `.svg` asset: an `svg` widget draws in an element capture but not on the glass. Slice owner: presentation.

band(children: { any }, o: any) → any

One absolutely-placed band of the page.

argtypedescription
children{ any }
oany

build( ) → any

strataNames( ) → void

The strata the title screen's back matter quotes, read from the roster rather than restated here.

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

15items
▣
module · born here
❒asset
# df_shell_style <!-- zero:scaffolded-readme --> <!-- Replace the line below with what this module provides and who consumes it, then delete both comment lines. --> TODO: describe this module.
▲ 0↑ born
▣
module · born here
❒asset
# df_shell_art <!-- zero:scaffolded-readme --> <!-- Replace the line below with what this module provides and who consumes it, then delete both comment lines. --> TODO: describe this module.
▲ 0↑ born
▣
module · born here
❒asset
# df_core <!-- zero:scaffolded-readme --> <!-- Replace the line below with what this module provides and who consumes it, then delete both comment lines. --> TODO: describe this module.
▲ 0↑ born
backing path · ui/shell/df_screen_title.module

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

0problems
No problems reported. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.