Implementation by source
Prompts that read like product, code, design, debugging, or deployment work.
YGOPLUS · public analysis layer
How the build history took shape.
A readable layer on top of the build history: what kept getting built, where the assistant loop helped, and when the work found its rhythm.
- Prompts analyzed
- -
- Most active day
- -
- Longest run
- -
- Implementation prompts
- -
- Assistant surfaces
- -
Build style
What the build history says about how this project got made.
Dominant pattern
-
Loading profile.
Implementation footprint
How much product work the assistant loop carried.
Implementation prompts include all assistants.
Implementation by focus area
Where the product work clustered.
About file counts
-
Exact edited-file counts are treated as secondary metadata, not the main measure of implementation.
Activity rhythm
The hours and days that carried the work.
Weekdays
The weekly cadence.
Sources
Where the work was captured.
Months
The busiest build months.
Focus areas
What the prompts were usually about.
Longest prompting runs
Focused stretches of iteration.
Grouped when prompts arrive within 45 minutes of each other.
Build read
A working record of shipping, debugging, and polishing YGOPLUS.
Primary pattern
Loading profile.
Most prompts are practical: fix the rough edge, wire the feature, clean the interface, check the data.
Implementation prompts
-
This counts product, code, design, debugging, and deployment work across every assistant surface.