dust-tt
- 18 skills
- 0 followers
- 15 hours ago last updated
- ▌ Wb · dust-ttUse the wb CLI to browse the web, search, read pages, and interact with websites. Use when the user asks to look something up online, visit a website, extract content from a page, or interact with web elements.
- ▌
- ▌ Dust LLM · dust-ttStep-by-step guide for adding support for a new LLM in Dust, and for deprecating or removing the model it supersedes (including the agent-config repoint migration). Use when adding a new model, updating a previous one, or retiring a decommissioned one.
- ▌ Dust Test · dust-ttStep-by-step guide for writing focused, practical tests for Dust codebases following the 80/20 principle.
- ▌ Dust Flavify · dust-tt bundleReview a pull request, branch, commit, diff, or pending changes against Dust's strictest review bar. Use when the user asks to "dust-flavify", "flavify", run a Flavify review, or audit a change against Dust's review standards. Produce a read-only, evidence-backed review that prioritizes existing-pattern reuse, ownership boundaries, database access paths, simplicity, current Dust coding rules, and relevant platform risks. Never post review output or mutate anything on GitHub.
- ▌ Dust Swagger · dust-ttMANDATORY guideline - Always keep Swagger documentation in sync when modifying API endpoints or schemas.
- ▌ Dust Temporal · dust-ttStep-by-step guide for creating Temporal workflows in Dust. Use when adding background jobs, async processing, durable workflows, or task queues.
- ▌
- ▌ Dust Call Agent · dust-ttCall a Dust agent for Dust company context or to access tools, data, and actions unavailable through the current agent's native capabilities. Never use a Dust agent as a proxy for Slack, Notion, Google Drive, calendars, or any other service when native access is available; use the native tool instead because it is faster and more efficient.
- ▌ Dust MCP Server · dust-ttStep-by-step guide for creating new internal MCP server integrations in Dust that connect to remote platforms (Jira, HubSpot, Salesforce, etc.). Use when adding a new MCP server, implementing a platform integration, or connecting Dust to a new external service.
- ▌ Dust DB Migration · dust-ttStep-by-step guide for creating and running SQL schema migrations in `front` or `connectors` using the `npm run migration:*` tooling (pg-schema-diff + Umzug). Use when adding or removing columns, tables, or indexes that require a coordinated deploy.
- ▌ Dust Elasticsearch · dust-tt bundleCreate, migrate, or query Elasticsearch indices in `front`. Use when adding a new front Elasticsearch index, changing mappings or settings, wiring indexing logic, or exposing Elasticsearch-backed analytics/search endpoints.
- ▌ Dust Webhook Source · dust-ttImplement a new built-in webhook source provider in `front`. Use when adding a webhook provider such as Linear, GitHub, or Fathom, including provider research, OAuth prerequisites, provider-specific types and client code, preset registration, UI components, and end-to-end testing.
- ▌ Dust Audit Log Event · dust-ttAdd a new audit log event in `front`. Use when instrumenting a new user or system action for WorkOS audit logging, including schema creation, `AuditAction` updates, and the correct emit call after the mutation path.
- ▌ Dust Breaking Changes · dust-ttCRITICAL guideline - Never introduce breaking changes to the private API without explicit user approval. Always warn and ask for validation first.
- ▌ Dust Writing React Effects · dust-ttWrites React components without unnecessary useEffect. Use when creating/reviewing React components, refactoring effects, or when code uses useEffect to transform data or handle events.
- ▌ Dust React Hook Form Writer · dust-ttWrite and refactor React forms using react-hook-form with Zod validation. Use when creating new form components, converting existing forms to react-hook-form, or implementing form validation patterns.
- ▌ Dust Hive · dust-ttInformation about dust-hive, a CLI tool for running multiple isolated Dust development environments. ALWAYS enable this skill when the working directory is under a repository's `.hives/` directory or `~/dust-hive/`, when its `.envrc` identifies a dust-hive environment, or when working with dust-hive. Use for understanding port allocation, running tests, and working with the environment.