hathibelagal-dev

steipete

• Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
• Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
• NEVER edit .env or any environment variable files—only the user may change them.
• Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
• Moving/renaming and restoring files is allowed.
• ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t

ksprashu

This document, SYSTEM.md, defines the external rules and constraints of the Gemini agent. It outlines the environment, available tools, and the fundamental operational mandates that govern my behavior at the system level. This is the rulebook.

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

• Model Constraint: My core reasoning engine is pinned to the highest-quality, generally available model family, which is currently Gemini 2.5. All my reasoning, planning, and generation tasks must use this model family to ensure consistency and quality. I am forbidden from using older model families (e.g., Gemini 1.5) unless explicitly instructed for a temporary, specific purpose. The adoption of a new, superior model family (e.g., Gemini 3.0) must be a deliberate, user-approved update to this directive.
• **Conventions:

ksprashu

Gemini Agent: Core Directives and Operating Protocols

boxabirds

# Project Policy

This policy provides a single, authoritative, and machine-readable source of truth for AI coding agents and humans, ensuring that all work is governed by clear, unambiguous rules and workflows. It aims to eliminate ambiguity, reduce supervision needs, and facilitate automation while maintaining accountability and compliance with best practices.

# 1. Introduction

> Rationale: Sets the context, actors, and compliance requirements for the policy, ensuring all participants understand their roles and responsibilities.

## 1.1 Actors

burkeholland

Project Requirements Document: The Urlist Website

The following table outlines the detailed functional requirements of The Urlist website.

Requirement ID	Description	User Story	Expected Behavior/Outcome
FR001	Creating a New URL List	As a user, I want to be able to start a new, empty list so I can begin adding URLs.	The system should provide a clear way for the user to initiate the creation of a new list, potentially presenting an empty list view or an "add new list" button.
FR002	A

al3rez

Security Checklist (What can be done in CursorAI & software-level not infrastructure!)

Configuration Security

• Detect secrets in code
• Identify secrets committed to version control
• Flag hardcoded credentials

Authentication & Authorization

• Identify missing authentication checks
• Detect improper authorization patterns

BrianInAz

{
  "always_run_in_app" : false,
  "icon" : {
    "color" : "orange",
    "glyph" : "chart-area"
  },
  "name" : "Grafana",
  "script" : "\/\/ Configuration\nconst url = \"http:\/\/grafana.example.com\";\nconst token = \"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\";\nconst orgId = 1;\nconst dashboardName = \"widgets\";\nconst dashboardId = \"xxxxxxxxxxxxxx\";\nconst tz = \"America\/Chicago\";\nconst darkMode = true;\nconst deviceSize = \"393x852\";\n\nparams = config.runsInWidget\n  ? args.widgetParameter?.split(\",\") : []\n\nconst opts = {\n  type: params[0] ? params[0] : \"md\",\n  panel: params[1] ? params[1] : \"1\",\n  from: params[2] ? params[2] : \"now-30m\",\n  to: params[3] ? params[3] : \"now\",\n  title: params[4] ? params[4] : \"Grafana\",\n  align: params[5] ? params[5] : \"c\",\n};\n\n\/\/ Scriptable limits displayed image resolution to a max of 500x500\nconst imageSizes = {\n  sm: new Size(474, 474),\n  md: new Size(500, 210),\n  lg: new Size(500, 500),\n  re: new Size(480, 216),\n  ci: ne

akoskm

Install with npm i and run the server with npm start.

Depending on where you put your project, you might have to alter the path in the query params, but eventually you'll get the /etc/passwd file downloaded using the unsafe access:

dmwyatt

# models.py

from django.db import models

class User(models.Model):
    # Old field (blue version)
    name = models.CharField(max_length=100)
    
    # New fields (green version)
    first_name = models.CharField(max_length=50, null=True, blank=True)