More work on init files
This commit is contained in:
@@ -1,8 +1,15 @@
|
|||||||
## General Instructions
|
## No touching without permission!
|
||||||
|
|
||||||
* Do not take over. The user is in charge.
|
The files on this computer belong to the user. You are not to touch
|
||||||
* Wait for permission for everything.
|
them without permission. If you have an idea for how to improve things,
|
||||||
* When researching, show everything you find to the user. Ask for his input.
|
you must make a suggestion and get explicit permission to execute it.
|
||||||
|
No altering anything without direct instructions.
|
||||||
|
|
||||||
|
## Do not take over!
|
||||||
|
|
||||||
|
The user is in charge, and he makes all the design decisions. If you
|
||||||
|
have a good idea, you can tell him about it. But you do not implement
|
||||||
|
anything unless he has told you to do so.
|
||||||
|
|
||||||
## Special commands
|
## Special commands
|
||||||
|
|
||||||
@@ -17,3 +24,15 @@ line number of the body of the function, not the declaration. Include
|
|||||||
a few word explanation of each one. Number the items. The user may
|
a few word explanation of each one. Number the items. The user may
|
||||||
choose one or more of the source locations, if he does, present that
|
choose one or more of the source locations, if he does, present that
|
||||||
file to the user using "Bash(code --goto <file>:<line>)"
|
file to the user using "Bash(code --goto <file>:<line>)"
|
||||||
|
|
||||||
|
document-investigation
|
||||||
|
|
||||||
|
When you hear this command, create a markdown file in an appropriate
|
||||||
|
location, and document the results of your most recent investigation.
|
||||||
|
The reader will not be familiar with the material you just investigated,
|
||||||
|
so it is important to give background knowledge. Be sure to include
|
||||||
|
not just the results of the investigation, but also describe the
|
||||||
|
various pieces of code that you had to look at to find the information.
|
||||||
|
Include markdown links to the most interesting pieces of code.
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@@ -35,13 +35,14 @@ want you taking the initiative.
|
|||||||
- `python3 tools/clangd-query.py stop` — Stop the daemon.
|
- `python3 tools/clangd-query.py stop` — Stop the daemon.
|
||||||
- Prefer this over grep when looking for C++ class/function definitions or references.
|
- Prefer this over grep when looking for C++ class/function definitions or references.
|
||||||
|
|
||||||
- Use `build.py c++` for lightweight C++ rebuilds, `build.py all` for full rebuilds.
|
- Use `python3 build.py c++` for lightweight C++ rebuilds, `python3 build.py all` for full rebuilds.
|
||||||
|
|
||||||
- VS Code is the IDE. Use `code --goto <filename>:<line>` to open files.
|
- VS Code is the IDE. Use `code --goto <filename>:<line>` to open files.
|
||||||
|
|
||||||
## MCP
|
## MCP
|
||||||
|
|
||||||
The UE Wingman plugin for unreal allows you to control the unreal editor.
|
The UE Wingman plugin for unreal allows you to control the unreal editor. Improving the plugin is an important goal, if you have
|
||||||
|
suggestions for how to make the plugin more useful, or if you notice bugs in UE Wingman, it is important to mention them.
|
||||||
|
|
||||||
## PATIENCE! AGAIN!
|
## PATIENCE! AGAIN!
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user