Loading...
Loading...
Found 8,858 Skills
[Pragmatic DDD Architecture] Guide for creating tests. Use when creating unit tests, integration tests, or understanding test conventions. Covers our tightly coupled stack: Vitest (unit, integration, ui projects), file naming, transactional database integration tests (txTest) with testcontainers/node-postgres/drizzle, mock patterns (createMock*RepoWithAssertions), and neverthrow Result assertions.
Hostaway integration. Manage data, records, and automate workflows. Use when the user wants to interact with Hostaway data.
Chatfuel integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chatfuel data.
Kibana integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kibana data.
Customer.guru integration. Manage Persons, Organizations, Deals, Leads, Projects, Pipelines and more. Use when the user wants to interact with Customer.guru data.
Ramp integration. Manage Organizations. Use when the user wants to interact with Ramp data.
Copperx integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with Copperx data.
MUST be used whenever adding a task/todo list feature to a Dune app with Atlas chat. Do NOT manually create todo state management or tool definitions — this skill handles the full module (context, provider, tool, hooks, UI components) and all integration wiring. Prerequisite: integrate-atlas-chat must already be set up. Triggers: todo list, task list, task tracking, TodoWrite, todo panel, task panel, progress tracking, add todos, add tasks.
Prismic integration. Manage Repositories. Use when the user wants to interact with Prismic data.
Beacon integration. Manage data, records, and automate workflows. Use when the user wants to interact with Beacon data.
Zephyr Essential Cloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zephyr Essential Cloud data.
Loads orchestrate mode — a disciplined delivery loop that enforces BDD specs in specs/, real integration tests (no mocks), PR CI and CodeRabbit babysitting, and mandatory end-user QA via computer-use or CLI dogfooding before anything is considered done. Use when starting any non-trivial implementation task, feature build, or delivery where you want the work driven from spec to proven-shipped state rather than stopping at "tests pass".