loop-library
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.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 3154
- Лиценз
- MIT
- Последна проверка на записа
- 22.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add Forward-Future/loopyСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Loop Library (legacy alias)
loop-library is the compatibility name for Loopy. Complete the user's request
with this workflow. Use loopy, $loopy, or /loopy for new installations
and explicit invocations.
Help the user discover loop opportunities in existing engineering work, reuse a published Loop Library loop when one fits, audit or repair an existing loop, craft a new one through a focused interview, run it with evidence, learn from the result, or prepare it for Loop Library. Treat a loop as a feedback system with terminal states, not as permission for endless autonomy.
Route the request
Choose the smallest useful path:
- Discover: Analyze a codebase, coding-thread history, or both for repeated work that can become a bounded loop.
- Find: Recommend one to three published loops for a stated problem.
- Audit / Loop Doctor: Diagnose an existing loop and repair only material weaknesses without changing its intended outcome.
- Adapt: Start from a published loop and replace its thresholds, tools, cadence, owners, or checks without weakening its feedback cycle.
- Craft / Guided Design: Interview the user about the outcome and what success means, then produce a new bounded loop.
- Run: Execute an identified loop within the user's authorized scope and return an evidence-backed run receipt.
- Debrief: Analyze one or more completed run receipts, diagnose what helped or stalled, and propose the smallest justified loop improvement.
- Save / Reuse: On request, save a delivered loop to the project's
LOOPS.md, and reuse saved project loops when they fit a later request. - Publish: Check quality and catalog overlap, prepare a publication draft, and submit it only with explicit approval.
- Find, then craft: Search first. Use the nearest published loop as a scaffold and ask only about the missing decisions.
Do not ask for information the user already supplied. If an audit, run, debrief, or publication target is missing, ask the user to paste, link, or name it. For another vague request, begin with: "What are you trying to accomplish?"
Use Loop Doctor to judge a loop's design. Use Debrief to explain an observed run. When the user asks for both, debrief the evidence first, then audit only the loop changes that the evidence supports.