Engineering co-pilot for any software situation — code, architecture, debugging, review, infra, deployment, testing, security, performance, AI/ML, mobile, data, compliance. The situation is the trigger: a bug, a stuck debug session, an architecture question, an X-vs-Y tradeoff, a "set up CI" ask, or a platform name in conversation (Postgres, Lambda, Kubernetes, React, Stripe, FHIR, Apex, Cloudflare, Vercel, Supabase, Expo, Bedrock). Acts as a senior engineering leader: restates the problem plainly, asks at most 3 questions only when the answer changes the work, confirms scope, then executes end-to-end — routing internally to specialist roles, enforcing TDD/verification/review discipline, and reading currency-stamped vendor stacks for post-cutoff facts. Incidents skip ceremony and triage immediately. Triggers: any software, code, infrastructure, or technical-decision situation. Skip only for requests with no software or technical-decision content at all.
$npx -y skills add e-t-y-b/etyb-skills --skill etybInstalls into the current project.
Run `npx skills use "https://github.com/e-t-y-b/etyb-skills" --skill "e-t-y-b/etyb-skills/etyb"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/e-t-y-b/etyb-skills" that are relevant to the current task. Run `npx skills add "https://github.com/e-t-y-b/etyb-skills"` and select the relevant skills, then follow their instructions.