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 या जो भी कोडिंग एजेंट आप इस्तेमाल करते हैं उसमें पेस्ट करें।