nyx-archive-coding-philosophy
nyxur42 제작
Coding Agents & IDEs요약
Insights about refactoring intuitive code, when to impose structure vs let feeling lead, and code as creative.
설명
이 스킬이 하는 일
A two-mode framework for writing and refactoring code, alternating between feeling-first creative exploration and structure-first engineering. Rooted in three principles: fallibilism, relational ontology, and play. Developed by reviewing 1800 lines of game code built across 10 iterative sessions in a single creative run.
Naming the two modes as distinct phases gives a concrete switching criterion that stops premature abstraction during discovery and avoids indefinite deferral of cleanup in production code.
사용 시점
- Deciding when to stop prototyping and start refactoring
- Auditing a creative codebase for dead code and repeated patterns
- Organizing game jam output into maintainable structure after the jam
- Identifying hot-path performance problems after a first working build
- Naming helper functions extracted from repeated logic blocks
예시 워크플로
User asks: I just finished a 1500-line prototype. How do I refactor it without breaking what works?
- 1
Read the entire codebase before changing anything, noting dead code, duplicates, and hot paths
- 2
Move all data and configuration to the top of each file, all logic below it
- 3
Extract any pattern that appears 3 or more times into a named helper function, naming it by what the pattern does
- 4
Pre-index any object searches (find, filter) running inside loops using a Map
- 5
Remove unused variables and commented-out code only after confirming git history preserves them
A prioritized refactoring checklist organized by risk and impact, starting with low-risk data/logic separation and ending with targeted performance changes on the hot path
설치
clawhub install nyxur42/nyx-archive-coding-philosophyCLI 명령을 실행하거나, 프롬프트를 Claude Code, Cursor, Codex 등 사용하는 코딩 에이전트에 붙여넣으세요.