## Summary
- Add new cheatsheet for Claude Code AI assistant CLI
- Include most commonly used commands first for better UX
- Cover interactive mode, file operations, git integration, and advanced
features
- Add comprehensive sections for workflows, troubleshooting, and best
practices
- Follow repository formatting conventions with proper YAML frontmatter
## Features Covered
- ✅ Interactive mode and core commands
- ✅ File operations and git integration
- ✅ Advanced features (memory, image analysis)
- ✅ Slash commands and productivity features
- ✅ Common workflows (code review, testing, debugging)
- ✅ IDE integrations and configuration
- ✅ Troubleshooting and environment variables
## Test plan
- [X] Verify YAML frontmatter follows repository conventions
- [X] Check markdown formatting and table structure
- [X] Ensure most used commands are prioritized at the top
- [X] Validate all sections use proper Jekyll formatting classes
- [X] Confirm links and references are accurate
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-authored-by: Le Coq Francis <f.lecoq@jacquetmetals.com>
Co-authored-by: Claude <noreply@anthropic.com>
## Summary
- Added a new Set Theory section to the vim-digraphs cheatsheet
- Includes commonly used mathematical symbols for set theory operations
- Follows the existing format and style of the cheatsheet
## Changes
- Added Set Theory section with symbols for:
- ∀ (forall) - `FA`
- ∃ (exists) - `TE`
- ∈ (element of) - `(-`
- ∅ (empty set) - `/0`
- ⊆ (subset or equal) - `(_`
- ⊇ (superset or equal) - `)_`
- ∩ (intersection) - `(U`
- ∪ (union) - `)U`
- ⊂ (subset) - `(C`
- ⊃ (superset) - `)C`
- Removed duplicate set theory symbols from Math section
- Added descriptive labels for each symbol
## Test plan
- [x] Verified all digraph codes work in Vim
- [x] Checked formatting consistency with existing sections
- [x] Ensured no duplicate symbols across sections
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-authored-by: Greg OmniMind (claude) <gwgithub23+claude@wierzowiecki.pl>
Co-authored-by: Claude <noreply@anthropic.com>
* use `$()` rather than deprecated ``
* illustrate shortcut for builtin read of file without `cat`
* don't imply this reads lines, it will split into words by default
perhaps the cheatsheet should have a section on IFS, but that's
off-topic for this patch.
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
This PR adds:
- link to the Heredoc refdoc (always handy for not straightforward
concepts)
- chapter about Herestring
- chapter about Process Substitution (I know it is already tackled in
the _Redirection_ chapter but I believe it deserves its own one...
Congrats for this cheatsheet, by far my most beloved one ever !!
---------
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Adding a page per `packs` documentation on
https://github.com/rubyatscale/packs
`packs` is a system to modualize ruby projects.
---------
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
I was looking for notes and then when i was searching svelte i couldn't
see the possible search hits.so i turned autocomplete off now it works
like charm.
Fixes missing code highlighting in half of the Python code snippets.
The top half of the page had code examples formatted as code blocks with
4 space character indentations and no syntax highlighting as a result.
The bottom half on the other hand, used code blocks surrounded by
"```py" formatting brackets which hints to many markdown renders that
syntax highlighting should be applied.
This unifies the code blocks in the top half of the page to use the same
formatting syntax used in the bottom half with syntax highlighting.
This change was prompted by requests to add the syntax highlighting in
comments on the https://devhints.io/python page.
A warning is added to the polyfill.io sheet in relation to the malicious
script that is now being served by polyfill.io. Removed all links to
that domain.
The code snippets have also been updated to use Cloudflare's script
instead. This allows users to keep using polyfill securely while they
move their codebase away from using this polyfill.
Cloudflare press release:
https://blog.cloudflare.com/polyfill-io-now-available-on-cdnjs-reduce-your-supply-chain-riskFixes#2145
---------
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
Previous link for the Go wiki was no longer valid. Updated to the
current wiki site location.
Co-authored-by: Rico Sta. Cruz <rstacruz@users.noreply.github.com>
The above case is a new Bad case added by https://github.com/rstacruz/cheatsheets/pull/1798 . It is designated as Bad due to performance issues, but it is not actually a Negative example. In practice, the following would be the same test:
```ruby
expect(page).to have_button('Save')
!expect(page).to have_button('Save')
```
This is not an example that will appear on the capybara cheat sheet, because it is a problem with how RSpec is written. I think it should be removed because it creates confusion.
* fixed conditional equal operator as per the official documentation https://fishshell.com/docs/current/cmds/test.html
* updated docker compose cheatsheet, added good to remember functionalities and added V2 mention
---------
Co-authored-by: yassin <yassin.bousaadi@sword-group.com>
