productivity▌

Thread-safe data persistence in Swift using actors with in-memory cache and file-backed storage. \n \n Implements an actor-based repository pattern that eliminates data races at compile time, replacing manual synchronization with Swift's actor model \n Combines fast O(1) in-memory lookups with atomic file persistence, supporting any Codable & Identifiable model type \n Provides synchronous initialization to avoid async complexity, with automatic await enforcement on all public API calls \n

Screen job applications against role requirements to identify top candidates efficiently.

Structured meeting summaries with action items, decisions, and key discussion points. \n \n Provides a standardized markdown template covering agenda, discussion points, decisions, and action items with ownership and deadlines \n Emphasizes capturing outcomes and key points rather than verbatim transcription, with best practices for timing and clarity \n Includes a parking lot section for tabled topics and next steps tracking to keep discussions organized and follow-up clear \n

Initial file system scaffolding for Recoup sandbox accounts with organizations and artists. \n \n Fetches organizations and artists from the connected Recoup account via CLI, then creates an opinionated folder structure under orgs/{org}/artists/{artist-slug} \n Generates a RECOUP.md identity file in each artist directory to track setup status and connect the workspace to the Recoupable platform \n Requires RECOUP_ACCOUNT_ID environment variable only when using an Org API Key; omit it for Persona

You are a database observability expert specializing in Change Data Capture, real-time migration monitoring, and enterprise-grade observability infrastructure. Create comprehensive monitoring solutions for database migrations with CDC pipelines, anomaly detection, and automated alerting.

Port existing Semgrep rules to new target languages with applicability analysis and test-driven validation. \n \n Takes an existing Semgrep rule and target languages as input; produces independent rule and test directories for each applicable language \n Requires mandatory applicability analysis per language before porting, rejecting shortcuts like assuming identical patterns across different ASTs \n Enforces test-first methodology: write minimum 2 vulnerable and 2 safe test cases before creatin

Help teams write focused, actionable product requirements documents using frameworks from 11 product leaders. \n \n Start with problem and context before solutions; include \"why now\" to justify timing and urgency against competing priorities \n Choose the right format for your product type: traditional PRDs for feature specs, prototypes or prompt sets for AI features, executable evals as living requirements \n Define success upfront with clear metrics and outcomes; keep documents lightweight a

Comprehensive code review for diffs with auto-detected domain-specific checks. \n \n Analyzes changed code for security vulnerabilities, anti-patterns, quality issues, and breaking changes across generic, frontend, and backend domains \n Auto-detects domain (frontend, backend, CLI, config) from file paths and applies relevant checklists \n Generates structured markdown reports with severity levels, file locations, code snippets, and actionable recommendations \n Performs impact analysis to ident

Skill by ara.so — Daily 2026 Skills collection.

Scans TON smart contracts for 3 critical vulnerabilities: integer-as-boolean misuse, fake Jetton contracts, and unsafe gas forwarding. \n \n Detects FunC contracts via file extensions ( .fc , .func ) and TON project structure (Blueprint, toncli configs) \n Identifies three vulnerability patterns: missing sender validation in Jetton handlers, incorrect boolean logic using positive integers instead of -1/0, and forward TON amounts without gas checks \n Provides detailed findings with vulnerable co