القائمة
Conventions for working with the user's personal dotfiles repo at ~/.dotfiles. Use when modifying tracked config files (anything mapped in ~/.dotfiles/dotfiles.json) or when the user mentions "dotfiles".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Enable concise, focused mode for the rest of the conversation
Fast-path Playwright CLI recipes for ad-hoc browser testing and screenshots. Use when manually verifying UI changes in a local dev environment - covers installation, the open-snapshot-interact-screenshot loop, stable element targeting, and the gotchas that waste time.
Run a one-shot Claude Code subagent review of the current branch or PR without editing files.
Use when working with the user's dotfiles managed by the `dotfiles` CLI — saving live config into the tracked repository, installing tracked files to live paths, inspecting tracked-file status, or scaffolding a new dotfiles repo.
Use the notes CLI to create, list, read, append to, update, annotate, and delete notes in a date-based markdown archive — including daily todos with task rollover and tag operations across the store.
Enable "Explain Like I'm a Smart 18 Year Old" mode for the rest of the conversation. Use when the user types /eli18.
| name | dotfiles |
| description | Conventions for working with the user's personal dotfiles repo at ~/.dotfiles. Use when modifying tracked config files (anything mapped in ~/.dotfiles/dotfiles.json) or when the user mentions "dotfiles". |
Personal dotfiles repo at ~/.dotfiles, managed by the dotfiles-cli tool (dotfiles on $PATH).
For commands and flags, run dotfiles --help (and dotfiles <command> --help) — it's self-describing. Add --json to any command for machine-readable output.
~/.dotfiles/dotfiles.json maps source paths in $HOME to mirrored paths under ~/.dotfiles/config/<tool>/. Entries are files or directories (trailing / = directory, tracked recursively). Adding a file inside an already-mapped directory needs no manifest change — just save.
$HOME (not the copy under ~/.dotfiles/config/).dotfiles status — confirm drift.dotfiles save — local → repo. Prefer scoping with --tool / --file (see dotfiles save --help) to avoid touching unrelated drift.~/.dotfiles, branch and make an atomic commit.The reverse direction (repo → live) is dotfiles install.
--help)git add -A. An unscoped save syncs every drifted tracked file, so git status may surface unrelated changes the user made earlier. Stage only the files for the current logical change — one change per commit.install vs save direction is ambiguous (unexpected drift, possible data loss), ask the user which side is authoritative.Co-authored-by, no agent signatures.