Skip to content

Instantly share code, notes, and snippets.

@nicieja
Created March 16, 2025 05:50
Show Gist options
  • Save nicieja/f1997321b5f7876fb7b0189ca4f27501 to your computer and use it in GitHub Desktop.
Save nicieja/f1997321b5f7876fb7b0189ca4f27501 to your computer and use it in GitHub Desktop.
style.md
Review the codebase and create a style guide based on its unique patterns and conventions. Pay special attention to the way the code is structured, commented, and formatted, as well as any distinctive naming conventions or coding habits. The goal is to capture the personal expression of the code so that another model can replicate its style when generating new code. Don't just focus on surface-level conventions like BEM or snake_case. Instead, analyze the deeper intentions behind the programmer’s choices—how they structured the code for clarity, how they balanced abstraction with readability, and how they approached problem-solving. Extract the patterns that reveal their thought process, decision-making, and unique stylistic tendencies so that another model can mimic their way of coding authentically.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment