feat(pygal): implement slope-basic

[github-actions]

Implementation: slope-basic - python/pygal

Implements the python/pygal version of slope-basic.

File: plots/slope-basic/implementations/python/pygal.py

Parent Issue: #981

---

🤖 impl-generate workflow

[claude]

AI Review - Attempt 1/3

Image Description

Light render (plot-light.png): Warm off-white background matching #FAF8F1. Title "slope-basic · python · pygal · anyplot.ai" centered in dark ink, clearly readable. Y-axis title "Sales (units)" rotated on the left, x-axis title "Time Period" below the "Q1 2024" / "Q4 2024" tick labels. Subtle dotted y-only grid. 10 lines connect a Q1 dot to a Q4 dot per product category — rising entities (Furniture, Beauty, Home Decor, Electronics, Sporting Goods, Automotive) in Imprint brand green #009E73, falling entities (Apparel, Food & Bev, Office Supplies, Toys) in matte red #AE3030. Each dot carries its category name directly beside it at both endpoints; legend correctly omitted. All text is clearly readable against the light background.

Dark render (plot-dark.png): Warm near-black background matching #1A1A17. Title, axis titles, and numeric tick labels all render in light ink, clearly legible. Data colors are identical hexes to the light render (#009E73 / #AE3030) — only chrome flipped, as required. Category point-labels render in a muted grayish tone but remain clearly distinguishable from the near-black background — no dark-on-dark failure observed.

Both renders pass the theme-readability check; no legibility failures in either theme.

Score: 82/100

Category	Score	Max
Visual Quality	26	30
Design Excellence	12	20
Spec Compliance	14	15
Data Quality	13	15
Code Quality	10	10
Library Mastery	7	10
Total	82	100

Visual Quality (26/30)

• VQ-01: Text Legibility (6/8) — readable in both themes, but point/category labels (36) are smaller than tick labels (44) and the axis title.
• VQ-02: No Overlap (5/6) — Q1-column labels start right on the vertical gridline, which runs through the first characters of each label.
• VQ-03: Element Visibility (6/6) — dot/stroke sizes appropriately prominent for this sparse 10-point dataset.
• VQ-04: Color Accessibility (2/2) — direction color is redundantly backed by slope geometry, not a sole signal.
• VQ-05: Layout & Canvas (3/4) — correct 3200×1800 canvas, no clipping; mid-chart crossings create a busy convergence zone.
• VQ-06: Axis Labels & Title (2/2) — descriptive, with units.
• VQ-07: Palette Compliance (2/2) — first series #009E73; red is the valid semantic-anchor exception for decline; both theme backgrounds correct.

Design Excellence (12/20)

• DE-01: Aesthetic Sophistication (5/8) - Deliberate semantic-direction palette and documented legend-omission rationale, above generic defaults
• DE-02: Visual Refinement (3/6) - Y-axis-only grid, generous margins, but no marker edge/stroke treatment
• DE-03: Data Storytelling (4/6) - Color-by-direction + direct labels give an immediate read, diluted somewhat by busy mid-chart crossings

Spec Compliance (14/15)

• SC-01: Plot Type (5/5)
• SC-02: Required Features (3/4) — time points labeled via shared x-ticks rather than a per-column header as classic slopegraphs use
• SC-03: Data Mapping (3/3)
• SC-04: Title & Legend (3/3)

Data Quality (13/15)

• DQ-01: Feature Coverage (5/6)
• DQ-02: Realistic Context (5/5)
• DQ-03: Appropriate Scale (3/4) — 40-114 "units" reads small for company-wide product-category totals

Code Quality (10/10)

• CQ-01: KISS Structure (3/3)
• CQ-02: Reproducibility (2/2)
• CQ-03: Clean Imports (2/2)
• CQ-04: Code Elegance (2/2)
• CQ-05: Output & API (1/1)

Library Mastery (7/10)

• LM-01: Idiomatic Usage (4/5)
• LM-02: Distinctive Features (3/5) - Creative print_labels + interpolate=None workaround for a chart type pygal has no native support for

Score Caps Applied

• None

Strengths

• Clever repurposing of pygal's Line chart (no interpolation, only two x-ticks) into a genuine slopegraph, with print_labels carrying entity names at both endpoints so the legend can be safely omitted
• Correct, well-reasoned semantic color exception: brand green for increases and matte red (#AE3030, Imprint position 5) for decreases, redundantly encoded by slope direction as well as color
• Clean, fully deterministic code: no randomness needed, only os/sys/pygal imports (all used), comments explain the legend-omission and color-direction rationale
• 10 entities (within the spec's 5-15 sweet spot), plausible Q1-vs-Q4 product-category sales data, values deliberately spaced so same-column labels don't collide
• Canvas is exactly 3200×1800 and theme chrome is correctly threaded through the Style object for both light and dark renders

Weaknesses

• Point/category labels render at value_label_font_size=36 — smaller than the tick labels (44) and axis title — bump to ~44-48 so entity names read as prominently as the numeric ticks
• On the Q1 (left) column, each entity's label starts right at the vertical Q1 gridline, so the guide line runs through the first characters of every label — nudge left-column labels a few px right, or don't extend the guide through the label text
• Sales scale of 40-114 "units" reads as unrealistically small for whole product-category totals — scale the data up (thousands of units) or relabel the axis to reflect a smaller reporting unit
• The two time points are only labeled via the shared x-axis ticks rather than as a header directly above each column the way classic slopegraphs do — consider whether this reads clearly enough at a glance
• Visual refinement is fairly standard (single y-axis grid, no marker edge/stroke treatment) — a subtle ink/white outline on the dots would add definition in the busy mid-chart crossing zone

Issues Found

1. VQ-01 / SC-02: Point labels undersized relative to ticks, and time-point identification relies solely on x-axis ticks
   • Fix: raise value_label_font_size toward ~44-48; optionally reinforce which column is which time point
2. VQ-02: Q1-column labels overlap the vertical guideline
   • Fix: small left-margin/label-offset adjustment so the guide doesn't run through label text
3. DQ-03: Sales scale (40-114 units) is low for company-wide category totals
   • Fix: scale up the data or adjust unit framing

AI Feedback for Next Attempt

Solid slopegraph adaptation — keep the direction-based color coding and direct endpoint labels. For the next pass: increase the point-label font size closer to the tick-label size, nudge the Q1-side labels off the vertical gridline, and reconsider the sales scale so "units" reads as a plausible company-wide total. These are refinements, not structural problems.

Verdict: REJECTED

[github-actions]

🔧 Repair Attempt 1/4

Applied fixes based on AI review feedback.

Status: Repair completed, re-triggering review...

---

🤖 impl-repair

[claude]

AI Review - Attempt 2/3

Image Description

Light render (plot-light.png): Warm off-white background matching #FAF8F1. Title "slope-basic · python · pygal · anyplot.ai" centered in dark ink, clearly visible and not clipped. Y-axis title "Sales (thousands of units)" rotated on the left; x-axis title "Time Period" below the "Q1 2024" / "Q4 2024" tick labels. Numeric y-tick labels (30-120) and category endpoint labels all render in dark ink at matching font sizes (44). Subtle dotted y-only grid. 10 lines connect a Q1 dot to a Q4 dot per product category — rising entities (Furniture, Beauty, Home Decor, Electronics, Sporting Goods, Automotive) in Imprint brand green #009E73, falling entities (Apparel, Food & Bev, Office Supplies, Toys) in matte red #AE3030. Each dot carries its category name directly beside it at both endpoints; legend correctly omitted. Q1-side labels now clear the vertical axis guideline (previously overlapping), and no text is clipped at the canvas edge. All text is clearly readable against the light background.

Dark render (plot-dark.png): Warm near-black background matching #1A1A17. Title, axis titles, and numeric tick labels all render in light ink, clearly legible. Data colors are identical hexes to the light render (#009E73 / #AE3030) — only chrome flipped, as required. Category point-labels render in a muted light tone but remain clearly distinguishable from the near-black background — no dark-on-dark failure observed.

Both renders pass the theme-readability check; no legibility failures in either theme.

Score: 85/100

Category	Score	Max
Visual Quality	28	30
Design Excellence	12	20
Spec Compliance	14	15
Data Quality	14	15
Code Quality	10	10
Library Mastery	7	10
Total	85	100

Visual Quality (28/30)

• VQ-01: Text Legibility (7/8) — value_label_font_size raised to 44, now matching the tick-label size; entity names read as prominently as the numeric ticks, in both themes
• VQ-02: No Overlap (6/6) — Q1-column labels no longer collide with the vertical guideline (fixed via the value_font_size offset bump)
• VQ-03: Element Visibility (6/6) — dot/stroke sizes appropriately prominent for this sparse 10-line dataset
• VQ-04: Color Accessibility (2/2) — direction color is redundantly backed by slope geometry, not a sole signal
• VQ-05: Layout & Canvas (3/4) — correct 3200×1800 canvas, no clipping; mid-chart crossing zone remains visually busy
• VQ-06: Axis Labels & Title (2/2) — descriptive, with units
• VQ-07: Palette Compliance (2/2) — first series #009E73; red is the valid semantic-anchor exception for decline; both theme backgrounds correct

Design Excellence (12/20)

• DE-01: Aesthetic Sophistication (5/8) - Deliberate semantic-direction palette and documented rationale, above generic defaults
• DE-02: Visual Refinement (3/6) - Y-axis-only grid, generous margins, but still no marker edge/stroke treatment
• DE-03: Data Storytelling (4/6) - Color-by-direction + direct labels give an immediate read, diluted somewhat by busy mid-chart crossings

Spec Compliance (14/15)

• SC-01: Plot Type (5/5)
• SC-02: Required Features (3/4) — time points still labeled via shared x-ticks rather than a per-column header
• SC-03: Data Mapping (3/3)
• SC-04: Title & Legend (3/3)

Data Quality (14/15)

• DQ-01: Feature Coverage (5/6)
• DQ-02: Realistic Context (5/5)
• DQ-03: Appropriate Scale (4/4) — re-labeling the axis "thousands of units" fixes the previously-flagged implausibly small scale

Code Quality (10/10)

• CQ-01: KISS Structure (3/3)
• CQ-02: Reproducibility (2/2)
• CQ-03: Clean Imports (2/2)
• CQ-04: Code Elegance (2/2)
• CQ-05: Output & API (1/1)

Library Mastery (7/10)

• LM-01: Idiomatic Usage (4/5)
• LM-02: Distinctive Features (3/5) - Creative print_labels + interpolate=None workaround for a chart type pygal has no native support for

Score Caps Applied

• None

Strengths

• Point/category labels now render at value_label_font_size=44, matching the tick-label size — entity names read with the same prominence as the numeric axis (fixed from attempt 1's VQ-01 weakness)
• Q1-column labels no longer collide with the vertical y-axis guideline — the value_font_size bump to 40 widened the dot-to-label offset enough to clear the axis line
• Y-axis re-labeled "Sales (thousands of units)" — the same 40-114 data range now reads as a plausible 40,000-114,000 unit quarterly total instead of an implausibly tiny company-wide figure (fixed DQ-03)
• Clever repurposing of pygal's Line chart (no interpolation, exactly two x-ticks) into a genuine slopegraph, with print_labels carrying entity names at both endpoints so the legend can be safely omitted
• Correct, well-reasoned semantic color exception: brand green for increases and matte red (Imprint position 5) for decreases, redundantly encoded by slope direction as well as color
• Clean, fully deterministic code; comments explain the legend-omission, color-direction, and value_font_size-offset rationale

Weaknesses

• The two time points are still only labeled via the shared x-axis ticks rather than as a header directly above each column the way classic slopegraphs do
• Visual refinement is still fairly standard: single y-axis grid, no marker edge/stroke treatment — a subtle ink/white outline on the dots would add definition in the busy mid-chart crossing zone
• Mid-chart crossing zone (where increasing and decreasing lines intersect) remains visually busy
• Design excellence is still close to a well-configured default — typography/whitespace treatment hasn't moved beyond the library-default look

Issues Found

1. DE-01/DE-02 LOW: Visual refinement and aesthetic polish are above-default but not yet publication-level
   • Fix: add a subtle ink/white stroke outline on the dots for definition in the crossing zone; consider refining typography weight/hierarchy further
2. SC-02: Time points identified only via shared x-axis ticks, not per-column headers
   • Fix: optional — consider a header label directly above each column if it improves at-a-glance readability

AI Feedback for Next Attempt

This attempt resolved the prior review's concrete issues (label sizing, Q1-label/guideline overlap, and the implausible sales scale). What remains is polish: the plot is correct and readable but still reads as a well-configured default rather than a publication-quality design. If further iteration happens, focus on Design Excellence — a subtle marker outline, tighter typography hierarchy, and/or easing the busy mid-chart crossing zone.

Verdict: APPROVED