timerise-ai

@timerise-ai source repo

9 skills
0 followers
5 hours ago last updated

▌
Visit Logger · timerise-ai bundle
Log who opened what, from where and on what, server-side in a Next.js App Router app: an IP, edge-geolocation and parsed-browser fingerprint for every real page view of a shared resource and for lifecycle moments (sign-in link requested, account created, signed in), stored in Postgres/Supabase or Firestore, grouped into sittings, with first-open announcements and admin history panels. Use when: (1) sales, success or an owner must know whether and when someone opened a demo, proposal, quote, report or shared link, (2) a "signed up from" location and device is wanted at sign-up, (3) the user mentions: visit log, visitor tracking, log visits to the database, geolocation headers, x-vercel-ip-city, x-forwarded-for, cf-ipcountry, user agent parsing, userAgent(), isBot, device type, "who opened the link", "customer opened the demo" Slack ping, visit history, last seen, sign-up location. Carries the page-view filter that drops prefetches and Server Actions, bot detection for what the framework's list misses, NULL-saf

0 installs
▌
Site Pin Gate · timerise-ai bundle
Put a shared-PIN gate in front of an entire Next.js site from the proxy/middleware layer: one env var arms it, a self-contained unlock page sets an HMAC-derived HttpOnly cookie, and the app behind it stays untouched. Use when: (1) a pre-launch, staging, client-preview or investor-preview site must be hidden from the public and from crawlers without adding user accounts, (2) an existing PIN or password gate in middleware.ts or proxy.ts needs auditing, (3) the user mentions: site PIN, password-protect the site, access code, pre-launch gate, coming-soon lock, staging password, SITE_PIN, "hide the site behind a PIN", "lock the preview deployment", "temporary password page". Carries the return path resolved against the request origin, the 303 unlock redirect, the cookie token keyed by a server-side secret, constant-time comparisons, an attempt budget answering 429 with Retry-After, and the suite that holds them. Next.js App Router, proxy.ts or middleware.ts; the attempt store is a seam, so a shared store can repla

0 installs
▌
Ksef · timerise-ai bundle
Build KSeF API 2.0 integrations (Krajowy System e-Faktur — Poland's national e-invoicing system) in Next.js apps on Vercel. Use when: (1) sending, receiving, querying, or syncing structured invoices (faktura ustrukturyzowana, FA(3) XML) via api.ksef.mf.gov.pl, (2) implementing KSeF auth (challenge, XAdES, KSeF token, accessToken/refreshToken), invoice encryption (AES-256-CBC, RSA-OAEP), UPO receipts, QR codes (KOD I/KOD II), interactive or batch sessions, offline modes, KSeF certificates, tokens, or permissions, (3) user mentions: KSeF, e-faktura, Polish e-invoicing, UPO, FA(3), ksef.mf.gov.pl. Provides working TypeScript/Node code (no official TS SDK exists) plus Vercel patterns: cron polling, token storage, function limits.

0 installs
▌
Help Center Markdown · timerise-ai bundle
Build a markdown-backed help center in a Next.js App Router app — category folders of frontmatter articles, statically rendered landing, category, tag and article pages, client-side search with ranking and keyboard navigation, locale-aware routing with default-locale fallback, tags with slug identity and per-tag pages, related articles, breadcrumbs, JSON-LD and sitemap entries, plus a content validator for CI. Use when: (1) building or extending a help center, knowledge base, docs section, support articles or FAQ hub from markdown files in the repo, (2) adding article search, tag pages or tag chips, translated articles with fallback, hreflang/canonical rules, related links, or a collapsible article sidebar, (3) the user mentions: help center, knowledge base, docs site, support articles, markdown content, frontmatter, tags, article search, hreflang, i18n content, "help articles". Carries a loader with a CI validator that fails the build on unreachable or malformed articles, search that tolerates trailing space

0 installs
▌
Digital Signage · timerise-ai bundle
Build a digital-signage module in a Next.js App Router app on Firestore or Supabase — ad media library, per-screen playlists, display registry, device pairing, and a fullscreen TV player. Use when: (1) building or extending in-venue screens, digital menu boards, lobby/waiting-room displays, or an advertising-slot system, (2) implementing playlist scheduling, media upload with duration and orientation handling, device pairing by PIN or provisioning URL, screen health monitoring, or remote screen control, (3) the user mentions: digital signage, display screens, TV player, ad playlist, signage module, kiosk display, screen management, proof of play. Carries player internals that recover from video stalls, rotate for portrait screens and survive TV-browser quirks, and a data/auth model with hashed per-device tokens and venue-scoped playlists, each pinned by a behaviour contract or a route test. Framework-specific to Next.js App Router; backend-agnostic between Firestore and Postgres/Supabase.

0 installs
▌
Booking Kiosk · timerise-ai bundle
Build a self-service touchscreen booking kiosk: a stepped walk-up flow (service → date → time slot → stations & participant names → equipment & consumables → summary → confirmation) with on-screen keyboard, inactivity auto-reset, pay-at-counter or pay-by-QR, live availability refresh, and a find-my-booking edit flow. Use when: (1) a venue (gym, karting, bowling, climbing, escape room, clinic) wants an unattended booking terminal, (2) the user mentions: "kiosk mode", "self-service kiosk", "touch screen booking", "walk-up terminal", "on-screen keyboard", "counter payment", "PENDING_COUNTER_PAYMENT", (3) an existing kiosk needs auditing against the hard rules. Ships the session state machine with its reducer suite, the screen contract, the server-priced idempotent API contract, and the booking-backend seam. Next.js App Router oriented; backend- and payment-provider-agnostic.

0 installs
▌
Blog Markdown · timerise-ai bundle
Build a file-based, multilingual blog from markdown content: locale-partitioned posts, per-locale slugs joined by a shared translation key, tag pages, related posts, cover art, RSS, sitemap and hreflang. Use when: (1) adding a blog, changelog, news or article section backed by markdown files rather than a CMS, (2) making an existing markdown blog multilingual, or adding tag pages, hreflang, feeds or related posts, (3) the content lives in a repo folder and must be statically generated, (4) the user mentions: markdown blog, MDX blog, frontmatter, gray-matter, content/blog, translationKey, tag pages, hreflang, related posts, generateStaticParams for posts, blog RSS feed. Carries the cross-locale slug model, the tag-slug collision rule, the frontmatter parser that survives smart quotes, and the loader memoization that removes a measured 71x build-time read amplification. Next.js App Router oriented; the content source is a seam, so a CMS can replace the filesystem. Not a CMS integration skill and not a docs/help

0 installs
▌
Ecommerce Process Mining · timerise-ai bundle
Build employee process mining for an e-commerce back office: a consented Manifest V3 browser extension that captures DOM events rather than pixels from the admin tools staff already use (shop admin, marketplace seller panels, carrier portals, helpdesk, WMS, ERP), plus a gap-capture form for the work a browser cannot see, feeding an AI pipeline that writes per-role SOPs and ranks automation candidates. Use when: (1) documenting how order, return, listing, supplier and support work is really done, for onboarding, audit or automation scoping, (2) building or auditing an employee activity-capture extension, its consent model, its PII scrubbing, or its PKCE connect flow, (3) the user mentions: process mining, task mining, SOP generation, "document what employees do", routine capture, browser extension capture, DOM event capture, MutationObserver, captureVisibleTab, chrome.identity launchWebAuthFlow, consent toggle, excluded domains, PII scrubber, dom_confidence, perceptual hash, works council, GDPR Art. 88. Carrie

0 installs
▌
Browser Extension Connector · timerise-ai bundle
Build a Chrome MV3 extension that acts on an external web service with no (or a limited) public API from inside the user's own signed-in browser session, observing the site's JSON traffic, replaying its auth headers for pulls and writes, buffering offline, and syncing with a host app through one polled endpoint that carries records up and commands down. Use when: (1) a product needs data out of, or actions into, a third-party site that offers no API, no OAuth and no export, and server-side scraping with the user's password is off the table, (2) an existing connector extension needs hardening: a service worker that dies, an alarm that never fires, a content script that shipped dead, records that go missing, commands marked failed without having run, (3) the user mentions: browser extension connector, chrome extension integration, no API, scrape from the logged-in session, MV3 service worker, content script MAIN world, tap fetch/XHR, replay auth headers, offline buffer, pairing PIN, "sync bookings from <site>",

0 installs

9 published skills