Felipe Coury fcoury

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

System Prompt

Identity

You are Kiro, an AI assistant and IDE built to assist developers.

When users ask about Kiro, respond with information about yourself in first person.

You are managed by an autonomous process which takes your output, performs the actions you requested, and is supervised by a human user.

You talk like a human, not like a bot. You reflect the user's input style in your responses.

Building Your Own MCP Server for Claude Code

This guide will walk you through creating a custom MCP (Model Context Protocol) server that integrates with Claude Code, allowing you to extend Claude's capabilities with external tools, APIs, or even other AI models.

What is MCP?

MCP (Model Context Protocol) is a protocol that allows Claude to communicate with external servers to access tools and capabilities beyond its built-in features. Think of it as a plugin system for Claude.

Prerequisites

From `init.lua` to `default.nix`

In a previous post I explained how to manage Neovim plugins with Nix and Home Manager. In this post I want to go further and show how to migrate Neovim configuration from ~/.config/nvim to ~/.config/home-manager entirely. The end result will be to split our Neovim setup into multiple modules that colocate plugin sourcing and configuration.

If you haven't read the post linked above, do so now. We will assume the

Manage Neovim plugins (and more!) with Nix and Home Manager

Highly extensible software like Emacs, Vim, and Neovim tend to grow their own package managers. A software developer, for example, might want to install editor plugins that hook into a particular programming language's linter or language server. The programmer's text editor is therefore extended to support managing additional software to extend the text editor. If this loop continues for too long, the programmer's editor becomes more delicate and complex. The remedy for this problem is to manage software using dedicated tools apart

Install the toolchain

brew tap SergioBenitez/osxct
brew install x86_64-unknown-linux-gnu

this should get installed in:

/opt/homebrew/Cellar/x86_64-unknown-linux-gnu/

Installing the macOS OpenSSL - if not already installed

	#!/bin/bash

	# Read the JSON input from stdin
	input=$(cat)

	# Extract the cwd from the JSON
	if command -v jq &> /dev/null; then
	cwd=$(echo "$input" \| jq -r '.cwd')
	# If cwd is empty or null, use workspace_roots[0] as fallback
	if [ -z "$cwd" ] \|\| [ "$cwd" == "null" ]; then

	# /etc/nixos/configuration.nix
	{ config, pkgs, ... }:

	{
	imports =
	[
	./hardware-configuration.nix
	];

	boot.loader.systemd-boot.enable = true;

	{
	config,
	pkgs,
	lib,
	inputs,
	...
	}: let
	ipu6-camera-bin = with pkgs;
	stdenv.mkDerivation rec {
	pname = "ipu6-camera-bin";

	[package]
	name = "testcontainers-sample"
	version = "0.1.0"
	edition = "2021"

	[dev-dependencies]
	async_once = "0.2.6"
	aws-sdk-s3 = "0.28.0"
	ctor = "0.2.4"
	lazy_static = "1.4.0"