---

About

I build offline-first AI tools, Rust desktop utilities, educational simulators, and automation systems.

My current direction is practical engineering: tools that run locally, explain complex systems clearly, automate repetitive work, and turn experimental ideas into usable software.

Local AI · Rust · Python · TypeScript · React · Vite · Windows Tools · Developer Automation

---

Navigation

Section	Description
Featured Projects	Main public repositories worth opening first
Tech Stack	Languages, frameworks, tools, and workflow
Interactive Map	Visual overview of my engineering direction
Project Notes	Extended project descriptions
Roadmap	Current development direction
Contact	Contact and collaboration notes

---

Featured Projects

🏗️ Arch Trainer Interactive browser-based sandbox for learning the Arch Linux installation process. Core idea: terminal simulator + installation flow map + browser VM experiments. Stack: React, Vite, TypeScript, v86, xterm, SQLite, Vitest, Playwright.	🎮 MCZ Launcher Portable Windows-style launcher for Minecraft NeoForge modpacks. Core idea: automatic downloads, JSON modpack configuration, Rust desktop app architecture. Stack: Rust, Iced, Tokio, Windows portable app design.
📚 GitInstructionSite Interactive multilingual learning site for Git and GitHub fundamentals. Core idea: explain Git/GitHub through simple terms, GUI/CLI workflows, and beginner-friendly lessons.	🪟 Win2RayUI Windows V2Ray client concept with automatic configuration and server parsing. Core idea: practical Windows networking utility with clean UI direction.

---

Tech Stack

Open full stack matrix

Area	Tools
Languages	Python, Rust, TypeScript, JavaScript
Frontend	React, Vite, HTML, CSS
Desktop	Rust GUI, Tauri direction, Windows-first portable tools
AI / Automation	Ollama, local LLM workflows, RAG concepts, ChromaDB direction
Testing	Vitest, Playwright, scripted validation
Data	SQLite, JSON configs, local-first storage
DevOps	GitHub Actions, portable builds, release packaging
Systems	Windows tooling, Linux learning environments, CLI workflows

---

Interactive Map

Engineering direction map

flowchart TD
    A["radik097"] --> B["Local AI Systems"]
    A --> C["Rust Desktop Tools"]
    A --> D["Educational Simulators"]
    A --> E["Developer Automation"]

    B --> B1["Offline assistants"]
    B --> B2["RAG / memory"]
    B --> B3["Tool orchestration"]

    C --> C1["Windows utilities"]
    C --> C2["Portable apps"]
    C --> C3["Async download managers"]

    D --> D1["Arch Trainer"]
    D --> D2["GitInstructionSite"]
    D --> D3["Interactive learning flows"]

    E --> E1["Project supervisors"]
    E --> E2["Testing without screenshots"]
    E --> E3["Long-running coding workflows"]

Loading

How I think about projects

Idea
  ↓
Architecture
  ↓
Working prototype
  ↓
Validation scripts
  ↓
README + screenshots + release
  ↓
Clean public portfolio project

---

Current Build Direction

• Making experimental projects easier to understand from the outside.
• Turning rough tools into clean, documented repositories.
• Building local-first AI and automation systems.
• Improving Windows portable app packaging.
• Designing UI workflows that are practical, not just decorative.

---

GitHub Activity

---

Repository Quality Rules

What I want every public repository to contain

• Clear one-line description.
• Screenshot or demo link when UI exists.
• Installation instructions that actually match the repository.
• Tech stack section.
• Known limitations.
• Roadmap.
• No placeholder links.
• No unfinished AI Studio / template text.
• Clean public-facing README.

---

Contact

For collaboration, project discussion, or technical feedback, use GitHub issues/discussions on the relevant repository.

Building local tools, educational systems, and AI-assisted automation.