anti-kaku
Skill1 starsChanged 51 days agoMITView on GitHub
Panduan menulis dan menyunting copy website, artikel blog, dokumentasi, atau teks apa pun dalam Bahasa Indonesia dan Bahasa Inggris (Bilingual ID-EN) agar tidak kaku (birokratis/robotik AI) sekaligus tidak terlalu santai (gaul/slang). Menghasilkan nada bahasa editorial modern yang lugas, bernas, berbobot, dan enak dibaca manusia (Smart Conversational / Modern Editorial).
In this repository6 other files it gives its agents.
- artikelgenSkill
- obscura-windowsSkill
- okfSkill
- pdf-inspector-windowsSkill
- tgrep-skillSkill
- translate-id-enSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 83
When writing or editing English copy, use this three-tier spectrum as your compass:
- Distinctive: line 127
Instead of *"utilize"* $\rightarrow$ use "use".
- Distinctive: line 128
Instead of *"facilitate"* $\rightarrow$ use "help" or "enable".
- Distinctive: line 129
Instead of *"expedite"* $\rightarrow$ use "speed up" or "quicken".
- Distinctive: line 130
Instead of *"comprehensive"* $\rightarrow$ use "complete" or "thorough".
- Distinctive: line 134
Keep capitalization disciplined: Avoid Title Case on body copy or excessive bolding across entire paragraphs.
- Distinctive: line 140
Before finalizing any copy or article in either language, run this quick 3-question audit:
- Distinctive: line 143
If a senior practitioner read this out loud to a colleague or client during a standup or presentation, would it sound natural and confident …
- Distinctive: line 147
If you strip out all the buzzwords, filler adjectives, and transitional fluff, does the sentence stand on its own feet with greater …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Anti-Kaku: Panduan Nada Suara Bernas dan Alami (Bilingual ID & EN)
Skill ini memandu penulisan dan penyuntingan teks dalam Bahasa Indonesia maupun Bahasa Inggris agar mencapai titik temu ideal: tidak kaku seperti birokrasi atau robot AI, tetapi juga tidak terlalu santai seperti obrolan tongkrongan.
Target nada suara (voice & tone): Profesional hangat, lugas, dan berbobot (Smart Conversational / Modern Editorial). Bayangkan tulisan seorang praktisi senior atau jurnalis majalah editorial bermutu (seperti Monocle, Stripe Docs, atau Linear Release Notes): bahasanya bersih, runut, nyaman dibaca, percaya diri, tanpa basa-basi birokratis, dan tanpa kata-kata gaul murahan.
🇮🇩 BAGIAN 1: PANDUAN BAHASA INDONESIA
🎯 Spektrum Tiga Tingkat: Menemukan Titik Temu
Saat menyunting atau membuat teks Bahasa Indonesia, gunakan spektrum tiga tingkat ini sebagai kompas:
| Konteks | ❌ Terlalu Kaku (Birokrasi / Robot AI) | ❌ Terlalu Santai (Gaul / Slang Tongkrongan) | ✅ Titik Temu Ideal (Lugas, Bernas, Profesional) |
| Deskripsi Nilai | "Guna merealisasikan optimalisasi efisiensi kerja tim..." | "Biar kerjaan tim lo makin sat-set dan nggak ribet..." | "Membantu tim Anda bekerja lebih cepat dan teratur." |
| Desain Antarmuka | "Menghubungkan pengguna dengan arsitektur sistem yang aksesibel..." | "Bikin web yang gampang banget dibuka siapa aja tanpa pusing..." | "Merancang antarmuka web yang terstruktur, ringan, dan nyaman digunakan siapa saja." |
| Pendidikan & Belajar | "Pemberdayaan talenta lokal dalam rangka akselerasi transformasi digital daerah." | "Bikin anak-anak muda lokal makin jago ngoding biar daerahnya maju..." | "Membuka ruang belajar bagi talenta lokal untuk membangun teknologi di daerahnya sendiri." |
| Prinsip Kerja | "Setiap komponen kode diimplementasikan secara komprehensif tanpa redundansi." | "Tiap tombol dan kodingan beneran ada fungsinya, bukan cuma tempelan doang." | "Setiap baris kode dan komponen visual dirancang dengan fungsi yang jelas, bukan sekadar pelengkap." |
| Panggilan / Ajakan | "Pihak kami senantiasa membuka peluang kerjasama strategis..." | "Yuk ngobrol santai sambil ngopi kalau ada ide seru..." | "Pintu kami selalu terbuka untuk berdiskusi atau memulai kolaborasi baru." |
🚫 Ciri-Ciri yang Wajib Dihindari (Bahasa Indonesia)
1. Zona Terlalu Kaku (Birokrasi & Slop AI)
- Tumpukan Nominalisasi (pe-...-an, ke-...-an): "Melakukan pemanfaatan sistem pendataan..." (Ubah jadi kata kerja aktif: "Memanfaatkan sistem pendataan...").
- Jargon Proposal Hibah / LPJ: "Dalam rangka", "guna mendukung", "optimalisasi", "sinergi", "akselerasi", "solusi tepat guna", "persoalan riil".
- Kalimat Pasif Berjarak Tanpa Pelaku: "Seluruh berkas telah diselesaikan pengunggahannya oleh pihak pengembang." (Ubah aktif: "Tim kami telah mengunggah seluruh berkas.").
- Pembuka Klise AI: "Dalam era digital yang serba cepat ini...", "Di tengah pesatnya perkembangan teknologi...".
2. Zona Terlalu Santai (Overcorrection / Gaul Tongkrongan)
- Partikel dan Slang Percakapan Non-Baku: "Beneran", "banget", "nggak ribet", "makin jago", "ngoding", "sat-set", "gaspol", "cuan", "doang", "nih", "dong", "kan".
- Kata Ganti Informal Tanpa Kesepakatan: Menggunakan "lo-gue" atau gaya percakapan media sosial yang kekanak-kanakan untuk konteks profesional.
- Kalimat Lepas yang Mengabaikan Kaidah: Menulis kalimat tanpa struktur subjek-predikat yang jelas dengan alasan "biar santai".
🛠️ Aturan Praktis Menulis Bahasa Indonesia yang Bernas
- Ubah Kata Benda Abstrak Menjadi Kata Kerja Nyata:
- Kaku: "Pengoptimalan performa aplikasi menghasilkan peningkatan retensi pengguna."
- Terlalu Santai: "Aplikasi dibikin kenceng biar user betah."
- Bernas: "Aplikasi yang cepat dan responsif membuat pengguna betah bertahan."
- Pertahankan Kalimat Aktif dengan Pelaku Jelas:
- Kaku: "Perubahan sistem telah diterapkan demi kenyamanan pembaca."
- Bernas: "Kami memperbarui sistem agar Anda membaca dengan lebih nyaman."
- Variasikan Ritme dan Panjang Kalimat (Sentence Cadence):
- Selingi kalimat panjang penjelas dengan kalimat pendek penegas.
- Contoh: "Menata tipografi bukan sekadar memilih rupa huruf yang cantik. Di balik setiap jarak baris dan ukuran teks, ada pertimbangan keterbacaan yang matang. Sederhana, tetapi berdampak besar."
- Gunakan Kosakata Sehari-Hari yang Tetap Tertib:
- Alih-alih "mengakselerasi" (kaku) atau "ngebutin" (santai) $\rightarrow$ gunakan "mempercepat".
- Alih-alih "mengeliminasi friksi" (kaku) atau "ngilangin ribet" (santai) $\rightarrow$ gunakan "mempermudah" atau "meringkas alur".
- Alih-alih "komprehensif" (kaku) atau "lengkap banget" (santai) $\rightarrow$ gunakan "menyeluruh" atau "lengkap".
- Jaga Kebersihan Teks (Anti-Slop Protocol):
- Hindari tanda em dash (
—): Ganti dengan koma, titik dua, tanda kurung, atau titik pemisah kalimat. - Hindari emoji berlebihan: Jangan gunakan emoji di judul heading (
##) atau label resmi. - Pertahankan istilah teknis yang baku: Istilah domain spesifik seperti Nuxt, Flutter, API, SSR, grid layout tidak perlu dipaksakan diterjemahkan jika komunitas teknis terbiasa menggunakannya dalam bahasa asli.
- Hindari tanda em dash (
🇬🇧 PART 2: ENGLISH LANGUAGE GUIDELINES
🎯 The Three-Tier Spectrum: Finding the Sweet Spot
When writing or editing English copy, use this three-tier spectrum as your compass:
| Context | ❌ Overly Stiff (Corporate AI Slop) | ❌ Overly Casual (Juvenile Slang / Slack Chatter) | ✅ Sweet Spot (Smart Conversational / Modern Editorial) |
| Value Proposition | "In order to facilitate the optimization of team productivity paradigms..." | "So your team can crush tasks super duper fast without any headaches..." | "Helping your team work faster and stay organized." |
| Interface Design | "Empowering seamless visual architectures for enhanced stakeholder interactions..." | "Making cool screens so folks don't get lost clicking stuff..." | "Designing clean, responsive interfaces that feel natural to use." |
| Education & Learning | "Facilitating the pedagogical transformation of localized demographic cohorts..." | "Teaching kids to hack code so they make big bucks..." | "Opening practical avenues for students to solve real problems with technology." |
| Engineering Principles | "Leveraging state-of-the-art composable paradigms without architectural redundancy..." | "Slapping in clean widgets so the build looks fresh..." | "Writing clean, purposeful code where every module serves a clear function." |
| Call to Action | "Our enterprise maintains continuous readiness for strategic partnerships..." | "Hit me up bro, let's grab coffee and chat about cool stuff..." | "Always open to exploring new ideas, feedback, or collaborations." |
🚫 Forbidden Zones (English)
1. The Robotic AI & Corporate Fluff Zone (STRICTLY FORBIDDEN)
- Banned AI Openers: "In today's fast-paced digital world...", "In the ever-evolving landscape of...", "In recent years, technology has revolutionized...".
- Meta-Talk and Padded Filler: "Let's delve into...", "Dive deep into...", "It is important to remember that...", "Needless to say...", "At the end of the day...".
- Empty Corporate Buzzwords: "Game-changer", "revolutionize", "tapestry", "beacon of", "crucial role", "harness the power of", "paradigm shift", "seamless synergy".
- Robotic Transitions: Overusing "Furthermore,", "Moreover,", "Additionally,", or "In conclusion," at every section transition. Connect paragraphs through logic, questions, or narrative momentum instead.
- Distant Passive Voice: "A resolution was implemented by the engineering department." (Change to active: "Our engineers fixed the issue.").
2. The Overly Casual & Juvenile Slang Zone (STRICTLY FORBIDDEN)
- Juvenile Slang: "Super duper", "bro", "cray-cray", "crushing it", "hacks", "vibes", "legit", "freaking".
- Sloppy Fragments: Writing incomplete sentences that lack proper subject-verb structure under the guise of being "chill".
- Excessive Exclamation Marks: Stacking exclamation points (
!!) or using them to fake enthusiasm.
🛠️ Practical English Editorial Rules
- Turn Abstract Nouns into Active Verbs (Kill Nominalization):
- Stiff: "The implementation of server-side caching produced an acceleration in page delivery."
- Too Casual: "Caching made the web run crazy fast."
- Modern Editorial: "Server-side caching cut our page load times in half."
- Maintain Active Voice with Clear Subjects:
- Stiff: "Architectural modifications were deployed to enhance user retention."
- Modern Editorial: "We refined the interface so visitors can navigate without friction."
- High Burstiness and Varied Sentence Cadence:
- Mix short, punchy 3-to-6 word statements with longer, flowing explanations.
- Example: "Typography is never just about aesthetics. Behind every font weight and line height lies a deliberate choice about how people read. Clean, functional, and durable."
- Choose Confident, Everyday Vocabulary over Pseudo-Academic Jargon:
- Instead of "utilize" $\rightarrow$ use "use".
- Instead of "facilitate" $\rightarrow$ use "help" or "enable".
- Instead of "expedite" $\rightarrow$ use "speed up" or "quicken".
- Instead of "comprehensive" $\rightarrow$ use "complete" or "thorough".
- Clean Punctuation (Anti-Slop Protocol):
- Strictly avoid em dashes (
—): Replace with colons, commas, parentheses, or separate sentences. - Keep capitalization disciplined: Avoid Title Case on body copy or excessive bolding across entire paragraphs.
- Strictly avoid em dashes (
📋 The 3-Step Self-Audit (Both Languages)
Before finalizing any copy or article in either language, run this quick 3-question audit:
- The Spoken Reality Test:
- If a senior practitioner read this out loud to a colleague or client during a standup or presentation, would it sound natural and confident (neither like an official press release nor a sloppy group chat)?
- The Action Clarity Test:
- Does the reader immediately understand who did what, why it happened, and what practical benefit it brings?
- The Word Density Test:
- If you strip out all the buzzwords, filler adjectives, and transitional fluff, does the sentence stand on its own feet with greater authority? If yes, keep it lean.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

