613건 · 관련도순
AutoResearch-inspired self-evolution loop for ANY Claude Code skill. Finds flaws, fixes them, benchmarks against a diverse prompt pool (anti-overfitting), and uses blind A/B judging. Fully automated — no human input needed during the loop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adversarial dialectic tool inspired by GAN. Alternates between Generator (creative advocate) and Discriminator (adversarial critic). Supports forced role selection (g/d), intensity modes (hard/soft), and multi-language output. Use for stress-testing ideas, business plans, code, and spec designs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Architect systems like Fable 5 — deep understanding before design, modular thinking, iterative refinement. Use this skill when starting a new project, designing system architecture, planning a major refactor, or making technology decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured step-by-step problem decomposition and iterative analysis; explicit request only, never for regular coding tasks, and at most once per task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deep analysis of articles/long-form via thinking frameworks (SCQA, mental models, inversion) — 'analyze article', 'deep dive', 'extract insights', URL/text wanting depth not summary.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing PRs/diffs/branches/documents for .NET quality, correctness, performance, security, data access, messaging, and observability. Includes adversarial critical-thinking mode for skeptical/cynical review requests. Keywords: code review, review PR, review diff, critical review, cynical review, adversarial review, production readiness, low GC, AOT, security review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lateral-thinking playbook that always returns a five-tier strategy portfolio (Quick Win through Moonshot). Use when you need options, alternatives, or trade-offs; when progress is stalled or failing repeatedly; or when you ask to think creatively, reframe constraints, and choose a strategic path before execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Construa, depure e otimize aplicativos com Claude API / SDK Anthropic. Aplicativos construídos com esta skill devem incluir cache de prompt. Também lida com migração de código Claude API existente entre versões de modelo (4.5 → 4.6, 4.6 → 4.7, substituições de modelo descontinuado). TRIGGER quando: código importa `anthropic`/`@anthropic-ai/sdk`; usuário solicita Claude API, SDK Anthropic ou Managed Agents; usuário adiciona/modifica/afina um recurso Claude (cache, thinking, compaction, tool use, batch, files, citations, memory) ou modelo (Opus/Sonnet/Haiku) em um arquivo; dúvidas sobre prompt caching / cache hit rate em um projeto SDK Anthropic. SKIP: arquivo importa `openai`/SDK de outro provedor, nome de arquivo como `*-openai.py`/`*-generic.py`, código agnóstico de provedor, programação geral/ML.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guia completo para usar Claude Code de forma eficaz. Inclui templates de configuração, estratégias de prompting com keywords "Thinking", técnicas de debugging e melhores práticas para interagir com o agente.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GStack canary method for staged release thinking, smoke gates, rollout checks, and rollback signals before or after deployment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when a plan needs hard scrutiny, a board meeting is coming, a painful decision has been avoided, or a failure needs an honest post-mortem.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Competitive positioning diagnostic — figures out where you actually stand relative to competitors and whether that position is defensible. Use this skill when someone needs to understand their real competitive position (not the one on the slide deck), when a new competitor has entered the market, when customers are switching and nobody can explain why, when pricing power is eroding, when a strategic investment depends on knowing whether the moat is real, or when leadership says "we're differentiated" but can't explain how. Draws on Playing to Win, Porter's generic strategies, and Blue Ocean thinking — applied as diagnosis, not planning. Based on practice by Eterdis (eterdis.com).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The Eterdis Strategy Diagnostic — an AI-guided conversation that helps leadership teams understand their strategic situation before committing to a direction. This is the entry point skill. It runs an open-ended discovery conversation, detects which strategic frameworks are most relevant, and produces a strategy-ready brief. Use this skill when someone asks for a general strategic assessment, when they don't know which framework they need, when they want to "figure out where we stand," or when they're preparing for a strategy engagement. This skill orchestrates other Eterdis skills — it does not replace them. Triggers on: "help me think through our strategy," "where should we start," "we need to figure out what's going on," "strategic health check," "prepare for a strategy review," or any open-ended request for strategic thinking. Based on 20 years of consulting practice by Eterdis (eterdis.com).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stress-test plans before committing by imagining they've already failed. Three modes. Diagnostic mode runs a full pre-mortem session — vivid failure scene-setting, six failure categories, the monkey test, and concrete plan adjustments. Review mode checks previous findings monthly for changed probabilities and new failure modes. Alert Triggers mode defines and monitors early warning signals across four trigger categories. Use before any major commitment — strategy, investment, product launch, partnership — or regularly to keep assumptions honest. The planning fallacy is real. The spreadsheet looked great so everyone stopped thinking. This is the antidote. Based on practice by Eterdis (eterdis.com).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when work needs deeper thinking, less generic output, repo evidence, tradeoffs, monitoring signals, or stronger quality discipline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Start a working doc — a drafting space where spec-level and implementation thinking co-exist before splitting into specs, plan, and test cases
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.