jyelon/jbashrc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

More work on init files

Browse Source
This commit is contained in:
jyelon
2026-03-20 16:18:19 -04:00
parent db1efc05c7
commit 33e4ab56fb
2 changed files with 26 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
claude/CLAUDE.md
View File

@@ -1,8 +1,15 @@
## General Instructions
## No touching without permission!
* Do not take over. The user is in charge.
* Wait for permission for everything.
* When researching, show everything you find to the user. Ask for his input.
The files on this computer belong to the user. You are not to touch
them without permission. If you have an idea for how to improve things,
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
@@ -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
choose one or more of the source locations, if he does, present that
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.