AgiFlow/doompi

AgiFlow 프로필

최근 기록된 소스 활동: 2026년 10월 8일 03:20

SkillsMP 카탈로그 업데이트: 2026년 10월 17일 00:09

수집된 skills: 40

GitHub 스타: 42
GitHub 포크: 4

저장소 README

README 원본 파일: README.md

README 원본 보기

README 전체 펼치기

<p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="packages/cli/doompi/assets/logo.png"> <source media="(prefers-color-scheme: light)" srcset="packages/cli/doompi/assets/logo-light.png"> <img alt="DoomPi" src="packages/cli/doompi/assets/logo-light.png" width="440"> </picture> </p> # DoomPi **A coding agent that loads only the skills and tools you name.** > It begins with one useful MCP server. Then another. Soon the agent fixing a heading > wakes up with database tools, browser controls, and their small novel of schemas. This > is our config. DoomPi is an opinionated, composable distribution of [Pi](https://github.com/earendil-works/pi). It is closer in spirit to Spacemacs, Doom Emacs, or a curated Neovim setup than to a single plugin. It is tailored for people whose agents have too many skills and tools. It turns extensions, skills, MCP servers, and system prompts into config instead of background noise. ![DoomPi terminal interface showing tasks, Plan mode, and the Leader menu](packages/cli/doompi/assets/doompi-tui.png) Plugin systems often rely on model-driven discovery to decide what context to load. Codex, for example, selects plugins from their descriptions and then loads their skills, but relevant skills do not always load reliably. DoomPi makes the session composition explicit. Pick a major mode and some domains; add a profile if you want one. Four YAML files decide what loads; `doompi --explain` tells you what got in, why, and what it costs before launch. It borrows its shape from [Doom Emacs Core](https://github.com/doomemacs/core): quick to start, close to Pi, opinionated where defaults help, and easy to pull apart when they do not. Use it as-is, build your own config on top, or raid it for parts. ## Contents | Guide | What it covers | | -------------------------------------------------------------- | ---------------------------------------------------------------------------------- | | [Getting started](docs/getting-started.md) | Installation, requirements, DPI, sync storage, and Pi registration | | [Concepts](docs/concepts.md) | Major modes, minor modes, domains, profiles, and context costs | | [Automation](docs/automation.md) | Workflows, native plugin examples, and loops | | [Features](docs/features.md) | Fixed host packages, selectable features, and capability contracts | | [Configuration](docs/configuration.md) | The four YAML files, field-specific merge rules, examples, and matrix checks | | [Composition and bundling](docs/bundling.md) | How configuration becomes TUI runtime bundles and synchronized generations | | [Security model](docs/securities.md) | Threat model, remote-access boundaries, containment, and known limits | | [Trust and data boundaries](docs/trust-and-data-boundaries.md) | Executable inputs, credentials, model calls, voice, native binaries, and telemetry | | [Observability](docs/observability.md) | Session metrics, local log storage, trace lookup, and telemetry controls | | [CLI reference](docs/cli-reference.md) | Commands, options, exact effects, and direct package use | | [Architecture](docs/architecture.md) | Package composition, lifecycle ownership, transitions, and isolation | | [Extension lifecycles](docs/lifecycles.md) | Mount stages, rollback, host differences, scopes, composition, and failure policy | | [Extension layout](docs/extension-layout.md) | Folder-based authoring: scopes, sides, surfaces, filename grammar, and transports | | [Development](docs/development.md) | Workspace commands and maintainer release flow | | [Contributing](CONTRIBUTING.md) | Local setup, repository boundaries, checks, commits, and pull requests | ## Install ```bash npm install -g @agimon-ai/doompi ``` The package pins and installs the upstream Pi version used by `dpi`. The root package contains the fixed host foundation only. Feature packages are selected by `.doom/modes.yaml` and installed into the consumer repository when they are first needed. See [Getting started](docs/getting-started.md) for the full setup and sync behavior. ## Status and requirements DoomPi is alpha software. Configuration and package boundaries may still change between alpha releases. - Node.js 22.19.0 or newer for the published package - Node.js 22.22.1 or newer when contributing from this workspace - macOS or Linux on arm64 or x64 for the bundled Runner backend - Pi 1.0.0 and Pi TUI 1.0.0 for packages that declare them as peer requirements ## Try DoomPi without replacing your Pi setup `dpi` is the comparison runner. Use it to try DoomPi beside your current `pi` customization before registering anything in Pi's settings: ```bash dpi init dpi sync dpi ``` `dpi init` creates this repository's `.doom` configuration. `dpi sync` installs required configured packages and writes synchronized state without persisting a Pi settings overlay. `dpi` runs the pinned Pi version with that in-memory overlay. Your existing `pi` setup remains available for comparison. See [Getting started](docs/getting-started.md) for worktree storage, permanent registration, and per-run matrix flags. ## Philosophy An agent does not need every tool for every job. DoomPi separates the base session from the things you switch on for a while: modes choose behavior, domains choose subject matter, and profiles choose a point of view. ### Major and minor modes A major mode is the preset. It names the extension layers that should run together. Minor modes are batteries-included switches inside the session. They stack freely and keep their tools and skills out of context until turned on. ### Domains A domain is a named group of Codex or Claude Code plugins. It carries the skills and MCP servers for one kind of work, and `/domains` switches it while the session is running. ### Profile A profile can supply a narrative, brand rules, or a different voice. It is optional; no profile is a perfectly good profile. See [Concepts](docs/concepts.md) for discovery, caching, merge behavior, and examples. ## Why scope the session Every tool schema and skill name consumes context and gives the model another possible choice. A smaller composition uses fewer tokens before work starts and reduces the number of irrelevant tools the model can select. Workflow jobs can choose their own composition instead of inheriting the previous job's toolbox. ### Copilot Press `SPC` on an empty draft to open a map of the commands available in the current composition. When the keyboard is the wrong tool, autonomous Voice mode can keep the conversation going. ### Autopilot Loop and Workflow keep work moving when you are not present. Together they can dispatch structured jobs from one live session. See [Automation](docs/automation.md) for workflow syntax, tracked examples, and loop behavior. ## Features DoomPi is a distribution, not one giant extension. Each package owns one job; shared TUI, Cordis services, and session contracts make them behave like one. - **Foundation and interface:** configuration, domains, hashline tools, the Leader key, logs, and telemetry. - **Coordinated work:** agent teams, persistent tasks, supervised commands, and staged compaction. - **Context and access:** Help mode, scoped MCP access, structured questions, and operational metrics. - **Modes and automation:** Plan, Loop, Goal, Workflow, and Voice modes. See [Features](docs/features.md) for the complete package catalog and behavior of each feature. ## Configuration DoomPi reads four configuration files: - `config.yaml` defines runtime settings such as trust, editor, planning, and voice behavior. - `modes.yaml` defines default packages, extension layers, and major modes. - `domains.yaml` catalogs plugins and sets session access. - `profiles.yaml` supplies persona files and environment defaults. Personal defaults live in `~/.pi/.doom/`; repository overrides live in `<repository>/.doom/`. See [Configuration](docs/configuration.md) for resolution rules, complete examples, and matrix checks. ## Security and trust DoomPi executes the extensions, remote Git/npm plugins, hooks, MCP stdio commands, workflows, and shell commands you configure. Treat them as trusted executable code. See the [Security model](docs/securities.md) for the threat model, what guards the cockpit once it is reachable from a phone, and what is deliberately left open. See [Trust and data boundaries](docs/trust-and-data-boundaries.md) for process privileges, credentials, model calls, voice, and telemetry behavior. ## CLI reference | Command | Effect | | --------------------- | ------------------------------------------------------------------------------------------------- | | `dpi init` | Creates missing repository `.doom` files without changing Pi settings. | | `dpi sync` | Installs required packages and builds synchronized state without persisting its settings overlay. | | `dpi` | Runs the pinned Pi version with an in-memory DoomPi settings overlay. | | `doompi init` | Seeds personal config, writes integration resources, and registers them in Pi user settings. | | `doompi sync` | Rebuilds synchronized state using the integration created by `doompi init`. | | `doompi sync --check` | Checks drift and exits non-zero without writing when state is stale. | | `doompi doctor` | Reports configuration, package, sync-state, and drift problems without changing anything. | | `doompi --explain` | Prints the resolved matrix and estimated prompt cost without launching Pi. | See the [CLI reference](docs/cli-reference.md) for more commands, options, and direct-use guidance. ## Troubleshooting and direct use See [Troubleshooting and direct use](docs/cli-reference.md#troubleshooting-and-direct-use) for sync drift, Runner fallbacks, headless sessions, and direct package installation. ## Architecture See [Architecture](docs/architecture.md) for standard Pi package composition, canonical fingerprints, transition classification, synchronized bundles, shared-host Cordis lifecycle ownership, and parent/child isolation. ## Development See [Contributing](CONTRIBUTING.md) for local setup, repository boundaries, verification, commits, and pull requests. See [Development](docs/development.md) for the maintainer release order. DoomPi is maintained by [Agimon](https://agimon.ai/about). ## License [MIT](LICENSE)

저장소 README를 불러오는 중…

이 저장소의 skills

네트워크·컴퓨터 시스템 관리자 기타 컴퓨터 관련 직업 소프트웨어 개발자 소프트웨어 품질 보증 분석가·테스터

직업 카테고리 8개 · 53% 분류됨

기타 컴퓨터 관련 직업

Use @agimon-ai/doompi-model-guidance: per-model system prompt guidance, layered across global and repository scope

원문 언어: 영어

2026-09-13

소프트웨어 품질 보증 분석가·테스터

Review a code change for concrete defects, regressions, missing tests, and contract violations. Use when the user asks for code review, diff review, or risk assessment, not as a general implementation workflow.

원문 언어: 영어

2026-08-22

doompi-testing

소프트웨어 품질 보증 분석가·테스터

Design, add, and run focused tests for repository behavior. Use for test implementation, regression coverage, verification, or diagnosing a failing test, not for a review-only request.

원문 언어: 영어

2026-08-22

수집된 skill 40개 중 40개를 표시합니다.

AI 어시스턴트로 설치

이 프롬프트를 복사해 사용 중인 AI 어시스턴트에 입력하세요.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/AgiFlow/doompi.