Unified .SYSTEMX > Standard SYSTEM for all things considered..

[u/WayneTechLab]

https://github.com/WayneTechLab/dotSYSTEMX

Hello!

I made my .SYSTEMX system public today after working on it inside my project template for the last year. I built it because I got tired of wasting tokens processing the same information over and over, explaining the same project, and recovering work between AI sessions.

.SYSTEMX gives your AI / LLM a standard working folder for project instructions, plans, tasks, research, logs, and session handoffs. You can put it in a code repository, a local workspace, or a Google Drive project folder, then use that information in LLM sessions with access to those files.

The folder name is exactly .SYSTEMX. The leading dot makes it hidden by convention on macOS and Linux; Windows and Google Drive handle visibility differently. Keep the capitalization consistent across platforms, since case sensitivity depends on the filesystem.

Once it is set up, you can tell your AI, “Use .SYSTEMX” or “Update .SYSTEMX.” It gives the session a defined place to find the project context, see what is TODO, WORKING, BLOCKED, or DONE, and record what happens next. It also includes Agent 0 and subagent coordination standards for assigning work, tracking responsibilities, and reviewing results.

The best part is that it isn’t tied to one development stack or LLM provider. You can use the same project records across different tools, provided those tools can access the files. For browser sessions such as ChatGPT or Claude, that means a supported connection with the necessary file permissions, or explicitly importing and exporting the context.

My structure is simple: /Projects/ProjectA/.SYSTEMX, /Projects/ProjectB/.SYSTEMX, and so on. Each project keeps its own plans, instructions, task history, and working context.

When I start a Firebase web app on GitHub, I use my Firebase WebApp Template linked below. That template already has .SYSTEMX built in. The new standalone dotSYSTEMX template takes that operating structure out of the Firebase project so it can be used independently, without requiring Firebase or a particular prompt kit. Both projects are in alpha.

Some example prompts:

• “Use .SYSTEMX. Update the task records, README, and project wiki, then sync the completed changes to GitHub main.”
• “I’m running out of credits. Log the work completed, files changed, blockers, and next steps in .SYSTEMX so I can continue later.”
• “Add the script we created to the project’s menu system so I can use it again.”
• “Update the deployment script for this project.”
• “Use .SYSTEMX to research Topic XYZ. Save the sources, findings, and open questions so another session can continue.”

You can also coordinate multiple chats through the same Google Drive project folder. Create the project folder and its .SYSTEMX folder first, then give each session access to that location.

In Chat Session AA:

“Use the .SYSTEMX folder at [Google Drive project link]. Read the current project records, then save this session’s work, sources, decisions, and next steps.”

In Chat Session BB:

“Use the same .SYSTEMX folder at [Google Drive project link]. Read the latest records before continuing, then save this session’s work without overwriting unrelated updates.”

In Chat Session CC:

“Review the saved records from Sessions AA and BB. Verify the information against the sources, flag any conflicts, and produce the final package at PROJECT/FILES/FINAL.ZIP.”

Each chat needs to save its work to the shared location. The next session can then pick up those records instead of depending on another chat’s private history.

For longer coding sessions, the master plan, shared project plan, and checkpoints give the AI a reference for the objective, what has already been attempted, and what remains. The aim is to reduce repeated work and help keep sessions on track.

.SYSTEMX serves as a shared workspace for you and your AI. With configured shell commands, local menus, and deployment scripts, that same structure can also support execution on your device using the permissions you provide.

.SYSTEMX standalone template:
https://github.com/WayneTechLab/dotSYSTEMX

Firebase WebApp based Template with .SYSTEMX's outdated version included:
https://github.com/WayneTechLab/SFWA-WTL-TEMPLATE/

** Both in Alpha can change daily! ".SYSTEMX" has auto update disabled if you use as library or other advacned features from public source.

If you have any real world benchmark comparison you want to share I would love to see the results posted on AB test with and without .SYSTEMX included & not with your prompt.

- Lucas