EM

e-m-albright/workbench

Developer tools

이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기

1 stars 품질 54 트렌드 22

Core: agent workbench - shared rules, skills, and tooling

개요

The portable intelligence and engineering-guidance layer for my development environment. Workbench is where I version the behavior I want Pi, Claude Code, and Codex to share: agent rules, skills, prompts, safety policy, engineering doctrine, and reusable project-health tools. It turns those canonical sources into each harness's native configuration and verifies the live result. This is a personal, opinionated repository. It optimizes one workflow rather than trying to become a general agent platform. Workbench is the agent-intelligence layer of the capability stack described canonically in STACK.md: dotfiles provisions the host and installs Workbench; private workflow layers may apply both public layers through their CLI contracts. Each layer stands alone - integration is composition and provisioning order, never cross-repository Python imports. Workbench gives me one place to answer four questions: 1.

README

원문 README의 일부입니다. 원문 보기.

Workbench

The portable intelligence and engineering-guidance layer for my development environment.

Workbench is where I version the behavior I want Pi, Claude Code, and Codex to share: agent rules, skills, prompts, safety policy, engineering doctrine, and reusable project-health tools. It turns those canonical sources into each harness’s native configuration and verifies the live result.

This is a personal, opinionated repository. It optimizes one workflow rather than trying to become a general agent platform.

Position in the Stack

Workbench is the agent-intelligence layer of the capability stack described canonically in STACK.md:

dotfiles   host foundation and machine capabilities
    ↓
workbench  reusable agent intelligence and engineering standards
    ↓
private workflow layers

dotfiles provisions the host and installs Workbench; private workflow layers may apply both public layers through their CLI contracts. Each layer stands alone - integration is composition and provisioning order, never cross-repository Python imports.

What It Does

Workbench gives me one place to answer four questions:

  1. How should my coding agents behave? Shared rules, safety boundaries, reusable skills, and review guidance live under agents/.
  2. How do those instructions reach each harness? workbench sync translates and deploys the canonical sources into Pi, Claude Code, and Codex configuration.
  3. Has live configuration drifted? workbench drift compares the deployed files and installed plugins directly with the repository.
  4. What engineering judgment should carry between projects? The playbook, health kit, and review skills preserve reusable decisions without coupling them to a particular codebase.
                    canonical sources
              agents/   playbook/   health/
                           │
                  workbench sync all
                           │
          ┌───────────────┼───────────────┐
          │               │               │
         Pi          Claude Code         Codex
  rules, settings,   rules, settings,   rules, TOML,
  skills, extensions skills, plugins    skills, plugins
          │               │               │
          └───────────────┼───────────────┘
                          │
                workbench drift all
                    live drift report

The repository is both the source material and the deployment contract. It does not store a snapshot of the machine and compare against that stale observation.

Ownership Boundaries

Concern Owner
Agent rules, skills, prompts, MCP declarations, hooks, and permissions Workbench
Engineering doctrine, stack guidance, review skills, and portable health tooling Workbench
GitHub에서 전체 README 보기

추천 도구

다른 키워드를 입력하거나 필터를 제거해 보세요.

설치

npx skillfish add e-m-albright/workbench
MCP 초보자라면? mcpskill.org 가이드부터 시작하세요 →