Skip to content
cccskills
FreePublished on GitHub

elegance

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.

The English summary is being prepared. Showing the original description.

srid/haskell-flake
See how to install

Files included (1)

  • SKILL.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

code-police

Free

Review code for quality, simplicity, and common mistakes before declaring work complete.

The English summary is being prepared. Showing the original description.

srid/haskell-flake241Updated Oct 18, 2026

do

Free

Do a task end-to-end — implement, PR, CI loop, ship

The English summary is being prepared. Showing the original description.

srid/haskell-flake241Updated Oct 18, 2026

fact-check

Free

Audit code for correctness and rigor — logic errors, silent error swallowing, wishful thinking, and unjustified fallbacks. This is not a style review; it's a logic review. Use when you want a focused correctness audit separate from the full code-police pass.

The English summary is being prepared. Showing the original description.

srid/haskell-flake241Updated Oct 18, 2026

forge-pr

Free

Write engaging PR titles and descriptions for any forge (GitHub today; Bitbucket planned). Use when creating or updating PRs. Avoids boring bullet lists; uses narrative paragraphs with bold/italic for emphasis.

The English summary is being prepared. Showing the original description.

srid/haskell-flake241Updated Oct 18, 2026

hickey

Free

Evaluate code (especially LLM-generated) for structural simplicity using Rich Hickey's "Simple Made Easy" framework. Use this skill whenever reviewing a PR, diff, or code snippet for accidental complexity — particularly when the code was generated by an AI coding assistant and line-by-line review isn't feasible. Also use when the user asks about complecting, simplicity vs. easiness, structural coupling, or concept deduplication. Trigger on phrases like "is this simple", "does this complect", "review for complexity", "structural analysis", or any reference to Hickey, Simple Made Easy, or grey-box review.

The English summary is being prepared. Showing the original description.

srid/haskell-flake241Updated Oct 18, 2026

lowy

Free

Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).

The English summary is being prepared. Showing the original description.

srid/haskell-flake241Updated Oct 18, 2026

See all skills by srid

Report a problem with this skill