bama
BAMA: 모든 Mac 앱을 만들 수 있습니다
Claude Code·Codex·Pi용 에이전트 스킬, 상태 기반 시스템 및 인터랙티브 설명기
Agent Skills for Claude Code, Codex, and Pi: stateful-systems and interactive-system-explainer
스킬HTML · JavaScriptGitHub @Yeshwanthyk직접 설치운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
설치형 프로젝트는 배포 도메인 없이도 확인할 수 있습니다. 개인 저장소는 GitHub 로그인으로, 조직 저장소는 위의 저장소 확인 파일로 직접 확인해 주세요.
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Use yesh-router when you want one entry point to select methods and apply engineering principles. Every skill also works directly. Its Triggers section covers the complete collection; its groups are navigation, not mandatory stages. yesh-router is the sole router activation name.
Delegation follows the portable delegation contract. Model and reasoning defaults are host preferences, kept in the host configuration template (config/AGENTS.md) rather than the portable docs.README 전문 보기 ↗Skills for Claude Code, Codex, pi, and other agents that read SKILL.md folders. Each skill works on its own. yesh-router picks a skill for each task and applies the engineering principles in references/principles.
Powerball mode sends yesh-router to the agent on every turn, so each task starts with a method. Set it up for each host.
Build the output style from the installed router:
python3 scripts/build-mode.py # writes ~/.claude/output-styles/powerball.md
It also installs the per-turn reminder: a UserPromptSubmit hook in ~/.claude/settings.json that runs turn-reminder.py and adds one line asking the agent to re-match each new ask. The router text loses weight deep into long threads; this line sits next to the newest message. Pass --no-hook to skip it. T3 Code runs the same claude binary, so it gets the hook too.
When your login shell is not bash, it also sets CLAUDE_CODE_SHELL to a bash 4+ (brew install bash on macOS). Agents write bash; under an interactive zsh their commands fail on unmatched globs (a ? in a URL), echo ====, unsplit $VAR, and .zshrc aliases like ls=eza. That was about 5% of Bash calls before the change. An existing CLAUDE_CODE_SHELL is left alone, and --no-shell skips this. It also warns when timeout is missing (brew install coreutils).
It also sets "attribution": {"commit": "", "pr": ""}, so agent commits carry no Co-Authored-By trailer and PR bodies no "Generated with" line. --no-attribution skips this.
Link the worker subagent, so delegated steps start with the router loaded:
ln -sfn "$PWD/config/agents/powerball-worker.md" ~/.claude/agents/powerball-worker.md
Add "outputStyle": "powerball" to ~/.claude/settings.json, then restart Claude Code.
The status line segment in config/statusline is optional. It shows which skills a session read.
Install the pi-powerball extension (private repo), then restart pi:
pi install git:github.com/Yeshwanthyk/pi-powerball
It reads the router from ~/.pi/agent/skills/yesh-router/SKILL.md and is on in every new session. Toggle it with /powerball on or /powerball off. To confirm it found the router, run pi -p "/powerball status".
| Host | Reminder |
|---|---|
| Claude Code, T3 Code | On, installed by build-mode.py |
| pi | Not set up. Port it into pi-powerball (run turn-reminder.py on each user message) only if the session audit shows the header fading in long pi threads too |
| Codex | Not set up; check for a per-prompt hook first |
Whether it helps is measured with python3 scripts/audit-sessions.py --days N, which splits header and read rates by turns with and without the reminder.
| Skill | Use it to |
|---|---|
architect | Pick a target architecture from the real contracts, call paths, and state ownership. |
benchmark-checklist | Check a performance number before you report it or act on it. |
blast-radius | Find what a change could break beyond what grep shows. |
correct | Stop a mistake agents keep repeating in a repo, with types, checks, or tests. |
deep-dive-explainer | Research a topic and write it up as a long offline article. |
diagnose | Reproduce a bug, find the cause, and prove the smallest fix. |
how | Explain how code works and why it was built that way. |
interactive-explainer | Build an interactive HTML model of behavior or state. |
interrogate | Run independent adversarial reviews and merge them into one judgment. |
Name a skill to run it: /how in Claude Code, /skill:how in pi, or "use how" in prose. Skills marked disable-model-invocation: true stay out of the agent's skill list, so reach them by name or through the router.
None of these are required. A few skills call them when they are installed.
| Tool | Used by |
|---|---|
gh | show-me PR workflow |
calldiff (Node 22+) | show-me, viz, meat-review |
Quint (JDK 17+ for quint verify) or TLA+ | invariants, verification-skill |
| Lean 4 | invariants, verification-skill |
| Kani, Verus, CBMC, or Dafny | invariants, verification-skill |
python3 scripts/check-skill-routing.py to check links and router coverage.node tools/skill-map/build.mjs to rebuild the skill map.scripts/retired-names.json.gitgud update --global and gitgud apply --global. A repo edit does not reach installed copies until you do.yesh-router, run python3 scripts/build-mode.py and restart Claude Code. pi picks up the change on its own.config/AGENTS.md is the host instructions template. python3 scripts/audit-sessions.py reports how recent Claude Code and pi sessions used powerball.
research and writing-for-agents are adapted from mattpocock/skills (MIT). The show-me PR sections draw on its pr skill and on Dex Horthy's humanlayer/skills. The router and its playbooks draw on the Cursor pstack plugin (MIT), and the formal branch of verification-skill on its create-formal-verification-skill (0.15.27). The forward implementation first principle draws on Vuk97/forward-implementation-first.
invariants| Model state in Quint, TLA+, or Lean, then break the invariants with property tests or fuzzing. |
meat-review | Review a diff, branch, or PR as a short annotated reading. |
motion-explainer | Build a narrated, timeline-driven explainer, optionally rendered to MP4. |
plan | Turn a settled approach into ordered chunks with risks and proof. |
recap | Catch up on a chat: what's done, what's left, and what needs your call. |
reflect | Pull reusable lessons out of a session. |
research | Send a question to a background agent that saves a cited note in the repo. |
sharpen | Tighten a task before starting it, then do it. |
show-me | Explain a topic with diagrams and focused HTML. Also writes visual PR descriptions. |
structure-review | Audit code structure and propose fixes backed by evidence. |
teach | Teach a subsystem or change in plain layers, built on how, with diagrams that build up. |
swarm | Run parallel agents for coverage, a solution race, or a best-of pick. |
unslop | Clean up prose, docs, PR bodies, and commits. |
verification-skill | Build or fix a project skill that drives one real app surface, or formally verifies one high-risk property. |
viz | Render a flow, DAG, call tree, or call diff from a few lines of text. |
writing-for-agents | Write or review docs agents read: skills, AGENTS.md, CLAUDE.md. |
yesh-router | Pick the method for each task and apply the principles. |