ksprashu

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.
• **

ksprashu

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

bradtraversy

# GET VERSION
npm -v (or --version)

# GET HELP
npm help
npm

# CREATE PACKAGE.JSON
npm init
npm init -y (or --yes)

Vadorequest

# Gist: https://gist.github.com/Vadorequest/9d1f86b19dff5e1f7946a2f6b15a97f3
# Best practices: See https://blog.gitbutler.com/how-git-core-devs-configure-git
[push]
    default = simple
    autoSetupRemote = true
    followTags = true
[alias]
    fetch = git fetch --tags
    reflog = git reflog --date=iso
    st = status

rondy

FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.

---

Effective Engineer - Notes

• By Edmond Lau
• Highly Recommended 👍
• http://www.theeffectiveengineer.com/

What's an Effective Engineer?

simply-coded

This has been updated and moved here: https://gist.github.com/codeartery/e40316d5bb5fc1ce3424c7707bc342d0

avel

Locators

element(by.<...>)

• id
• js
• css
• className
• name

isaacs

# Hello, and welcome to makefile basics.
#
# You will learn why `make` is so great, and why, despite its "weird" syntax,
# it is actually a highly expressive, efficient, and powerful way to build
# programs.
#
# Once you're done here, go to
# http://www.gnu.org/software/make/manual/make.html
# to learn SOOOO much more.

awidegreen

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

loonies

PHPUnit API reference

• version 3.6

TODO

Check those constraints:

$this->anything()