Showing 30721–30750 of 42323 skills
Use when adding a new Next.js App Router API route under services/app/src/app/api/** — new endpoint file (route.ts), new HTTP method on an existing route, or a new list/GET endpoint needing pagination. Also use when reviewing a route.ts diff for missing requireRole/handleRoute or ad-hoc error handling.
danyelarguelho21-cmd/estoque-saas
Use when you need a working local integration environment for estoque-saas outside full Docker Compose — app+worker as local processes against test/dev Postgres+Redis containers, debugging integration tests, or reproducing an upload/NF-e/webhook bug locally. Also use when local runs fail with EACCES on uploads, unexpected 401s, or Redis rate-limit errors during test loops.
danyelarguelho21-cmd/estoque-saas
Use when adding or modifying a stock-mutating operation in services/app/src/modules/stock (or any new module that reads/writes stock_movements balance) — new movement type, new transfer-like flow, new perishable/batch handling, or touching entries.ts/exits.ts/transfers.ts/sales.ts/nfe-import.ts. Also use when reviewing a PR that adds a function calling tx.stockMovement.create or nextBalanceAfter.
danyelarguelho21-cmd/estoque-saas
Use before trusting a green integration test run, after editing tests/fixtures/db-test-helpers.ts or tests/integration/docker-compose.test.yml, when adding a new migration file to schemas/migrations, or when integration tests are flaky/failing in a way that looks environmental (auth failures, "relation does not exist", container crash loops). Verifies the test harness itself genuinely exercises a fresh environment instead of silently passing against a broken or partial setup.
danyelarguelho21-cmd/estoque-saas
Use when building new pages or components for the JapaConnect Academy app (apps/academy, port 3003, SSR, academy.japa.to). Covers the unified app shell adapted for Academy (ADR-060), the lesson-player reading exception, the SSR/CSR progress boundary, TrackCard, LayerChart 2.0.1 progress analytics, and the API-Readiness Gate.
jedafe/japa
Use when performing a comprehensive quality audit of the JapaConnect Admin Panel (apps/admin) before merge or release. Verifies RBAC CRUD completeness per entity, full DataTable spec compliance, LayerChart usage, SPA architecture, and security.
jedafe/japa
Use when building new pages or components for the JapaConnect Admin Panel (apps/admin, port 3001, SPA). Covers the mandatory DataTable spec (sort/search/filter/paginate/actions/bulk/create), the RBAC CRUD Gate, LayerChart dashboards, and SPA auth patterns.
jedafe/japa
Use when performing a comprehensive quality audit of the JapaConnect Go backend before merge or release. Reconciles routes/nodes/catalogs against code, runs the BE-series regression checklist, and verifies security, tenancy, and GDPR erasure completeness.
jedafe/japa
Use when building new features, endpoints, services, or entities in the JapaConnect Go backend (github.com/jedafe/japa). Covers the layered architecture (Handlers→Services→Stores), the Spec-Readiness and Contract-Delivery Gates, full RBAC CRUD delivery per entity, sqlc/pgx patterns, and catalog maintenance.
jedafe/japa
Use when performing a comprehensive quality audit of the JapaConnect Control Panel (apps/control) before merge or release. Verifies security-critical key handling, polling reliability, RBAC CRUD completeness, DataTable spec, and LayerChart compliance.
jedafe/japa
Use when building new pages or components for the JapaConnect Control Panel (apps/control, port 3002, SPA). Covers infrastructure dashboards with LayerChart, the RBAC CRUD Gate, the mandatory DataTable spec, API key/extension/settings/job-queue patterns, and safe polling.
jedafe/japa
Use when updating or refactoring existing JapaConnect Control Panel code (apps/control). Fixes polling patterns, upgrades tables to full DataTable spec, migrates ops charts to LayerChart, hardens key handling.
jedafe/japa
Fetch transcripts from YouTube videos for summarization, analysis, or reference. Accepts video ID or full URL. No API key required. Triggers: YouTube transcript, video transcript, get subtitles, what did they say in the video, summarize YouTube, extract video text, caption from video.
canvascoding/canvas-notebook
Aplica el patrón ultrathink de revisión Nivel 1 a un ADR del corpus de Runcriticon. Detecta gaps en bloques A-G, propone sub-decisiones con anchors, lanza tandas de preguntas con AskUserQuestion, y termina con PRs encadenadas de revisión + aceptación. Úsala cuando se proponga reabrir un ADR aceptado, cuando entre un ADR nuevo, o cuando el equipo quiera auditar un ADR contra el patrón consolidado.
avgarcia/runcriticon
Revisa los contratos de la API REST en cuanto a semántica HTTP, compatibilidad hacia atrás y coherencia de las respuestas. Úsala cuando el usuario solicite «revisar la API», «comprobar endpoints» o «revisión REST», o antes de publicar cambios en la API. Para editar o crear la spec OpenAPI con el workflow contract-first, usar openapi-spec-editor.
avgarcia/runcriticon
Desarrollo de una feature (caso de uso) dentro de un módulo backend existente: domain con Either, @ApplicationService con autorización explícita, adaptadores REST/JPA, migración Flyway y pirámide de tests completa, ajustado a ADR-0007/0008/0009/0010 y a los docs de arquitectura. Usar al añadir o modificar casos de uso en un módulo ya creado.
avgarcia/runcriticon
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