Adam Kaminski thimslugga

Agent Guidelines for Rust Code Quality

This document provides guidelines for maintaining high-quality Rust code. These rules MUST be followed by all AI coding agents and contributors.

Your Core Principles

All code you write MUST be fully optimized.

"Fully optimized" includes:

name

generate-agents

description

Analyzes any project and scaffolds a complete .agents/ folder with AGENTS.md, sync script, and starter skills tailored to the detected tech stack. Use when bootstrapping AI agent configuration for a new or existing repository.

metadata

tags
meta, scaffolding

Generate .agents Folder

You are a meta-scaffolding expert. Analyze the project's codebase and produce a complete .agents/ folder that gives AI coding agents project-specific context, conventions, and reusable skills.

https://aiopsschool.com/blog/complete-codex-slash-commands-and-cli-options-guide-updated-april-2026/

https://github.com/Graphify-Labs/graphify

https://aiopsschool.com/blog/complete-graphify-guide-install-use-with-codex-and-claude-code-and-build-knowledge-graphs-for-ai-coding/

https://aiopsschool.com/blog/codex-is-using-bubblewrap-bwrap-for-coding-isolation-a-complete-guide/

https://github.com/aws-samples/sample-context-aware-ai-with-bedrock-mcp-server-and-kiro/tree/main

name

api-developer

description

Implement API endpoints following team conventions

skills

api-conventions

error-handling-patterns

Implement API endpoints. Follow the conventions and patterns from the preloaded skills.

You can scale a SQLite database to multiple GByte in size and many concurrent readers by applying the below optimizations.

Run these every time you connect to the db

(some are applied permanently, but others are reset on new connection)

pragma journal_mode = WAL;

Instead of writing directly to the db file, write to a write-ahead-log instead and regularily commit the changes. Allows multiple concurrent readers, and can significantly improve performance.

Installing Perfetto on Fedora and Amazon Linux 2023

On Fedora, the simplest path is sudo dnf install perfetto (official RPM, currently perfetto-49.0-1.fc42 and perfetto-49.0-5.fc45 in Rawhide), which installs traced, traced_probes, the perfetto CLI, and ready-made systemd units.
On Amazon Linux 2023, there is no perfetto package in the core repos or SPAL, so download the prebuilt tracebox from get.perfetto.dev (a single statically linked binary) or build from source.
For trace analysis on either distro, download the trace_processor wrapper from get.perfetto.dev or python3 -m pip install perfetto; the AL2023 glibc (exactly glibc-2.34-52.amzn2023) meets the prebuilt trace_processor_shell requirement (GLIBC_2.34) with zero headroom.
Trace visualization uses ui.perfetto.dev, which processes the trace entirely in your browser (nothing is uploaded unless you click "Share", which only works for Googlers); you can self-host the same UI on any static web server.

Instructions

The first file is the script to be run, which you can store in your home directory. The second file is the systemd unit file which goes in /etc/systemd/system. Make sure on line 6 it references the location of the first file, and that you run systemctl daemon-reload after editing the unit file.

To run the service automatically on boot, run sudo systemctl enable avahi-alias@[domain], followed by sudo systemctl start avahi-alias@[domain] to start it immediately.

	{
	"version": "0.2",
	"language": "en",
	"ignorePaths": [
	"node_modules/**",
	"binaries/**",
	".vscode-test/**",
	"assets/*",
	"dist/**",
	"out/**",

	# syntax=docker/dockerfile:1
	# Download, build, and run:
	# curl -fsSL https://gist.githubusercontent.com/nikarh/6381b3d43eb92b2479f06482fbf8e02f/raw/Dockerfile -o /tmp/Dockerfile && docker build --build-arg UID="$(id -u)" --build-arg GID="$(id -g)" --build-arg USERNAME="${USER:-dev}" -t agents:latest -f /tmp/Dockerfile /tmp && docker run --name agent -it -v "$(pwd):/workspace" -e GIT_AUTHOR_NAME="$(git config --get user.name)" -e GIT_AUTHOR_EMAIL="$(git config --get user.email)" -e GIT_COMMITTER_NAME="$(git config --get user.name)" -e GIT_COMMITTER_EMAIL="$(git config --get user.email)" agents:latest

	FROM archlinux:latest

	SHELL ["/bin/bash", "-o", "pipefail", "-c"]

	ARG UID=1000
	ARG GID=1000

	#!/usr/bin/env zsh
	# Multi-project worktree manager with Claude support
	#
	# ASSUMPTIONS & SETUP:
	# - Your git projects live in: ~/projects/
	# - Worktrees will be created in: ~/projects/worktrees/<project>/<branch>
	# - New branches will be named: <your-username>/<feature-name>
	#
	# DIRECTORY STRUCTURE EXAMPLE:
	# ~/projects/