refinement-loop
Iterative refinement through multiple passes. Use when the user asks to 'meditate on', 'distill', 'refine', or 'iterate on' something, or proactively when a problem benefits from multiple passes rather than a single attempt.
- License 许可
- Unlicense
- 所属仓库
- saski/arnesto
- 最近更新
- 2026-11-12
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- refinement-loop
- description
- Iterative refinement through multiple passes. Use when the user asks to 'meditate on', 'distill', 'refine', or 'iterate on' something, or proactively when a problem benefits from multiple passes rather than a single attempt.
03 SKILL.md 正文
Refinement Loop
STARTER_CHARACTER = 🔄
Iterative refinement through file artifacts. Each pass removes one layer of noise, revealing the next.
Setup
Ensure playground/ exists and is in .gitignore. All iteration files go there.
Process
1. Clarify Goal (if the user hasn't defined it for you already earlier in the conversation)
Ask the user:
- What are you refining and what is the goal of refinement?
- Derive a short tag that we'll use as filename for iterating:
{goal}-{subject}(e.g.,gist-nullables,simplify-api,distill-auth-docs)
2. Capture Starting Point
Write original to: playground/{goal}-{subject}-0.md
3. Iterate
Loop:
- Read back the current file (forces fresh perspective)
- Reflect critically: What's missing? What's weak? What could be clearer?
- If improvements found: Write improved version to
playground/{goal}-{subject}-{N+1}.md, then loop again
Before Stopping - Exhaustive Check
When you think you're done, you're probably not. Run through this:
- List everything that could still be improved - even small things (formatting, word choice, structure, clarity)
- Consider what we haven't considered - what angles did we miss? What would someone else notice?
- Try improving in a new direction - not just polishing what's there, but questioning assumptions
- Read as if seeing it for the first time - does it immediately make sense? Is anything unclear?
Only stop when you've gone through this checklist extensively multiple times and genuinely found nothing. There is no "good enough" - someone will use this later and shouldn't waste time on mediocre results.
4. Present Final
Show the user the final version with a brief summary of the refinement journey and number of iterations you used. If deeper issues or questions surfaced, present them to the user as well.
Principles
- Read back forces fresh eyes: Reading from file breaks the "I just wrote this" blindness
- No "good enough": Every detail matters. Formatting, word choice, structure - all of it
- Consider the unconsidered: What angles haven't we explored? What would someone else see? Is there something that the user hasn't even considered, too? (you can surface it as questions at the end)
- Files force iterative improvement: Writing to files prevents "pretend" iteration in conversation. Real iteration gets to much better results.
- Earn the stop: Run the exhaustive check. If you find nothing, you've earned stopping.
04 同仓库更多 Skills
visualize
Use /visualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.
update-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
update-cli-config
View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.
statusline
Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.
split-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
shell
Runs the rest of a /shell request as a literal shell command. Use only when the user explicitly invokes /shell and wants the following text executed directly in the terminal.