A Neurodivergent Coder's Journey with AI

Welcome! This project documents the creation of a modern, professional development environment, built from the ground up in a collaborative process with Gemini Code Assist.

As a developer with dyslexia, dyscalculia, ADHD, and Autism, I found that traditional learning paths often presented barriers. This repository is the story of overcoming those challenges by using AI as a patient, knowledgeable, and non-judgmental mentor.

It demonstrates a new, more accessible way to learn, debug, and build complex technical setups. You can explore the full story on the mdfile project's GitHub repository.

The Core Concept: "Hardware Compatibility"

Standard AI tools are often designed for Linear Thinkers, processing information as a stream of text. However, for a Visual-Spatial / AuDHD brain, this creates a "Translation Layer" of cognitive friction.

This project does not ask for "accommodation." It engineers "compatibility."

We configure the AI to output data in a format that bypasses linear processing:

The Tech Stack

1. The Kernel: Google Antigravity (GEMINI.md)

The "BIOS" level configuration. It enforces Object Permanence and Visual First protocols. The "No-Tab" protocol keeps mental RAM clear by banning the opening of unrequested tabs.

2. The Editor: Cursor (.cursorrules)

Acts as a "Visual Simulator." It forces the AI to use ASCII charts and Mermaid.js flowcharts to explain bugs rather than linear text, serving as a visual anchor.

3. LifeOS: Custom Gems

Beyond code, these configurations help manage the "Lost Generation" hardware, stripping away "empathy fluff" to deliver raw, high-density data.

The Workflow: Artifact-Driven Development

We rely on Artifacts (persistent maps) to verify logic before writing code. The workflow has evolved from "Trial and Error" to "Map and Build."

Workflow Logic Map
Text Version
  1. User describes problem.
  2. AI generates topology artifact.
  3. User reviews map.
  4. If flawed, User corrects map (Loop).
  5. If sound, AI writes code.
  6. User verifies object stability.
                                         |
                                         |
                                         |
                                         |
   _______                   ________    |
  |ooooooo|      ____       | __  __ |   |
  |[]+++[]|     [____]      |/  \/  \|   |
  |+ ___ +|     ]()()[      |\__/\__/|   |
  |:|   |:|   ___\__/___    |[][][][]|   |
  |:|___|:|  |__|    |__|   |++++++++|   |
  |[]===[]|   |_|_/\_|_|    | ______ |   |
_ ||||||||| _ | | __ | | __ ||______|| __|
  |_______|   |_|[::]|_|    |________|   \
              \_|_||_|_/               jro\
                |_||_|                     \
               _|_||_|_                     \
      ____    |___||___|                     \
     /  __\          ____                     \
     \( oo          (___ \                     \
     _\_o/           oo~)/
    / \|/ \         _\-_/_
   / / __\ \___    / \|/  \
   \ \|   |__/_)  / / .- \ \
    \/_)  |       \ \ .  /_/
     ||___|        \/___(_/
     | | |          | |  |
     | | |          | |  |
     |_|_|          |_|__|
     [__)_)        (_(___]

asciiart

"The Three Laws of Robotics:"
  1. A robot may not injure a human being or, through inaction, allow a human being to come to harm.
  2. A robot must obey orders given it by human beings, except where such orders would conflict with the First Law.
  3. A robot must protect its own existence as long as such protection does not conflict with the First or Second Laws.
— I, Robot (Isaac Asimov)