Skip to content

Instantly share code, notes, and snippets.

@ajitid

ajitid/successful-prompts-and-other-things.md

Last active March 10, 2026 19:03
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save ajitid/d2cbafe3e97c9b513954fbf9ad97798e to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save ajitid/d2cbafe3e97c9b513954fbf9ad97798e to your computer and use it in GitHub Desktop.
Download ZIP
[not for public consumption] better ui, better chatgpt
Raw
successful-prompts-and-other-things.md

I want you to explore https://blog.jetbrains.com/kotlin/2026/01/the-journey-to-compose-hot-reload-1-0-0/ and anything that you find any concepts that you find you can further explore in the web and help me plan out because right now the way we have hot load implemented the hot load does work but it's not like instant it takes a second or two you can read our code our current code to understand why is that happening and then propose solution of whatever these guys are using these jet brains guys are using if we if it's if it's possible to use it then we probably want to use it in our case as well the same mechanism so we can have a faster hot reload like an instant hot reload any adjustments any breaking changes that we have to do I am okay with that if you have any questions please ask.

implement 01xcaa3f-d7ce-7841-8fe6-83ef644152b5.md . ask questions if any. check web if you want and temp scripts if you need to confirm something. project-to-refer is in path/to/project-to-refer if you need . i also want to you create todos in todo.md with phases and check out items as you progress

to self: 01xcaa3f-d7ce-7841-8fe6-83ef644152b5.md is the whole convo exchange not just plan file in codex

that works. thanks. i want you look at last commit and think and tell why all those changes are necessary and which ones of them are redundant, fallback, not useful or not in use anymore so we can drop them. please think really hard and check web if you need

can you check the code and think really hard and check web if you need to tell why it could be happening? you can run local tests if you want to confirm hypothesis or to grab findings

better ui llm:

❯ Great, thanks. Now I want you to create a fresh plan to show this in the UI. use tailwind css . Also add in the fact that this JSON file may not be there because the command would not have been on. So assume the fact that this could have happened and also incorporate it. You know, that I think suppose the UI should tell you that run this please, run this command please and then refresh something like that. also Don't add any flare in this site. This should be as simple as possible. I do want a search though, so I'm not sure, use minisearch or something, the main things I want to search for is by searching searching through like filtering by by an environment, like if the deployments have happened essentially NOT_EXECUTED is not there for environment for that environment yeah so yeah so show only those then also a way to essentially if you i'm not totally sure how you're going to demonstrate show all of this but if what a way to essentially a way to toggle all those blocks for all the builds in which NO_EXECUTED is there so I can easily see where the build has flown through. I would also prefer a way to mention a tag SCM_TAG and see all the places where it's deployed. see @data/history.json to understand the structure first

Also search the web to understand like what sort of policies that LLMs make when they create UI like for example showing a purple gradient and all because we want to avoid that and then also explore like good designs I'm not sure maybe on dribble or in spotted in prod or check some design studios like not design studios because they show a lot of there using 3js and all we don't want that we want a simple great clean website for this but yeah take some inspirations from the web. I'm not sure there are other places as well from which you can take the inspiration so take the inspiration from there.

  • prepare an implementation-ready patch spec with exact edit points so it can be applied immediately once execution mode is enabled.
  • cite relevant references (paths, links)
  • ask questions if any

https://github.com/JetBrains/kotlin-desktop-toolkit So we have this Kotlin desktop toolkit and I wanted to create a sample program in this folder using it. In case if you want to consult the code to understand the project better, you can use these resources:

prepare an implementation-ready patch spec with exact edit points so it can be applied immediately once execution mode is enabled.

cite relevant references in the plan and in the code comments if needed

no fallback or maintaining backwards compatibility pls, let's make proper breaking change

unrelated to chatgpt:

local and remote isolated vms:

in cursor:

Shared Knowledge
View team-wide Rules, Commands, and Hooks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment