Stories are how I process the world. Software is one of the ways I give them structure.

I’m a software engineer and narrative designer building tools, systems, and experiments for people who live by stories. The work I care about lives where story and software stop pretending to be separate things.

My background spans full-stack across EdTech, FinTech, Fitness Tech, HealthTech, analytics, and real-time systems.

Lately, I have been interested in writer-facing design, interactive fiction and machinery beneath story: state, consequence, and the tools that help stories persist and respond.

I have also worked on a couple of games and helped out studios and cool startups from the Narrative side.

• wordbound: a portfolio, job board, and discovery platform for writers, narrative designers, and storytellers, built around real work samples (a scene, a character bible, a quest design doc) instead of the generic portfolio tools that flatten every writer into the same template. (closed beta)
• resumancer CLI: a reflective journal for engineers, developers, indie makers, and other creative-technical people. Records what you build day-to-day and turns it into resume entries, brag docs, and standup updates. (live)
• resumancer web: the web companion to the CLI, bringing the same journaling model to a browser-based interface. (closed alpha)
• tardigrade-db: an experiment in durable memory structures for LLM-driven systems leveraging their internal states/tensors rather than text. (open beta)
• poltergink: an LLM-native TypeScript wrapper around inkjs that makes Ink narratives two-sided. An LLM holds a persona and is forced to pick from the author-defined choices, no freeform generation. (pre-alpha)
• farist: a continuity system for creative work under unstable energy, built around one doctrine ("recognized before responsible") and two mechanisms most productivity apps don't have. A daily loop that asks what energy you've actually got and offers one move that fits it; and Hearthbeat, a Poisson-sampled experience-sampler with Bayesian drift detection that tells you whether your week actually matched your intent, without making you log everything. (private beta)

A lot of the work I care most about right now lives in products, prototypes, and half-wild experiments rather than neatly polished public repositories. I’m trying to change that without turning the whole thing into theatre.

• Stories: flagrare.com.br
• Storyteller-journey and Game Dev lessons: The Ignition Blueprint
• LinkedIn: linkedin.com/in/flagrare

Claude Code tools I maintain:

• agent-skills: skills that wrap your full dev cycle in Claude Code. Ticket-to-plan, ATDD, multi-perspective code review, Figma pixel-matching, doc-drift audits, PR writing, and patch-note changelogs. One install command.
• claude-statusline: replaces Claude Code's default status bar with rate limits, context window progress, git state, and thinking level. Multiple icon modes and toggle commands, no config required.
• llm-tutor: a Socratic tutor plugin. No answers until you've tried; hints in layers; asking for help costs a daily-resetting currency and figuring it out yourself earns long-term progress, so the cheap path is independent discovery. (alpha)

One-offs:

• swizard: native macOS app for installing Switch games via USB. Three transport modes; works on Apple Silicon + macOS Tahoe where MTP breaks.
• artemis-2-orbital-timelapse: cinematic timelapse from every Artemis 2 crew photograph, sequenced by EXIF capture time rather than file modification time.