Roadmap
What works today, what we're building next, and what stays research until it earns its place.
Read the menus. Save the list.
The part working now. We launch a PC game, walk the settings screens, and write down each option: name, value, menu path, screenshot, and feature matches.
Play the game. Measure what each setting costs.
Next, tests need to leave menus and capture useful frame-rate data from real gameplay. The Decky plugin returns here as a read-only way to surface recommended settings once those recommendations exist.
Pick an FPS target. The plugin handles the rest.
When the cost map is good enough, the Decky plugin can ask one simple question when a tested game launches: apply optimized settings for 30, 40, 45, or 60 FPS?