'loop' 검색 결과

Investigate observed slowdowns or increased CPU, memory allocation, and IO costs in a process you control. Use controlled timing and runtime-specific profiling tools to test a cause, then check performance and behavior after a fix.

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

• Investigate a command that has become slower
• Locate CPU or memory allocation hotspots
• Separate transport waits from backend processing costs

Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.

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

• Finding code patterns to prioritize for cleanup
• Preparing measurement files for an improvement loop
• Repeating targeted edits to reduce casts to any

Compatibility alias for Loopy. Use only when an existing installation or older instruction explicitly invokes loop-library; use Loopy for new installations and requests. Provides the same discovery, recommendation, audit, repair, adaptation, guided crafting, bounded execution, run debrief, project loop saving, and publication-preparation workflows.

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

Spin up a new loop (domain) in a file-based knowledge base — bootstrap the substrate if it's missing, gather the loop's charter, scaffold domains/<loop>/README.md, then do ONE real test run and record it in the loop's Timeline and LOG.md. Use when the user says "set up a new loop", "create a domain", "start a new beat/workstream", or names a recurring job they want the agent to own.

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

When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.

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

Turn a one-line description of a repetitive task into a reusable, self-guarding slash command. loop-forge diagnoses the task into one of 5 loop shapes (Batch / Pipeline / Refine / Watch / Explore), interviews for the blanks, and auto-injects two safety devices the user didn't know they needed — an independent verifier (maker ≠ checker) and a hardstop (a budget/count/cooldown ceiling) — then previews the result and stamps it as a `/command` they can run forever. Use when the user says "/loop", "/loop-forge", "/make-it-loop", "automate this", "make this repeatable", "turn this into a command", "do this for all 100 items", "do X every time Y happens", "generate several and pick the best", or otherwise wants to capture a recurring task as a reusable slash command instead of re-typing the prompt by hand. Works in any language: it interviews the user and writes the stamped command in the user's own language. Non-goal — it does not schedule unattended runs (launchd/cron) or publish externally on its own; it stamps the reusable command and stops there.

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

Sets up BMAD Loop Skills module in a project. Use when the user requests to 'install bmad-loop module', 'configure BMAD Loop Skills', or 'setup BMAD Loop Skills'.

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

Use when the user asks for Superloopy clone or asks to clone, rebuild, reverse-engineer, replicate, or copy a website or page into a Superloopy-governed implementation. Triggers on "loopy clone", target URLs plus requests such as "clone this site", "rebuild this page", "make a copy of this website", "pixel-perfect clone", or "AI website clone". Requires browser automation and records component specs, assets, implementation, build output, and visual QA as Superloopy evidence.

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

Inspect and explain bmad-loop run artifacts under `.bmad-loop/runs/`. Use for live health checks ("is it stuck?", "is the loop alive?", "what is the agent doing?") and post-run forensics ("what happened?", "why did story X fail?", "where did the tokens go?"). Also triggers on "monitor/check/summarize the loop", "why did the run pause?", Vietnamese "theo dõi bmad loop", "phân tích run", "đọc log của run", and equivalent requests in other languages. Use only for bmad-loop's own run artifacts, not application runtime logs or CI-provider build logs.

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

Select a `delaySeconds` value when scheduling a loop wakeup via the `ScheduleWakeup` tool or the `/loop` slash command. Covers the three-tier cache-aware decision (cache-warm under 5 minutes, cache-miss 5 minutes to 1 hour, idle default 20 to 30 minutes), the 300-second anti-pattern, the [60, 3600] runtime clamp, the minute-boundary rounding quirk, and writing a telemetry-worthy `reason` field. Use when designing an autonomous loop, when a heartbeat cadence is being planned, when polling cadence is being tuned, or when post-hoc review of loop costs reveals interval mis-sizing.

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

Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Drives all work through atomic commits — each loop operates on the smallest complete, reviewable change. Defines the Code Change Loop, Test Writing Loop, Lint Gate, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Requires `committer` for all commits. Includes bundled provider-aware review scripts that keep same-model shell-outs as the last resort, plus a fresh-context Codex fallback for code review and test audit. Use this skill when starting any implementation task.

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

从"手动做事"到"系统自动做事"的四步渐进构建路径。 当用户已经决定要做 loop、但不知道从何入手时;或团队正在将手工流程自动化时使用。 不适用于: 尚未决定要不要做 loop 的任务、或已经稳定运行的 loop 优化。 关键 trigger: "怎么开始做 loop"、"自动化第一步"、"从手动到自动"。

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

Spin up a new loop (domain) in a file-based knowledge base — bootstrap the substrate if it's missing, gather the loop's charter, scaffold domains/<loop>/README.md, then do ONE real test run and record it in the loop's Timeline and LOG.md. Use when the user says "set up a new loop", "create a domain", "start a new beat/workstream", or names a recurring job they want the agent to own.

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

Abbruchbedingung für autonome Loops: So weit wie möglich selbständig weiterarbeiten UND einen Loop erst beenden, wenn belegt ist, dass keine autonom ausführbare Aufgabe mehr vorliegt. Der bloße Eindruck "nichts mehr zu tun" reicht NICHT — er löst eine vierstufige Prüfkette aus (think/decide, _CONTROL/_DECISIONS, Gardener/USMC, decision-avatar/BYUM), die zuerst neue Aufgaben GEWINNEN muss, bevor der Loop enden darf. Jeder Kettenschritt meldet found/empty/unavailable statt eines binären Ergebnisses — "exhausted" gilt nur, wenn ALLE Quellen tatsächlich befragbar waren; ist mindestens eine Quelle unavailable, meldet der Skill "blind" statt "exhausted" und behauptet nichts Ungeprüftes. Nutze diesen Skill bei /work-autonomous, /waafap, "arbeite autonom weiter bis nichts mehr zu tun ist", als Goal-Bedingung innerhalb eines /loop, oder wenn geprüft werden soll, ob wirklich keine autonome Arbeit mehr übrig ist, bevor ein Loop/eine Session beendet wird.

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

When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.

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

Explain and control the stellar-build learning loop — the system that improves your skills from how you use them. Use when the user says "learning loop", "how does the learning loop work", "what is the learning loop", "self-improving skills", "stellar-loop", "show my skill usage", "is tracing on", or wants an overview / status of the local trace-capture + optimize + bench cycle.

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

인공지능 에이전트의 지속 작업 루프를 설계하고 품질 확인, 평가, 실패 시 중지와 재시도 방침을 결합해 진행 정체와 반복 실패에 대응합니다.

• 지속 작업에 맞는 루프 방식 선택
• 품질 확인과 평가 결합
• 실패나 진행 정체에서 복구

Claude Code에서 개발 작업을 반복하는 자율 루프 설계를 안내합니다. 순차 실행부터 병렬 작업까지 진행 상황 인계, 품질 확인, 변경 사항 통합과 중단 조건을 정리합니다.

• 순차적으로 실행할 개발 절차를 설계할 때
• 반복 실행 사이에 진행 상황을 인계할 때
• 병렬 작업과 변경 사항 통합을 조율할 때

Take implementation work through small, independently mergeable pull requests. Use a separate working directory for each PR, record manual QA evidence, write English review descriptions, resolve CI and review findings, then merge and clean up.

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

• Deliver implementation work through pull requests
• Split a large task into small, independently mergeable PRs
• Build independent PRs concurrently

Run a prompt or slash command repeatedly at a chosen interval, or let the agent decide when to run again. Use it for recurring checks, with event monitoring available when the next action depends on a change.

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

• Check deployment status every five minutes
• Run a slash command repeatedly
• Repeat checks as CI results or files change

Turn a development goal into a focused ralph-loop command through conversation and codebase research. Define context, setup steps, ordered tasks, and testing criteria, then produce a complete command ready to copy.

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

• Turning a vague feature idea into concrete tasks
• Planning work around existing code patterns
• Defining build checks and completion criteria

Plan a Claude Managed Agent around one clear job, then route work through setup, launch preparation, evaluation, and scheduling. Produce execution plans and curl commands that users run with their own Anthropic API key.

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

• Defining one clear job for a managed agent
• Preparing launch commands for an Anthropic account
• Planning evaluation and revision with an iteration limit

Compare five growth loops, mechanisms where user activity brings in more users, to find a suitable approach for a product. Develop an implementation roadmap, measurement plan, and growth estimates based on sharing, collaboration, content, or referrals.

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

• Designing product features that attract new users
• Planning growth with less reliance on paid acquisition
• Comparing sharing, collaboration, and referral mechanisms

Run iterative development with repeated implementation and verification, using failure history to guide changes. When a verification command is configured, an independent hook checks completion after the agent's own tests, with pause and abort markers available.

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

• Repeating fixes until failing tests pass
• Checking completion with a separate build or test command
• Revisiting an approach after repeated verification failures