Results for “rekor”

Verify signed artifacts and SLSA build provenance with Sigstore cosign and slsa-verifier, enforce keyless OIDC identity, and apply SLSA Build levels to harden the software supply chain.

Create, apply, and manage AgentRC policies to customize readiness scoring, disable checks, override impact levels, set pass-rate thresholds, and enforce CI gating.

Build performant React Native and Expo mobile apps with best practices for list performance, animations, navigation, UI patterns, state management, and monorepo configuration.

Police the project's vocabulary — bust vague terms, keep the CONTEXT.md glossary sharp, and lock in decisions worth remembering as ADRs. Use when the user debates naming, says "what should we call this", asks to pin down terminology, wants a decision recorded, or when another skill (hot-seat, whiteboard) surfaces a decision that clears the ADR bar. Just reading the glossary for vocabulary is NOT this skill — trigger only when the words or decisions are being changed.

Redis caching patterns, pub/sub, sessions, rate limiting, and data structures.

<!-- IJFW: narration-not-applicable -->

Expert-level PostgreSQL database administration, advanced queries, performance tuning, and production operations

Volume-based PUMP token reward system with day-indexed epochs, pro-rata distribution, accumulator tracking, and cross-program claiming on Solana.

Track open comment periods and draft a substantive, on-the-record comment that argues your position within the docket's rules and deadline.

FREE — God-tier long-context memory for AI agents. Injects 500K-1M clean tokens, auto-summarizes with tone/intent preservation, compresses 14-turn history into 800 tokens.

Record a decision: finalized → ADR (optionally rule + guide or spec + plan); open proposal → RFC. Use for 'we decided', 'record this decision', 'make it a standard', 'draft an RFC', 'should we switch to Y'. Not for feature planning or documenting existing code.

Redis in-memory data store. Covers data structures, caching, and pub/sub. Use for caching and real-time features. USE WHEN: user mentions "redis", "caching", "session storage", "rate limiting", "pub/sub", "sorted sets", "in-memory database", "cache invalidation" DO NOT USE FOR: relational data - use `postgresql` or `mysql` instead, document storage - use `mongodb` instead, full-text search - use `elasticsearch` instead

Log workouts, plan routines, track progress, and get intelligent coaching for any fitness level.

Use to review how call recordings are notified, stored, accessed, redacted and deleted, including the parts that differ from text conversations. Trigger for "review our call recording practices", "do we need to tell customers we're recording", "who can listen to our calls", recording retention, card details spoken on a call, or a request for a customer's own recording.

FREE — God-tier long-context memory for AI agents. Injects 500K-1M clean tokens, auto-summarizes with tone/intent preservation, compresses 14-turn history into 800 tokens.

Query resource usage metrics for Railway services. Use when user asks about resource usage, CPU, memory, network, disk, or service performance like "how much memory is my service using" or "is my service slow".

Produce the weekly regulatory digest — a prioritized rollup of new rules, open comment deadlines, and compliance gaps across every tracked matter.

Generate today's standup: what was done, what is in progress, what comes

Optimizes React and Next.js performance with 69 prioritized rules covering waterfalls, bundle size, server-side rendering, and re-rendering patterns.

Optimizes Active Record queries, implements Turbo Frames and Streams, configures Action Cable, sets up Sidekiq workers, and writes RSpec test suites for Rails 7+ applications.

Organizes 70+ React and Next.js performance optimization rules across 8 priority categories for use when writing, reviewing, or refactoring code.

Use to build an account's cumulative support record ahead of a renewal or QBR, so the review reflects the whole relationship rather than the most recent ticket. Trigger for "prepare for this renewal", "what has this account's support experience been", "which accounts are at risk before renewal", QBR preparation, account health review, or an account that renewed badly with no warning.

Bitcoin Core JSON-RPC interface: authentication (cookie, rpcauth), wallet vs node RPCs, common verbs (getblockchaininfo, getrawtransaction, scantxoutset, importdescriptors, walletprocesspsbt, submitpackage, testmempoolaccept), error handling. USE WHEN: scripting bitcoind, integrating a service, debugging RPC errors.

Design and deploy Salesforce restriction rules to subtract record access from users, covering eligibility, criteria syntax, metadata shape, and documented enforcement gaps.

Rep Operating Standards — Canonical (Heath-set 2026-06-07)

FREE — God-tier long-context memory for AI agents. Injects 500K-1M clean tokens, auto-summarizes with tone/intent preservation, compresses 14-turn history into 800 tokens.

Use to define handoff standards for support transfers and to measure whether context survives the handoff — cold vs warm, required fields, and re-ask rate after transfer. Trigger for "transfer protocol", "warm handoff", "customers repeat themselves after transfer", "ping-pong between teams", "what should agents include when transferring", handoff quality, or re-ask rate after escalation.

Build a USASpending relationship snapshot for the incumbent and buying agency on a pursuit row. Use when user needs award flows and rel counts before battlecard or teaming work — deterministic from DuckDB bulk.

KOMODO v1.0 — Momentum Event Consensus. Uses leaderboard_get_momentum_events (real-time threshold crossings) to detect when 2+ quality SM traders cross momentum thresholds on the same asset/direction within 60 minutes. Confirmed by market concentration + volume. Enters with the momentum. Replaces MANTIS v1.0 and SCORPION v1.1 (both used stale position data).

Konfiguracja systemu i funkcje domenowe platformy Soneta (enova365, Triva): (A) IMPORT/EKSPORT DANYCH I USTAWIEŃ przez pliki XML — element session, import według rekordów (business="false", *.dbinit.xml, demo) i przez logikę biznesową (business="true"), eksport datapacku, GUID, formaty wartości; (B) `scan-folders` — inwentaryzacja folderów menu (`[assembly: FolderView]`) z DLL; (C) KONFIGURACJA URUCHOMIENIOWA `appsettings.json` — porty i adresy komponentów (orchestrator/server/web/webapi/router/commhub), kolejność nadpisań (profil systemu, nakładki `-c`, zmienne `SONETA_`, CLI). Używaj gdy użytkownik: (1) buduje lub analizuje XML importu danych (dbinit.xml, dane demo, przenoszenie ustawień); (2) pyta o atrybuty guid/where/key/id/business/deleted/dbversion; (3) eksportuje rekordy guidowane; (4) mapuje menu z DLL lub wpina nowy folder; (5) konfiguruje porty/adresy albo pyta o klucz w `appsettings.json`. Kod importu (SessionReader/SessionWriter) → /soneta-programming; operacje na bazie z CLI → /soneta-tools.