Skip to content

Releases: comaraDOTcom/strokes-gained

0.0.39 — Delete a round

Choose a tag to compare

@github-actions github-actions released this 26 Sep 18:41

Delete a round

  • "Delete this round" at the bottom of your round's page. You confirm first, and it tells you
    how many shots go with it. Only you can delete your rounds; the organiser can't.
  • Empty rounds now show on Rounds. A round you started but never logged a shot on still counted
    towards "3 rounds logged at Elm Park" but never appeared in the list, so there was no way to open
    it. It now shows as a card marked "no shots yet": tap it to carry on, or delete it.

0.0.38 — Backdrop choice moves off Rounds, into Settings on your profile

Choose a tag to compare

@github-actions github-actions released this 26 Sep 18:07
5b9a60c

Backdrop choice moves off Rounds, into Settings on your profile

  • Rounds is back to just your rounds. The scene banner and the Backdrop picker are gone from the
    top of the page. The course scene at the bottom of every page stays.
  • Settings, at the bottom of your profile (the Played page): your name and email, and the
    Backdrop setting, with a preview of the current scene, then Auto or one of the four seasons.
    It's still saved on this device.
  • Your name (or initial, on a phone) in the top bar now opens those settings.

0.0.37 — Skills for Claude sessions, a quality register, and tests on shot editing

Choose a tag to compare

@github-actions github-actions released this 26 Sep 08:45
7157b25

Under the hood: how Claude works on this app, and what it's now allowed to trust

Nothing changes on screen. This release makes the numbers behind the screen better guarded and
the way the app is built more reliable.

  • New tests on shot editing. Marking an edited shot Holed removes the shots after it; editing an
    earlier shot re-derives the later starts and stores the right strokes gained for every shot; a
    stroke-and-distance penalty always costs exactly two strokes whatever was typed. These were the
    behaviours the app relied on but never checked.
  • A quality gate on the course directory. A test now checks the committed course list itself:
    every course has one of the 32 counties and sits on the island, the share with a known hole count
    can't fall, and the known gaps (missing clubs, duplicate entries) are listed and must shrink. It
    found a fourth non-course on its first run.
  • A quality register (docs/quality.md): every feature's data confidence, its known issues,
    the test that pins it and the GitHub issue, so a problem a player could notice is never only in a
    chat. Filed from it: a scoring bug where a shot entered as 0 ft and not holed is scored as holed
    (#40), the directory's missing clubs and hole counts (#38), and the thin scratch benchmark (#39).
  • Skills for Claude Code sessions (.claude/skills/): /how explains an area with parallel
    read-only explorers and can critique it with independent reviewers; /verify runs the same
    checks as CI in one command and has a separate verifier check a subagent's claims; /brigade
    runs many subagents at once with one writer per file and a verifier on every change;
    /correct turns a correction into a permanent fix at the lowest level that can hold it. A
    CLAUDE.md points every session at them.
  • Where code lives is now a test too: logic in src/lib with a test beside it, pages and
    routes thin, data under src/lib/*/data, and counts of the exceptions that may only go down.

0.0.36 — Course map background fix, course list corrections

Choose a tag to compare

@github-actions github-actions released this 26 Sep 08:03
43f81f0

Fix: the course map's background

  • The Played page's map showed "API KEY REQUIRED" tiles: CARTO's basemaps now need a key. It now
    uses OpenStreetMap's standard map, which needs none. A different provider can be set with
    NEXT_PUBLIC_MAP_TILE_URL (see .env.example) without a code change.

Course list corrections

  • Derry, not Londonderry.
  • A club named after a county is placed in that county even when the course sits just over the
    boundary: Waterford Golf Club is in Waterford (not Kilkenny), Carlow Golf Club in Carlow.
  • Courses mapped with only their own name get their venue in front, e.g. "Carton House – The
    O'Meara" rather than "The O'Meara".
  • Footgolf, practice academies and courses with fewer than 9 holes are no longer listed.

0.0.34 — Sign-up flow: welcome tour, first-round coaching, home-screen app

Choose a tag to compare

@github-actions github-actions released this 25 Sep 20:00
1db9570

Sign-up flow: a welcome tour, and the app on your home screen

For a new player, the path is now: WhatsApp link → an invitation (not a login wall) → sign in →
a two-minute welcome tour → their first round, with help at each step.

  • The invite page says what you're joining: three lines on what the app does, then Google or
    an emailed link. No password, and it says a short tour follows.
  • Welcome tour (/welcome), five swipeable screens after signing in, all skippable:
    1. Why: "Your scorecard says 84. It doesn't say why." Counts vs strokes gained, with an
      example split by area.
    2. How it's scored: the one sum, and the Learn hub's bogey scored by the real engine
      (drive +0.06, approach −0.55, … = −0.91).
    3. Logging a round: where it finished, how far to the hole (not how far you hit it), Holed;
      Brief first; nothing is final.
    4. What you get back: a recap after one round, Insights after a few, Trends and What to work on
      after four; honest about small samples.
    5. Set up your phone: "Add to Home Screen" instructions for the phone in hand (iPhone Safari,
      another iOS browser, Android, or a laptop), and a nudge to check the course library. Ends on
      Log your first round.
      It only appears unasked to a player with no rounds; Skip or finishing remembers that in the
      browser, and Learn has a Welcome tour link to reopen it any time.
  • Rounds, before the first round: a three-step "Getting started" card (course, first round,
    recap) instead of an empty list.
  • The first shot: on a player's first round, a dismissible card on the round page walks the
    three inputs until the first hole is finished.
  • Learn gains a Logging a round topic (the same three steps, plus penalties, moving between
    holes, editing and notes).
  • Home-screen app: a web app manifest, 192/512px icons (scripts/make-pwa-icons.sh), iOS
    full-screen mode with a safe-area-aware nav, and a theme colour, so "Add to Home Screen" gives
    an icon that opens straight to Rounds. Sign in before adding it: the emailed link opens in
    Safari, not the home-screen app.

0.0.33 — Seasonal backdrops, and voice golf-word repair

Choose a tag to compare

@github-actions github-actions released this 25 Sep 20:10
379a6f3

Seasonal backdrops on the Rounds page

  • Four scenes of the course: windy spring (azaleas, petals on the wind), sunny summer
    (sun out, hydrangeas, flag hanging still), windy autumn (turning trees, leaves blowing across)
    and rainy winter (grey sky, rain on the creek, puddles on the green, holly). Same course in each,
    so the green and flag never move.
  • A banner at the top of Rounds shows the current scene, with a Backdrop picker underneath.
  • Auto (the default) follows the season: spring Mar–May, summer Jun–Aug, autumn Sep–Nov,
    winter Dec–Feb. Pick a scene to keep it all year.
  • One choice, everywhere: the footer and the sign-in page switch to the same scene. It's saved
    on this device (a cookie), not your account.

Voice: golf words put back, and how to say a hole

  • Transcripts snap back onto golf words. Recognisers hear the commoner English word, so
    "eight iron" comes back as "eight hour", "two putts" as "two pots", "holed it" as "hold it"
    and "40 yards" as "40 hours". Each is fixed only when the words around it make the golf reading
    near-certain, the page shows every change ("hour → iron") next to what was actually heard, and
    numbers are never touched.
  • How to say it: a guide on the Voice page. Say where each shot was played from ("second
    shot, 157 yards from the fairway, left"), number every shot so a dropped one can be caught,
    always say the unit, say the lie, and call penalties out loud.

0.0.32 — Learn: what the numbers mean

Choose a tag to compare

@github-actions github-actions released this 25 Sep 19:08
6694cd2

Learn: what the numbers mean

  • A new Learn page (in the nav) that explains every score in the app, in plain words.
  • Strokes gained, one shot at a time: a scroll-through tour of one bogey on a 400-yard par 4.
    As you scroll, each shot is drawn on the hole in green if it gained on a scratch golfer and red
    if it lost, with the sum behind it (e.g. "3.03 − 2.58 − 1 = −0.55") and a running total. It ends
    on −0.91, which is exactly 4.09 expected minus 5 taken. It shows that the drive and bunker shot
    were fine, and the approach and missed six-footer cost the bogey. The numbers come from the app's
    own strokes-gained engine.
  • The hexagon, explained: tap any hexagon to see what that number means for that round, e.g. "81
    means your average shot lost 0.19 strokes to a scratch golfer's. Over these 85 shots that adds up
    to 16.4 strokes lost." Learn also has a table of what each score works out to over a round, and
    your latest round's score explained.
  • How to read a round card, What to work on, Where you miss, and a note on small samples.
  • A first-visit tip on Rounds with three pointers and a link to the tour. "Got it" hides it for
    good in that browser, leaving a small "How to read these numbers" link.

0.0.31 — Where you miss and putting profile

Choose a tag to compare

@github-actions github-actions released this 25 Sep 18:41

Where you miss, and your putting profile (Insights)

Two new sections built from the tags you log in Detailed entry. Neither changes strokes gained.

  • Where you miss: one sentence on your main tendency, e.g. "Approach shots that miss the green
    mostly finish short (39% of 104 tagged misses); putts you miss tend to finish short." Under it:
    • a cross for approach shots (over 30 yards) and another for short game and greenside bunkers:
      long above, short below, left and right either side, and how often you found the green in the
      middle. Your most common miss is highlighted;
    • approach misses by distance band, so you can see whether a 150-yard miss is different from a
      100-yard one;
    • off the tee: one bar of missed left, fairway and missed right.
  • Putting profile: for each putt length, how many you hole, whether your misses finish short or
    long
    (and which you lean to), and high side or low side on breaking putts. Then the same by
    break: left-to-right, right-to-left and straight.
  • Small samples say so. Anything with fewer than 8 tagged misses is faded and tells you how many it
    has. A course with no tags yet explains how to start.

0.0.30 — Brief or Detailed entry, misses and putt slope and break

Choose a tag to compare

@github-actions github-actions released this 25 Sep 18:41

Log where you missed, and how each putt broke

  • Brief or Detailed: starting a round now asks how much you want to log. Brief is lie and
    distance, with the extra tags one tap away. Detailed opens them on every shot. It remembers
    your last choice. (This replaces the "Track mentality" checkbox; old rounds keep their setting.)
  • Where it missed, tapped under the distance box once you've picked the result:
    • off the tee on a par 4 or 5: left or right of the fairway;
    • any other shot that missed the green: left, right, long or short of the hole;
    • a missed putt: short, long, left or right.
      Only the options that fit the shot appear, and nothing shows when you found the fairway or green.
  • Putts: slope (uphill, downhill, flat) and break (left-to-right, right-to-left,
    straight), above the lie buttons. Once you've picked the break, the miss row says which side is
    the high side.
  • Tap a selected tag again to clear it. Tags show on the shot list (e.g. "uphill · l→r · missed
    left"), survive edits, and are cleared if an edit means they no longer fit (a putt that's now a
    chip loses its slope and break).
  • None of this changes strokes gained. The charts that use it come next.

0.0.29 — Shot quality over time

Choose a tag to compare

@github-actions github-actions released this 25 Sep 18:41

Shot quality over time (Trends)

  • A new Shot quality over time section on Trends: a chart for all your shots, then one for
    each area (off the tee, approach, short game, bunker, putting, recovery).
  • The line is your last 5 rounds pooled together, so a round with one bunker shot doesn't swing
    it like a round with six. Dots are single rounds, and a dashed line marks 100 (scratch).
  • A hollow point has fewer than 10 shots behind it. An area without 10 shots in its last 5
    rounds shows a sentence instead of a chart, saying how many it has.
  • Covers the last year, or all your rounds until you have two in the last year.