STXIC LABS

Independent Software Laboratory

Inside the mind of STXIC.

Software, experiments, and everything in between.

View Works
RoninClipsShipped
WorthiShipped
STXIC RealmIn Development
The Shoe BoyShipped
PolySkillShipped
STXIC HaloIn Development

A few things from inside my head. Open a folder.

How STXIC Thinks.

Every project begins with a problem worth solving.

We approach development with a clear objective: understand the problem, determine what matters, and build a solution that serves its purpose. Every decision, from architecture to interface, must have a reason.

We do not build for complexity. We build for function, clarity, and longevity.

INSIDE THE
STXIC MIND

An exploration of how an idea becomes a working system.

STXIC LABS
GENERATIVE STUDY / 001
UNSORTED INPUT / OPEN FIELD

01 OBSERVE

Understand before acting.

We begin by studying the problem, its context, and the people it affects. We question assumptions, identify limitations, and determine what actually needs to be solved.

A solution is only as good as our understanding of the problem.

RELATIONSHIP MAPPING / EMERGENT CLUSTERS

02 DECONSTRUCT

Remove what is unnecessary.

Complex problems become manageable when broken into smaller parts. We separate requirements from assumptions, identify dependencies, and establish priorities.

The objective is not to make everything simple. It is to make everything understandable.

SPATIAL CONSTRAINTS / ORDERED TOPOLOGY

03 ARCHITECT

Structure before execution.

We define how the system should operate before committing to implementation. This includes its architecture, interactions, data flow, and the relationship between its components.

Good structure reduces unnecessary work and allows the system to grow without losing direction.

SIGNAL PROPAGATION / ACTIVE CONNECTIONS

04 ENGINEER

Build with intention.

Ideas are translated into working software. We focus on reliable functionality, deliberate interfaces, and maintainable code.

Every component must contribute to the system. Nothing exists merely to fill space.

CONTINUOUS FEEDBACK / ADAPTIVE TOPOLOGY

05 REFINE

Test. Evaluate. Improve.

A working product is not necessarily a finished product. We examine its behavior, identify weaknesses, and improve what can be improved.

We retain what works, correct what fails, and remove what no longer serves a purpose.

Skip to projects
  1. 01 OBSERVE

    Understand before acting.

    We begin by studying the problem, its context, and the people it affects. We question assumptions, identify limitations, and determine what actually needs to be solved.

    A solution is only as good as our understanding of the problem.

  2. 02 DECONSTRUCT

    Remove what is unnecessary.

    Complex problems become manageable when broken into smaller parts. We separate requirements from assumptions, identify dependencies, and establish priorities.

    The objective is not to make everything simple. It is to make everything understandable.

  3. 03 ARCHITECT

    Structure before execution.

    We define how the system should operate before committing to implementation. This includes its architecture, interactions, data flow, and the relationship between its components.

    Good structure reduces unnecessary work and allows the system to grow without losing direction.

  4. 04 ENGINEER

    Build with intention.

    Ideas are translated into working software. We focus on reliable functionality, deliberate interfaces, and maintainable code.

    Every component must contribute to the system. Nothing exists merely to fill space.

  5. 05 REFINE

    Test. Evaluate. Improve.

    A working product is not necessarily a finished product. We examine its behavior, identify weaknesses, and improve what can be improved.

    We retain what works, correct what fails, and remove what no longer serves a purpose.

Explore the projects

STXIC / PRINCIPLE 001

Less assumption.
More understanding.
Less complexity.
More purpose.

We do not measure our work by how much we build, but by how well it solves the problem.

The archive.

12 projects, collected in four folders.

Pick a folder. Follow your curiosity.

AI & Automation4 items
AI & Automation4 artifacts

Local AI pipelines, agent tooling, and work that should not need a person.

Software & Applications4 items
Software & Applications4 artifacts

Mobile apps, desktop software, and full-stack products people actually use.

Systems & Tools2 items
Systems & Tools2 artifacts

Personal operating tools, developer utilities, and local-first infrastructure.

Experiments2 items
Experiments2 artifacts

Interface experiments, generative explorations, and tactile web spaces.

CHRONOLOGY

Experiment & Release Log

Authentic record of milestones, builds, and releases.

2026.10BuildSTXIC Realm: account, friends, direct messages, and shared homes slice implemented.
2026.10BuildSTXIC Realm v1.0 planning specification written.
2026ReleaseThe Shoe Boy deployed for the College of Computing Education, with 96 feature tests.
2026BuildStarted RoninClips, the offline clipping and captioning engine.
2026MilestoneBegan mentoring as a QA Mentor at the UM Skills Clinic.
2025ReleaseCyberNex POS v1.0 released.
2025ReleasePawfectMatch delivered as freelance work.
2024MilestoneStarted a BS in Information Technology at the University of Mindanao.

ABOUT THE MAKER

Christian Lascuña

STXIC Labs is where I keep the software, experiments, and ideas that don't always fit neatly into a traditional portfolio.

I build local-first AI pipelines, full-stack systems with Laravel and Python, and desktop tools using Tauri and Rust. I study Information Technology at the University of Mindanao and mentor at the UM Skills Clinic.

Every project recorded here represents real working code, verified architectures, and genuine engineering trade-offs.

COMMUNICATION

Let’s work together.

Bring your next product to life, automate the repetitive work, or build a better way to manage customers. I develop web, mobile, and desktop apps, integrate AI, build CRM systems, and test software for quality and reliability.

Have a product to build, a workflow to automate, or software to test? Tell me what you need, where things stand, and what you’d like to achieve.