A full-featured Discord application that runs Naruto 5e play inside the server where it happens: character data, dice and combat, initiative, missions, resources, and rules reference in one bot.

Context

A campaign run over Discord keeps its state in several places at once: character spreadsheets, chat history, and whoever is tracking the fight. Rolls, turn order, and rules questions all depend on finding the right number somewhere else.

Engineering decisions

Import instead of re-entry

Characters are imported from Google Sheets (stats, saves, skills, attack bonuses, chakra, and HP) and stored in MySQL, so players can switch characters and carry data across sessions.

Guard shared state

Resource commands for Ryo and downtime validate every change, so a balance can never drop below zero.

A dice engine, not a random number

Supports exploding dice, conditional rerolls, minimum values, arithmetic expressions such as (2d6+1d4)*2, advantage and disadvantage, and repeated rolls with summaries.

Tolerate imperfect input

Slightly mistyped stat or skill names resolve to the closest match. Jutsu and feat searches accept partial names and ask the user to choose when a result is ambiguous.

Keep the session in one place

Attack rolls use bonuses from the imported sheet, and initiative tracking and mission tools keep the flow of play inside Discord.

A multi-step React loan application built on schema-backed validation and document workflows, with complete applicant journeys tested for accessibility and across browsers.

ConfidentialDescribed at a high level only; code, screens, and implementation details are intentionally not shown.

Context

Multi-step applications fail in the gaps: between steps, between browsers, and for people who don’t use a mouse. Correctness has to be checked across the whole journey, not one field at a time.

Engineering decisions

Validation as a schema

Form rules are declared as schemas with Zod and enforced through React Hook Form.

Documents inside the journey

Document workflows are part of the applicant journey and are tested with it.

Test complete journeys

Cypress and Playwright exercise complete applicant journeys end to end, across browsers.

Accessibility as coverage

Accessibility is part of the test coverage, alongside functional behavior.