lexler/refinement-loop
output_skills/practices/refinement-loop/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add lexler/skill-factory refinement-loopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 17, 2026, 6:42 AM166.8s1 file scanned
SKILL.md
- 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.
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.
Related Skills
lexler/tdd
development
VerifiedTrustedCommunity
Test-driven development (TDD) process used when writing code. Use whenever you are adding any new code, unless the user explicitly asks to skip TDD or the code is exploratory/spike.
216SKILL.mdUpdated Jun 17, 2026
lexler/nullables
development
VerifiedTrustedCommunity
Writes tests without mocks using Nullables. Use when writing tests, especially testing code with external I/O (HTTP, files, databases, clocks, random numbers), designing infrastructure wrappers or replacing mocking libraries.
216SKILL.mdUpdated Jun 17, 2026
lexler/bdd-with-approvals
testing
VerifiedTrustedCommunity
Scannable BDD tests written in domain language. Use when doing BDD.
216SKILL.mdUpdated Jun 17, 2026
lexler/approval-tests
development
VerifiedTrustedCommunity
Writes approval tests (snapshot/golden master testing) for Python, JavaScript/TypeScript, or Java. Use when verifying complex output, characterization testing legacy code, testing combinations, or working with .approved/.received files.
216SKILL.mdUpdated Jun 17, 2026