Results for “reflex”

Pauses mid-conversation to reassess direction, assumptions, and bias, then recommends whether to continue, pivot, or pause.

週次リフレクション（1週の振り返りサマリ）を生成するスキル。直近の完了週の日記から4要素（作業傾向/思考癖/繰り返す課題/CCアドバイス）を生成し、_INDEX気づきTop3はユーザー承認後に反映。ユーザーが「リフレクション」「今週の振り返り」「思考癖まとめて」と言った時、または /reflection を呼んだ時に発動。resume-sessionの検知提案からも起動される。

Execute self-learning system that captures corrections during sessions and syncs them to CLAUDE.md. Use when discussing learnings, corrections, or when the user mentions remembering something. Trigger with phrases like "remember this", "don't forget", "use X not Y", or "actually...".

Select alternative execution paths when a plan step fails — branch on outcomes instead of blind retry. Load when a structured plan step fails, an unexpected observation arrives, or the user asks what to try next after an error. Also triggers on "try another approach", "route around this failure", "replan on failure", "if X fails try Y", or outcome-based branching during multi-step work. Pairs with structured-planning and debug-and-fix. Does not replace root-cause debugging — adds plan-level path selection.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Use for bugs, unexpected behavior, regressions, or failing tests you did not write.

Makes AI responses feel more human by adding an inner dialogue loop that reflects on and revises the initial instinctive reply.

当意识到当前行为模式可能导致不理想的未来，需要一种具体方法来激发改变动力时

Retro

Facilitate a structured sprint retrospective to surface insights and produce actionable improvements with owners and deadlines.

Runs a disciplined debugging loop for hard bugs and performance regressions, covering reproduction, hypothesis testing, instrumentation, fixing, and regression testing.

Extrai conhecimento de negócio implícito do projeto legado — regras de negócio, ADRs retroativos via Git, máquinas de estado e matriz de permissões. Use na fase de interpretação de uma análise de engenharia reversa.

当感到生活失控、注意力分散，需要系统性重获专注力时

韩寒（作家车手）认知与表达框架（压缩蒸馏）：反套路叙事、冷幽默、公共发言锋利… 触发：三重门赛车 等。不伪造赛事实；尊重他人

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

A reflective tarot draw for emotional support (presence-first, non-clinical, non-predictive).

Multi-perspective dialectical reasoning with cross-evaluative synthesis. Spawns parallel evaluative lenses (STRUCTURAL, EVIDENTIAL, SCOPE, ADVERSARIAL, PRAGMATIC) that critique thesis AND critique each other's critiques, producing N-squared evaluation matrix before recursive aggregation. Triggers on /critique, /dialectic, /crosseval, requests for thorough analysis, stress-testing arguments, or finding weaknesses. Implements Hegelian refinement enhanced with interleaved multi-domain evaluation and convergent synthesis.

Performance — Forge Skill

Runs a disciplined diagnosis loop for hard bugs and performance regressions, from reproduction through hypothesis testing, instrumentation, fixing, and regression testing.

Refactors a class toward the Single Responsibility Principle by identifying responsibilities, grouping cohesive behavior, and extracting focused classes.

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.

Runs a full retrospective and dev cycle analysis, chaining /recall and /new-features to reconstruct what went wrong, extract lessons learned, identify rework patterns, and synthesize feature ideas from the findings.

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.

Understand through recursive decomposition and modular reconstruction of simple operations to reproduce emergent complexity. Use this skill whenever reasoning is required. Framework for [[#parse|parsing]], [[#branch|branching]], [[#reduce|reducing]], [[#ground|grounding]] and [[#emit|emitting]]. Employs metacognitive reasoning epistemology, leveraging first principles through recursive decomposition[^1]. Self-referential and scale-invariant.

Reproduces failures, gathers evidence, tests hypotheses, fixes root causes, and adds regression coverage.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

当遭遇挫折、失败或结果不如预期时，用于将负面经验转化为成长燃料

Remix patterns including loaders, actions, nested routing, progressive enhancement, and deployment strategies.