About — principles, migration notes, and the live tech stack behind ThanhNguyxnOrg
How the practice works.
TNORG is not tied to one product category. These are the principles every project follows.
- BuildUseful beats impressive.Projects aim at real problems and ship as working software.
- ExploreIdeas start as experiments.Small prototypes test whether an idea deserves to become a tool.
- EvolveReleases compound.Good work keeps improving through issues and honest critique.
- Second lifeGood projects get a cleaner home.Older work is preserved, rebuilt, and given a second life.
Migration
Migration & Legacy Note
A meaningful part of ThanhNguyxn’s workspace is dedicated to restoring and continuing work from earlier stages of my GitHub journey.
Why migration matters here
Some projects deserve:
- a cleaner home
- better structure
- stronger documentation
- a second life
- a better future
Migration can mean
Depending on the repository, migration may be:
- a direct re-upload
- a cleaned-up rewrite
- a modernized rebuild
- a continuation of older work
- an archived snapshot for history
Why repo quality may vary
Because repositories come from different learning phases, the code style and structure may not always match perfectly. That is expected. This workspace reflects:
- where I started
- what I rebuilt
- what I’m becoming
Goal
The goal is not only to preserve old code. The goal is to preserve growth and build forward from it.
The stack, live.
The stack reflects what the organization actually ships. Language counts update automatically.
Core Languages
TypeScript and JavaScript carry most repositories. Python powers research and platform work. Go and Rust power systems tooling. PowerShell powers Windows-first utilities.
Frontend
React, Vue (Nuxt), and Svelte depending on the project. Tailwind CSS for styling.
Backend, Data & Infra
Node.js with Express, Django with Channels and Celery, PostgreSQL, Redis, MongoDB, Docker.
AI & Automation
Claude Code orchestration, MCP servers, agent skills, Gemini APIs, speech pipelines, GitHub Actions.
Tooling
Git, GitHub, VS Code, Windows, Linux — the daily drivers.
Mindset
Fewer trends, deeper understanding. The stack evolves with the work, and this page follows it.
Where the code lives.
Repositories, packages, people and resources. Every number below was verified.
Snapshot 2026-10-15. Numbers refresh daily from the GitHub and npm APIs.
- 01OrganizationThanhNguyxnOrg on GitHubHome of every TNORG repository, issue tracker and discussion. (opens in a new tab)
- 02Packagearchpulsev0.5.3 138/30dLiving architecture diagrams for modern codebases - auto-generate and maintain draw.io diagrams from your code
npm i archpulse(opens in a new tab) - 03Packageproduction-backend-kitv1.1.2 168/30dProduction-grade backend engineering patterns, checklists & AI adapters
npm i production-backend-kit(opens in a new tab) - 04ResourceControl roomOrg profile and community files: contributing, support and security notes. (opens in a new tab)
- 05BotThanhNguyxnAgentGitHub App running releases and repository automation. (opens in a new tab)
- 06PeopleRealThanhNguyxnOrganization member. (opens in a new tab)
- 07PeopleThanhNguyxn07Organization member. (opens in a new tab)
Use it. Fork it. Make it better.
Personal workspace, best effort. Active work gets priority review; archives may not update. Start with an issue.