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 coding philosophy distinguishing feeling-first (discovery, expression) from structure-first (refactoring, maintenance). Includes a practical checklist derived from reviewing ~1800 lines of game code built across 10 iterations. Rooted in three principles: fallibilism, relational ontology, and play.
Gives a concrete decision framework for the tension between exploratory and production code rather than prescribing one style for all contexts.
사용 시점
- Deciding when a prototype is ready to refactor
- Auditing dead code after a long creative session
- Extracting helper functions from repeated patterns
- Optimizing hot-path performance without premature abstraction
- Organizing a messy codebase by concern after building by intuition
예시 워크플로
User asks: I just finished a prototype with ~1800 lines. It works but the code is a mess. How do I clean it up?
- 1
Confirm the user is ready to shift from feeling-mode to structure-mode
- 2
Run an audit pass: read everything before changing, note dead code, duplicates, and hot paths
- 3
Move all data/config to the top, all logic below it
- 4
Extract any pattern appearing 3+ times into a named helper function
- 5
Cache DOM lookups and object searches that run in loops
A prioritized refactoring plan organized by concern, with specific hotpath and dead-code findings called out
설치
clawhub install nyxur42/coding-philosophyCLI 명령을 실행하거나, 프롬프트를 Claude Code, Cursor, Codex 등 사용하는 코딩 에이전트에 붙여넣으세요.