287건 · 관련도순
Collaborative writing partner that assists with research, outlining, drafting, citations, and iterative feedback. Helps writers create high-quality content while maintaining their unique voice and style.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify and test Jupyter notebooks with iterative fixing. Arguments: [target] [--quick] [--fix] [--python-only] [--dotnet-only]
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build or improve Jupyter notebooks iteratively with quality scoring. Arguments: <new|improve|fix> <path> [--topic] [--domain] [--level] [--quality] [--max-iter]
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs the full implement-and-commit loop over a task list — selects the next incomplete sub-task, implements it, runs linters and tests, marks it done, commits, and repeats until the list is finished. Use when asked to work through a feature's task list at .ai/[feature]/tasks.md unattended, or to keep going until every sub-task is complete. For a single sub-task with no commit, use task-implementation; to stop for approval between each one, use iterative-development.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements sub-tasks from a task list at .ai/[feature]/tasks.md strictly one at a time, stopping after each to ask the user before starting the next, and keeping the task list and Relevant Files section current. Use when the user wants to review or approve each sub-task before work continues, rather than letting the agent run the list unattended with task-orchestration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Autonomously improve a real artifact (code, training recipe, agent harness, data pipeline, prompt) against an objective and an evaluator, using Hypothesis Tree Refinement (HTR) from the Arbor paper. Use this whenever someone wants to iteratively optimize something over many experiments without overfitting — e.g. "get my model's eval score up", "improve this agent/harness", "tune this pipeline", "beat the baseline on this benchmark", "run a search over approaches and keep the best", "do an MLE-bench / Kaggle-style optimization", or any long-horizon "make this artifact better and don't just memorize the dev set" task. Trigger it even when the user doesn't say "Arbor" or "hypothesis tree" but describes repeated experiment-and-evaluate loops, branching exploration of competing ideas, or worries about a dev/test gap. Runs Claude itself as the coordinator with subagent executors in isolated git worktrees; for the standalone `arbor` CLI tool see references/arbor-upstream.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically QA-tests a web app and fixes bugs: test, then iteratively fix, re-verify, commit each fix. Tiers: Quick, Standard, Exhaustive. Produces before/after health scores and fix evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Worker-Reviewer iterative pipeline for quality-critical code with review cycles
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when user says "simmer this", "refine this", "hone this", "iterate on this", or asks to improve a specific artifact over multiple rounds. Runs an iterative refinement loop with investigation-first judges that read the code, understand the problem, and propose evidence-based improvements. Auto-selects single judge or multi-judge board based on complexity. Works on any artifact type: documents, prompts, specs, emails, creative writing, API designs, pipelines, codebases. Supports multi-file workspace targets, runnable evaluators, and open-ended optimization (model selection, pipeline topology, prompt tuning).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pattern for progressively refining context retrieval to solve the subagent context problem
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Iterative Python via live Jupyter kernel (hamelnb).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level numerical methods knowledge. Use when working with root finding, numerical integration, numerical differentiation, interpolation, numerical linear algebra, ODEs, PDEs, or optimization algorithms. Also use when the user mentions 'Newton method', 'bisection', 'Runge-Kutta', 'finite difference', 'finite element', 'interpolation', 'numerical integration', 'quadrature', 'iterative solvers', 'condition number', 'round-off error', or 'truncation error'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until it reaches the repository's configured Greptile merge threshold with zero unresolved actionable comments, or until the five-review maximum is reached. Triggers Greptile review, fixes all actionable comments, pushes/re-shelves, re-triggers review only for new head SHAs unless a 5/5 score is already published, and repeats. Use when the user wants to optimize a PR/MR/CL against Greptile's code review standards without creating runaway review loops.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run Ruff checks with optional scope and rule overrides, apply safe and unsafe autofixes iteratively, review each change, and resolve remaining findings with targeted edits or user decisions. Use when cleaning up Ruff lint findings across a Python codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SOP for the automated refinement loop (/refine) workflow. Trigger when: - Exhaustively auditing and optimizing pre-existing codebase artifacts. - Applying iterative contraction mapping to reduce code entropy. - Prompt contains: /refine, refinement loop, contraction mapping, fixed-point sweep.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Track design iteration history and apply consistent styling decisions across revision cycles. Use when handling follow-up change requests that reference previous design decisions (e.g., '前回も色で良いんだけど', 'same style as before', 'like we discussed').
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Solves complex, open-ended problems using an evolutionary search mechanism inspired by genetic algorithms. Generates a diverse population of candidate answers, scores them against a rubric, then iteratively applies selection, crossover, and mutation to breed progressively better solutions. Use this skill whenever the user wants to explore a solution space deeply, asks for the "best" answer to a subjective or multi-dimensional problem, wants to evaluate competing approaches and distill the strongest, or uses any of these triggers: "evolutionary search", "genetic algorithm", "evolve an answer", "breed solutions", "population-based search", or phrases like "give me multiple approaches and refine the best one". Also trigger when the problem is complex, open-ended, or has no obvious single correct answer and the user wants a high-quality, well-explored result, not just a quick response.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.