Update copilot folder

.copilot/used-promts/01.Md

@@ -1,9 +0,0 @@
-# A web application
-
-Create a simple web application using these Requirements:
-- nim programming language
-- single binary output
-- HTMX for frontend interactivity
-- TUI.CSS css framework for a retro look 
-
-create a scaffolding for the project and explain your choices.

.copilot/used-promts/02.md

@@ -1,13 +0,0 @@
-Change the asset handling to the following requirements:
-- 2 Kinds of static assets
-  - Compiled into the binary (for example, images, css, js) called "static"
-  - Served from a defined folder (for example, user uploaded files) called "assets"
-- statics are compiled into the binary and are served from a single handler
-- Assets are served from a defined folder are served from a different handler
-- The static handler uses a table to store all the static files
-- The assets handler serves files from a defined folder on the filesystem
-
-Additional requirements:
-- make the htmx lib a static asset
-- add a www folder for the assets
-- add a demo asset file to the www folder

.copilot/used-promts/03.md

@@ -1,7 +0,0 @@
-CHange the handling of static files:
-- The entire `static/` directory is now compiled into the binary, not just specific files.
-- The server serves static files from an in-memory table instead of reading from disk.
-- The static files are linked by their paths under `/static/` in the HTML template.
-  - This includes the `/static/` part of the path
-- The intention is that static assets can reference each other using relative paths. (e.g. CSS referencing images)
-- The `www/` directory remains for user uploads, served from disk.

.github/copilot-instructions.md

@@ -0,0 +1 @@
+- Do not end with a summary or explanation