daggr
|
readthedocs-build-optimization
Optimize Read the Docs build performance and resource usage. Use when Read the Docs builds are slow, timing out, or hitting memory limits, or when users want to speed up builds by adjusting formats, dependencies, conda/mamba usage, or Python API documentation strategy.
readthedocs-project-manager
Manage Read the Docs projects via the RTD API. Use when creating projects, listing repos, triggering builds, syncing versions, or checking build status on Read the Docs.
readthedocs-redirects-manager
Manage Read the Docs redirects via the RTD API. Use when listing, creating, updating, or deleting custom redirects for a project.
readthedocs-search-api
Query the Read the Docs Search API to find documentation across projects and repositories. Use when searching documentation, finding related docs, finding API documentation, or gathering information about projects on Read the Docs.
readthedocs-write-config
Create or update Read the Docs `.readthedocs.yaml` v2 configuration files for Sphinx or MkDocs builds, including build images/tools, dependency installs, formats, custom build jobs/commands, conda environments, submodules, and search settings. Use when a user asks for a Read the Docs config file, YAML changes, or build behavior updates.
readthedocs-api
Full Read the Docs API v3 client guidance. Use when building or updating an API client, generating requests, or answering questions about Read the Docs API v3 endpoints (projects, versions, builds, subprojects, translations, redirects, environment variables, organizations, remote VCS resources, or embed content).
readthedocs-build-failure-triage
Triage Read the Docs build failures using build logs and config context. Use when a build fails, logs need analysis, or you need fix recommendations.
custom-code-review
Routes Fusion Framework pull request reviews through the repository canonical review policy. USE FOR: review this PR, review these changes, Copilot code review, inspect a pull request diff. DO NOT USE FOR: dependency update PRs, resolving existing review comments, implementing fixes, or repository-wide audits.
custom-dependency-pr-solver
Batch-processes Dependabot PRs in Fusion Framework: list, confirm, checkout, rebase, review, changeset, validate, comment, and merge high-confidence updates. USE FOR: process all Dependabot PRs, clear dependency backlog, batch-merge safe dependency updates. DO NOT USE FOR: feature PRs, non-Dependabot PRs, single-PR deep review, or updates needing manual code changes.
custom-npm-publishing
Guides npm publishing for Fusion Framework packages through trusted publishing (OIDC) from release.yml. USE FOR: adding a new public package, preparing a first release, reserving a package name on npm, snapshot or pre-release publishing, diagnosing failed or partial npm releases (ENEEDAUTH, 401, 404, provenance), npm trust audit/bootstrap/verify, changing the release workflow. DO NOT USE FOR: writing changesets, Dependabot PRs, VS Code Marketplace publishing, rebasing Version Packages PRs, or application code changes.
custom-rebase
Rebases Fusion Framework feature branches onto main and handles monorepo conflict traps. USE FOR: rebase this branch, refresh branch from main, fix pnpm-lock.yaml conflicts, resolve Version Packages conflicts, generate a rebase risk report. DO NOT USE FOR: dependency PR review, branch cleanup unrelated to rebase, or destructive reset without explicit approval.
fusion-code-conventions
Applies and explains code conventions across TypeScript, React, C#, and Markdown. Enforces naming rules, file naming patterns, TSDoc and XML doc standards, inline comment intent (the *why*, not the *what*), code structure, error handling, async patterns, and dead code policy. Also enforces ADR and contributor doc decisions, and flags decisions that appear stale or misaligned with current tooling. USE FOR: convention questions, code review against project standards, applying naming rules, auditing intent comments, checking TSDoc completeness, enforcing recorded ADR decisions, and flagging stale architectural decisions. DO NOT USE FOR: security vulnerability scanning, performance profiling, runtime debugging, or generating net-new code without a review target.
fusion-dependency-review
Review dependency PRs with structured research, existing-PR-discussion capture, multi-lens analysis (security, code quality, impact), and a repeatable verdict template. USE FOR: dependency update PRs, Renovate/Dependabot PRs, library upgrade reviews, "review this dependency PR", "should we merge this update". DO NOT USE FOR: feature PRs, application code reviews, dependency automation/bot configuration, or unattended merge without confirmation.
fusion-devtools
Use Fusion DevTools CLI (fdev) for API testing, token acquisition, service discovery, and person lookup during development. USE FOR: calling Fusion REST APIs, getting access tokens as JSON, discovering services and environments, resolving persons, PIM role activation. DO NOT USE FOR: modifying backend service code, deploying services, infrastructure changes, CI/CD pipeline configuration, or Service Bus operations.
fusion-github-review-resolution
Resolves unresolved GitHub PR review threads end-to-end: evaluates whether each review comment is correct, applies a targeted fix when valid, replies with rationale when not, commits, and resolves the thread. USE FOR: unresolved review threads, PR review feedback, changes requested PRs, PR review URLs (#pullrequestreview-...), fix the review comments, close the open threads, address PR feedback. DO NOT USE FOR: summarizing feedback without code changes, creating new PRs, or read-only branches.
fusion-issue-authoring
Classify issue type, activate the matching agent mode for type-specific drafting, and enforce shared safety gates before GitHub mutation.
fusion-issue-solving
Handles GitHub issue resolution end-to-end for prompts like "solve #123", "lets solve #123", "work on #123", "work on https://github.com/owner/repo/issues/123", or by pasting a direct GitHub issue URL as the request. USE FOR: solve #123, continue work on issue #123, work on https://github.com/owner/repo/issues/123, paste a GitHub issue URL for implementation work. DO NOT USE FOR: issue drafting only, PR review only, or non-implementation research.
fusion-issue-task-planning
Plan and break down user-story issues into ordered, traceable task issue drafts with explicit publish gates.
fusion-mcp
Explain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows.
fusion-research
Source-backed research orchestrator for the Fusion ecosystem. Routes to the correct research agent based on question type. Returns source-backed evidence only; will not invent Framework behavior, component APIs, skill catalog relationships, platform guidance, or backend implementation details. USE FOR: any research question needing source-backed evidence about Fusion Framework APIs, EDS components, the Fusion skill catalog, Fusion platform documentation, or backend service implementation. DO NOT USE FOR: implementing code changes, installing or editing skills, MCP setup or troubleshooting, or inventing Fusion behavior without evidence.
fusion-skill-authoring
Creates or modernizes repository skills with clear activation cues, purposeful support files, and practical review loops. USE FOR: creating a new skill, tightening an existing skill, improving discovery wording, and structuring references/assets/optional helper agents when they genuinely add value. DO NOT USE FOR: product-code changes, routine copy edits outside skills/, or documentation that should not become an installable skill.
fusion-skills
Entrypoint for all Fusion skill lifecycle operations. USE FOR: finding, installing, updating, syncing, or greenkeeping skills; setting up skill automation; creating or authoring a new skill; reporting a bug with a skill. DO NOT USE FOR: resolving GitHub issues, reviewing PRs, planning task breakdowns, or authoring GitHub issues — those are handled by other Fusion skills.
custom-index-eval
Evaluates Fusion MCP search quality against eval/index domain files. USE FOR: eval core, eval all, validate MCP index recall, check search freshness, verify documented framework patterns. DO NOT USE FOR: authoring eval patterns, editing docs, CI automation, or application-development search answers.
velt-approval-engine-best-practices
Best practices for the Velt Approval Engine (docs: Review Workflow Builder) for multi-step agent and human approval. Use for review workflows, /v2/workflow/ REST calls, definitions with agent, human, notification, or webhook nodes, edge on roles and reject loop-backs, quorum groups, SLAs, triggers (inbound webhook, cron, GitHub/Vercel app), agent node aiConfig, idempotent dispatch, reviewer decisions, or signed webhook delivery, even if the user does not say 'Approval Engine'.
velt-area-best-practices
Best practices for Velt Area Comments, the rectangle annotation mode of Comments where users draw a box and attach a thread to it. Use when toggling area comments (areaComment prop on VeltComments, or commentElement.enableAreaComment / disableAreaComment), styling area pins with CSS, reading the area pin componentConfig model, or typing AreaAnnotation, AreaProperty, and AreaTargetAnnotation (links to comments). Triggers on area comments or draw-a-box-and-comment UI, even without the word Velt.
velt-arrows-best-practices
Best practices for Velt Arrows, the directional arrow annotations users draw on DOM elements for design review and collaborative pointing. Use when placing VeltArrows and VeltArrowTool (or velt-arrows / velt-arrow-tool), restricting arrows with allowedElementIds, enabling darkMode, replacing or styling the tool button (custom button slot, ::part), calling getArrowElement, or typing ArrowAnnotation (arrowLength, arrowAngle). Triggers on Velt arrows or arrow annotations, even without the word Velt.
velt-chat-sdk-adapter-best-practices
Velt Chat SDK Adapter best practices for building bots that read and reply in Velt comment threads. Use when building a greeting, support, or AI bot that answers @-mentions, wiring createVeltAdapter and the webhook route, choosing v1 or v2 webhooks, handling reactions, or deploying the bot. Triggers on @veltdev/chat-sdk-adapter, createVeltAdapter, onNewMention, onSubscribedMessage, onReaction, thread.post, or Velt comment webhooks, even if the user doesn't say 'chat SDK adapter'.
velt-comments-best-practices
Velt Comments implementation patterns for React, Next.js, and web apps. Use when adding collaborative comments, including comment modes (Freestyle, Popover, Stream, Text, Page, Inline), editor integrations (TipTap, ProseMirror, Lexical, SlateJS, Apryse), comments sidebar V1/V2, private comments and Access Context, progress rows and action chips, agent comments and suggestion accept/reject, comment REST APIs, comment events, standalone components, wireframes, primitives, or template variables.
velt-crdt-best-practices
Velt CRDT (Yjs) collaborative editing best practices for real-time applications. Use when implementing collaborative features with Velt CRDT stores (useStore, createVeltStore), integrating Velt multiplayer editors (Tiptap, BlockNote, CodeMirror, ReactFlow, Lexical, Slate, Draft.js, ProseMirror, Quill, TinyMCE, CKEditor, SuperDoc, Monaco, Ace, Apryse, Nutrient, SpreadJS), or debugging sync issues. Triggers on real-time collaboration, multiplayer editing, CRDT stores, or Velt SDK integration.
velt-cursors-best-practices
Velt Cursors patterns for React, Next.js, and web apps. Use when adding live cursors (VeltCursor), confining cursors with allowedElementIds, avatar mode, cursor inactivity timeouts, useCursorUsers / getOnlineUsersOnCurrentDocument data, onCursorUserChange events, cursor pointer wireframes and componentConfig variables, or Live Selection indicator styling. Triggers on any task showing where other users point or select on a canvas or page, even if the user doesn't say 'cursors'.
velt-huddle-best-practices
Velt Huddle patterns for React, Next.js, and web apps. Use when adding in-app audio, video, or screen-sharing huddles (VeltHuddle, VeltHuddleTool), choosing the huddle type, in-call chat, flock mode on avatar click, cursor-mode huddle bubbles, serverFallback, huddle webhooks (created / joined, huddle.create / huddle.join), tool slots and CSS parts, or huddle wireframe variables. Triggers on any task involving huddles, voice or video calls, or screen sharing, even if the user doesn't say 'huddle'.
velt-live-state-sync-best-practices
Velt Live State Sync best practices for React, Next.js, and web apps. Use when adding real-time shared state across clients, syncing a Redux store, or broadcasting state from a server. Triggers on useLiveState, useSetLiveStateData, useLiveStateData, useLiveStateSyncUtils, getLiveStateSyncElement, fetchLiveStateData, useServerConnectionStateChangeHandler, createLiveStateMiddleware, livestate broadcast, or broadcastEvent, even if the user doesn't say 'live state sync'.
velt-node-sdk-best-practices
Velt Node SDK (`@veltdev/node` 2.x) patterns for Node.js and TypeScript backends, covering `VeltSDK.initialize` (REST-only or self-hosting), `sdk.api.*` REST services, `sdk.selfHosting.*` on MongoDB or PostgreSQL plus S3, `accessControl.generateToken` for frontend JWTs, `verifyToken` resolver auth, `filterUnknownFields`, and typed errors (`VeltApiError`, `VeltDatabaseError`). Triggers on `@veltdev/node`, `VeltSDK`, `sdk.api`, `sdk.selfHosting`, or server-side Velt Node code.
velt-notifications-best-practices
Velt Notifications implementation patterns and best practices for React, Next.js, and web applications. Use when adding in-app notifications, notification panels, email notifications via SendGrid, webhook integrations (private-comment visibility), user preference management, cross-organization feeds (enableCrossOrganization), user-scoped For You notifications (enableUserScopedNotifications), self-hosted custom notifications, or binding Notifications Panel/Tool wireframe variables.
velt-presence-best-practices
Velt Presence patterns for React, Next.js, and web apps. Use when adding who's-online avatars (VeltPresence), online/away/offline status, inactivity timeouts, maxUsers overflow, location-scoped presence, usePresenceData / getData subscriptions, userStateChange events, AI agent or bot participants via addUser, flock mode (follow me), VeltCursor setup, or presence wireframes. Triggers on any task involving user presence or collaborative awareness, even if the user doesn't explicitly say 'presence'.
velt-proxy-server-best-practices
Velt proxy server setup for routing Velt SDK traffic through your own reverse proxies on Cloudflare Workers or nginx. Use when configuring proxyConfig (cdnHost, apiHost, v2DbHost, v1DbHost, storageHost, authHost, forceLongPolling) on VeltProvider or initVelt, deploying velt-proxy-server recipes, whitelisting Velt in a Content Security Policy, enabling SRI, or debugging proxy issues. Triggers on Velt proxy, reverse proxy, CSP, or network-policy tasks, even if the user doesn't say 'proxy'.
velt-reactions-best-practices
Best practices for Velt Inline Reactions, emoji reactions anchored to elements of your app (articles, posts, images, charts). Use when adding VeltInlineReactionsSection with targetReactionElementId, configuring custom emojis (url, iconUrl, emoji) via customReactions or setCustomReactions, using getReactionElement or useReactionElement, building custom UI with the reaction wireframes and componentConfig variables, or typing ReactionAnnotation. Triggers on Velt reactions or emoji feedback on content.
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.
Page 5 of 1675 · 83716 results