CommunityCodierung & Entwicklunggithub.com

everyinc/ce-compound

Dokumentiere ein kürzlich gelöstes Problem, um das Wissen deines Teams zu bündeln, oder aktualisiere CONCEPTS.md – das gemeinsame Domänenvokabular des Projekts.

Was ist ce-compound?

Diese Fertigkeit hilft Entwicklern und KI-Agenten, wertvolles Wissen aus der täglichen Arbeit systematisch festzuhalten. Wenn du ein Problem gelöst oder eine neue Erkenntnis gewonnen hast, erstellt `everyinc/ce-compound` automatisch strukturierte Notizen oder aktualisiert die zentrale Wissensdatei `CONCEPTS.md`. Dadurch entsteht ein wachsendes, gemeinsames Domänenvokabular für das gesamte Team. Die Fertigkeit ist plattformunabhängig und funktioniert mit jedem modernen KI-Agenten, indem sie Markdown-Dateien im Projektverzeichnis erzeugt oder erweitert. Sie reduziert den Aufwand für Wissensmanagement auf ein Minimum und verhindert, dass Lösungen mehrfach erarbeitet werden müssen. Der Workflow ist einfach: Nach der Lösung eines Problems genügt ein Trigger-Befehl, und der Agent extrahiert die Kerninformationen in ein standardisiertes Format.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/everyinc/compound-engineering-plugin/tree/main/skills/ce-compound

Installed? Explore more Codierung & Entwicklung skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Original anzeigen→Alle Skills durchsuchen

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Dokumentation

Was macht ce-compound?

Dokumentiere ein kürzlich gelöstes Problem, um das Wissen deines Teams zu bündeln, oder aktualisiere CONCEPTS.md – das gemeinsame Domänenvokabular des Projekts.

Verwendung

  • Problem dokumentieren: Nachdem du ein Problem gelöst hast, verwende den Befehl, um die Lösung in einer strukturierten Notiz festzuhalten.
  • CONCEPTS.md aktualisieren: Erweitere die zentrale Wissensdatei um neue Begriffe, Definitionen und Konzepte aus dem aktuellen Kontext.

Funktionsweise

  1. Der Agent analysiert den aktuellen Chat- oder Arbeitskontext.
  2. Er identifiziert kürzlich gelöste Probleme oder neu entdeckte Konzepte.
  3. Er generiert eine Markdown-Datei mit standardisierten Abschnitten (Problem, Lösung, Erkenntnisse) oder hängt einen Eintrag an CONCEPTS.md an.
  4. Die Ausgabe erfolgt als lokale Datei im Projektverzeichnis.

Beispiel

# Problem: Fehlerhafte API-Authentifizierung

## Problembeschreibung
Die OAuth2-Tokenvalidierung schlug fehl beim Aufruf des `/user`-Endpunkts.

## Lösung
Der Fehler lag in der falschen Reihenfolge der Middleware: Die Tokenvalidierung muss vor der Routenverarbeitung erfolgen.

## Erkenntnisse
- Middleware-Reihenfolge ist kritisch für korrekte Authentifizierung.
- Debugging mit `curl -v` zeigte den fehlenden Authorization-Header im zweiten Request.

Konfiguration

Keine spezielle Konfiguration erforderlich. Die Fertigkeit arbeitet mit jedem Standard-Markdown-Projekt.

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-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/.

everyinc/ce-proof

Publish, view, comment on, and edit markdown via Proof (proofeditor.ai) — create a shareable doc, read a shared doc, and make comment/suggestion/block edits over its API. Use when the user says "view this in proof", "share to proof", "publish to proof", or wants a shareable markdown surface for a spec, plan, or draft, including publish handoffs from ce-brainstorm, ce-ideate, or ce-plan. Do not trigger on "proof" meaning evidence, math proofs, proof-of-concept, or "proofread this".

Verwandte Skills

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 Codierung & Entwicklung skills