Focused software for repeatable problems
StoreProof is live storefront QA software. CatalogCue is a Shopify product-to-content workflow currently in private development.
About RXR Code
A founder-led studio for the work behind commerce.
RXR Code is an independent software studio founded and operated by commerce engineer Gilriel Rodriguez.
The studio builds its own products, publishes open-source tooling, and takes on selective client engineering around commerce workflows.
Why RXR Code exists
The recurring problems were larger than the storefront.
Working directly with commerce systems exposed the same friction repeatedly: product work moving through manual handoffs, integrations becoming difficult to trust, storefront issues being discovered late, and internal workflows outgrowing the tools around them.
RXR Code was created as a place to build focused software around those recurring problems. Sometimes that becomes a product. Sometimes it becomes an open-source foundation. Sometimes the right answer is a client system shaped around one operation.
Shopify is where the studio's current public work goes deepest, but the organizing idea is broader: solve concrete commerce problems without building more software than the workflow needs.
What the studio builds
Three kinds of work, clearly separated.
Product status and ownership are stated as they are. Employer work is not presented as RXR Code client work, and unfinished products are not presented as established businesses.
Useful foundations kept public
Shopify Fixtures is public, MIT-licensed developer tooling for reproducible Shopify development-store data.
Purpose-built systems for specific workflows
Selective storefront, application, integration, and automation work when an off-the-shelf tool does not fit the operation.
Founder experience
Production experience informs the work without becoming borrowed proof.
Gilriel's professional experience includes commerce platform migrations, ERP-connected workflows, storefront delivery, and operational tooling. That experience shapes how RXR Code approaches systems, failure states, and long-term operation.
It is attributed to the founder and is not represented as RXR Code client work. Detailed public career case studies remain on the founder's separate portfolio.
Engineering character
Four qualities the finished work should preserve.
These are practical tests for the software and the way it is built—not claims about scale, process, or a team that does not exist.
Observable
Important states, problems, and changes should be visible instead of hidden.
Structured
Ad-hoc work becomes an explicit workflow with clear inputs, review, and outputs.
Deliberate
Plan first, define boundaries, then make changes intentionally.
Operable
Software should remain understandable, supportable, and maintainable after launch.