Results for “recurring-events”

Debug local web or Electron apps interactively using a persistent Playwright session with js_repl, enabling fast iterative UI debugging and visual QA.

Handle .NET MAUI application state transitions, Window lifecycle events, and state preservation across backgrounding and resume cycles.

Advanced Tauri event patterns for bidirectional communication, streaming data, window-to-window messaging, and custom event handling

Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

通用多轮迭代改进：对任意研究制品反复调用 /review → 解析反馈 → 修复 → 更新 wiki，直到达标

Restore working context saved earlier by /context-save. Loads the most recent saved state (across all branches by default) so you can pick up where you left off — even across Conductor workspace handoffs. Use when asked to "resume", "restore context", "where was I", or "pick up where I left off". Pair with /context-save. Formerly /checkpoint resume — renamed because Claude Code treats /checkpoint as a native rewind alias in current environments. (gstack)

Start an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.

セッション再開時に最新5件のhandoffを読み込み文脈を復元するスキル。「おはよう」「こんにちは」「こんばんは」「再開」「restart」または /resume-session を呼んだ時にトリガーする。new-session の対（読込側）。

Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of sprints, projects, or milestones to reflect and improve team practices.

Recover session state from git, plans, and open PRs, then continue from the last completed phase without repeating work

Legacy/migration guidance for v1 Schedule entities. In v2, define recurring cadences as Binding(type=time-window) records with recurrence conditions instead of creating new Schedule records.

Recursive self-improving holon λ(ο,Κ,Σ).τ' for knowledge compounding and schema evolution. USE WHEN learning, improving, optimizing, assessing, reflecting, debugging, synthesizing, or refining—whether human, AI, or organizational. Triggers on /learn, /compound, /improve, /refine, /optimize, /assess, /reflect, "lessons learned", "best practices", "continuous improvement". Preserves Κ-monotonicity, η≥4, homoiconicity.

Progressively refines context retrieval in multi-agent workflows to solve the subagent context problem.

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.