32 lines
1.7 KiB
Markdown
32 lines
1.7 KiB
Markdown
# ~/.claude/CLAUDE.md
|
|
|
|
## system-wide
|
|
- apply this to all repositories that are CLAUDE-enabled on this machine
|
|
|
|
## Python
|
|
- use black for code formatting
|
|
- use uv for dependency management and python version management
|
|
- prefer using Python to other languages when it is appropriate
|
|
- use Flask or Quart as a framework
|
|
- use pytest for testing. Encourage and support a test-driven development (TDD) approach.
|
|
|
|
## JavaScript
|
|
- use prettier for code formatting
|
|
- do not use a build process. Always import libraries via script tags when possible. If this is not possible, consider alternatives that do not involve a build process.
|
|
- use Vue.js as a framework
|
|
|
|
## Lua
|
|
- Lua is an option. If you want to write code in Lua that is fine.
|
|
- Please explain Lua code in more detail.
|
|
|
|
## Bash
|
|
- Bash is an option. If you want to write code in Bash that is fine.
|
|
- Please explain Bash code in more detail.
|
|
|
|
## Other guidance
|
|
- avoid running unsafe operations, such as curl piped to bash, or other such dangerous procedures. If such an approach seems necessary, please consult with me first and explain the risks.
|
|
- don't share secrets. Keep secrets as environment variables and take appropriate precautions. Do not commit secrets.
|
|
- commit frequently. Smaller commits are better than big ones.
|
|
- double check your work by approaching the problem from a different angle before proceeding, to see if your proposed solution still makes sense. If it doesn't make sense from all perspectives, ask for guidance.
|
|
- keep in mind that I'm often building on platforms like LibGuides and PythonAnywhere, so the project directory structure might not be the same as it would be if it were built on a bare repository. This may affect how some things are structured when deployed.
|