Surface Claude's assumptions about a phase approach before planning
日本語の概要は準備中です。原文の説明を表示しています。
442 件 ・ 関連度順
概要と使いどころ
Surface Claude's assumptions about a phase approach before planning
日本語の概要は準備中です。原文の説明を表示しています。
Challenge system assumptions against accumulated evidence. Triages observations and tensions, detects patterns, generates proposals. The scientific method applied to knowledge systems. Triggers on "/rethink", "review observations", "challenge assumptions", "what have I learned".
日本語の概要は準備中です。原文の説明を表示しています。
Role profile — a reviewer who is fact-seeking, bedrock-seeking, honest, and rejecting. Demands that arguments rest on small facts that cannot be wrong (not on stacked assumptions dressed up as foundation), and that deliberately-unclear concepts be quarantined — never leaked into solid layers, never mixed with each other. Catches the failure mode where designs ship after partial grounding: most of the spec researched, the design feels finished, and the unresearched remainder holds the deal-breaker. Invoke with `/pedantic <target>` (e.g. `/pedantic review this design doc`, `/pedantic review the SDK design`, `/pedantic review this PR`). Probes cover logical structure (definitions, assumptions, boundaries, contradictions, unfalsifiability, vague quantifiers, counterexamples), epistemic honesty (researchable vs. discoverable-only-by-doing), bedrock integrity (assumed-bedrock, leaked uncertainty, mixed unclarity), and design pathology (YAGNI, wrong-layer abstraction, unclear responsibility, fragmentation, over-engineering). Use when you want a hard critique of a plan, design doc, technical doc, code change, or PR description — not a copy edit, not a vibe check.
日本語の概要は準備中です。原文の説明を表示しています。
Pressure-test a business or side-hustle idea before you sink money and months into it — find the real demand, the risky assumptions, and the cheapest way to test them. Use when asked to validate my business idea, is this a good business idea, test my side hustle, or should I start this. Produces a read on the core assumptions the idea depends on, who the customer really is and whether the pain is real, the cheapest experiments to test demand before building, a rough viability check (market, competition, economics), and a go/refine/rethink call — honest, not a cheerleader.
日本語の概要は準備中です。原文の説明を表示しています。
Extract and maintain global and method-specific mathematical-model assumptions from the problem frame, active method cards, data profile, and risk probes, while leaving necessity and impact judgments to the human modeler.
日本語の概要は準備中です。原文の説明を表示しています。
Challenge a proposed solution by identifying and testing consequential assumptions. Use when the brief feels too certain or discovery reveals contradictions.
日本語の概要は準備中です。原文の説明を表示しています。
Surface beliefs, assumptions, stories, and values shaping a system. Use when deeper mental models need examining with care and evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Slow down interpretation from observation to action. Use when students or adults need to examine assumptions in conflict, dialogue, or inquiry.
日本語の概要は準備中です。原文の説明を表示しています。
Check an educational practice or task for cultural bias, WEIRD assumptions, and cross-cultural validity. Use when adapting resources for diverse contexts or questioning universal claims.
日本語の概要は準備中です。原文の説明を表示しています。
Track and document analytical assumptions and decisions. Use when making analytical choices, documenting trade-offs, ensuring transparency, or creating audit trails for analytical work.
日本語の概要は準備中です。原文の説明を表示しています。
Applies the dialectical reasoning and intellectual humility of Socrates (ancient Greek philosopher, 470-399 BCE). Use this skill whenever the user is grappling with fundamental definitions, moral dilemmas, educational approaches, self-reflection, or making high-stakes ethical decisions. Trigger this skill when encountering topics like virtue, justice, the pursuit of truth, questioning assumptions, coaching, or when the user seems overly confident in unexamined beliefs. It helps dismantle false assumptions through probing questions and redirects focus toward the "care of the soul" and objective truth over external validation or material success.
日本語の概要は準備中です。原文の説明を表示しています。
Identify and challenge implicit assumptions in plans, proposals, and technical decisions. Use when strategic-cto-mentor needs to surface hidden assumptions and wishful thinking before they become costly mistakes.
日本語の概要は準備中です。原文の説明を表示しています。
Surface beliefs, assumptions, stories, and values shaping a system. Use when deeper mental models need examining with care and evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Slow down interpretation from observation to action. Use when students or adults need to examine assumptions in conflict, dialogue, or inquiry.
日本語の概要は準備中です。原文の説明を表示しています。
Check an educational practice or task for cultural bias, WEIRD assumptions, and cross-cultural validity. Use when adapting resources for diverse contexts or questioning universal claims.
日本語の概要は準備中です。原文の説明を表示しています。
Review the insurance product design, payout terms, and pricing assumptions for viability and profitability. Use when critiquing thesis, economics, risk controls, underwriting assumptions, premium strategy, and solvency posture of this vehicle insurance protocol.
日本語の概要は準備中です。原文の説明を表示しています。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for malware configuration recovery, staged payload boundaries, beacon parameter extraction, and IOC decoding. Use when the user asks to recover a malware config, decode C2 or beacon fields, unpack staged payloads, extract bot or campaign IDs, or tie recovered config to observed protocol behavior under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
日本語の概要は準備中です。原文の説明を表示しています。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for kernel attack surface, namespace and cgroup boundaries, container isolation assumptions, syscall paths, and escape primitive verification. Use when the user asks to analyze container-to-host escape paths, kernel exploit prerequisites, namespace crossover, capability misuse, or prove whether an exploit primitive crosses the sandbox boundary. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
日本語の概要は準備中です。原文の説明を表示しています。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Kerberos delegation, SPN trust edges, S4U abuse, RBCD, constrained or unconstrained delegation, and service-ticket acceptance. Use when the user asks about constrained delegation, unconstrained delegation, RBCD, S4U, SPNs, ticket acceptance, or how a Kerberos trust edge turns into effective privilege under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
日本語の概要は準備中です。原文の説明を表示しています。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for reverse engineering, malware, DFIR, firmware, pwnable, and native exploit challenges. Use when the user asks to reverse a binary, unpack a sample, inspect a memory dump or PCAP, recover malware behavior, debug a crash, or build or verify an exploit chain under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
日本語の概要は準備中です。原文の説明を表示しています。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for AI-agent, prompt-injection, MCP or toolchain, cloud, container, CI/CD, and supply-chain challenges. Use when the user asks to analyze prompt-to-tool flows, retrieval poisoning, mounted secrets, deployment drift, runtime-vs-manifest mismatches, registry provenance, or CI-produced artifacts under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
日本語の概要は準備中です。原文の説明を表示しています。
AI intuitive exploration for approaching unknown codebases, problems, or systems without preconceptions. Adapts the Coordinate Remote Viewing protocol to AI investigation: cooldown (clear assumptions), staged data gathering (raw signals → dimensional → analytical), AOL management (separating observations from premature labels), and structured review. Use when investigating an unfamiliar codebase with unknown architecture, debugging a problem where premature hypotheses could mislead, exploring a domain with limited context, or when previous attempts have been led astray by assumptions and "beginner's mind" would be more productive.
日本語の概要は準備中です。原文の説明を表示しています。
Shakes your mental models with critical rigor, challenges assumptions, exposes blind spots, and provides multi-perspective insights as a strict thinking mentor. Deliberately breaks format conventions to stimulate genuine cognitive discomfort. Use when you want to stress-test an idea, shake your mental model, ask to challenge my assumptions, find blind spots, deepen my thinking, or request critical review with phrases like yusaburi or what do you think of this plan.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure architecture/design docs state traffic assumptions, performance budgets, resource limits, and cost risks for critical paths.
日本語の概要は準備中です。原文の説明を表示しています。