This branch covers two things: the catalogue of every Claude skill we've built, and the methodology behind how we structure work in Claude Projects. Together they're the operating system for how we use AI day to day.
Loadable capabilities that travel with Claude across every Project. A skill is a folder of structured instructions Claude reads when its triggers fire. Same skill, same behaviour, whether the chat is in BD, Advisory or any client Project.
dttt-advisory-creditsPersistent workspaces with their own knowledge, memory and chat history. A Project is a container for a distinct stream of work. Knowledge in one Project doesn't bleed into another, which is why we use them deliberately.
Full inventory of every skill currently available, organised by domain. Each entry covers what the skill does, what triggers it, what's inside it, and what it depends on. The source of truth — update here when a skill ships, is materially changed or is deprecated.
How we name, structure and use Claude Projects. When to create a new one, when to retire one, what goes in Project knowledge versus in chats, and the working patterns for switching context. Plus the current Project inventory.
Gaps surfaced through ongoing work. Skills that should exist but don't yet, what each would do, and what triggered the need. When a roadmap item ships, it moves to the catalogue.
A quick view of every skill we have, grouped by domain. Open the skills catalogue for full detail on each.
When a roadmap skill is built, the entry moves out of Roadmap and into the relevant section of the Skills catalogue. When a skill is deprecated, it stays in the catalogue under a Deprecated subsection but is removed from active categories. The catalogue is the source of truth — this landing page mirrors it.
Two naming patterns. [Client/Event] · [Year] for time-bound work that wraps when the engagement or event ends. DTTT · [Production] for standing Projects that don't expire. Keep the convention tight; sprawl is the real cost.
| Project | Type | Notes |
|---|---|---|
| Client & Event · time-bound | ||
| XDW 2026 | Event | X. Design Week — Destination AI Intensive |
| CAMPUS 2026 | Event | Annual capability-building programme |
| FRONTIERS 2026 | Event | Frontiers research event |
| FDB 2026 | Event | Future Destinations Brussels |
| ATM 2026 | Event | Arabian Travel Market activation |
| WTM 2026 | Event | World Travel Market activation |
| ITB 2027 | Event | ITB Berlin activation |
| VisitBritain AI Programme 2026 | Client | AI programme engagement |
| Visit Greenland Strategy 2026 | Client | Strategy engagement |
| Aruba Tourism Authority 2026 | Client | Client engagement |
| Airbnb Rural Tourism Renaissance 2025 | Client | Research partnership engagement |
| DTTT · standing | ||
| DTTT Production | Standing | Production work across the business |
| DTTT Marketing | Being created | Marketing & communications workstream |
| DTTT Admin & Logistics | Standing | Operational admin and logistics |
| DTTT Research | Standing | Research workstream |
The inventory drifts. The Claude UI is the live source — this table reflects the naming convention agreed May 2026. The standalone Internal | Knowledge System Project (where this intranet is being built) sits outside both categories.