svallejo-dev

Large-scale systems design, starting from what already exists or, without metrics, from the business archetype: system design sparring as a delta (AS-IS → TO-BE → migration) or a PoC plan, a parallel red team, capacity computed in code with scenarios and thresholds, DDD strategic design, business archetypes and a curated catalog of building blocks.

Diseño de sistemas a gran escala en español, partiendo de lo que ya existe o, sin métricas, del arquetipo del negocio: sparring de system design como delta (AS-IS → TO-BE → migración) o plan de PoC, red team en paralelo, capacidad calculada en código con escenarios y umbrales, diseño estratégico DDD, arquetipos de negocio y un catálogo curado de bloques.

Language-agnostic engineering workflow: glossary and ADRs, local specs and tickets, TDD, bug diagnosis, deep-module design, code review, commits and PRs. Delegates language-specific work to language plugins (go, ...). Based on mattpocock/skills (MIT).

General-purpose skills: where to start (workflow router and AGENTS.md template), grilling a plan, teaching with analogies, writing for agents, handoffs between sessions and research from primary sources. Adapted from mattpocock/skills (MIT).

Go domain: idiomatic Go (Go 1.26), design rules, tactical DDD in Go, behavior-preserving simplification (go-simplify, with go fix and modernizers) and the role skills the engineering plugin uses: go-review, go-testing, go-debugging and go-design.

Flujo de ingeniería en español y agnóstico al lenguaje: glosario y ADRs, specs y tickets locales, TDD, diagnóstico de bugs, diseño de módulos profundos, code review, commits y PRs. Delega lo específico de cada lenguaje en plugins de lenguaje (go, ...). Basado en mattpocock/skills (MIT).

QA separated from dev: acceptance criteria with a usage oracle, scenario design with ISTQB techniques, automation with existing tools (Gherkin, Hurl, Testcontainers, Toxiproxy, Pact, Schemathesis, Playwright), verification by rungs with traceability and an integrity seal, failure classification and bug injection to test the tests. The implementing agent never writes the oracle and QA never certifies.