Software Development
1,831 results
- Marketplace Rate LimitingvtexApply when implementing retry logic, rate limit handling, or resilience patterns in VTEX API integrations. Covers VTEX rate limit headers (X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After), 429 status handling, exponential backoff with jitter, circuit breaker patterns, and request queuing.
- Payment Async FlowvtexApply when implementing asynchronous payment methods (Boleto, Pix, bank redirects) or working with callback URLs in payment connector code. Covers undefined status response, callbackUrl notification, X-VTEX-signature validation, sync vs async handling, correct delayToCancel configuration for each async method, and redirect-based flows where inboundRequestsUrl does not support browser GET…
- Payment IdempotencyvtexApply when implementing idempotency logic in payment connector code or handling duplicate payment requests. Covers paymentId as idempotency key, payment state machine transitions, retry semantics for cancellation and refund operations, and requestId handling.
- Payment Provider ProtocolvtexApply when implementing a VTEX Payment Provider Protocol (PPP) connector or working with payment/connector endpoint files. Covers all nine required endpoints: Manifest, Create Payment, Cancel, Capture/Settle, Refund, Inbound Request, Create Auth Token, Provider Auth Redirect, and Get Credentials. Use for building or debugging any payment connector that integrates with the VTEX Payment Gateway.
- Vtex Io Application PerformancevtexApply when improving VTEX IO Node or .NET services for latency, throughput, and resilience: in-process LRU, VBase, stale-while-revalidate, AppSettings loading, request context, parallel client calls, and avoiding duplicate work. Covers application-level performance patterns that complement edge/CDN caching. Use when optimizing backends beyond route-level Cache-Control.
- Vtex Io Auth Tokens And ContextvtexApply when choosing which VTEX IO authentication token should back a request from a backend app. Covers `ctx.authToken`, `ctx.storeUserAuthToken`, `ctx.adminUserAuthToken`, `authMethod`, and how requester context should determine the identity used by VTEX clients.
- Vtex Io Data Access PatternsvtexApply when deciding where and how a VTEX IO app should store and read data. Covers when to use app settings, configuration apps, Master Data, VBase, VTEX core APIs, or external stores, and how to avoid duplicating sources of truth or abusing configuration stores for operational data.
- Vtex Io Graphql APIvtexApply when working with GraphQL schema files in graphql/ or implementing resolvers in node/resolvers/ for VTEX IO apps. Covers schema.graphql definitions, @cacheControl and @auth directives, custom type definitions, and resolver registration in the Service class. Use for exposing data through GraphQL queries and mutations with proper cache control and authentication enforcement.
- Vtex Io Masterdata StrategyvtexApply when deciding whether and how VTEX IO apps should use Master Data v2 for custom data. Covers entity boundaries, schema lifecycle, indexing strategy, and when Master Data is the right storage mechanism versus another data approach. Use for reviews, wishlists, forms, or other custom data modeling decisions in VTEX IO apps.
- Vtex Io Service Paths And CdnvtexApply when defining service.json routes, choosing public vs segment vs private URL prefixes for VTEX IO services, or setting HTTP cache headers that interact with the VTEX edge and CDN. Covers path patterns, cookie visibility, edge caching behavior, and aligning Cache-Control with data sensitivity. Use for Node or .NET IO backends where request path and response headers determine CDN safety.
- FeedbackTinyFishFile structured feedback about TinyFish — bug reports, confusing setup steps, missing features, or a doctor diagnostic report. Creates a GitHub issue on tinyfish-io/tinyfish-cookbook with the user's approval; nothing is sent without an explicit preview.
- Tinyfish ResearchTinyFishWeb research powered by TinyFish search and fetch, plus TinyFish deep research runs when the user explicitly asks for deep research. Use for any question needing current web information, and for deep research — competitive analysis, literature reviews, lead generation, deep dives — including phrases like 'research this', 'find everything about', 'find me all', or 'deep dive on'.
- Product Tracking Model ProductAccoilBuild a structured product model by scanning the codebase and talking to the user. Produces .telemetry/product.md — a description of what the product does, who uses it, how value flows, and what entities exist.
- Code Formattervuralserhat86Otomatik kod formatlama, Prettier/ESLint entegrasyonu ve kod stil tutarlılıÄı rehberi.
- Commit ChangesPhilipp J. ThossStage, commit, amend w/ conventional msgs. Covers review, selective staging, HEREDOC msgs, history verify. Use → save logical unit, conventional commit, amend last, or review staged before commit.
- Consult A Decision OraclePhilipp J. ThossAdd an external probabilistic classifier to a decision path without letting it take the path over. Covers finding the externally-graded rows you are already logging, measuring the confidence separation between the overrides it got right and the ones it got wrong, choosing an operating point your data licenses, failing open at the call site, and proving the whole arrangement offline with no API…
- Decode Minified Js GatesPhilipp J. ThossClassify gate call variants in minified JS bundle. Covers ctx-window extraction around flag occurrence, ID of 4–6 reader variants (sync bool, sync config-object, bootstrap-aware TTL, truthy-only, async bootstrap, async bridge), default-value extraction (bool / null / numeric / config- object literal), conjunction detection across `&&` predicates, kill-switch inversion detection, gate-mechanics…
- Domain-Focused NamingobraName code by what it does in the domain, not how it's implemented or its history
- Instrument Distributed TracingPhilipp J. ThossInstrument applications with OpenTelemetry for distributed tracing: auto and manual instrumentation, context propagation, sampling strategies, integration with Jaeger or Tempo. Use when debugging latency in distributed systems, understanding request flow across microservices, correlating traces with logs and metrics for root cause, measuring end-to-end latency, or migrating from legacy tracing…
- Manage Git BranchesPhilipp J. ThossGit-Branches erstellen, verfolgen, wechseln, synchronisieren und bereinigen. Umfasst Namenskonventionen, sicheres Branch-Wechseln mit Stash, Upstream-Synchronisation und das Loeschen zusammengefuehrter Branches.
- Manage Git BranchesPhilipp J. ThossCrea, rastrea, cambia, sincroniza y limpia ramas de Git. Cubre convenciones de nombres, cambio seguro de ramas con stash, sincronización con el upstream y eliminación de ramas fusionadas. Úsalo al comenzar trabajo en una nueva funcionalidad o corrección de error, al cambiar entre tareas en distintas ramas, al mantener una rama de funcionalidad actualizada con main, o al limpiar ramas tras…
- Rust Developmentvuralserhat86Rust systems programming, memory safety, Axum/Tokio ve WebAssembly rehberi.
- Serialize Data FormatsPhilipp J. ThossSerialize and deserialize data across common formats: JSON, XML, YAML, Protocol Buffers, MessagePack, Apache Arrow/Parquet. Covers format selection criteria, encoding/decoding patterns, performance tradeoffs, and interoperability.
- Chat Roomrivet-devBuild a realtime chat room backend with Rivet Actors: one actor per room, SQLite-backed message history, and WebSocket broadcast to every connected client.