everyinc
- 34 skills
- 0 followers
- 1 week ago last updated
- ▌ Ce Pov · everyinc bundleJudge a supplied subject against the project's evidence and constraints, returning a supported position, tradeoffs, and conditions. 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. Use ce-bakeoff to develop competing solutions to a defined brief, ce-ideate to explore opportunities, or ce-brainstorm to establish goals.
- ▌ Ce Explain · everyinc bundleExplain how something works and why it has its current shape, grounding behavior in evidence and separating documented rationale from inference. Use when understanding a system, change, idea, or recent work is needed for learning or further work, including deeper teaching explanations. Use ce-pov for a judgment or recommendation.
- ▌ Ce Babysit Pr · everyinc bundleBabysits 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 Commit Push Pr · everyinc bundleCommit, 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 Prototype · everyinc bundleBuild a throwaway prototype to answer how something should work, feel, or read. Use when committing the wrong answer would be expensive to unravel and a cheap sketch cannot settle it. Not a rough visual probe during brainstorming, not for deciding what to build, not polishing a feature that already works, not implementing the real thing.
- ▌ Ce Bakeoff · everyinc bundleDevelop independent competing solutions to a defined brief, compare them, and synthesize a winning approach. Use when choosing well requires developing alternatives beyond their current form. Use ce-pov to judge developed material and ce-ideate to discover opportunities.
- ▌ Ce Noslop · everyinc bundleRewrite, check, or draft prose so it reads plainly on the first read and carries no AI writing patterns, keeping every fact the source states. Use when the user asks to make text plainer, humanize it, remove AI-sounding writing, or check whether it reads as machine-written; when a draft is wanted from supplied content; and when a skill about to compose a PR body, plan, finding, or reply names this skill. Use ce-promote for channel-specific marketing copy.
- ▌ Lfg · everyinc bundleRun the full autonomous shipping pipeline end-to-end, hands-off with no check-ins. Use only when the user explicitly asks to build or ship something autonomously all the way to an open PR, or invokes lfg directly — it pushes and opens a PR without stopping. Not for in-the-loop work where the user reviews each step: use ce-plan, ce-work, ce-debug, or ce-commit-push-pr instead.
- ▌ Ce Simplify Code · everyinc bundleSimplify recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use for tidy/refactor passes; use ce-debug for bugs.
- ▌ Ce Product Pulse · everyinc bundleGenerate time-windowed product pulse reports from configured signals.
- ▌ Ce Handoff · everyincCreate 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 Code Review · everyinc bundleStructured code review for bugs, regressions, tests, and standards. Use before PRs or when asked for review; report-only by default, with explicit local apply available for user-directed fix workflows.
- ▌ Ce Brainstorm · everyinc bundleExplore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning. Also use when the user must scope work in territory they say they do not know ("I know nothing about X but need to...") or asks for a blindspot pass — mapping the decision surface before questions begin. Not for executing already-specified work — direct implementation, debugging, or code review where no product scope is left to decide. Not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or platform — brainstorming scopes what to build, not whether to commit to an outside option.
- ▌
- ▌ Ce Retune · everyinc bundleRetune 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 Sweep · everyinc bundleSweep 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:headless for scheduled runs.
- ▌ Ce Doc Review · everyinc bundleReview requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.
- ▌
- ▌ Ce Proof · everyincPublish, 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 Optimize · everyinc bundleRun metric-driven optimization loops. Use when improving measurable outcomes such as search relevance, clustering quality, build performance, prompt quality, or scored behavior through experiments.
- ▌ Ce Worktree · everyincSet up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch/PR/commit to work on it in isolation. Use when starting isolated work or isolating an existing ref; detects existing isolation first.
- ▌ Ce Work · everyinc bundleExecute 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. Standalone use owns the shipping tail; outer orchestrators pass `mode:return-to-caller [implementation_engine:<compact-json>] [implementation_run:<safe-id>] <plan path>` for implementation, recovery, and local verification only.
- ▌ Ce Compound · everyinc bundleDocument a recently solved problem as a durable repo learning, or capture project vocabulary in CONCEPTS.md. Use when capturing a learning after work.
- ▌ Ce Riffrec Feedback Analysis · everyinc bundleAnalyze Riffrec feedback captures from bundles or standalone recordings. Always load for `riffrec-*.zip`, `session.json` + `events.json` + `recording.webm` + `voice.webm` bundles, `.mp4`/`.mov`/`.webm` videos, `.m4a`/`.mp3`/`.wav` audio, or capture/share requests.
- ▌ Ce Resolve Pr Feedback · everyinc bundleResolve PR review feedback. Use when addressing review comments, resolving review threads, or fixing code-review feedback.
- ▌ Ce Compound Refresh · everyinc bundleRefresh 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 Polish · everyinc bundleStart the dev server, inspect the feature in browser, and iterate on polish.
- ▌ Ce Commit · everyincCreate a git commit with a clear, value-communication message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate, value-communicating message.
- ▌
- ▌ Ce Strategy · everyinc bundleCreate or update STRATEGY.md. Use when starting a product, changing direction or roadmap, or when ce-ideate, ce-brainstorm, or ce-plan need upstream product grounding.
- ▌
- ▌ Ce Debug · everyinc bundleDiagnosis loop for bugs and failing behavior. Use for errors, stack traces, regressions, failed tests, issue-tracker bugs, stuck investigations after failed fixes, or asks to debug/fix a bug.
- ▌ Ce Ideate · everyinc bundleGenerate and evaluate grounded ideas. Use when the user asks for ideas, improvements, surprising options, or AI-generated directions before choosing one to develop; use ce-brainstorm to refine the user's own idea.
- ▌ Ce Dogfood · everyinc bundleHands-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.