Skill four-elements
✓ VerifiedMenyediakan 24 prinsip engineering yang dikategorikan ke dalam empat elemen untuk memandu pengambilan keputusan saat melakukan refactoring, debugging, dan desain arsitektur.
- Bintang GitHub
- 113
- File
- 25
- Commit terakhir
- 1 Nov 2026
- Lisensi
- MIT
- Tool yang diizinkan
- —
Apa fungsi skill four-elements?
Menyediakan 24 prinsip engineering yang dikategorikan ke dalam empat elemen untuk memandu pengambilan keputusan saat melakukan refactoring, debugging, dan desain arsitektur.
Ringkasan dibuat dari SKILL.md skill ini.
Tentang skill four-elements
Skill ini memungkinkan developer dan AI agent untuk memandu keputusan engineering melalui prinsip-prinsip yang terstruktur. Skill ini menyediakan dua puluh empat prinsip berbeda yang disusun ke dalam empat kategori elemen: Air, Water, Earth, dan Fire. Seorang agent sebaiknya memuat skill ini saat perlu melakukan refactor code, debugging sistem yang kompleks, mendesain arsitektur baru, atau mengelola technical debt.
Dengan menggunakan lookup prinsip yang spesifik, agent dapat menentukan apakah harus mengurangi kompleksitas, beradaptasi dengan requirement baru, menjaga stabilitas melalui disiplin, atau mendorong progres melalui eksekusi. Skill ini mengandalkan sekumpulan referensi markdown yang mendefinisikan setiap prinsip secara mendalam. Saat agent menerapkan sebuah prinsip pada suatu task, ia akan menghasilkan keputusan yang beralasan dengan menyebutkan prinsip spesifik yang digunakan dan menjelaskan bagaimana prinsip tersebut mengubah pilihan teknisnya. Pendekatan ini membantu mencegah kesalahan umum seperti menambahkan abstraksi yang tidak perlu, gagal menemukan root cause saat debugging, atau membuat context window membengkak selama sesi yang panjang.
Apa yang bisa dilakukan agent dengannya
- 1Refactoring dan mengurangi kompleksitasAgent dapat menggunakan prinsip Air untuk memutuskan apakah akan menambah abstraksi baru atau sekadar menghapus dead code.
- 2Debugging dan root cause analysisKetika beberapa perbaikan gagal, agent dapat menerapkan prinsip menyerang premis yang mendasarinya.
- 3Mendesain struktur data yang robustDeveloper dapat menggunakan prinsip Earth untuk memastikan bahwa state yang ilegal tidak mungkin terjadi di dalam type system mereka.
Ditulis dari SKILL.md milik skill tersebut. Setiap use case diverifikasi dengan kutipan darinya.
Cara install skill four-elements
Setiap perintah menyalin folder skill ke direktori skills client. Restart client atau mulai sesi baru untuk memuatnya.Install skill four-elements di Plugin
/plugin marketplace add tmcfarlane/team-avatar /plugin install team-avatar@team-avatar
Install skill four-elements di Claude Code
~/.claude/skills/four-elements/SKILL.md
$ npx degit tmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements ~/.claude/skills/four-elementsInstall skill four-elements di Claude Code (project)
.claude/skills/four-elements/SKILL.md
$ npx degit tmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements .claude/skills/four-elementsInstall skill four-elements di Codex
~/.agents/skills/four-elements/SKILL.md
$ npx degit tmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements ~/.agents/skills/four-elementsInstall skill four-elements di Gemini CLI
~/.gemini/skills/four-elements/SKILL.md
$ npx degit tmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements ~/.gemini/skills/four-elementsInstall skill four-elements di Claude.ai
npx degit tmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements four-elements && zip -r four-elements.zip four-elements # claude.ai → Customize → Skills → + → Create skill → Upload a skill → four-elements.zip
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos cek otomatis kami. Ini bukan audit keamanan: baca skripnya sebelum membiarkan agent menjalankannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkautmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements is public and reachablegithub.com/tmcfarlane/team-avatar/tree/HEAD/plugins/team-ava ↗Lolos
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit 2026-11-01github.com/tmcfarlane/team-avatar/commits ↗Lolos
- Skrip tanpa unduh-lalu-jalankan atau pencurian kredensialNo scripts in the skill folderLolos
- Tidak ada instruksi tersembunyi di SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/tmcfarlane/team-avatar/blob/HEAD/plugins/team-ava ↗Lolos
- Tool yang diizinkan otomatis dibatasiNo pre-approved tools; the agent asks before using onegithub.com/tmcfarlane/team-avatar/blob/HEAD/plugins/team-ava ↗Lolos
- SKILL.md mengikuti format Agent SkillsValid name and description; says when to use it; 55 linesgithub.com/tmcfarlane/team-avatar/blob/HEAD/plugins/team-ava ↗Lolos
SKILL.md
Lihat di GitHubThe four elements
Each element is a stance. Read the element the moment calls for. Each bullet names when its principle applies and links the principle in full.
Read the linked reference in full before you apply a principle. In your reply, name each principle that shaped a decision and the specific choice it changed. Cite only principles whose reference you read this session.
Air: subtract
The Air Nomads carry nothing they do not need. Lightness is the discipline.
- Laziness Protocol. Refactoring, sizing a diff, or tempted to add abstractions, layers, or signal threading. Make the smallest change that solves it, and give a repeated decision one source of truth.
- Subtract Before You Add. Sequencing an addition, refactor, or rewrite. Delete dead code, stale flags, and speculative guards first. Design for observed usage. Then build on the simpler base.
- Minimize Reader Load. Reviewing or shaping code that is hard to trace. Count layers and hidden state, inline one-caller wrappers, and shrink mutable scope.
- Attack the Premise. Two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before another fix. Aang found a third option when everyone said there were two.
- Experience First. Product, UX, or feature-scope tradeoffs. Choose user delight over implementation convenience. Ship fewer, polished features.
- Exhaust the Design Space. A novel interaction or architectural decision with no precedent. Build two or three competing prototypes with
scouting-flightand compare before committing.
Water: adapt
Water takes the shape of what holds it and still finds the lowest point.
- Foundational Thinking. Before writing logic. Get the core types and data structures right, do scaffold before features, and ask what concurrent actors share.
- Model the Domain. Stateful logic, or code that branches a lot or repeats a shape assumption across files. Encode the domain in a state machine, typed model, table, reducer, or the right collection instead of scattered conditionals.
- Redesign from First Principles. A new requirement arrives for an existing design. Design as if it had been there from day one. Do not bolt it onto the side.
- Fix Root Causes. Debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
- Make Operations Idempotent. Commands, lifecycle steps, or loops that run amid crashes and retries. Converge to the same end state when run twice or resumed after a crash.
- Migrate Callers Then Delete Legacy APIs. A new internal API while old callers exist. Move every caller and delete the old path in the same wave.
Earth: hold
Earthbenders wait and listen, then strike once. Stability comes from what you have verified.
- Boundary Discipline. Wiring validation, error handling, or framework adapters. Validate and parse at the edges (CLI, config, network, external APIs). Inside, trust the types and keep business logic pure.
- Type System Discipline. Designing types or a signature in a typed language. Make illegal states unrepresentable, brand primitives that mean different things, and derive types from the schema that owns the shape.
- Separate Before Serializing Shared State. Concurrent actors might write the same file, branch, key, or object. Give each its own write target first. Lock only when one shared writer is a real invariant.
- Prove It Works. After a task, before declaring done. Check the real artifact directly. A proxy, a cached screenshot, and an agent's report are not proof.
- Test Behavior, Not Implementation. Writing, changing, or keeping a test. Assert what a caller can observe, so the test fails when behavior breaks and passes when only internals change.
- Explain the Number. Before you trust, report, or act on a measured speedup, regression, latency, or eval score. Find what limits it and rule out that it measured something else.
Fire: drive
Iroh taught that fire is life, not destruction. Its source is breath, not rage.
- Outcome-Oriented Execution. Planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture. Do not preserve throwaway compatibility states.
- Never Block on the Human. Tempted to ask "should I do X?" on reversible work. Do it, show the result, and let them correct course. Save questions for product and preference calls.
- Build the Lever. Any non-trivial work. Write the script, codemod, generator, or shared brief that does or proves it. The tool is the artifact a reviewer can rerun.
- Sequence Work into Verifiable Units. Multi-step work and how you stack commits and PRs. Each step ends in a check, verified before the next. Land a failing test before its fix.
- Encode Lessons in Structure. You catch yourself writing the same instruction a second time. Turn it into a lint, a flag, a runtime check, or a script instead of more text.
- Guard the Context Window. Context fills with large outputs, long files, repeated reads, or fan-out planning. Route bulk reading to a dispatched character. Keep summaries, not dumps, in the main thread.
Berkas dalam skill ini
25Pertanyaan seputar skill four-elements
Bagaimana cara install skill four-elements di Claude Code?
Jalankan npx degit tmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements ~/.claude/skills/four-elements. Claude Code memuat skill dari ~/.claude/skills (semua proyek) atau .claude/skills (satu proyek) dan menggunakan skill saat deskripsinya cocok dengan tugas.
Client mana saja yang bisa menggunakan skill four-elements?
Client apa pun yang membaca format Agent Skills: Claude Code, Codex, Gemini CLI, dan claude.ai (unggah sebagai ZIP). Script dalam skill hanya berjalan di client yang mengizinkan eksekusi kode.