Skip to content

Instantly share code, notes, and snippets.

View Esl1h's full-sized avatar
🌎
Quem não tem cUrl, caça com get.

Esli Silva Esl1h

🌎
Quem não tem cUrl, caça com get.
View GitHub Profile
@Esl1h
Esl1h / CoC.md
Created March 28, 2025 13:51
Code of Adult Conduct

Code of Adult Conduct

1. Principle of Charity

When interacting with people around this project try to assume the best of them. If something seems offensive start by assuming you've misunderstood. Treat others as you would wish them to treat you.

2. Principle of Agency

We all possess the capacity to chose how we feel as well as how we react. Other people cannot "make" you feel bad or "hurt" your feelings unless you allow them to. Choose to take responsibility for your own mental state and exercise your agency. Do not give other people power over you that they do not have; the power to trigger you. You have the ability to ignore most anything. Use it.

@Esl1h
Esl1h / [NO]CODE_OF_CONDUCT.md
Last active March 28, 2025 14:01
No Code of Conduct

Contributor Code of Conduct

This project adheres to No Code of Conduct. We are all adults. We accept anyone's contributions. Nothing else matters.

For more information please visit the No Code of Conduct homepage.

@Esl1h
Esl1h / deploy.v
Last active April 5, 2025 22:31
deploy.vsh
#!/usr/bin/env -S v
// A linha cima associa pelo env o .vsh ao V
// Então basta dar permissão de execução (+x) executar o script .vsh no terminal
// como `./deploy.vsh`
// print command then execute it
fn sh(cmd string) {
println('❯ ${cmd}')
print(execute_or_exit(cmd).output)
@Esl1h
Esl1h / SRE_en.md
Created April 26, 2025 22:32
System Prompt for SRE, DevOps, Sysadmins and Engineers

You are an Artificial Intelligence assistant specialized in infrastructure operations, SRE, system administration, and DevOps. Your goal is to provide accurate, secure, and practical answers for professionals working in IT management, automation, monitoring, and troubleshooting.

General Guidelines:

  • Always prioritize security, best practices, and automation.
  • Be objective, clear, and avoid ambiguity.
  • When suggesting commands, scripts, or configurations, briefly explain what each part does.