David Teren davidteren

This is a desktop application built with Phoenix LiveView and packaged with Tauri for native macOS/Windows/Linux distribution.

Project guidelines

Use mix precommit alias when you are done with all changes and fix any pending issues
Use the already included and available :req (Req) library for HTTP requests, avoid :httpoison, :tesla, and :httpc. Req is included by default and is the preferred HTTP client for Phoenix apps

Phoenix v1.8 guidelines

Always begin your LiveView templates with <Layouts.app flash={@flash} ...> which wraps all inner content

Webpacker to Vite Migration: A Phased Approach

!NOTE: this guide currently only covers the first phase. The Vite setup and migration are not detailed here.

Overview

This guide documents our approach to migrating from Webpacker to a modern frontend asset pipeline. We implemented a phased strategy:

Phase 1 (Current): Replace Webpacker with CDN-based resources
Phase 2 (Future): Migrate to Vite for a modern build system

Rules for LLM Agentic Coding in Docker Containerization Projects

1. Container Architecture Patterns

Follow the Established Pattern: Always respect the established architecture patterns across services (Dockerfile, entrypoint script, management script).
Separate Concerns: Keep build-time operations in Dockerfile, initialization in entrypoint scripts, and user operations in management scripts.
Delegate Appropriately: Entrypoint scripts should handle environment initialization; management scripts should provide a clean interface.
Minimize Verbosity: Management scripts should be concise in output; verbose operations belong in entrypoint scripts.

2. Environment Detection & Configuration

Use Defaults Wisely: Always provide sensible defaults for environment variables.
Check Dependencies: Explicitly check for required dependencies (database, Redis, other services).
Respect Technology Specifics: Recognize and accommodate technology-specific patterns (rake vs rails, Nod

Model Context Protocol (MCP) Servers Configuration Guide

Common Server Setup

All MCP servers follow a basic configuration pattern:

import { Server } from "@modelcontextprotocol/sdk/server/index.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";

const server = new Server({

Model Context Protocol (MCP) Servers Quick Reference

Filesystem Server

Provides filesystem operations within allowed directories.

Tool	Description	Required Parameters
`read_file`	Read complete file contents	`path` (string)
`read_multiple_files`	Read multiple files at once	`paths` (string[])
`write_file`	Create/overwrite file	`path` (string), `content` (string)

Role: Expert Ruby on Rails Assistant Guidelines v0.1.3

You are an Expert Ruby on Rails engineer with over 15 years of experience. Your role is to assist developers with Ruby on Rails projects, providing expert guidance, code reviews, and solutions to complex problems.

Traits:

You have over 15 years of experience building scalable, maintainable Rails applications with a deep understanding of the framework and its ecosystem.
You practice the Rails way and Test-Driven Development with an emphasis on Boring Rails concepts and leverage object-oriented programming, with SOLID principles, as well as other design principles to ensure extendable, clean and well-tested code with meaningful tests.
You prefer using dependency injection and do your best to not introduce any tight coupling or unnatural indirection.
You use your vast and in-depth knowledge to leverage the Ruby & Rails internals and apply these where relevant in responses and solutions.

Prompt: Analyze and Test Ruby on Rails Code with RSpec

Task Description:

You have been given a Ruby on Rails code snippet. Your task is to analyze the code, identify key functionalities, and outline RSpec tests that should be written to ensure the code performs as expected under various conditions. The goal is to achieve thorough test coverage, catching any potential bugs and ensuring code quality.

Code Snippet:

# Please insert the given Ruby on Rails code here

	#!/bin/bash
	# GitHub Label Configuration Script
	# Creates comprehensive label system with color psychology and workflow organization
	# Based on search results best practices
	git_hub_label_configuration_script
	# --------------------------
	# Core Issue Types
	# --------------------------
	# Bug - Critical system failures (Red for urgency)
	gh label create bug --color d93f0b --description "System malfunction or error" --force

	#!/usr/bin/env ruby

	require 'open3'
	require 'signal'
	require 'openai'

	# Define the silence threshold and duration for detection
	@silence_threshold = '-30dB'
	@silence_duration = 0.5

	class TailwindClassBuilder
	include ActionView::Helpers::TagHelper

	def button_classes(options)
	button_type = options.delete(:button_type) { :button }

	class_names(
	# general classes
	"mt-4 px-1 sm:px-3 py-sm sm:py-1 font-semibold bg-transparent border rounded",
	case button_type