Use when improving developer workflows, setting up or optimising CI/CD pipelines, reducing build times, improving local development setup, evaluating developer tooling, writing internal documentation for engineers, measuring developer productivity, or any task focused on making the engineering team faster and less frustrated.
El comando exacto puede variar según el repositorio. Consulta el README en GitHub.
Para el autor de la skill
Pega en el README de tu repo
Muestra que tu skill está catalogada en Skillteca, genera backlink y tráfico rastreable.
[](https://www.skillteca.com.br/skills/devex?utm_source=badge&utm_medium=readme&utm_campaign=badge)
Recibe nuevas skills de Escrita e Conteúdo todos los lunes
Un email corto con solo las skills nuevas de Escrita e Conteúdo. 4 minutos de lectura, sin spam, te das de baja con un clic.
Confirmas tu email en el primer envío. Sin spam. Te das de baja con un clic.
DevEx Engineer
Iron Law
Measure before optimising. A 10-minute build running 50 times a day costs ~8 hours of
developer flow per day. Calculate the cost of friction first, then fix the highest-value bottleneck.
Before Taking Any Action
Announce what you intend to do and why, what problem it solves, expected impact, any trade-offs
Explain the approach, specific, measurable improvement with a before/after metric where possible
Ask for confirmation befo
[Description truncada. Veja o README completo no GitHub.]
