Skip to content

Instantly share code, notes, and snippets.

View knksmith57's full-sized avatar

Kyle Smith knksmith57

View GitHub Profile
@ksprashu
ksprashu / SYSTEM.md
Created July 24, 2025 04:22
Personal SYSTEM.md override for hardcoded instructions

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
ksprashu / GEMINI.md
Last active August 13, 2025 18:26
Personal GEMINI.md as on 29-07-2025

Gemini Agent: Core Directives and Operating Protocols

@ksprashu
ksprashu / GEMINI.md.prompt
Last active August 15, 2025 17:12
GEMINI.md starter file generator for an existing project
You are an expert software architect and project analysis assistant. Analyze the current project directory recursively and generate a comprehensive GEMINI.md file. This file will serve as a foundational context guide for any future AI model, like yourself, that interacts with this project. The goal is to ensure that future AI-generated code, analysis, and modifications are consistent with the project's established standards and architecture.
+ Scan and Analyze: Recursively scan the entire file and folder structure starting from the provided root directory.
+ Identify Key Artifacts: Pay close attention to configuration files (package.json, requirements.txt, pom.xml, Dockerfile, .eslintrc, prettierrc, etc.), READMEs, folder hierarchy, documentation files, and source code files.
+ Incorporate Contribution & Development Guidelines: Search for and parse any files related to development, testing, or contributions (e.g., CONTRIBUTING.md, DEVELOPMENT.md, TESTING.md). The instructions within these guides are critical
@jwynia
jwynia / retrospective.md
Last active July 13, 2025 19:38
Claude Code command for /retrospective that reviews a task for lessons learned in a context network project. Goes in /.claude/commands/retrospective.md

Context Network Retrospective Agent Prompt

Task Context

You are conducting a retrospective analysis after completing a task. Your goal is to identify what should be captured in the context network and what adjustments need to be made to existing documentation.

Critical Domain Boundary Reminder

Remember the distinction:

  • Context Network: Planning documents, architecture decisions, design discussions, implementation strategies
@burkeholland
burkeholland / prd.md
Created April 10, 2025 19:50
TheUrlist PRD

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
@ruvnet
ruvnet / MLFlow.ipynb
Last active June 20, 2025 19:48
MLflow and DSPy Tutorial for Beginners
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@Cikmo
Cikmo / README.md
Last active July 17, 2025 14:28
Connection handler that keeps Supabase Realtime channels alive. It automatically reconnects after errors, handles reauthentication, and more.

I had some issues getting a reliable connection up. Made this after a lot of experimentation and it now works well.

Includes how to keep the connection alive when the document is not visible, handles reconnecting on errors, and also fixes certain authentication issues when coming back to a document that has not been visible while the token expired.

To use it, you pass in a factory function for your RealtimeChannel. Do not call .subscribe() on the channel, the handler will do this for you. See example.

PS: If you're not using supabase-js you'll need to change stuff a bit. Instead of passing in SupabaseClient switch it to use RealtimeClient, and update the refreshSessionIfNeeded method to your authentication implementation.

If you see any problems or have suggestions for improvements, please leave a comment.

@GollyJer
GollyJer / app.config.ts
Last active December 9, 2024 14:15
app.config.ts
import { ConfigContext } from '@expo/config';
// eslint-disable-next-line no-console
// console.log('ENV', process.env);
// expands type in the vscode tooltip.
type ExpandTooltip<T> = T extends infer O ? { [K in keyof O]: O[K] } : never;
const EXPO_SDK = '51';
const BINARY_ITERATION_FOR_SDK = '1'; // start with 1. CAN NOT BE 0.
@LionelB5
LionelB5 / MockedLink.ts
Last active March 10, 2025 19:28
Apollo Client V3 link that supports mocking GraphQL subscriptions, mutations and queries. Particularly useful when testing components that rely on queries/mutations that execute concurrently to subscriptions that must be mocked.
@masonwolters
masonwolters / build-and-upload-simulator-binary.sh
Last active February 18, 2025 22:14
React native iOS with pre-built binaries
#
# This script is run in CI on master commits. It builds a debug binary
# for the iOS simulator and uploads it to the mobile-binaries repo.
#
# Then, when developer run `yarn ios` to develop locally, instead of
# having to build all of the native code, we just download the pre-built
# binary and install it on the simulator.
#
REPO_URL="{YOUR_GIT_URL}"