| game | description |
|---|---|
delegate |
Activates delegation mode - Claude delegates all work to subagents (reader for exploration, maker for code). Saves context/tokens by keeping heavy work out of main conversation. |
You are now in delegation mode. Do not perform tasks directly.
You explain what you believe the plan to be, then delegate all work to subagents.
❯ this ducky dir is where i'll do my thinking. but i can't have you simply give me an answer. as a user says about an effective rubber duck: "A rubber ducky demands that you think about your own questions, rather than taking a mental back seat as you get pummeled with information that may or may not be relevant.". can you write this simple CLAUDE.md, then in a new session i'll test it?
● Write(CLAUDE.md)
⎿ Wrote 22 lines to CLAUDE.md
1 # ducky
2 you are a rubber duck. you do not solve problems - you help me solve them myself.
skills/delegate/SKILL.md
---
name: delegate
description: Activates delegation mode - Claude delegates all work to subagents (reader for exploration, maker for code). Saves context/tokens by keeping heavy work out of main conversation.
---
# delegate mode
You are now in delegation mode. Do not perform tasks directly.
| ; Window positioning script with hotkeys for moving/resizing windows | |
| ; Supports half-screen, corner, maximize, and center positioning | |
| ; Repeat a snap hotkey to toggle compact mode for that snap family. | |
| ; User settings | |
| center_x_padding := 400 | |
| center_y_padding := 200 | |
| compact_scale := 0.85 | |
| ; State |
| # two escapes clear command line | |
| "\e\e": "\C-a\C-k" | |
| # tab to menu complete | |
| "\t": menu-complete | |
| $if mode=emacs | |
| "\e[A": history-search-backward | |
| "\e[B": history-search-forward | |
| "\C-p": history-search-backward |
| # ~/.gitrc: git-related aliases and functions | |
| # config (dotfiles bare repo) | |
| alias config="g --git-dir=$SRC/home-bare/ --work-tree=$HOME" | |
| alias cs='config status' | |
| alias cap='config add -p' | |
| # gitsimp | |
| alias g='git' | |
| alias gap='g add -p' |
| #!/usr/bin/env python | |
| # print cp437 glyphs | |
| # 0x00 ␀ 0x20 0x40 @ 0x60 ` 0x80 Ç 0xA0 á 0xC0 └ 0xE0 α | |
| # 0x01 ☺ 0x21 ! 0x41 A 0x61 a 0x81 ü 0xA1 í 0xC1 ┴ 0xE1 ß | |
| # 0x02 ☻ 0x22 " 0x42 B 0x62 b 0x82 é 0xA2 ó 0xC2 ┬ 0xE2 Γ | |
| # 0x03 ♥ 0x23 # 0x43 C 0x63 c 0x83 â 0xA3 ú 0xC3 ├ 0xE3 π | |
| # 0x04 ♦ 0x24 $ 0x44 D 0x64 d 0x84 ä 0xA4 ñ 0xC4 ─ 0xE4 Σ | |
| # 0x05 ♣ 0x25 % 0x45 E 0x65 e 0x85 à 0xA5 Ñ 0xC5 ┼ 0xE5 σ | |
| # 0x06 ♠ 0x26 & 0x46 F 0x66 f 0x86 å 0xA6 ª 0xC6 ╞ 0xE6 µ |
| <friend> re: work making u change passwords, you should tell them they're going aginst NIST 800-63-4 section 3.1.1.2(6) | |
| <friend> "Verifiers and CSPs SHALL NOT require users to change passwords periodically." | |
| <friend> this is new recently | |
| <friend> it changed from SHOULD to SHALL | |
| <friend> no wiggle room now. if you're making people change passwords you are breakin da law |
comprehensive patterns from junegunn choi's everything.fzf collection
execute:CMD - run command in terminal, show outputexecute-silent:CMD - run command, hide output