velt-recorder-best-practices
Velt Recorder implementation patterns and best practices for React, Next.js, and web applications. Use when adding audio, video, or screen recording (VeltRecorderTool, VeltRecorderControlPanel, VeltRecorderPlayer, VeltRecorderNotes), recording playback, the video editor, AI transcription, recorder lifecycle events, the recorder.done webhook, the Get Recordings REST API, or binding Recorder and Transcription wireframe slots with template variables (velt-data / velt-if / velt-class).
velt-rest-apis-best-practices
Velt REST API v2 and webhook best practices for server-side integration. Use when calling Velt REST endpoints, generating JWT tokens, managing users/documents/organizations/notifications, provisioning API keys, running review agents (/v2/agents), querying Memory (/v2/memory), or handling basic and Svix webhooks. Triggers on x-velt-api-key, generate_token, agent executions, memory search/ask, or webhook signatures. For velt-py self-hosting, see velt-self-hosting-data-best-practices.
velt-rewriter-best-practices
Best practices for the Velt Rewriter, the AI text rewriter that lets users select text and apply AI rewrites or anchor AI comments. Use when calling enableRewriter, subscribing to textSelected, calling askAi (provider routed by model prefix), replaceText, or addComment, toggling the default toolbar, using useAIRewriterUtils, building custom rewriter wireframes, or debugging a rewriter that does nothing inside TipTap or ProseMirror editors. Triggers on AI rewrite or selection-toolbar AI features.
velt-self-hosting-data-best-practices
Velt self-hosting patterns. Partial self-hosting keeps comments, attachments, reactions, recordings, notifications, activity, and user PII on your infrastructure through VeltProvider dataProviders (endpoint or function based), with backend routes, resolver auth, and the velt-py Python SDK on MongoDB or PostgreSQL. Also distinguishes full self-hosting (the whole Velt stack on your own GCP project) and its config.selfHosted wiring. Use for data providers, resolvers, or self-hosted Velt.
velt-setup-best-practices
Velt SDK setup for React, Next.js, Angular, Vue, and HTML. Use when installing Velt, configuring VeltProvider or initVelt, authenticating users with authProvider and backend JWTs (generate_token), setting documents and locations with setDocuments, configuring featureAllowList, proxyConfig, or setUnstyledMode, adding VeltUserInviteTool, installing the Velt AI plugins or Docs MCP in Claude Code or Cursor, or debugging setup. Triggers on any Velt setup task, even if the user doesn't say "setup".
velt-single-editor-mode-best-practices
Velt Single Editor Mode patterns for React, Next.js, and web apps. Use when implementing exclusive editing (one editor, read-only viewers), enableSingleEditorMode, setUserAsEditor error codes, useUserEditorState / useEditor, editor access requests and handoff, timeout-based transfer, singleEditorModeContainerIds, data-velt-sync-access and auto-sync attributes, single-tab editing, heartbeat, SEM events, or customizing the VeltSingleEditorModePanel wireframe.
velt-suggestions-best-practices
Velt Suggestions best practices for React, Next.js, and web apps. Use when adding suggestion mode (propose-then-review edits by humans or AI agents), suggestion targets, autoCommit or detect-only capture, summaryHtml bodies, accept/reject flows, or the pending/accepted/rejected/stale lifecycle. Triggers on data-velt-suggestion-target, enableSuggestionMode, commitSuggestion, acceptSuggestion, rejectSuggestion, suggestionAccepted, or useSuggestionUtils, even if the user doesn't say 'suggestions'.
velt-view-analytics-best-practices
Best practices for Velt View Analytics, the who-viewed-this-document indicator with a count badge, recent-viewers dialog, and per-user or per-date view data. Use when adding VeltViewAnalytics, scoping it with type=location and location-id, reading views with useUniqueViewsByUser / useUniqueViewsByDate, useViewsUtils, or getViewsElement observables, or customizing view-analytics wireframes (todayViewsCount, treadsVisible). Triggers on document view counts or recent viewers, even without the word Velt.
yjs-best-practices
Yjs CRDT best practices for building real-time collaborative applications. Use this skill when implementing collaborative editing, real-time sync, shared data structures, or any feature using Yjs (Y.Doc, Y.Text, Y.Array, Y.Map, Y.XmlFragment). Triggers on tasks involving Yjs, CRDTs, collaborative editors, y-websocket, y-webrtc, y-indexeddb, y-prosemirror, y-codemirror, y-quill, y-monaco, awareness/presence, undo/redo with shared types, or any mention of real-time document collaboration — even if the user doesn't explicitly say 'Yjs'.
velt-activity-best-practices
Velt Activity Logs implementation patterns and best practices for React, Next.js, and web applications. Use when adding real-time activity feeds (VeltActivityLog, useAllActivities, getAllActivities), custom activity logging with createActivity, audit trails and immutability, CRDT activity debounce, workspace activityServiceConfig, server-side activity management via REST API, or customizing the VeltActivityLog wireframe and its template variables (velt-data, velt-if, velt-class).
mobile-use-setup
Set up a local-first Minitap mobile-use SDK project for iOS or Android, including local devices, BrowserStack, Minitap cloud devices, and supported LLM providers.
task-estimator
Estimates compute tokens and cost for TaskMarket tasks before posting or bidding. Use when planning task compute cost, setting fair bounty rewards, evaluating reward-versus-cost ROI, or comparing multiple tasks by expected margin.
taskmarket
Operates Taskmarket tasks end to end on Base using the first-party CLI. Use when an agent needs bounty, claim, pitch, benchmark, auction, evaluator, artifact, payment, or requester-review workflows.
trend-discovery
|
lucid-agent-creator
|
lucid-agent-editor
|
lucid-agents-sdk
|
lucid-client-api
|
paid-agent
|
railway-deploy
|
b2a-agents
|
agent-factory
|
api-research
|
beamer-presentation
Create academic presentations in Beamer with professional themes
econ-visualization
Create publication-quality charts and graphs for economics papers.
api-data-fetcher
Fetch economic data from FRED, World Bank, and other APIs
stata-data-cleaning
Clean and transform messy data in Stata with reproducible workflows
code-simplifier
Simplify and clean up code after changes are complete. Reduces complexity, improves readability, and ensures consistency.
commit-push-pr
Commit changes, push to remote, and create a pull request. Use for completing features or fixes ready for review.
sdd
>
techdebt
Find and fix technical debt including duplicated code, dead code, outdated patterns, and code smells. Run at the end of sessions to clean up.
research-ideation
Generate research questions from economic phenomena
lit-review-assistant
Search, summarize, and synthesize economics literature
general-equilibrium-model-builder
Build and solve Walrasian general equilibrium models with theory derivations and Julia computation
latex-econ-model
Write and typeset economic models in LaTeX with proper notation
academic-paper-writer
Draft economics papers with proper structure and academic style
latex-tables
Generate publication-ready regression tables in LaTeX.
python-panel-data
Panel data analysis with Python using linearmodels and pandas.
r-econometrics
Run IV, DiD, and RDD analyses in R with proper diagnostics
stata-regression
Run regression analyses in Stata with publication-ready output tables.
near-cli-rs
Generate near-cli-rs v0.14+ commands for NEAR Protocol — account management, NEAR/FT/NFT token transfers, staking delegation, contract deployment and calls, transaction signing (keychain, Ledger, seed phrase, MPC, offline), and network config
near-contract-audit
Comprehensive security audit skill for NEAR Protocol smart contracts written in Rust. Use when auditing NEAR contracts, reviewing security vulnerabilities, or analyzing contract code for issues like reentrancy, unhandled promises, unsafe math, access control flaws, and callback security.
near-kit
TypeScript library for NEAR Protocol blockchain interaction. Use this skill when writing code that interacts with NEAR Protocol, including viewing contract data, calling contract methods, sending NEAR tokens, building transactions, creating type-safe contract wrappers, integrating wallets (Wallet Selector, HOT Connect), React hooks and providers (@near-kit/react), managing keys, testing with sandbox, meta-transactions (NEP-366), and message signing (NEP-413).
near-smart-contracts
NEAR Protocol smart contract development in Rust. Use when writing, reviewing, or deploying NEAR smart contracts. Covers contract structure, state management, cross-contract calls, testing, security, and optimization patterns. Based on near-sdk v5.x with modern macro syntax.
near-intents
Cross-chain token swap integration using NEAR Intents 1Click API. Use when building swap widgets, bridge interfaces, or multi-chain transfers across EVM, Solana, NEAR, TON, Stellar, and Tron.
near-ai-cloud
NEAR AI Cloud private inference and verification. Use when integrating NEAR AI Cloud API for verifiable private AI inference, verifying model or gateway TEE attestation (NVIDIA NRAS, Intel TDX), verifying chat message signatures, implementing end-to-end encrypted chat, using specialized TEE endpoints (embeddings, reranking, images, audio, PII redaction), or using the OpenAI-compatible API with NEAR AI Cloud.
near-api-js
>-
near-dapp
>
create-documentation
Generate markdown documentation for a module or feature
envelope-editor-v2-e2e
Writing and maintaining Playwright E2E tests for the Envelope Editor V2. Use when the user needs to create, modify, debug, or extend E2E tests in packages/app-tests/e2e/envelope-editor-v2/. Triggers include requests to "write an e2e test", "add a test for the envelope editor", "test envelope settings/recipients/fields/items/attachments", "fix a failing envelope test", or any task involving Playwright tests for the envelope editor feature.
Page 365 of 1645 · 82232 results