If you share my view that raylib is somewhat low level where a lot one has to build themselves.

Which is 1 of the benefits of raylib having control of everything yourself.

Please share what kind of high level libraries as extensions to raylib would you be interested in seeing built so that it can be imported and used where only raylib is the library's only dependency.

Based off upvotes I will attempt to build library extension for raylib where raylib is the library's only dependency.

If there is already a resource with libraries built on top of raylib please share.

If you have built one and open sourced already please share below for others to find.

Is it just me I was about to uninstall antigravity and just be done but now with the ridiculous usage l_mits I now only use AntiGravity only for analyzing hard problems that my most used model cannot reason to figure out how to solve.

I only use AntiGravity to analyze and document the problem in detail explicitly without any solution just pure analysis and documenting of the problem.

Then feed the document analysis to my most used model to work on the problem it had trouble understanding, due to lower reasoning but with guide of document analysis it leads to better reasoning.

Because trying to use AntiGravity for both analyzing problem and solving it will use up even more of the ridiculous limiting usage l_mits and never actually finish solving problem.

It is less likely to make mistakes only reading and analyzing than writing.

And when it does write and makes mistakes it has to read the mistakes it already made and perform another write using up the usage l_mits, so I leave all the writing and edits to other models and AntiGravity models purely for analyzing.

Anybody else?

What I mean by "1 shot prompts":

1. Start new session
2. Prime the model with prompt
3. Write 1 shot prompt for implementation, update, fix or refactor

Has been getting the job done.

Just wanted to share a prompt that I have been using to prime the models to produce accurate results quickly.

After a long conversation with Opus 4.8 not implementing something I asked for at the end I sent:

Finally!
Now even with all the specified protocols I provided and I instructed you with.
Explain why all the failures.
Explain what you can do and what I can do to prevent the failures from happening again
including having me input on obvious things that could have been done,
for you not to rely on me for input to fix everything.
Give me a full prompt I can use to make sure never happens again.

I am sure the prompt can be improved but that is what I have been sending in order to prevent failures by it first explaining, then producing a full prompt based of explanation.

Turns out if you have the LLMs break things down in laymen's terms then when it actually gets to solving it the explanation becomes part of the context helping solve the problems.

The Prompt:

Here is the prompt I got it to generate after long conversation of continuous failures (works really well even when avoid Test Driven Development - not that I recommend that but just an observation):

Before implementing, updating or debugging any feature:

List every system that reads or writes the affected implementation.
Do not write any code until this list is complete.

Map every event that can fire within requested implementation.
For each event, state whether it can interfere with the targeted implementation.

Identify any system that could undo or overwrite what the implementation is doing.
If one exists, design the fix for that conflict before writing the code.

Do not patch.
If a conflict is found,
redesign the relevant systems together,
not independently.

Describe the expected symptom of failure before shipping — so that if it fails,
the symptom immediately points to the cause.


Every update and refactor must be implemented following
functional style programming, separation of concerns, pure functions.
Follow best practices like:

1. Keep pure logic in pure functions.
2. Keep side effects isolated at the edges.
3. Do not mix rendering, state transitions, input handling, animation,
and scene construction in the same function.
Each process must be own named function at module level.
Never mix concerns inside a single dispatch function or hook block.
4. If a file grows beyond a focused responsibility,
stop and split before editing.
5. When find code file that can be split up into
separate files with separation of concerns, proceed to do so before making updates.
6. If a function mixes more than one concern,
stop the implementation before it starts.
7. Execute a collective redesign of all affected systems
when addressing architectural conflicts.
Always redesign the affected systems together.

Setting Up Custom Slash Command

I even made it into a custom slash command I use starting every new session in Gemini CLI:

description = "Pre Prompt Implementation"

prompt = """

Before implementing, updating or debugging any feature:

List every system that reads or writes the affected implementation.
Do not write any code until this list is complete.

Map every event that can fire within requested implementation.
For each event, state whether it can interfere with the targeted implementation.

Identify any system that could undo or overwrite what the implementation is doing.
If one exists, design the fix for that conflict before writing the code.

Do not patch.
If a conflict is found,
redesign the relevant systems together,
not independently.

Describe the expected symptom of failure before shipping — so that if it fails,
the symptom immediately points to the cause.

Every update and refactor must be implemented following
functional style programming, separation of concerns, pure functions.
Follow best practices like:

1. Keep pure logic in pure functions.
2. Keep side effects isolated at the edges.
3. Do not mix rendering, state transitions, input handling, animation,
and scene construction in the same function.
Each process must be own named function at module level.
Never mix concerns inside a single dispatch function or hook block.
4. If a file grows beyond a focused responsibility,
stop and split before editing.
5. When find code file that can be split up into
separate files with separation of concerns, proceed to do so before making updates.
6. If a function mixes more than one concern,
stop the implementation before it starts.
7. Execute a collective redesign of all affected systems
when addressing architectural conflicts.
Always redesign the affected systems together.
"""

Saved as pre-prompt-implement.toml so can use as /pre-prompt-implement

Closing Thoughts:

I will really love to see a good resource of conversations from the community of how they got to the LLMs to stop producing mistakes and actually solve problems.

There is a lot of posts about what LLMs suck at or bad at or just can't do.

Let us not use this thread to shit on LLMs there are plenty of threads for that.

Can we use this thread to share what has been solving major pain points.

For example:

- Custom Slash Commands

- Prompts

- Skills

- Detailed Workflows

- Specific Harness Use & Configurations

- Agents

- Sub Agents

Anyone know of any Meta Developers for Quest 3 that are active in this reddit community?

Hello community I have the goal, desire and good AI workflow for building software so I want to propose the idea of building an Local Free Open Sourced Google AI Studio that will be based of and optimized for Gemini Nano and Gemma 4, where connecting cloud models will be the optional feature.

I have no idea how long it will take most likely 2 weeks of actual work hours, it will definitely not be 2 weeks consecutively just so I avoid burnout.

Help me use this thread to comment all the features you love about AI Studio and features you wish were implemented.

Based of the upvotes is how I will decide what to prioritize when building the open sourced version.

Stick to 1 comment per feature, do not mix all features into 1 comment, you can even list out features in 1 comment and make subcomments for each individual feature that will be used to upvote feature.

Please start commenting below and upvoting features.

The latest updates introduced the following problems:

- Navigator does not show at all when login to non owner account, forced to sign into owner account then other account to see navigator on non owner account

- Having browser locked with passcode before would only open 1 window at a time, which helped saved memory and performance if have lots of tabs open, now all windows open and end up crashing which forced me to close most of my windows now can barely use multiple windows reliably

- Signing in now drains 10% of my battery just for signing in by loading owner account then other account (I do use the quest heavily so could be degrading battery but the quest is never HOT and always used in cool temperature room)

Anyone else experiencing this?

Please use this thread to comment problems experiencing in latest updates.