'what' 검색 결과

Think through the consequences of consequences — not just what happens immediately, but what happens next, and next after that, across time. Load when a decision looks obviously good or obviously bad on initial read, when the user is optimising for a short-term outcome that might create a long-term problem, when unintended consequences are a concern, or when deep-thinking diagnoses a second-order frame. Triggers on "what are the downstream effects", "what happens after that", "unintended consequences", "think ahead on this", "long-term vs short-term", or "what comes after that". Based on Howard Marks second-level thinking and Farnam Street mental models. Most powerful for decisions with delayed consequences or systemic effects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Flip a problem, goal, or decision 180 degrees to find what forward thinking misses. Asks what would guarantee failure, then works backward to what must be avoided or changed. Load when the user says "invert this", "flip this problem", "what would guarantee failure", "think backward", "reverse engineer the goal", "think about it backwards", or when deep-thinking diagnoses an inversion frame. Also triggers on "what's the opposite of success here", "how would we sabotage this". Two methods: Failure Inversion and Opposite Goal. Max 2 clarifying questions before inverting. Always returns forward actions. For broader analysis, deep-thinking calls this.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[30] ANALYZE. Understand how changes impact the system — what's the core, what's affected, what depends on what. Use when planning changes, analyzing systems, debugging issues, or anytime you need to see the full picture of cause and effect. Triggers on "what's affected", "impact analysis", "dependencies", "scope mapping", or when you need to understand ripple effects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Socratic mentoring for junior developers and AI newcomers. Guides through questions, never answers. Triggers: "help me understand", "explain this code", "I'm stuck", "Im stuck", "I'm confused", "Im confused", "I don't understand", "I dont understand", "can you teach me", "teach me", "mentor me", "guide me", "what does this error mean", "why doesn't this work", "why does not this work", "I'm a beginner", "Im a beginner", "I'm learning", "Im learning", "I'm new to this", "Im new to this", "walk me through", "how does this work", "what's wrong with my code", "what's wrong", "can you break this down", "ELI5", "step by step", "where do I start", "what am I missing", "newbie here", "junior dev", "first time using", "how do I", "what is", "is this right", "not sure", "need help", "struggling", "show me", "help me debug", "best practice", "too complex", "overwhelmed", "lost", "debug this", "/socratic", "/hint", "/concept", "/pseudocode". Progressive clue systems, teaching techniques, and success metrics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

공개 전 원고를 예상 독자의 관점에서 읽고, 읽기 시작할지, 어디서 관심이 줄어드는지, 무엇을 기억하는지 확인합니다. 글을 고치지 않고 독자의 반응을 보고합니다.

• 게시물을 끝까지 읽을지 확인
• 독자가 읽기를 멈추는 지점 파악
• 수정 전후 독자 반응 비교

기술 주제를 쉬운 영어로 설명하며, 관련된 사람, 기술의 의미, 사용 장소, 필요한 이유, 사용 시점이라는 다섯 관점으로 기본 개념과 배경을 이해하도록 돕습니다.

• 낯선 기술의 기본 개념을 이해할 때
• 기술을 어디서 언제 쓰는지 알고 싶을 때
• 관련된 사람과 필요한 이유를 정리할 때

대화를 통해 claude-mem의 기록 유형과 태그를 업무나 학습에 맞게 설계합니다. 설정 설치, 활성화, 작동 확인과 선택적인 Telegram 알림을 지원합니다.

• 기억 분류를 업무나 학습에 맞출 때
• 기록할 내용과 생략할 내용을 정할 때
• 특정 기록을 Telegram으로 받을 때

Answer questions about past decisions, usual practices, and changes over time by reasoning across Hindsight memories. When information spans multiple memory banks, combine the answers and identify their sources, while acknowledging gaps or contradictions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check what was decided in previous discussions
• Review how the team usually handles a task
• Trace how a practice changed over time

Define and deploy Azure infrastructure with ARM templates and Bicep, languages for describing cloud resources in files. Get guidance on reusable modules, resource dependencies, environment parameters, and previewing deployment changes before applying them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining Azure networks and virtual machines in code
• Sharing modules across development and production
• Previewing infrastructure changes with What-If

Consult a field reference for slide JSON, the structured data behind each page. It explains where content and styling live, how edits are validated, and why a saved change may display differently or have no visible effect.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding the field that controls text color or fonts
• Investigating rejected slide edits
• Diagnosing saved changes with no visible effect

Verify Codewhale changes with checks matched to their scope and risk. Collect actual test counts, automated limit checks, and command output to show what passed, what failed, and what remains unverified.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Verify a fix before marking it complete
• Choose tests for the changed area
• Check limits and consistency rules enforced by CI

Investigate LLM application failures with Phoenix CLI by reviewing execution records, recording observations, and grouping mistakes into counted categories. Inspect datasets and experiments to identify which failure types deserve evaluation tests first.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating failures in LLM applications
• Grouping observed mistakes into failure categories
• Choosing which evaluation tests to build first

Turn work history into clear accomplishment statements for performance reviews, promotion cases, and weekly updates. Use Copilot CLI sessions, git commits, and GitHub pull requests to connect each action with its result and supporting evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recovering work accomplishments missing from a personal log
• Preparing evidence for a performance review
• Organizing achievements for a promotion case

Check Bicep infrastructure definitions before deploying to Azure. Validate syntax, preview resource changes, check deployment permissions, and produce a Markdown report of issues and recommendations using Azure CLI or Azure Developer CLI workflows.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Validating Bicep files before deployment
• Previewing resource creation, modification, and deletion
• Checking deployment permissions

Set up a sales workspace by checking connected tools and displaying deals, pending replies, meetings, and suggested actions. Analyze sent emails to match your writing style, with a starter dashboard and connection guidance when tools are missing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check connected sales tools and what each provides
• View deals, pending replies, and meetings together
• Match drafts to the style of your sent emails

Analyze paid advertising reports from CSV files or connected accounts, explain performance, and recommend changes with monthly dollar amounts. Draft ad copy and visual briefs, then execute connected-account changes only after explicit approval for each one.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review advertising performance from exported CSV reports
• Decide which campaigns to pause or adjust
• Compare platform conversions with CRM results

Organize EU AI Act compliance work with references to Articles and Annexes. Classify AI systems by risk, plan conformity assessments that check regulatory requirements, prepare technical documentation checklists, and map obligations and deadlines to organizational roles.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing risk classification for a new AI system
• Planning conformity assessments for high-risk AI
• Preparing technical documentation checklists

Plan what content to create using business goals, customer questions, and competitor gaps. Organize related topics, prioritize ideas for search or sharing, and turn them into content calendars or briefs with clear audiences and purposes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning core themes for a company blog
• Prioritizing topics from customer questions
• Grouping related articles into topic clusters

Turn feature ideas into backlog items, a team's planned units of work, using Why, What, and Acceptance Criteria. Connect each item to business goals and define observable outcomes in independent pieces sized for one sprint.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Breaking a feature into independent work items
• Explaining the business purpose behind development work
• Writing observable acceptance criteria

Compare documented permissions and data boundaries with actual code to find meaningful gaps. Produce findings that connect each documented rule to implementation evidence, identify who could exploit it and who is affected, and propose a concrete fix.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing code built by AI agents
• Checking access controls against documented permissions
• Finding gaps between documentation and code

Explain which process holds a port or file lock, what started it, and what keeps it running. Uses the witr CLI to trace services, containers, and parent processes without stopping or changing anything.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding what holds an occupied port
• Tracing a development server left running
• Explaining an unknown or stuck process

Inspect Mac performance to find processes using excessive CPU, GPU, memory, or energy. Combine measurements with explanations of known system processes to diagnose slowness, heat, and startup load, then recommend actions without changing system settings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find the cause of a slow Mac
• Investigate loud fans and overheating
• Check memory pressure and swap activity

Examine articles, reports, or pasted text for bias in the data, the producing organization's interests, and the reporting. It seeks cited studies and returns a structured report separating supported findings from editorial interpretation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether an article's headline matches the cited study
• Assess survey methods and sponsor conflicts of interest
• Review a PDF report and trace its underlying sources

Analyze recent work history and recurring frustration to identify problems that existing skills or workflows do not address. Receive a ranked shortlist of new skill ideas, with supporting evidence, for deciding what to build next.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing which skill to build next
• Investigating recurring work frustrations
• Checking whether existing skills cover a problem