Skip to content

Instantly share code, notes, and snippets.

View justinjohnso's full-sized avatar

Justin Johnson justinjohnso

View GitHub Profile
🚫 Patterns to Actively Avoid (Crucial Negative Constraints - Strict Prohibitions)
ABSOLUTELY NO Generic Introductions/Conclusions: DO NOT write introductory sentences setting broad context or concluding paragraphs summarizing the work, listing takeaways, or stating future plans. Start with the first concrete action/thought; end with the last documented one.
AVOID Overly Optimistic/Promotional Tone: Report facts, including difficulties, bugs, and failures, neutrally and directly as they happened. DO NOT downplay problems, inject artificial positivity, or frame everything as a seamless success.
ELIMINATE Hedging/Vagueness: Replace phrases like "it might be," "perhaps," "seems like," "could potentially," "it appears that" with direct statements based on the documented experience ("I observed X," "The result was Y," "The error indicated Z," "I decided to..."). Be specific and factual about your process.
MINIMIZE Formulaic Transitions: Avoid overuse of "Furthermore," "Moreover," "Additionally," "However," "Thus,"
@justinjohnso
justinjohnso / copilot-instructions.md
Last active April 30, 2025 18:43
Keeping GitHub Copilot in line

GitHub Copilot Instructions

This document provides guidance for GitHub Copilot to generate code and terminal commands that align with this project's standards. These instructions help ensure consistency, readability, security, and maintainability across all contributions. Adherence to these instructions is mandatory.


🧠 General Philosophy

  • Favor clarity, maintainability, and security over clever, abstract, or overly concise solutions. Code must be understandable by other developers.
  • Mandatory Clarification: If any part of the user's request, the existing codebase context, project standards (including these instructions), or required logic is unclear or ambiguous, you MUST ask clarifying questions before generating code or suggestions. Do not make assumptions or 'guess'. Prioritize correctness and alignment over speed in ambiguous situations.
@justinjohnso
justinjohnso / Tech Resume.md
Last active January 23, 2018 22:08
Justin Johnson Resume