All use Cursor AI as an interactive coding tool. Cool. But not fully.
LLMs evolve, so there will be less and less intermediate interactions.
You already could use Cursor AI as a “higher level non-interactive compiler materializer” working in one shot.
A working example
One could create bootstrap.md file, populate it with instructions about the desired target (app, picture, doc, etc), open it in the Cursor AI Composer and say “go!”. Actually even one dot ‘.’ could be enough to trigger the creation process – if you are lucky in choosing your LLM engine. Also, if you are lucky there will be no interactions, just a single “Apply All” click after triggering.
Well, sometimes you are unlucky even with the advanced LLM-engine and your LLM refuses to create files. Then you’ll need to convince it. Be a good cop, or bad cop, be a good person, or be an abusive manipulator – model will likely agree after a few rounds 
Below I attach embed my bootstrap.md. You may want to reproduce the SVG-graph described in bootstrap.md on your own.
Not all LLM-engines are the same. Some will just shallowly give you an advice on how to proceed and will refuse to create files. But some will do the job! (As you see the attached pictures they are still not flawless though)
Your bootstrap.md
bootstrap.md for your targets could be a self-containing like the attached one or be referring to other files.
For example, you could create an interactive 3D-version of the above example. The funny thing is that you could even avoid telling what libraries/platforms/languages to use. Just focus around “i need an interactive visualization” not even telling whether it is an desktop app, web-app, smartphone app, or whatever else.
Afterword
Why ‘bootstrap’?
Forward pass
when we have a goal in our mind we write it down in form of instructions, technical specification, etc. Then LLM-agents (Cursor AI Composer) materialize the instructions in the way they were understood.
Feedback
If instructions were not good enough (or LLM was not smart enough) we don’t obtain what we wanted. We do a feedback to patch the detouring from our original plan.
Backward pass!
Will our patching feedback work out as we expect or we’ll need more patches to be added and applied?
Do we want at the end a starter-plan plus thousand patches chained to it?
Or do we want our patches back-propagated to some bootstrap.md (+ populated doc folder, etc)
That’s it. The target is to get the “DNA” of our project – the bootstrap thing, not the secondary thing like (source code) which is rather “mRNA” or the “proteins” of our project.
After-Afterword
Compose AI can’t do git commands yet. So “crossover” between your bootstrap-branches could rather come somewhat later in the future
BTW, choosing (or changing on the fly) the LLM-engine directly from the bootstrap.md would be also fun…
bootstap.md:
# Instruction to Cursor AI Composer
According to the technical specification below create an SVG file 'doc/blackhole-slinging-trajectory.svg'
with an SVG graph for the scientific article.
# Technical Specification
## Objective
Create a realistic 2D SVG sketch depicting the trajectory of a photon emitted from a light source (such as a star) towards a black hole (BH).
The photon should approach the gravitational field of BH tangentially, bend around the BH on the Schwarzschild radius,
due to gravitational lensing, and then depart tangentially, heading back towards the light source.
## Purpose
The direct (but secondary) purpose of this graph is to illustrate the phenomenon the photon being returned to the source due to the intense gravitational field.
The primary purpose though is to start a discussion on the question:
*What is the topology of the observable universe?*
Black holes probably are just a special case of the (simple?) forms on how "outer time-space" could be incapsulated within of our "inner time-space" we exist in.
The complexity of the topology of the observable universe could be much richer than just "an expanding body with (black) holes in it".
The "outer time-space" could be massivelly interconnected so that our observable universe is rather incapsulated within the outer time-space similarly to how the black holes are incapsulated in ours.
Also, the discussion should be started on the what light sources on the sky are indeed primary sources and which ones are just actually secondary ones re-routing light from primary ones via slingshot effect.
Last but not least, is slingshot effect could happen only on the gravitational radius or could it also happen for trajectories non-tangentially bumping into the BH due to the non-homogeneity of BH's gravitational field?
## Key Graph elements
- Canvas
- Light Source ("Source")
- Black Hole ("BH")
- Photon trajectory
## Requirements
### Canvas
- The canvas should be dark gray
### Source
- The source should be placed at the left side of the graph and be colored in orange.
### Black Hole
- The BH should be placed at the right side of the graph
- The BH should be displayed as a black filled circle with a radius smaller than the radius of the Source
- The Schwarzschild radius of BH should be marked as a thick gray circle around the BH. Radius should be equal to the radius of the Source.
- two tangent points on the gravitational radius circle should be marked. Upper one should be colored in green, lower one in blue
### Photon trajectory
The photon trajectory should be drawn in white and consist of three components:
1. The first component starts from the Source and moves straightly towards the upper tangent point on the gravitational radius circle.
2. The second component smoothly connects to the first at the upper tangent point, starts from there and bends as an arc behind the BH along the gravitational radius circle towards the lower tangent point on the gravitational radius circle
3. The third component smoothly connects to the end of the second component at the lower tangent point and continues back towards the Source as a straight line.
Small arrows should be added near each component depicting the direction of the photon.
## Delivery
- don't tell me how to create the graph, just create the file
- ensure that the SVG file './doc/blackhole-slinging-trajectory.svg' is indeed created and populated completely and correctly by you
Results (cursor ai 0.40.4)
claude-3.5-sonnet
o1-mini
gpt-4o
cursor-small
cursor-small refuses to create any files 