Skip to content

srid/haskell-flake / .claude/skills/elegance

elegance

Verified

Iteratively study and apply elegant coding patterns. Each iteration - understand the code, research what simple and elegant code looks like, apply learnings, verify with CI. Use as a standalone refactoring pass or when the user asks to make code more elegant, simple, or idiomatic.

Elegance

Iteratively study and apply elegant coding patterns. Each iteration: understand the code, research what simple & elegant code looks like, apply learnings, verify with CI.

Run for 3 iterations (or as specified by the user — can be a number or a duration like 2h).

0. Determine Scope

  • Before starting, use the AskUserQuestion tool to ask: should this operate on the whole codebase or only on changes in the current branch/PR?
  • If scoped to current branch/PR, use git diff main...HEAD (or the appropriate base branch) to identify changed files and limit all subsequent steps to those files only.

For each iteration (1 to N):

1. Understand

  • Read through the relevant source files.
  • Note patterns, repetition, unnecessary complexity, non-idiomatic code.

2. Research

  • Use WebSearch/WebFetch to research what simple, elegant (yet readable!) code looks like for the relevant technology.
  • Look for idiomatic patterns, standard simplifications, and community best practices.
  • Focus on: simplicity, readability, removing unnecessary abstraction, leveraging language features.

3. Apply

  • Refactor based on what you learned.
  • This can include: edits, code reorganization, or even rewrites where simplicity demands it.
  • Prefer fewer lines, clearer intent, and idiomatic style.
  • Don't add abstractions — remove them.

4. Verify

  • Run tests/CI to check edits.
  • If CI fails, fix the issues before proceeding to the next iteration.

5. Log Progress

  • Briefly note what changed in this iteration and why.

After all iterations

  • Do not git commit. Leave all changes in the working directory for the user to review.
  • Present a summary of what changed across all iterations.

Principles

  • Simple over clever: Elegant code is simple code.
  • Readable over terse: Brevity is good, but not at the cost of clarity.
  • Idiomatic over generic: Use the language's strengths. Write TypeScript like TypeScript, not like Java.
  • Each iteration builds on the last: Don't undo previous improvements. Deepen them.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 114kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 114kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 114kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 114kUpdated Claude CodeCodexVerifiedInstall