Kod Ajanı Değişiklik Risk Raporu
Kod ajanının değişiklikten önce kapsam ve geri dönüş planı oluşturmasını sağlar.
308+ test edilmiş prompt şablonu; yazıdan koda, görsel üretiminden kariyere kadar. Değişkenleri ({böyle}) kendinize göre doldurup doğrudan kullanın.
Kod ajanının değişiklikten önce kapsam ve geri dönüş planı oluşturmasını sağlar.
Kod kalitesini ve güvenliğini sistematik olarak denetler.
Bir kod bloğunu güvenlik, performans ve okunabilirlik açısından yapılandırılmış şekilde inceler.
Wanted to share a skill I built for designing and reviewing the prompts that run AI agents. Most prompt engineering advice for agents still treats the system prompt as a text block: "write a clear role, add examples, be specific." That helps with a chat answer, but agents fail in ways text-block advice doesn't cover. I kept watching the same three failures: an agent with overla
Most people run general Claude for everything and never touch these. They're free, official, and each one loads Claude with the workflows an actual specialist in that field uses. The legal one is the standout. Install it, then: Review the attached contract. Flag every clause that deviates from standard terms, classify each risk as low, medium, high or critical, and generate red
https://daniele.tech/2026/09/linus-torvalds-skill-soul-or-how-i-distilled-the-knowledge-for-code-reviews-from-32k-emails/ A report about the changes after the first announcement and all the improvements, including Soul.md (with profanities), 4 different version Skill/Soul from 4 different LLMs, a comparison with/without skills and a reproducible pipeline. submitted by /u/Mte90
Hi everyone — I made this tiny macOS menu bar app to quickly edit and copy my daily prompts. I work as a software developer and I use a few prompts on a daily basis, so having this saves me a lot of time. Some examples of the prompts I commonly use: Create pull request Code quality & readability review (reduce AI bloat, comments, useless tests) Language simplification — give me
Junior product analyst at a fintech. Building the deck stopped being the hard part a while ago. The hard part is standing in the room when a VP asks the one question I did not think about. So before every review I run this on my own deck or summary. ``` You are a skeptical senior executive reviewing my analysis before I present it. Here is what I am presenting: {paste your key