RivalRy — Log Every Rivalry, Feel Every Match, Hear the Hype

Arjun Pratap Das — Mon, 13 Jul 2026 06:47:20 +0000

This is a submission for Weekend Challenge: Passion Edition

What I Built

RivalRy is a passion tracker for football rivalries. Fans can log every match against their biggest rivals — win, loss, or draw — rate how intense it felt, and write down the moment as it happened. Over time, it builds a Timeline of every battle and a "Passion Card": a shareable stat card showing total battles, win/loss/draw tally, an overall Passion Rating out of 10, and your single most intense moment — narrated aloud by an AI hype announcer.

Passion isn't just about the big clásicos — it's every derby, every gutting loss, every last-minute comeback that stays with you. RivalRy lets you bank that feeling instead of letting it fade, whether it's Real Madrid vs Barcelona, Argentina vs Brazil, or a World Cup 2026 group-stage upset.

Demo

Youtube demo link- https://youtu.be/6WiRpMUcmGk
Live app:- https://rivalryweb.lovable.app/

Code

https://github.com/arjunpratapdas/rivalry-pulse-logger

How I Built It

RivalRy is built with React, Vite, and Tailwind CSS, using browser localStorage to keep every rivalry entry persisted with zero backend setup — fast to build, fast to use.

The standout feature is the "Narrate My Rivalry" button on the Passion Card, powered by the ElevenLabs Text to Speech API. When clicked, the app generates a short hype-announcer-style summary of the rivalry's stats and most intense moment, sends it to ElevenLabs, and plays back a natural AI voice narrating it — turning a stat card into something that actually feels like a stadium announcer hyping up your rivalry.

One honest note: ElevenLabs free-tier credits are limited, and if they run out, the app gracefully falls back to the browser's built-in speech synthesis with a clear on-screen message, so the feature never breaks — it just degrades gracefully.

Prize Categories

Submitting for Best Use of ElevenLabs — the AI narration is central to the Passion Card experience, not a bolted-on extra.

How I built Security Guardian for Kiro

Arjun Pratap Das — Mon, 15 Sep 2025 18:55:59 +0000

How I Built a Security Guardian for Kiro

I was coding late one night when it hit me: I had no idea if my AI-generated code was secure. Like most developers, I was trading speed for security without even realizing it.

Then I saw this testimonial on kiro.dev: "In just four lines into a spec, Kiro was able to write user stories like a product manager..." That's when KiroSpecGuard was born.

The Simple Breakthrough

I created a security spec with just four natural language lines:

"Prevent basic XSS vulnerabilities in all user input handling"
"Ensure all user input is sanitized before rendering to HTML"
"Block direct DOM manipulation with untrusted data"
"Follow OWASP Top 10 security practices"

Kiro converted these into working security logic that scans my code as I type. No complex setup. No security expertise needed.

What Blew Me Away

The most impressive moment? When Kiro caught an XSS vulnerability in my code before I even saved the file. My on_file_save.kiro hook automatically flagged dangerous patterns like .innerHTML = with user input and suggested the secure alternative.

Instead of spending hours writing security rules, I got instant protection. Instead of dreading audits, I had documentation automatically generated.

Why It Matters

Security shouldn't be an afterthought. With KiroSpecGuard, it's built right into my workflow - like a seatbelt that puts itself on while I drive.

In just one weekend, I built something that would have taken me weeks. All because Kiro lets me describe what I need in plain English, then handles the heavy lifting.

DEV Community: Arjun Pratap Das