Showing 40141–40170 of 77205 skills
Verifica que una migración Flyway de Runcriticon sea compatible hacia atrás (deploy-then-migrate, ADR-0010 D11), siga la convención de nombres y carpeta por módulo, declare la categoría RGPD de cada tabla nueva, y respete las reglas de persistencia (esquema por módulo, sin FK cruzado, club_id indexado). Usar antes de mergear una PR con migraciones SQL.
avgarcia/runcriticon
Scaffold de una feature Angular nueva (componente standalone OnPush, servicio Signals, ruta lazy, tests Jest y Playwright+axe-core) ajustada a ADR-0001 y ADR-0012. Usar al crear cualquier pantalla, sección o feature nueva del frontend de Runcriticon.
avgarcia/runcriticon
Crea un integration event público nuevo de un módulo del backend con todos sus artefactos coherentes - clase Kotlin en api/events con los 6 campos obligatorios + traceparent, JSON Schema versionado en schemas/{modulo}/, test de contrato con @Tag("contract"), actualización del README del módulo, y stub del listener consumidor si otro módulo debe reaccionar. Usar al modelar un hecho de dominio que otros módulos deben conocer.
avgarcia/runcriticon
Genera el scaffold completo de un módulo nuevo del backend (Identidad, Club, Planificación, Seguimiento o Auditoría) siguiendo la guía operativa de Runcriticon y los 5 subdocumentos. Crea estructura de paquetes, errores sellados, IntegrationEvent, puertos de consulta de reglas de relación + auditor de accesos, casos de uso con Either + Raise DSL, repositorios con @AuthScope, listeners idempotentes, MetricasDelModulo, ConfigurationProperties, migración Flyway inicial con categorización RGPD, y tests stub. Cumple los 30+ ítems del checklist por construcción.
avgarcia/runcriticon
Guía cualquier cambio del contrato de API por el workflow contract-first de ADR-0001 D10: spec primero en api/openapi.yaml, clasificación aditivo vs breaking (breaking → PR propia etiquetada breaking-api), regeneración de clientes, implementación back+front en el mismo PR y revisión cruzada. Usar al añadir o modificar cualquier endpoint, campo o status code.
avgarcia/runcriticon
Genera un runbook operativo en docs/runbooks/ siguiendo la plantilla del proyecto y cruzando con el ADR que lo invoca. Usar cuando se alcance un disparador que requiera un runbook nuevo (rotación de secreto, acceso a RDS, respuesta a brecha, disaster recovery, atención de un derecho RGPD, alarma de AMG, actualización de JDK). Crea el archivo con frecuencia, prerrequisitos, procedimiento paso a paso, rollback y registro.
avgarcia/runcriticon
Interpreta violaciones de fronteras de Spring Modulith y errores típicos del outbox de eventos en Runcriticon, y propone el fix coherente con events-first (proyección local + evento en lugar de llamada síncrona). Usar cuando ApplicationModules.verify() falla, cuando un @ApplicationModuleListener no se dispara, o cuando hay eventos atascados en event_publication.
avgarcia/runcriticon
Convierte una maqueta HTML/CSS hi-fi de docs/diseno/ en un componente Angular del proyecto: spartan.ng (helm) + utilidades Tailwind con los tokens del proyecto, standalone OnPush, textos con i18n, accesibilidad y tests. Usar al construir cualquier pantalla del MVP que tenga maqueta — la maqueta es la referencia visual obligatoria (frontend/CLAUDE.md: "no inventes layout desde cero").
avgarcia/runcriticon
Drive the Apex Factory app on a leased iOS simulator or Android emulator with agent-device through .agents/scripts/device-lane.sh — open the app, read the accessibility snapshot, tap, type, scroll, verify with wait/is/get, take screenshots, record evidence, and write or replay agent-device .ad scripts (the e2e tests under apps/mobile/e2e/). Use for any interaction with a device, when writing an e2e: test, or when someone says "check it on the simulator", "tap through the app" or "dogfood the app".
callstackincubator/apex-software-factory
Call the tools the running Apex Factory app registers with appduct (read app state, jump to a route, run an OTA check now, emulate the update banner, a feature's own seed tools) through .agents/scripts/device-lane.sh, and write or review those tools in apps/mobile. Use when a check needs app state or a deep screen without tapping through the UI, when a spec's Agent hooks names an appduct tool, or when someone mentions appduct.
callstackincubator/apex-software-factory
Deliver a ready issue end to end, unattended — a task, a bug, or a whole feature:ready feature (split it into the tasks its Technical spec lists; each task is then delivered by its own run as it turns ready). Claims, delegates implementation, the two blind reviews and the simulator check (in parallel) to fresh subagents, reasons only over their report blocks, and merges each PR through the gate so the merge ships an OTA update. Use when someone says "deliver
callstackincubator/apex-software-factory
Implement one claimed issue (task, bug, or single-PR feature) tests-first — commit the spec's tests red, open a draft PR, turn them green contract-first in checkpoint commits (with the appduct tools the spec's Agent hooks name), run pnpm check and the native check — or apply a list of review or simulator findings to its branch. Ends with a fixed report block. Loaded by the implementer subagent when the deliver orchestrator delegates implementation, or when someone says "implement
callstackincubator/apex-software-factory
The product-facing front door. A booth facilitator runs it with a reactCon visitor who has an idea for the app — interview in plain, non-technical words (the problem, who has it, what they would see, how they would know it works), show the draft, and on the visitor's yes file a request:new issue in their own words. Use when someone says "I have an idea", "/intent", "file a feature request", or a facilitator starts a booth session.
callstackincubator/apex-software-factory
Look back at recent factory runs from any machine — the run records and lessons on the factory-memory branch, the issues and PRs on GitHub, and, for one stage that needs a closer look, the run's transcript artifact — find what cost time or stopped runs and why, curate the lessons agents left, and propose concrete changes to skills, agents, scripts, templates or rules, ranked by what they would save. With a person, carry out the accepted proposals as a draft PR. Never needs OpenCode's local database. Use when someone says "retro", "/retro", "what went wrong with
callstackincubator/apex-software-factory
Run the two blind pre-merge reviews from delivery rule 14 on a PR — a spec review blind to the rules and a code review blind to the issue, each by a fresh subagent reading only the inputs directory prepared for it — then have a third fresh subagent verify every blocking finding and sort the nits, and hand back a fixed report block. Never edits code. Use when the deliver orchestrator reaches review, or when someone says "review PR N" or "/review N".
callstackincubator/apex-software-factory
Inspect the live Apex Factory app through Rozenite for Agents — network requests, console messages, the React component tree and renders, performance traces, heap snapshots, and the app's own tools — on a debug build with Metro started by .agents/scripts/device-lane.sh metro start. Use to collect evidence for a failing simulator check or a bug report, or when someone asks to debug the running app.
callstackincubator/apex-software-factory
Run a spec session on a GitHub issue — turn a request:new into a feature spec, write or amend its business sections with the product owner, write the Technical spec with a developer (ending with a fresh spec-checker subagent's report, fixed before the ready label), or (unattended, from deliver) split a feature:ready feature into task sub-issues from the slices its Technical spec lists. Always reconciles comments posted since the body was last edited before writing anything. Use when someone says "spec session for
callstackincubator/apex-software-factory
Triage a bug:triage issue — reproduce it as a failing test, find the root cause, and post a report proposing the simplest fix, without fixing it. Loaded by the triager subagent. Use when someone says "triage
callstackincubator/apex-software-factory
Prove a PR's simulator Done when lines and e2e: replay scripts on an iOS simulator — an Expo Simulators session running the PR's lane binary, started through .agents/scripts/device-lane.sh, checked with agent-device (open, snapshot, wait, is, replay) and shortcut with appduct — and hand back pass, fail, busy or unavailable. Always releases the session. Loaded by the mobile-verifier subagent. Use when the deliver orchestrator delegates simulator verification, or when someone says "verify #N on the simulator".
callstackincubator/apex-software-factory
After a delivery PR merges, check on an Expo Simulators iOS session that its OTA update actually landed — wait for the OTA publish run of the merge commit, start a session on the production build with the merge's native fingerprint, make the app check now with appduct's ota_check_now, apply the staged bundle by tapping the update banner with agent-device, and confirm the bundle id and the feature on screen. Always releases the session. Loaded by the ota-verifier subagent. Use when the deliver orchestrator hands over a merged PR, or when someone asks "did the update for
callstackincubator/apex-software-factory
Use when creating or changing agent instructions or their activation behavior. Skip edits that only correct spelling or formatting.
MVPavan/via
Use for Beads dependencies, intake states, recovery, workstream tracking, or unfamiliar task-lifecycle operations. Routine tracking uses AGENTS.md and runtime context.
MVPavan/via
Use when material scope or behavior decisions need exploration, or the user requests brainstorming. Handle a single routine ambiguity directly.
MVPavan/via
Use for substantive code review or to verify and act on review findings. Routine final diff inspection is not a separate review workflow.
MVPavan/via
Use for substantive module-interface, encapsulation, or testability decisions. Skip ordinary code explanations and cosmetic refactors.
MVPavan/via
Use when integrating supplied discussions or decisions into a self-contained next version of existing design documents.
MVPavan/via
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model. Trigger on ADR phrases (record, write, supersede an ADR).
MVPavan/via
Use to execute tracked multi-step work, a standalone plan, or a roadmap phase. Clear bounded implementation can proceed directly under AGENTS.md.
MVPavan/via
Use when explicitly requested, or only when a consequential decision hinges on an unresolved foundational assumption that ordinary inspection or the active workflow cannot settle. Skip routine edits, straightforward fixes, settled implementation plans, and generic requests to think critically.
MVPavan/via
Use when the user explicitly requests a grilling interview to resolve or challenge material decisions. For a written critique, review the artifact directly.
MVPavan/via