메뉴
Pause on non-trivial changes to ask for a more elegant solution. Skip for simple fixes. Use when a fix feels hacky, implementing non-trivial changes, or before presenting work. Elegance for non-trivial; pragmatism for trivial.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/unional/skills --skill demand-elegance명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Bring one of unional's repos or organizations up to the standard baseline — branch protection ruleset, merge and Actions settings, security toggles, and the CI/release file layout. Use when setting up a new repo, when asked to 'update branch protection', 'require all-checks', 'apply my repo settings', 'set up this repo like the others', or to audit which repos have drifted from the baseline.
Apply a consistent documentation standard: controlled plain prose, one home per fact, and every external claim backed by a source. Use when writing or revising documentation, READMEs, or skill bodies; when deciding where a document belongs; when moving, renaming, or splitting a page; when a draft reads as generated and needs its rhythm, filler words, or em dashes fixed; or on requests like 'improve the docs', 'audit the docs', 'this page is too long', 'this sounds like AI', 'humanize this', 'remove the em dashes', or 'where should this be documented'.
Sweep an owner's repos to find which ones stopped publishing, classify each failure by root cause, and report the evidence needed to fix them. Use when asked 'which of my repos are broken?', 'is anything not publishing?', 'audit my releases', 'find repos that need modernizing', or before running modernize-repo so you know which repos to run it on.
| name | demand-elegance |
| description | Pause on non-trivial changes to ask for a more elegant solution. Skip for simple fixes. Use when a fix feels hacky, implementing non-trivial changes, or before presenting work. Elegance for non-trivial; pragmatism for trivial. |
| metadata | {"internal":true} |
For non-trivial changes, pause and ask: is there a more elegant way?
Elegance for non-trivial work; pragmatism for trivial work.
| Situation | Action |
|---|---|
| Hacky fix | Pause, implement elegant solution |
| Non-trivial change | Ask "more elegant way?" before proceeding |
| Simple fix | Proceed; don't over-engineer |