Skill four-elements
✓ VerificadoProporciona 24 principios de ingeniería categorizados en cuatro elementos para guiar la toma de decisiones durante la refactorización, la depuración y el diseño arquitectónico.
- Estrellas en GitHub
- 113
- Archivos
- 25
- Último commit
- 1 nov 2026
- Licencia
- MIT
- Herramientas permitidas
- —
¿Qué hace la skill four-elements?
Proporciona 24 principios de ingeniería categorizados en cuatro elementos para guiar la toma de decisiones durante la refactorización, la depuración y el diseño arquitectónico.
Resumen generado a partir del SKILL.md de la skill.
Sobre la skill four-elements
Este SKILL permite a desarrolladores y agentes de IA guiar sus decisiones de ingeniería mediante principios estructurados. Ofrece veinticuatro principios distintos organizados en cuatro categorías elementales: Aire, Agua, Tierra y Fuego. Un agente debe cargar este SKILL cuando necesite refactorizar código, depurar sistemas complejos, diseñar nuevas arquitecturas o gestionar la deuda técnica.
Mediante la consulta de principios específicos, un agente puede determinar si debe restar complejidad, adaptarse a nuevos requisitos, mantener la estabilidad mediante la disciplina o impulsar el progreso a través de la ejecución. El SKILL se basa en un conjunto de referencias en markdown que definen cada principio en detalle. Cuando un agente aplica un principio a una tarea, genera una decisión razonada que nombra el principio específico utilizado y explica cómo ese principio cambió la elección técnica. Este enfoque ayuda a evitar errores comunes como añadir abstracciones innecesarias, no encontrar las causas raíz durante la depuración o saturar la ventana de contexto durante sesiones largas.
Lo que un agente puede hacer con ella
- 1Refactorización y reducción de complejidadUn agente puede usar los principios de Aire para decidir si debe añadir una nueva abstracción o simplemente eliminar código muerto.
- 2Depuración y análisis de causa raízCuando múltiples correcciones fallan, el agente puede aplicar el principio de atacar la premisa subyacente.
- 3Diseño de estructuras de datos robustasLos desarrolladores pueden usar los principios de Tierra para asegurar que los estados ilegales sean imposibles dentro de sus sistemas de tipos.
Escrito a partir del SKILL.md de la skill. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar la skill four-elements
Cada comando copia la carpeta de la skill al directorio de skills del cliente. Reinicia el cliente o inicia una nueva sesión para cargarla.Instalar la skill four-elements en Plugin
/plugin marketplace add tmcfarlane/team-avatar /plugin install team-avatar@team-avatar
Instalar la skill four-elements en Claude Code
~/.claude/skills/four-elements/SKILL.md
$ npx degit tmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements ~/.claude/skills/four-elementsInstalar la skill four-elements en Claude Code (project)
.claude/skills/four-elements/SKILL.md
$ npx degit tmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements .claude/skills/four-elementsInstalar la skill four-elements en Codex
~/.agents/skills/four-elements/SKILL.md
$ npx degit tmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements ~/.agents/skills/four-elementsInstalar la skill four-elements en Gemini CLI
~/.gemini/skills/four-elements/SKILL.md
$ npx degit tmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements ~/.gemini/skills/four-elementsInstalar la skill four-elements en 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
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Superó nuestras comprobaciones automáticas. No es una auditoría de seguridad: lee los scripts antes de dejar que un agente los ejecute. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibletmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements is public and reachablegithub.com/tmcfarlane/team-avatar/tree/HEAD/plugins/team-ava ↗Aprobado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit 2026-11-01github.com/tmcfarlane/team-avatar/commits ↗Aprobado
- Sin descargar y ejecutar ni robo de credenciales en los scriptsNo scripts in the skill folderAprobado
- Sin instrucciones ocultas en SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/tmcfarlane/team-avatar/blob/HEAD/plugins/team-ava ↗Aprobado
- Las herramientas preaprobadas están acotadasNo pre-approved tools; the agent asks before using onegithub.com/tmcfarlane/team-avatar/blob/HEAD/plugins/team-ava ↗Aprobado
- SKILL.md sigue el formato de Agent SkillsValid name and description; says when to use it; 55 linesgithub.com/tmcfarlane/team-avatar/blob/HEAD/plugins/team-ava ↗Aprobado
SKILL.md
Ver en 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.
Archivos de esta skill
25Preguntas sobre la skill four-elements
¿Cómo instalo la skill four-elements en Claude Code?
Ejecuta npx degit tmcfarlane/team-avatar/plugins/team-avatar/skills/four-elements ~/.claude/skills/four-elements. Claude Code carga las skills desde ~/.claude/skills (todos los proyectos) o .claude/skills (un proyecto) y usa una skill cuando su descripción coincide con la tarea.
¿Qué clientes pueden usar la skill four-elements?
Cualquier cliente que lea el formato Agent Skills: Claude Code, Codex, Gemini CLI y claude.ai (subir como ZIP). Los scripts de la skill se ejecutan solo donde el cliente permite la ejecución de código.