everyinc
GitHub33 skills
ce-brainstormeveryinc3.6KExplore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.ce-planeveryinc3.5KCreate structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.ce-code-revieweveryinc3.4KReview a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.ce-compoundeveryinc3.4KDocument a solved problem as a durable repo learning. Use when verified work produced non-obvious reasoning absent from its final code, tests, or existing docs; avoid routine fixes whose artifacts already explain the lesson.ce-doc-revieweveryinc3.4KReview requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.ce-workeveryinc3.3KExecute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without the shipping tail.lfgeveryinc3.3KTake a request all the way to done, hands-off, through the right Compound Engineering skills. A code change ends as an open pull request, pushed without stopping. Use only when the user explicitly asks for autonomous end-to-end work or invokes lfg directly. Use ce-plan, ce-work, ce-debug, or ce-commit-push-pr for work the user reviews step by step.ce-debugeveryinc3.2KDiagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.ce-commiteveryinc3.2KCreate a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.ce-simplify-codeeveryinc3.2KSimplify settled, recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use after implementation and before review; use ce-debug for bugs.ce-commit-push-preveryinc3.1KCommit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.ce-ideateeveryinc3.1KGenerate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).ce-compound-refresheveryinc3.1KRefresh the repo's captured learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless the learnings store is explicit.ce-setupeveryinc3.1KCheck Compound Engineering health and repo-local config, or scaffold a Compound Pack with `pack:<id>`.ce-optimizeeveryinc3.1KOptimize a named target with a measured loop: attribute a workload's cost, or score variants and keep winners. Use when a working system's metric should move and the winning change is not already known. Use ce-debug when the job is diagnosis; use ce-work when the change is already known.ce-resolve-pr-feedbackeveryinc3KResolve PR review feedback. Use when addressing feedback already left on a PR. Not for reviewing the code before feedback exists; that is ce-code-review.ce-worktreeeveryinc2.9KSet up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch, PR, or commit. Use when starting isolated work or isolating an existing ref.ce-test-browsereveryinc2.9KRun browser tests for pages affected by the current branch or PR. Use when asked to run or check browser tests for the current change.ce-proofeveryinc2.9KPublish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.ce-strategyeveryinc2.8KCreate or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.ce-test-xcodeeveryinc2.8KTest iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.ce-product-pulseeveryinc2.8KGenerate time-windowed product pulse reports from configured signals.ce-riffrec-feedback-analysiseveryinc2.7KAnalyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet.charlieeveryincYour AI CFO for bootstrapped startups, named after Charlie Munger who embodied the principle that capital discipline is a competitive advantage. Provides financial frameworks for cash management, runway calculations, unit economics (LTV:CAC), capital allocation, hiring ROI, burn rate analysis, working capital optimization, and forecasting. Use for questions like "should we make this hire?", "how much runway do we need?", "what metrics should I track?", "how do I forecast revenue?", or any stratece-babysit-preveryincBabysits an open GitHub PR until merge-ready. Use when asked to watch a PR over time — not for one-shot comment resolution or one CI failure. GitHub (incl. Enterprise) only.ce-dogfoodeveryincHands-off, diff-scoped browser QA of the active branch: maps user flows, drives a real browser, autonomously fixes small breakages with regression tests and commits, judges experience against product personas, and writes a durable dogfood report. Manual invocation only.ce-explaineveryincExplain how and why something has its current shape, or what happened over a window of work, grounded in evidence. Use when the user asks for an explanation. Use ce-pov for a judgment or recommendation.ce-handoffeveryincCreate a session handoff for another agent, or resume, find, and read any user-selected continuity source. Use when work or conversation must continue without access to the current session history.ce-polisheveryincPolish a working feature through user-directed live browser feedback. Use when a functional feature needs focused UX refinement before shipping.ce-poveveryincJudge a supplied subject against the project's evidence and constraints. Use when assessing an external-adoption question, a holistic take on a document, or a supplied approach set. Use for an oracle panel to consult other models and reconcile their opinions. Use ce-explain for understanding and ce-doc-review for findings review.ce-promoteeveryincDraft launch or promotion copy for a shipped feature.ce-retuneeveryincRetune a skill corpus for a new model, measurement-first: mine the run archive for a baseline, establish a noise floor, audit the corpus adversarially, then cut in measured passes until a pre-registered bar clears. Requires a benchmark harness that can A/B two builds of the corpus; refuses without one.ce-sweepeveryincSweep configured feedback sources (Slack, GitHub Issues; email experimental) for new items: acknowledge at source, analyze recordings, verify fixes merged to main, and emit an `lfg`-ready plan. First run sets up sources; supports mode:non-interactive for scheduled runs.