Community코딩 & 개발github.com

everyinc/compound-docs

해결된 문제를 분류된 문서로 캡처하고 YAML 머리말을 사용하여 빠르게 조회할 수 있습니다.

compound-docs란 무엇인가요?

`everyinc/compound-docs`는 개발자와 AI 에이전트가 문제 해결 과정에서 얻은 지식을 구조화된 문서로 캡처하고 쉽게 재사용할 수 있도록 설계된 스킬입니다. 각 문서는 YAML 머리말을 포함하여 제목, 태그, 카테고리, 날짜 등의 메타데이터를 정의하며, 이를 통해 빠른 검색과 필터링이 가능합니다. 이 스킬은 Claude Code, Cursor, Codex와 같은 다양한 AI 코딩 어시스턴트 플랫폼에서 사용할 수 있으며, 개발자가 과거에 해결한 문제를 다시 검색하거나 유사한 문제에 직면했을 때 신속하게 해결 방안을 찾도록 도와줍니다. `SKILL.md` 문서에 명시된 대로, 사용자는 간단한 명령어나 규칙을 통해 문서를 추가하고, 카테고리별로 정리하며, 필요할 때 YAML 필드를 기반으로 특정 문서를 검색할 수 있습니다. 이를 통해 지식 베이스를 체계적으로 관리하고, 팀 내 지식 공유를 촉진하며, 반복적인 문제 해결 시간을 크게 단축할 수 있습니다.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/everyinc/compound-engineering-plugin/tree/main/skills/compound-docs

Installed? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

원본 보기→모든 스킬 둘러보기

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

문서

compound-docs은(는) 무엇을 하나요?

해결된 문제를 분류된 문서로 캡처하고 YAML 머리말을 사용하여 빠르게 조회할 수 있습니다.

개요

이 스킬은 개발자가 문제를 해결한 후 그 과정과 해결책을 구조화된 문서로 기록할 수 있도록 합니다. 각 문서는 YAML 머리말을 포함하여 메타데이터를 정의하므로, 나중에 쉽게 검색하고 참조할 수 있습니다.

사용 방법

  1. 문서 추가

    • 해결된 문제를 설명하는 마크다운 파일을 생성합니다.
    • 파일 상단에 YAML 머리말을 추가하여 메타데이터를 정의합니다.

  2. YAML 머리말 구조

    ---
title: "문제 제목"
tags: [태그1, 태그2]
category: "카테고리명"
date: 2024-01-01
---

  3. 문서 검색

    • grep 또는 유사한 도구를 사용하여 YAML 필드나 내용을 검색할 수 있습니다.
    • 예: grep -r "tags:.*배포" docs/

지원 플랫폼

  • Claude Code
  • Cursor
  • Codex
  • 기타 AI 코딩 어시스턴트

예제

---
title: "Docker 컨테이너 네트워크 오류 해결"
tags: [docker, 네트워크, 오류]
category: 인프라
date: 2024-06-15
---

## 문제

Docker 컨테이너 간 통신이 불가능했습니다.

## 해결 방법

사용자 정의 브리지 네트워크를 생성하고 컨테이너를 연결했습니다.

주의 사항

  • YAML 머리말은 문서의 첫 줄에 위치해야 합니다.
  • 태그는 소문자로 작성하는 것을 권장합니다.
  • 카테고리는 일관된 이름을 사용하여 분류를 유지하세요.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

everyinc/ce-agent-native-architecture

Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.

everyinc/ce-agent-native-audit

Run comprehensive agent-native architecture review with scored principles

everyinc/ce-brainstorm

Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.

everyinc/ce-clean-gone-branches

Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.

everyinc/ce-code-review

Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. In interactive mode it applies safe, verified fixes and commits them when the working tree is clean (it never pushes); in mode:agent it reports only and the caller applies. Use when reviewing code changes before creating a PR.

everyinc/ce-commit

Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.

everyinc/ce-commit-push-pr

Commit, push, and open a PR with an adaptive, value-first description that scales in depth with the change. Use when the user says "commit and PR", "ship this", "create a PR", or "open a pull request". Also handles description-only flows ("write a PR description", "rewrite the PR body", "describe this PR") without committing or pushing.

everyinc/ce-compound

Document a recently solved problem to compound your team's knowledge or CONCEPTS.md, the project's shared domain vocabulary.

everyinc/ce-compound-refresh

Refresh stale learning and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, or deleting drifted ones. Use when the user asks to "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", or "consolidate overlapping docs", or when ce-compound flags an older doc as superseded. Do not trigger for general refactor, debugging, or code-review work unless the user has explicitly pointed at docs/solutions/.

everyinc/ce-debug

Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.

everyinc/ce-demo-reel

Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI features, or any work with observable behavior that benefits from visual proof. Also use when asked to add a demo, record a GIF, screenshot a feature, show what changed visually, create a demo reel, capture evidence, add proof to a PR, or create a before/after comparison.

everyinc/ce-dhh-rails-style

This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.

everyinc/ce-doc-review

Review requirements or plan documents using parallel persona agents that surface role-specific issues. Use when a requirements document or plan document exists and the user wants to improve it.

everyinc/ce-frontend-design

Build web interfaces with genuine design quality, not AI slop. Use for any frontend work - landing pages, web apps, dashboards, admin panels, components, interactive experiences. Activates for both greenfield builds and modifications to existing applications. Detects existing design systems and respects them. Covers composition, typography, color, motion, and copy. Verifies results via screenshots before declaring done.

everyinc/ce-gemini-imagegen

This skill should be used when generating and editing images using the Gemini API (Nano Banana Pro). It applies when creating images from text prompts, editing existing images, applying style transfers, generating logos with text, creating stickers, product mockups, or any image generation/manipulation task. Supports text-to-image, image editing, multi-turn refinement, and composition from multiple reference images.

everyinc/ce-ideate

Generate and critically evaluate grounded ideas about a topic. Use when asking what to improve, requesting idea generation, exploring surprising directions, or wanting the AI to proactively suggest strong options before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on X', 'surprise me', 'what would you change', or any request for AI-generated suggestions rather than refining the user's own idea.

everyinc/ce-optimize

Run metric-driven iterative optimization loops -- define a measurable goal, run parallel experiments, measure each against hard gates or LLM-as-judge scores, keep improvements, and converge on the best solution. Use when optimizing clustering quality, search relevance, build performance, prompt quality, or any measurable outcome that benefits from systematic experimentation.

everyinc/ce-plan

Create structured plans for multi-step tasks -- software features, research workflows, events, study plans, or any goal that benefits from breakdown. Also deepens existing plans with interactive sub-agent review. Use when the user says 'plan this', 'create a plan', 'how should we build', 'break this down', or when a brainstorm doc is ready for planning. Use 'deepen the plan' or 'deepening pass' for the deepening flow. For exploratory requests, prefer ce-brainstorm first.

everyinc/ce-polish-beta

[BETA] Start the dev server, open the feature in a browser, and iterate on improvements together.

everyinc/ce-product-pulse

Generate a time-windowed pulse report on what users experienced and how the product performed - usage, quality, errors, signals worth investigating. Use when the user says 'run a pulse', 'show me the pulse', 'how are we doing', 'weekly recap', 'launch-day check', or passes a time window like '24h' or '7d'. Configures via .compound-engineering/config.local.yaml and saves reports to docs/pulse-reports/.

관련 스킬

steipete/bluebubbles

Send and manage iMessages via BlueBubbles, including attachments, tapbacks, edits, replies, and groups.

community

steipete/eightctl

Control Eight Sleep pods (status, temperature, alarms, schedules).

community

steipete/blucli

BluOS CLI (blu) for discovery, playback, grouping, and volume.

community

steipete/bear-notes

Create, search, and manage Bear notes via grizzly CLI.

community

steipete/camsnap

Capture frames or clips from RTSP/ONVIF cameras.

community

steipete/gifgrep

Search GIF providers with CLI/TUI, download results, and extract stills/sheets.

community
← More 코딩 & 개발 skills