saas-dashboard
Skill0 starsChanged 3 days agoMITView on GitHub
Design SaaS workspaces for onboarding, recurring work, account context, and clear paths to product value.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ImBIOS/skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ImBIOS/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- accessibilitySkill
- admin-panelSkill
- ai-agent-interfaceSkill
- ai-chat-interfaceSkill
- ai-dashboardSkill
- ai-engineeringSkill
- analytics-and-data-visualizationSkill
- animation-and-motionSkill
- api-engineeringSkill
- authentication-and-rbacSkill
- backend-architectureSkill
- component-engineeringSkill
- dashboard-designSkill
- database-engineeringSkill
- design-intelligenceSkill
- design-systemsSkill
- frontend-engineeringSkill
- iconographySkill
- image-art-directionSkill
- integrations-and-webhooksSkill
- javascript-typescriptSkill
- performance-optimizationSkill
- premium-landing-pagesSkill
- python-engineeringSkill
- rag-and-knowledge-systemsSkill
- responsive-designSkill
- security-engineeringSkill
- super-admin-panelSkill
- testing-and-qualitySkill
- unslop-engineSkill
- ux-researchSkill
- visual-designSkill
- visual-regressionSkill
- website-architectureSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use for authenticated SaaS landing dashboards, organization workspaces, onboarding, or recurring product workflows.
- Distinctive: line 15
Do not assume every SaaS home needs KPI cards, a sales funnel, or a marketing-style hero.
- Distinctive: line 33
Keep global navigation and page-level actions predictable.
- Distinctive: line 34
Test role changes, multiple workspaces, narrow screens, and returning sessions.
- Distinctive: line 40
Do not use onboarding to force unnecessary data collection.
- Very specific: line 58
Verify workspace/role context, first-run and return flows, entitlements, empty/loading/error states, and clear access to recurring tasks.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SaaS Dashboard
When to use
Use for authenticated SaaS landing dashboards, organization workspaces, onboarding, or recurring product workflows.
When not to use
Do not assume every SaaS home needs KPI cards, a sales funnel, or a marketing-style hero. Follow the actual product task.
Inputs and assumptions
Identify roles, organization and project context, first-session state, recurring actions, entitlements, and available real data.
Workflow
- Establish which workspace or account the user is in and how to switch it.
- Prioritize the next useful action and recent relevant activity.
- For new accounts, provide a concrete first-run path with progress and optional setup steps.
- Reflect permissions and plan entitlements accurately; explain unavailable actions and upgrade paths without blocking unrelated work.
- Include loading, no-data, failure, stale-data, and completed onboarding states.
- Keep global navigation and page-level actions predictable.
- Test role changes, multiple workspaces, narrow screens, and returning sessions.
Decision rules
- Show metrics only when they help the user's next decision.
- Do not use onboarding to force unnecessary data collection.
- Preserve access to core tasks when optional setup is incomplete.
- Clearly distinguish account-level from project-level data.
Example
For a design collaboration product, a first visit can guide workspace creation, importing a project, or joining an invitation; an empty KPI grid does not help the user reach value.
Common failures
- The same dashboard for every role and lifecycle stage.
- Unclear organization context or inaccessible workspace switching.
- Empty states that merely say “No data”.
Validation
Verify workspace/role context, first-run and return flows, entitlements, empty/loading/error states, and clear access to recurring tasks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.