Brainrotify
Rewrite eligible text surfaces into meme-heavy prose while leaving program structure intact. Prefer the bundled script for file-based work because it handles file discovery, safe backups, comment targeting, and reporting more reliably than ad hoc edits.
This skill is agent-agnostic. Use the same workflow with Codex, Claude, or similar AI coding agents that can read files, run a script, and present a diff or summary.
Workflow
- Initialize the skill clearly.
In the first user-facing update, explicitly say that
brainrotify runs locally for normal rewrites, list the available intensity levels (L, Mid, and W), and present the scope options up front: single file, folder, or preview-only.
Recommended opening prompt:
brainrotify runs locally for normal rewrites. Available intensity levels are L, Mid, and W, and I will use Mid by default unless you want a quieter or louder tone.
I can brainrotify a single file, a folder, or do a preview-only pass first. What path do you want me to target, and do you want a timestamped backup in .brainrot-backup/ before I write changes?
Confirm scope.
Identify whether the user wants a single file, a folder, or a preview-only pass. Default to Mid unless the user asks for a quieter or louder tone.
Offer a backup before writes.
Ask once whether to create a timestamped backup in .brainrot-backup/<timestamp>/. Do not skip this question unless the user already said no backup, overwrite, or preview only.
Run the helper script.
Use the script for real file rewrites. Prefer --dry-run --show-diff first for large batches or unfamiliar file types.
python3 <path-to-skill>/scripts/brainrotify.py README.md --intensity L --dry-run --show-diff
python3 <path-to-skill>/scripts/brainrotify.py docs/ src/ --intensity Mid --backup
python3 <path-to-skill>/scripts/brainrotify.py . --intensity W --no-backup
- Review the result.
Report how many files were brainrotified, how many were unchanged, and how many were skipped. Mention the backup location when one was created.
Safety Rules
- Rewrite comments, Markdown, README files, HTML comments, and real docstrings only.
- Do not rewrite fenced code blocks, inline code, imports, identifiers, signatures, executable statements, or non-docstring string literals.
- Keep headings, list structure, indentation, comment markers, and surrounding formatting intact.
- Use
--dry-run --show-diff before bulk writes when the support matrix is only partially relevant to the target tree.
- Fall back to manual inspection when the file type is unsupported or the diff looks risky.
Script Notes
The script supports:
- Markdown and plain text docs outside fenced code blocks and frontmatter
- Python
# comments and true docstrings
// and /* */ comments in common JS/TS/C-family files# comments in shell and config files when they are outside quoted strings<!-- --> comments in HTML-like files- A separate lexicon file at
scripts/brainrot_lexicon.json, so vocabulary updates do not require Python edits
The script defaults to Mid intensity. In non-interactive mode it refuses to rewrite unless --backup or --no-backup is provided explicitly, which prevents silent destructive runs.
Keep runtime rewrites network-free. If you want fresher slang, update the lexicon file offline or add a separate refresh script that fetches and compacts terms into the local JSON cache. Do not make live scraping a requirement for normal rewrites.
Intensity Guide
L: keep the text readable; add a few slang substitutions and light emphasisMid: push harder on meme phrasing while keeping the message easy to followW: lean into chat-brained phrasing, but keep the meaning recoverable
Use tone-guide.md when you need to reason about style choices or explain the intensity differences before rewriting.
1---2name: brainrotify3description: Rewrite developer-facing prose into playful Gen-Z "brainrot" language without changing executable code. Use when an AI coding agent or assistant needs to transform comments, docstrings, Markdown, README files, or other documentation text surfaces in one file or a directory while preserving syntax, logic, formatting, and code fences. Support optional backup creation and three intensity levels: `L`, `Mid`, and `W`.4---56# Brainrotify78Rewrite eligible text surfaces into meme-heavy prose while leaving program structure intact. Prefer the bundled script for file-based work because it handles file discovery, safe backups, comment targeting, and reporting more reliably than ad hoc edits.910This skill is agent-agnostic. Use the same workflow with Codex, Claude, or similar AI coding agents that can read files, run a script, and present a diff or summary.1112## Workflow13141. Initialize the skill clearly.15In the first user-facing update, explicitly say that `brainrotify` runs locally for normal rewrites, list the available intensity levels (`L`, `Mid`, and `W`), and present the scope options up front: single file, folder, or preview-only.1617Recommended opening prompt:18`brainrotify` runs locally for normal rewrites. Available intensity levels are `L`, `Mid`, and `W`, and I will use `Mid` by default unless you want a quieter or louder tone.1920I can brainrotify a single file, a folder, or do a preview-only pass first. What path do you want me to target, and do you want a timestamped backup in `.brainrot-backup/` before I write changes?21222. Confirm scope.23Identify whether the user wants a single file, a folder, or a preview-only pass. Default to `Mid` unless the user asks for a quieter or louder tone.24253. Offer a backup before writes.26Ask once whether to create a timestamped backup in `.brainrot-backup/<timestamp>/`. Do not skip this question unless the user already said `no backup`, `overwrite`, or `preview only`.27284. Run the helper script.29Use the script for real file rewrites. Prefer `--dry-run --show-diff` first for large batches or unfamiliar file types.3031```bash32python3 <path-to-skill>/scripts/brainrotify.py README.md --intensity L --dry-run --show-diff33python3 <path-to-skill>/scripts/brainrotify.py docs/ src/ --intensity Mid --backup34python3 <path-to-skill>/scripts/brainrotify.py . --intensity W --no-backup35```36375. Review the result.38Report how many files were brainrotified, how many were unchanged, and how many were skipped. Mention the backup location when one was created.3940## Safety Rules4142- Rewrite comments, Markdown, README files, HTML comments, and real docstrings only.43- Do not rewrite fenced code blocks, inline code, imports, identifiers, signatures, executable statements, or non-docstring string literals.44- Keep headings, list structure, indentation, comment markers, and surrounding formatting intact.45- Use `--dry-run --show-diff` before bulk writes when the support matrix is only partially relevant to the target tree.46- Fall back to manual inspection when the file type is unsupported or the diff looks risky.4748## Script Notes4950The script supports:5152- Markdown and plain text docs outside fenced code blocks and frontmatter53- Python `#` comments and true docstrings54- `//` and `/* */` comments in common JS/TS/C-family files55- `#` comments in shell and config files when they are outside quoted strings56- `<!-- -->` comments in HTML-like files57- A separate lexicon file at `scripts/brainrot_lexicon.json`, so vocabulary updates do not require Python edits5859The script defaults to `Mid` intensity. In non-interactive mode it refuses to rewrite unless `--backup` or `--no-backup` is provided explicitly, which prevents silent destructive runs.6061Keep runtime rewrites network-free. If you want fresher slang, update the lexicon file offline or add a separate refresh script that fetches and compacts terms into the local JSON cache. Do not make live scraping a requirement for normal rewrites.6263## Intensity Guide6465- `L`: keep the text readable; add a few slang substitutions and light emphasis66- `Mid`: push harder on meme phrasing while keeping the message easy to follow67- `W`: lean into chat-brained phrasing, but keep the meaning recoverable6869Use [tone-guide.md](references/tone-guide.md) when you need to reason about style choices or explain the intensity differences before rewriting.
tengfone