The current panel is a star-map presentation over data-driven perk nodes. One lane is live now: Miner. The remaining lanes are present as planned data and need consumer checks before public wording treats them as shipped behavior.
Skill Constellations panel, opened from the live HUD path.
Live Miner Lane
Perk
Cost
Effect key
Effect value
Requires
Status
Stone Recovery
1
mining_speed
1.15
none
Live mechanical value.
Deep Sense
1
detect_ore_range
1.20
Stone Recovery
Groundwork; needs ore sensing feature before it is meaningful in play.
Tunnel Safety
2
cave_safety
1.20
Stone Recovery
Groundwork; needs cave hazard feature before it is meaningful in play.
Serious Work Needed
Area
Why it matters
Suggested next definition
Lane ownership
Planned lanes exist, but their gameplay loops are unevenly defined.
Add one acceptance note per lane: XP source, first useful perk, and live system dependency.
Effect semantics
Some effect keys are groundwork without shipped consumers.
Split every perk into live consumer, stub consumer, or no consumer yet.
Image direction
The star-map panel has a clear mood, but no authored skill icon set is documented.
Add a future skill-art convention only after runtime code agrees.
Balance
Current costs are readable, but not tied to a broad progression curve.
Record target time-to-first-perk, time-to-branch, and total points by milestone.
Continuation Prompt
Continue Coheronia skill-system planning from the current repo state. Read docs/wiki/skills.md, data/progression/perks.json, scripts/ui/skill_tree_panel.gd, and the live progression/save code before editing. Keep wiki wording separated from runtime changes. Do not imply planned lanes are shipped gameplay. For every proposed skill addition, document the effect key, live consumer, XP gate, prerequisite, cost, and art need. Avoid references to named commercial games, studios, characters, sprite sheets, UI styles, or living artists.