Working example

GEMINI.md

@@ -10,29 +10,6 @@ This project utilizes a `components/` directory at its root, which contains a co
 
 **The files within the `components/` directory are intended as a library of examples and building blocks.** They should **never be directly modified or edited** by the Gemini CLI.
 
-### Development Sandbox
-
-- **All file modifications must be confined to the `./playground/src/` directory**. This is the designated area for all development and coding work. The Gemini CLI must not, under any circumstances, attempt to create, modify, or delete files outside of the `./playground/src/`.
-- Gemini does not need to setup the `./playground` directory structure. The user will have done that before running Gemini.
-- Only modifiy the `./playground/src/css/input.css` and `./playground/src/index.html`. All other files will be created and maintained by the user.
-- The `./playground/src/index.html` has a valid structure for the project layout. When the user asks Gemini to make changes to it, Gemini should consider the prompt to be made in the context of changing the index.html body unless explicitly called out in the user's input prompt.
-- The `./playground/src/main.css` will be generated by the user before viewing the changes made by the agent. No tailwindcss cli command needs to be run by Gemini.
-
-
-Reference file structure for a new ./playground project.
-```
-./playground/
-├── README.md
-└── src
-    ├── css
-    │   └── input.css
-    ├── index.html
-    └── vendor
-        └── js
-            └── tailwindcss-elements.1.0.0.js
-
-5 directories, 4 files
-```
 ---
 
 ## Component Utilization Strategy

README.md

@@ -1,6 +1,6 @@
 # Tailwind-AI
 
-An lab to run experiments using agentic coding tools and Tailwind Plus Components.
+An lab to run experiments using agentic coding tools to use Tailwind Plus Components.
 
 ## Setup
 
@@ -10,7 +10,7 @@ The setup assumes you have `tailwindcss` installed globally on your machine.
 
 A makefile is present with the commands `prepare` and `clean`. Note these are destructive commands and will wipe the current contents of the `./playground` directory.
 
-Each experiment you want to run should be done within the `./playground` directory. Simply `make prepare` the directory then run your agentic coding tool with that directory as the target for changes. Use `make watch` to compile tailwind css, and `make live` to view changes in the browser.
+Each experiment you want to run should be done within the `./playground` directory. Simply `make prepare` the directory then run your agentic coding tool within that directory as the target for changes.
 
 ## Resources