Results for “reflexivity”

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

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

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

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.

Analyze complex systems through stocks, flows, and feedback loops to find high-leverage interventions. For organizational, environmental, social, and technical systems exhibiting circular causality. NOT for linear problems or simple cause-effect chains.

Universal transformation λ(ο,K).τ with recursive self-improvement. USE WHEN routing reasoning, validating knowledge graphs, preparing CICM/ANZCA examinations, or when self-improvement of reasoning/architecture/context is required. Routes queries through R0-R3 complexity pipelines, validates topology (η≥target) and governance (KROG), emits per style (Φ), and compounds learnings into knowledge K. Triggers on complexity assessment, multi-step reasoning, examination mode, or /λ invocation.

当观察到或经历某种极端转化现象，或试图主动促成根本性观念转变时

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

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

Evaluate UI designs through an emotional resonance lens, identifying what's missing and prescribing specific changes at the copy, motion, and interaction layer.

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.

当需要建立可持续的创造节奏，将灵感转化为行动时

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.

Design adaptive layouts and interactions that work across all screen sizes and input methods.

当个人希望提升自身在职业或社会中的不可替代性，以应对环境变化和不确定性时

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.

Simulates a multi-perspective deliberation council to explore complex questions, decisions, or creative challenges from diverse thinking archetypes.

Update old notes with new connections. The backward pass that /reflect doesn't do. Revisit existing notes that predate newer related content, add connections, sharpen claims, consider splits. Triggers on "/reweave", "/reweave [note]", "update old notes", "backward connections", "revisit notes".

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

Use when the user wants more human-like AI responses — less robotic, less listy, more authentic. Triggers: 'behuman', 'be real', 'like a human', 'more human', 'less AI', 'talk like a person', 'mirror mode', 'stop being so AI', or when conversations are emotionally charged (grief, job loss, relationship advice, fear). NOT for technical questions, code generation, or factual lookups.

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.

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

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

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.

Python resilience patterns including automatic retries, exponential backoff, timeouts, and fault-tolerant decorators. Use when adding retry logic, implementing timeouts, building fault-tolerant services, or handling transient failures.

当遇到令人情绪激动或陷入僵局的情境，需要跳出固有反应模式以做出更优决策时

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

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.

Analyzes evaluation patterns across completed plans and evolves the superpowers checklists accordingly.

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.