Aller au contenu
TakoAPI
Retour aux skills

coding-philosophy

par nyxur42

Coding Agents & IDEs
426Téléchargements rapportés par clawskills.sh
0Vues
0 mention J'aimeConnecte-toi pour aimer ce skill
—Pas encore noté
Ta note

Résumé

Insights about refactoring intuitive code, when to impose structure vs let feeling lead, and code as creative.

Description

Ce que fait ce skill

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.

Quand l'utiliser

  • 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

Exemple de workflow

ENTRÉE

User asks: I just finished a prototype with ~1800 lines. It works but the code is a mess. How do I clean it up?

AGENT
  1. 1

    Confirm the user is ready to shift from feeling-mode to structure-mode

  2. 2

    Run an audit pass: read everything before changing, note dead code, duplicates, and hot paths

  3. 3

    Move all data/config to the top, all logic below it

  4. 4

    Extract any pattern appearing 3+ times into a named helper function

  5. 5

    Cache DOM lookups and object searches that run in loops

SORTIE

A prioritized refactoring plan organized by concern, with specific hotpath and dead-code findings called out

Installation

clawhub install nyxur42/coding-philosophy

Exécute la commande CLI, ou colle l'instruction dans Claude Code, Cursor, Codex ou l'agent de code que tu utilises.

Liens