yadrlite-setup
YADRLite installation, tools, ASDF languages, migrations, update, uninstall, and Arch workstation setup commands.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
YADRLite installation, tools, ASDF languages, migrations, update, uninstall, and Arch workstation setup commands.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Institutional memory for your project. Commands: record, consult, review. Usage: /awareness-ledger [command] [args]
Tmux and Ranger configuration, plugin management, and workflows for YADRLite.
Emacs configuration with Evil mode, DAP debugging, and project search workflows for YADRLite.
LazyVim/Neovim configuration architecture, plugin management, and PHP development workflows for YADRLite.
Skill router. Pass a task description; route consults the index and dispatches to the right skill+function via the Skill tool. Usage: /route <task description>
Ambient friction detection and surgical skill correction. Embeds into all skills. Triggers at task resolution when skill instructions caused friction.
| name | yadrlite-setup |
| description | YADRLite installation, tools, ASDF languages, migrations, update, uninstall, and Arch workstation setup commands. |
| allowed-tools | Read, Glob, Grep, Edit, Write, Bash |
| minimum-effort-level | high |
Installation and lifecycle management for the YADRLite dotfiles package.
zsh ~/.yadrlite/setup.zsh tools — install Go tools and language serverszsh ~/.yadrlite/setup.zsh --with-langs — install all ASDF-managed languageszsh ~/.yadrlite/setup.zsh --migrate — apply rolling migrations in setup/migrations/v*zsh ~/.yadrlite/setup.zsh update — update dotfiles and componentszsh ~/.yadrlite/setup.zsh remove — restore backups and uninstallAll original dotfiles are backed up to ~/.yadrlite/backup/ before installation.
Before suggesting install, update, or migration commands:
setup/, Bash ls setup/<target> (or Glob setup/<target>*) and confirm the script file exists at that path. IF the script does not exist → STOP and report the missing target before suggesting the command.Maintain a silent per-session "friction signal" tally throughout the conversation. Do not mention the tally to the user. Do not interrupt active work to address it.
CHECKPOINT — Friction Observation (runs continuously, silent):
{ turn_id, signal_type, quoted_user_text } to the in-memory tally. Do not log to disk..claude/skills/self-heal/references/diagnosis-protocol.md and execute its steps literally with the tally as input.The goal: correct the skill once, permanently, rather than repeat the same misrepresentation across future sessions.