All ideas/devtools/Una plataforma SaaS para gestión automatizada y colaborativa de runbooks de auditoría de UI que facilite la creación, revisión y mantenimiento de invariantes de diseño con trazabilidad y control de versiones.

GitHubB2Bdevtools

Una plataforma SaaS para gestión automatizada y colaborativa de runbooks de auditoría de UI que facilite la creación, revisión y mantenimiento de invariantes de diseño con trazabilidad y control de versiones.

Scouted 6 hours ago

6.5/ 10

Overall score

Turn this signal into an edge

We help you build it, validate it, and get there first.

Go from idea to plan: who buys, what MVP to launch, how to validate it, and what to measure before spending months.

Extra context

Learn more about this idea

Get a clearer explanation of what the opportunity means, the current problem behind it, how this idea solves it, and the key concepts involved.

Score breakdown

Urgency7.0

Market size6.0

Feasibility8.0

Competition5.0

Pain point

La dificultad para mantener y evolucionar un conjunto de invariantes de diseño en la página principal sin perder conocimiento institucional ni aumentar la carga de mantenimiento.

Who'd pay for this

Equipos de desarrollo y diseño de software, especialmente aquellos responsables de la calidad visual y la auditoría UI en empresas tecnológicas medianas y grandes.

Source signal

"Runbook codifies when to add, when to remove, and how to author."

Original post

Runbook: evolving home-page invariants as design changes (QA-10.3)

Published: 6 hours ago

Repository: how-do-i-ai/how-do-i-ai.github.io Author: alexey-pelykh > Driving decision: [PDR-007 § Consequences — baseline maintenance burden](../hq/docs/decisions/PDR-007-ui-audit-strategy.md). See [audit-tooling-design.md § 6 Item 14](../hq/docs/website/audit-tooling-design.md). ## Context QA-10.3's MVP invariant set is 3-5 home-page assertions. As design evolves intentionally (new PDR, new design token, new page type), the invariant set must evolve — but undisciplined edits to the invariant set defeat the purpose (institutional knowledge persistence). Runbook codifies when to add, when to remove, and how to author. ## Acceptance Criteria - [ ] Create `tests/audit/INVARIANTS-RUNBOOK.md` with: - [ ] **\"When to add an invariant\"** section: new PDR/design decision; new failure class discovered during review or in production; new page type enters canonical surface set. - [ ] **\"When to remove an invariant\"** section: PDR supersession ONLY. \"Inconvenience,\" \"noise,\" or \"hard to maintain\" are NOT valid reasons. Deprecation goes through PR review with a referenced PDR. - [ ] **\"How to author\"** section: prefer boolean geometric predicates over pixel-exact measurements (Linux-parity constraint per design doc § 2.3); colocate selectors in `tests/audit/selectors.ts`; name invariants with the PDR/REQ that justifies them (e.g., `invariant_pillar_nav_overlap_PDR_006_C6`). - [ ] **\"PR review checklist\"** section: invariant named against a referenceable decision; selector reused from `selectors.ts` or added there with justification; boolean assertion; expected failure mode documented. - [ ] Cross-link from `tests/visual/README.md` (distinguishing audit vs regression — Item 9, #issue). - [ ] Runbook is the authoritative reference from the PR template for invariant changes. - [ ] At least one worked example: adding a new invariant for a hypothetical new design token. ## Dependencies - **Related to**: #121 (QA-10.3) — runbook documents its add/remove/author process. - **Part of**: Phase 1 gate per PDR-007 Constraint 4. ## References - `hq/docs/decisions/PDR-007-ui-audit-strategy.md` § Consequences — baseline maintenance burden - `hq/docs/website/audit-tooling-design.md` § 6 Item 14

View on github ↗