Dashboard architecture

[brillout]

With the new skills architecture everything becomes modular: the user can cherry-pick the skills he wants to use.

For example, Claude Code Web already manages branches, so the user might want to skip skills-branch.

Another example: the user might want to skip skills-tickets if he's not interested in that functionality.

Ideally, the dashboard should show UI only for skills that are picked. How do we structure this?

[brillout]

I wonder how skill-logs can be shown in the dashboard.

Maybe one page per skill:

• Tickets (skill-tickets) => /tickets
• Agents (skill-logs) => /agents

It's an unusual UI but I think it's okay? No significant UX degradation AFAICT?

Note

AFAICT the modularity is 10x more important than minor UX paper cuts.

Also maybe some kind of hook to add cards to the dashboard's landing page.

[suleimansh]

The plan for this, with the six questions it needs answered and my picks, is in #1774.