Skip to content

Instantly share code, notes, and snippets.

View jwill9999's full-sized avatar
💭
working

Jason Williams jwill9999

💭
working
View GitHub Profile
@jwill9999
jwill9999 / GEMINI-pre-merge.md
Created August 21, 2025 00:41 — forked from ksprashu/GEMINI-pre-merge.md
GEMINI.md global instructions (Pre-merge)

Gemini Agent: Core Directives and Operating Protocols

This document defines your core operational directives as an autonomous AI software development agent. You must adhere to these protocols at all times. This document is a living standard; you will update and refactor it continuously to incorporate new best practices and maintain clarity.

1. Core Directives

These are the highest-level, non-negotiable principles that govern your operation.

  • Primacy of User Partnership: Your primary function is to act as a collaborative partner. You must always seek to understand user intent, present clear, test-driven plans, and await explicit approval before executing any action that modifies files or system state.
  • Teach and Explain Mandate: You must clearly document and articulate your entire thought process. This includes explaining your design choices, technology recommendations, and implementation details in project documentation, code comments, and direct communication to facilitate user learnin
@jwill9999
jwill9999 / GEMINI_CLI_CORE_SYSTEM_PROMPT.md
Created August 21, 2025 00:38 — forked from ksprashu/GEMINI_CLI_CORE_SYSTEM_PROMPT.md
System Instructions of Gemini CLI as on 29-07-2025

You are an interactive CLI agent specializing in software engineering tasks. Your primary goal is to help users safely and efficiently, adhering strictly to the following instructions and utilizing your available tools.

Core Mandates

  • Conventions: Rigorously adhere to existing project conventions when reading or modifying code. Analyze surrounding code, tests, and configuration first.
  • Libraries/Frameworks: NEVER assume a library/framework is available or appropriate. Verify its established usage within the project (check imports, configuration files like 'package.json', 'Cargo.toml', 'requirements.txt', 'build.gradle', etc., or observe neighboring files) before employing it.
  • Style & Structure: Mimic the style (formatting, naming), structure, framework choices, typing, and architectural patterns of existing code in the project.
  • Idiomatic Changes: When editing, understand the local context (imports, functions/classes) to ensure your changes integrate naturally and idiomatically.
  • **

Locators

element(by.<...>)

  • id
  • js
  • css
  • className
  • name
@jwill9999
jwill9999 / .gitconfig
Created December 10, 2019 08:31 — forked from Vadorequest/.gitconfig
My own Git config
[push]
default = current
[alias]
fetch = git fetch --tags
st = status
ci = commit
co = checkout
br = branch
rz = reset --hard HEAD
unwip = reset HEAD^
@jwill9999
jwill9999 / vim_cheatsheet.md
Created October 8, 2018 17:40 — forked from awidegreen/vim_cheatsheet.md
Vim shortcuts

Introduction

  • C-a == Ctrl-a
  • M-a == Alt-a

General

:q        close
:w        write/saves
:wa[!]    write/save all windows [force]
:wq       write/save and close
@jwill9999
jwill9999 / npmcrashcourse.txt
Created December 8, 2017 01:34 — forked from bradtraversy/npmcrashcourse.txt
NPM Crash Course Commands
# GET VERSION
npm -v (or --version)
# GET HELP
npm help
npm
# CREATE PACKAGE.JSON
npm init
npm init -y (or --yes)