'iterative' 검색 결과

End-to-end pipeline for writing ML/AI research papers — from experiment design through analysis, drafting, revision, and submission. Covers NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Integrates automated experiment monitoring, statistical analysis, iterative writing, and citation verification.

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

Use a live Jupyter kernel for stateful, iterative Python execution via hamelnb. Load this skill when the task involves exploration, iteration, or inspecting intermediate results — data science, ML experimentation, API exploration, or building up complex code step-by-step. Uses terminal to run CLI commands against a live Jupyter kernel. No new tools required.

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

Delegate coding tasks to Claude Code (Anthropic's CLI agent). Use for building features, refactoring, PR reviews, and iterative coding. Requires the claude CLI installed.

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

Apply continuous improvement principles to iteratively enhance processes, code quality, team practices, and system performance through small, incremental changes. Use when improving development processes, optimizing workflows, reducing waste, enhancing code quality over time, implementing retrospective learnings, or fostering a culture of continuous improvement.

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

Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use /plan-design-review. Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish". Proactively suggest when the user mentions visual inconsistencies or wants to polish the look of a live site. (gstack)

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

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".

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

Delegate coding tasks to Claude Code (Anthropic's CLI agent). Use for building features, refactoring, PR reviews, and iterative coding. Requires the claude CLI installed.

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

Run build, deploy, inspect, and fix loops for .NET MAUI apps that already have MAUI DevFlow integrated. USE FOR: launching MAUI apps, selecting devices or emulators, waiting for or recovering agent connections, broker/port/adb connectivity issues, visual tree inspection, screenshots, UI interaction, Blazor WebView CDP debugging, reading DevFlow logs, and iterative app debugging. DO NOT USE FOR: first-time DevFlow package setup (use maui-devflow-onboard), or generic desktop automation unrelated to MAUI. INVOKES: maui devflow CLI, dotnet CLI, Android adb/android tools, and Apple simctl tools.

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

Add MAUI DevFlow to a .NET MAUI project with agent package references, MauiProgram.cs registration, Blazor WebView support, GTK variants, Central Package Management guidance, and verification commands. USE FOR: first-time DevFlow setup, reviewing what files to edit, choosing DevFlow packages, or continuing after `maui devflow init` installs skills. DO NOT USE FOR: troubleshooting an already-integrated app that cannot connect, iterative app debugging, UI inspection, or generic MAUI build failures (use maui-devflow-debug). INVOKES: maui devflow CLI and dotnet CLI.

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

Monitors a specified object against explicit stopping criteria and distinguishes replica convergence, iterative progress, and workflow terminal state. NOT for execution or setting goals.

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

Runs an iterative, conversational product-discovery process with a founder/stakeholder: structured interview, live low-fi wireframing, a linked feature/page node-graph built up as you go, a founder-confirmed lock-in checkpoint, then a generated PRD, a Mermaid-rendered sitemap, and a mockup with a full design system (palette, typography, dark mode). Use when building or operating an AI product-discovery chatbot, or when running founder/stakeholder discovery by hand and you need the structure (interview script, node-graph schema, PRD template, design-system handoff order). NOT for implementing the spec'd product once locked — hand off to feature-specific skills (ideal-web-app-builder, tailwind-v4-expert, color-theory-palette-harmony-expert, typography-expert, dark-mode-design-expert) for that. NOT for one-shot PRD generation without an interview loop — if the founder already has a written spec, this process is unnecessary overhead.

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

サブエージェントのコンテキスト問題を解決するための段階的コンテキスト取得パターン

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

This skill should be used when the user wants to "test a claim against data", "validate an empirical hypothesis", "refine a model/theory with evidence", "characterize a pattern and verify it", "演繹と帰納で検証", "仮説をデータで検証して更新", "実例と反例で確かめる", "弁証法ループ", "主張を現物で裏取り", "傾向分析を検証して精緻化", or mentions iteratively updating a hypothesis by deriving predictions and testing them against a real corpus. NOTE: Use this for VALIDATING/REFINING an empirical claim or model against real data through a derive→test→update loop. Use strong-inference for debugging an UNKNOWN cause, and devils-advocate for adversarially stress-testing a DESIGN proposal.

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

Create comprehensive academic research notes with deep literature coverage. Auto-detects language (EN prompt→EN output, TR prompt→TR output). Supports Obsidian markdown and PDF. Performs 8-15 iterative search cycles with 25-50+ sources for comprehensive coverage. Uses footnote citations and visual overviews.

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

[52] EXECUTE. Three-stage refactoring workflow: (1) iterative research of refactor/modularization options, (2) plan + risk/edge-case analysis + Scope150 validation, then implement with tests after user confirmation, and (3) apply Scout105 cleanup protocol. Use when asked to refactor, modularize, or restructure code safely.

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

Five Whys root cause analysis. Iteratively asks "why" to drill past symptoms to underlying causes. Use for debugging, investigating failures, or understanding why something went wrong.

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

Pattern for progressively refining context retrieval to solve the subagent context problem

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

Interactive Product Owner skill for requirements gathering, analysis, and PRD generation. Triggers when users request product requirements, feature specification, PRD creation, or need help understanding and documenting project requirements. Uses quality scoring and iterative dialogue to ensure comprehensive requirements before generating professional PRD documents.

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

Conduct exhaustive multi-source investigation with methodology tracking, source evaluation, and iterative depth.

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

Patterns and techniques for evaluating and improving AI agent outputs. Use this skill when: - Implementing self-critique and reflection loops - Building evaluator-optimizer pipelines for quality-critical generation - Creating test-driven code refinement workflows - Designing rubric-based or LLM-as-judge evaluation systems - Adding iterative improvement to agent outputs (code, reports, analysis) - Measuring and improving agent response quality

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