- Home
- Skills
- UX & UI Design
- SaaS Dashboard UI Architect
More screenshots
Works with the AI Agents you already use
SaaS Dashboard UI Architect
Architects professional SaaS dashboards for analytics products, admin panels, AI tools, CRMs, and B2B applications, covering navigation, layouts, metrics, cards, charts, filters, tables, workflows, onboarding, states, responsive behavior, accessibility, developer handoff, and QA.
$7.99
SaaS Dashboard UI Architect
Example session with this skill installed
Product name
PulseTrack Customer Success Platform
Product category
B2B customer success SaaS
Target users
Customer success managers
Customer success team leads
Revenue operations managers
Executives
Primary user roles
Customer Success Manager
Team Lead
Administrator
Executive Viewer
Core user jobs
Identify accounts at risk
Understand health-score changes
Review upcoming renewals
Assign follow-up tasks
Launch customer-success playbooks
Monitor product adoption
Prepare executive reports
Business model
Subscription-based SaaS with team and enterprise plans
Primary activation event
The first customer account is imported and receives a calculated health score.
Primary retention behavior
Customer success managers review account health and complete intervention tasks every week.
Core data entities
Organizations
Workspaces
Users
Customer Accounts
Contacts
Health Scores
Risk Signals
Tasks
Playbooks
Renewals
Activities
Integrations
Reports
Key metrics
Accounts at risk
Upcoming renewals
Open high-priority tasks
Average health score
Health-score change
Adoption risk
Renewal value at risk
Completed interventions
Critical workflows
Connect CRM
Import customer accounts
Review at-risk accounts
Open account detail
Review risk drivers
Assign follow-up task
Launch playbook
Update renewal status
Export executive report
Existing pages
Login
Dashboard
Accounts
Account Detail
Tasks
Reports
Integrations
Settings
Required pages
Onboarding
Workspace Setup
Dashboard Home
Accounts
Account Detail
Tasks
Playbooks
Reports
Integrations
Team Management
Billing
Settings
Audit Log
Navigation preference
Persistent desktop sidebar with mobile navigation drawer
Tenant model
Multi-tenant organizations with multiple workspaces
Permission model
Granular role-based permissions
Data density
High
Real-time requirements
Risk signals and task updates should refresh frequently.
Formal real-time behavior requires technical confirmation.
Frontend stack
Next.js
React
TypeScript
Tailwind CSS
Component library
Custom components based on Radix primitives
Design system
Partial
Responsive targets
Desktop
Tablet
Mobile
Accessibility target
WCAG 2.2 AA implementation review
Localization
English at launch
Future multilingual support
Allow approximately 30% text expansion
Need output
Complete SaaS dashboard architecture
Application shell
Navigation and route map
Dashboard home
Metric dictionary
Card and chart specifications
Filter system
Table specifications
User flows
Onboarding
Empty states
Loading and error states
Permissions
Responsive behavior
Component inventory
Accessibility requirements
Analytics events
Developer handoff
Acceptance criteria
QA checklist
Risk assessment
Special constraints
Clearly separate observed facts from assumptions.
Do not invent metrics or customer behavior.
Avoid dark patterns.
Include sample-data onboarding.
Make permissions visible before users attempt restricted actions.
Include loading, empty, error, offline, partial-data, and plan-limited states.
- Read your context and instructions
- Compiled the saas dashboard ui
=== SAAS DASHBOARD UI ARCHITECTURE ===
Product
PulseTrack Customer Success Platform
Product Category
B2B customer success SaaS
Primary Dashboard Job
Help customer success teams identify accounts requiring attention, understand the reason for risk, and initiate the correct intervention.
=== EXECUTIVE SUMMARY ===
PulseTrack should use an operational dashboard rather than a purely analytical dashboard.
The interface must help users complete a recurring decision loop:
Notice
Which customer accounts require attention?
Interpret
Why is the account considered at risk?
Decide
What intervention is appropriate?
Act
Assign a task, contact the customer, or launch a playbook.
Confirm
Verify ownership, deadline, and status.
Recover
Provide clear retry, reassignment, and escalation behavior when an action fails.
The dashboard should prioritize actionable exceptions and upcoming renewals above general summary metrics.
=== TARGET USERS ===
Customer Success Manager
Needs an operational queue, account context, tasks, risk drivers, and playbooks.
Team Lead
Needs team workload, account coverage, unresolved risks, and performance trends.
Administrator
Needs workspace setup, integrations, permissions, billing, and audit access.
Executive Viewer
Needs outcome-level metrics, renewal risk, trends, and exportable reports.
=== ACTIVATION AND RETENTION ===
Primary Activation Event
The first customer account is imported and receives a usable health score.
Activation Prerequisites
- Workspace created
- CRM connected or file imported
- Account data mapped
- Health model configured
- Initial synchronization completed
Primary Retention Behavior
Customer success managers review account health and complete intervention tasks weekly.
=== APPLICATION SHELL ===
Desktop
- Persistent 240-pixel sidebar
- Workspace switcher
- Global search
- Notification center
- Help menu
- Account menu
- Main content container
- Contextual page actions
Tablet
- Collapsible navigation rail
- Reduced top-bar controls
- Wrapped filter controls
- Two-column card grids
Mobile
- Modal navigation drawer
- Condensed top bar
- Stacked dashboard modules
- Filter drawer
- Full-width detail panels
- Sticky primary action only when it supports the current task
=== PRIMARY NAVIGATION ===
Home
Operational overview and priority work.
Accounts
Customer account list and segmentation.
Tasks
Personal and team task queues.
Playbooks
Reusable intervention workflows.
Reports
Analytical and executive reporting.
Integrations
CRM, product analytics, support, and communication connections.
Team
Users, roles, assignments, and workload.
Settings
Workspace, health model, notifications, billing, and security.
Audit Log
Administrator-only activity and configuration history.
=== ROUTE MAP ===
Route
/
Page
Dashboard Home
Primary Role
Customer Success Manager
Primary Action
Review accounts requiring attention
Route
Accounts
Page
Account Directory
Primary Role
Customer Success Manager
Primary Action
Open or segment customer accounts
Route
Accounts / Account ID
Page
Account Detail
Primary Role
Customer Success Manager
Primary Action
Review health drivers and initiate intervention
Route
Tasks
Page
Task Queue
Primary Role
Customer Success Manager
Primary Action
Complete, assign, or reschedule tasks
Route
Reports
Page
Reports Library
Primary Role
Team Lead and Executive Viewer
Primary Action
Open, schedule, or export reports
=== DASHBOARD HOME STRUCTURE ===
Section 1:
Page title, selected workspace, data freshness, and date context.
Section 2:
Setup or integration banner when critical data sources are incomplete.
Section 3:
Actionable priority cards.
Cards
- Accounts at Risk
- Upcoming Renewals
- High-Priority Tasks
- Accounts Without an Owner
Section 4:
Account Risk Queue
Purpose
Show customer accounts requiring immediate action.
Columns
- Account
- Health
- Primary Risk Driver
- Renewal Date
- Owner
- Last Activity
- Recommended Action
Section 5:
Health Score Trend
Question
How is portfolio health changing over time?
Chart
Line chart with current-period and comparison-period series.
Section 6:
Renewal Risk
Question
How much renewal value is associated with at-risk accounts?
Chart
Segmented bar chart with drill-down to filtered accounts.
Section 7:
Open Tasks
Purpose
Provide a direct operational queue.
Section 8:
Recent Account Activity
Purpose
Show material account events without becoming a noisy event stream.
Section 9:
Data Freshness and Integration Health
Purpose
Communicate delayed, disconnected, or partially synchronized data.
=== METRIC DICTIONARY ===
Metric
Accounts at Risk
Business Meaning
Customer accounts meeting the approved risk criteria.
User Meaning
Accounts likely to require intervention.
Formula
Defined by the approved health-scoring model.
Time Context
Current portfolio state.
Comparison
Change from the prior equivalent period.
Positive Direction
Lower, provided account coverage remains stable.
Drill-Down
Filtered account list.
Missing Data
Show an incomplete-data status rather than a misleading zero.
Metric
Renewal Value at Risk
Business Meaning
Expected renewal value associated with accounts currently classified as at risk.
Formula
Sum of approved renewal values for qualifying accounts.
Important Boundary
Do not calculate or display this metric unless renewal values and risk definitions are reliable.
=== KPI CARD SPECIFICATION ===
Component
Risk Summary Card
Anatomy
- Metric label
- Primary value
- Unit
- Comparison
- Trend indicator
- Data freshness
- Supporting context
- Optional drill-down
States
- Default
- Loading
- Empty
- Partial Data
- Stale Data
- Error
- Permission Restricted
Accessibility
- Trend direction must include text.
- Partial or stale data must be announced.
- Interactive cards require a clear accessible name.
- Loading updates should not repeatedly interrupt screen-reader users.
=== ANALYTICS PANEL ===
Panel
Health Score Trend
Business Question
Is the portfolio becoming healthier or riskier?
Chart Type
Line chart
X-Axis
Time
Y-Axis
Health score or approved health category share
Default Date Range
Last 90 days
Comparison
Previous 90 days
Tooltip
- Date
- Current value
- Comparison value
- Difference
- Data completeness note
Interaction
Select a period to open the filtered account list.
Accessibility
- Provide a textual trend summary.
- Provide an accessible data-table alternative.
- Do not rely on line color alone.
- Support keyboard access for interactive data points where required.
=== FILTER SYSTEM ===
Global Filters
- Workspace
- Date Range
- Account Segment
- Owner
- Health Status
Page-Level Filters
- Renewal Window
- Plan
- Industry
- Region
- Risk Driver
- Product Adoption Level
Filter Behavior
- Persist approved filters in the URL.
- Allow users to clear all filters.
- Show active-filter count.
- Save commonly used views.
- Filter options must respect permissions.
- On mobile, secondary filters open in a full-width drawer.
=== SAVED VIEWS ===
Fields
- View Name
- Owner
- Visibility
- Filters
- Sorting
- Visible Columns
- Grouping
- Date Range
- Default View
- Edit Permission
Visibility Options
- Private
- Team
- Workspace
=== ACCOUNT TABLE ===
Rows Represent
Customer accounts
Columns
- Account Name
- Health Status
- Health Score
- Primary Risk Driver
- Renewal Date
- Renewal Value
- Owner
- Open Tasks
- Last Activity
- Actions
Default Sort
Highest risk, then nearest renewal date
Available Features
- Search
- Filter
- Sort
- Column visibility
- Row selection
- Bulk owner assignment
- Bulk task creation
- Export subject to permission
Loading State
Use stable-row skeletons without shifting column widths.
Empty State
Explain whether there are no accounts, no matching filters, no permission, or no synchronized data.
Responsive Behavior
Desktop
Full table with configurable columns.
Tablet
Horizontal scroll with Account, Health, Renewal, and Owner prioritized.
Mobile
Transform rows into account cards with essential fields and a detail action.
=== CRITICAL USER FLOW ===
Flow
Respond to an At-Risk Account
User
Customer Success Manager
Entry
Dashboard risk queue or account list
Steps
- Open account.
- Review health score and risk drivers.
- Review recent product and support activity.
- Confirm renewal context.
- Select an intervention.
- Assign owner.
- Set deadline.
- Launch playbook or create task.
- Confirm creation.
- Return to updated queue.
Failure State
If task creation fails, preserve all entered values and provide retry.
Permission State
If the user cannot launch playbooks, explain the required role and provide an access-request path when available.
Analytics Events
- at_risk_account_opened
- risk_driver_viewed
- intervention_selected
- task_created
- playbook_launched
- intervention_failed
=== ONBOARDING ARCHITECTURE ===
Onboarding Model
Guided setup checklist with optional sample workspace.
Required Steps
- Create workspace.
- Connect CRM or import accounts.
- Map account fields.
- Configure health model.
- Invite team.
- Assign account owners.
- Review first risk queue.
Sample Data
Provide a clearly labeled sample workspace so users can understand the product before integration.
Completion State
Show the first real account health results and recommend reviewing the risk queue.
=== EMPTY STATES ===
First-Use Dashboard
Headline
Connect customer data to build your first health dashboard.
Explanation
PulseTrack needs account and activity data before it can calculate meaningful health signals.
Primary Action
Connect CRM
Secondary Action
Import CSV
Optional Action
Explore Sample Workspace
Filtered Empty
Headline
No accounts match these filters.
Primary Action
Clear Filters
Secondary Action
Edit Saved View
Permission Empty
Headline
You do not have access to account health data.
Action
Request access or contact the workspace administrator.
=== LOADING AND ERROR STATES ===
Initial Dashboard Loading
Use skeletons matching the final module dimensions.
Background Refresh
Keep current data visible and show a non-blocking refresh indicator.
Partial Data
Identify affected sources and preserve reliable modules.
Integration Failure
Show the disconnected integration, last successful sync, impact, and reconnect action.
Offline
Preserve cached information when technically and legally appropriate and explain that updates are unavailable.
=== ROLE AND PERMISSION MATRIX ===
Customer Success Manager
- View assigned and permitted accounts
- Create and complete tasks
- Launch approved playbooks
- View operational reports
Team Lead
- View team accounts
- Reassign work
- Review team workload
- Access team reports
Administrator
- Manage workspace
- Manage integrations
- Manage users and permissions
- Configure health model
- Access billing
- Access audit log
Executive Viewer
- View approved executive reports
- No operational editing
- No billing or user-management access unless separately granted
=== MULTI-TENANT BEHAVIOR ===
- Display the current workspace at all times.
- Scope navigation, search, notifications, and data to the selected workspace.
- Confirm destructive actions using the workspace name.
- Prevent cross-workspace data leakage.
- Preserve deep links only when the user has access.
- Remember the last approved workspace.
- Revalidate permissions after workspace switching.
=== RESPONSIVE MATRIX ===
Sidebar
Extra Large
Persistent full sidebar.
Large
Persistent full sidebar.
Medium
Collapsed rail or temporary drawer.
Small
Modal navigation drawer.
KPI Cards
Extra Large
Four columns.
Large
Four columns.
Medium
Two columns.
Small
One column.
Filters
Extra Large
Inline.
Large
Inline.
Medium
Wrapped.
Small
Primary filter visible with secondary filters in a drawer.
Risk Table
Extra Large
Full table.
Large
Full table.
Medium
Horizontal scroll with prioritized columns.
Small
Account cards.
=== COMPONENT INVENTORY ===
Foundations
- Semantic Colors
- Typography
- Spacing
- Borders
- Radii
- Elevation
- Motion
- Breakpoints
- Grid
Layout
- AppShell
- PageContainer
- Stack
- Inline
- Grid
- SplitPane
- ScrollArea
Navigation
- Sidebar
- TopBar
- WorkspaceSwitcher
- Breadcrumbs
- Tabs
- MobileDrawer
- CommandPalette
- Pagination
Actions
- Button
- IconButton
- SplitButton
- MenuButton
- Link
Forms
- TextField
- Select
- Combobox
- Checkbox
- RadioGroup
- Switch
- DateRangePicker
- FilterBar
- ErrorSummary
Data
- KPI Card
- Chart Card
- Data Table
- Account Card
- Status Badge
- Activity Feed
- Audit Log
- Progress
Feedback
- Alert
- Toast
- Skeleton
- Spinner
- Empty State
- Error State
- Permission State
- Offline State
Overlays
- Modal
- Drawer
- Popover
- Tooltip
- Confirmation Dialog
- Detail Panel
Domain Components
- Account Health Card
- Risk Driver List
- Renewal Risk Panel
- Intervention Selector
- Playbook Launcher
- Integration Status Panel
=== ACCESSIBILITY REQUIREMENTS ===
- Use semantic landmarks.
- Maintain logical heading hierarchy.
- Provide skip navigation.
- Support complete keyboard access.
- Use visible focus indicators.
- Preserve logical focus order.
- Provide persistent form labels.
- Use sufficient contrast.
- Do not rely on color alone.
- Associate errors with fields.
- Provide error recovery.
- Announce loading and asynchronous completion appropriately.
- Provide chart summaries and data alternatives.
- Use semantic table structures.
- Manage modal and drawer focus.
- Respect reduced-motion settings.
- Support browser zoom and responsive reflow.
- Keep mobile reading order logical.
- Provide accessible names for icon-only controls.
=== ANALYTICS INSTRUMENTATION ===
Event
dashboard_viewed
Properties
- workspace_id
- role
- setup_status
- data_freshness
Purpose
Measure dashboard use and setup readiness.
Event
risk_account_opened
Properties
- source_module
- risk_category
- user_role
Purpose
Measure whether dashboard modules lead to investigation.
Event
empty_state_action_clicked
Properties
- empty_state_type
- action
- user_role
Purpose
Evaluate onboarding and recovery paths.
Privacy Note
Do not include customer names, private contact data, or sensitive account details in analytics-event properties unless explicitly justified and approved.
=== IMPLEMENTATION SEQUENCE ===
- Confirm users, roles, jobs, and dashboard purpose.
- Confirm entities, metrics, formulas, and data freshness.
- Confirm application shell and routes.
- Confirm permissions and workspace boundaries.
- Define semantic design tokens.
- Build primitive components.
- Build navigation and page templates.
- Build KPI cards, charts, filters, tables, and account cards.
- Implement loading, empty, error, offline, and permission states.
- Implement risk-review workflow.
- Implement onboarding.
- Implement responsive behavior.
- Complete accessibility implementation.
- Add approved analytics events.
- Complete visual, functional, responsive, and accessibility QA.
- Resolve open decisions and document deviations.
=== ACCEPTANCE CRITERIA ===
First-Use Dashboard
Given a new workspace has no imported data,
when the user opens the dashboard,
then the system explains why analytics are unavailable, provides CRM and CSV setup actions, offers an optional sample workspace, and does not display meaningless zero-value KPI cards.
At-Risk Workflow
Given a permitted customer success manager opens an at-risk account,
when the account detail loads,
then the interface displays risk drivers, recent activity, renewal context, account owner, open tasks, and available intervention actions.
Mobile Navigation
Given the viewport is below the small-screen breakpoint,
when the user activates the navigation control,
then a modal drawer opens, focus moves into it, background keyboard interaction is prevented, Escape closes it, and focus returns to the trigger.
Partial Data
Given one integration fails while other data sources remain available,
when the dashboard loads,
then reliable modules remain visible, affected modules show a partial-data state, and the integration status area provides recovery guidance.
Permission State
Given a user lacks permission to launch a playbook,
when the intervention controls are displayed,
then the restricted action is communicated before the user enters unnecessary information and an access path is provided when available.
=== QA CHECKLIST ===
Product QA
- Verify dashboard purpose.
- Verify role-specific modules.
- Verify activation path.
- Verify operational priority.
- Verify empty-state actions.
Data QA
- Verify formulas.
- Verify time ranges.
- Verify comparisons.
- Verify units.
- Verify missing-data behavior.
- Verify freshness indicators.
Interaction QA
- Verify navigation.
- Verify filters.
- Verify saved views.
- Verify tables.
- Verify search.
- Verify bulk actions.
- Verify task creation.
- Verify retry behavior.
Responsive QA
- Verify sidebar transformation.
- Verify card reflow.
- Verify filter drawer.
- Verify mobile account cards.
- Verify overlay dimensions.
- Verify keyboard obstruction.
Accessibility QA
- Verify landmarks.
- Verify headings.
- Verify keyboard access.
- Verify focus.
- Verify labels.
- Verify contrast.
- Verify chart alternatives.
- Verify error recovery.
- Verify reduced motion.
- Verify zoom and reflow.
Permission QA
- Verify every role.
- Verify workspace boundaries.
- Verify exports.
- Verify billing access.
- Verify audit access.
- Verify session behavior after role changes.
=== RISK ASSESSMENT ===
Metric Definition Risk
High
Reason
Health scores and renewal-risk metrics require approved formulas and reliable source data.
Mitigation
Create a formal metric dictionary and data-quality rules before final UI implementation.
Permission Risk
High
Reason
Multi-tenant customer data must remain isolated by workspace and role.
Mitigation
Define and test a complete permission matrix across routes, search, notifications, exports, and cached data.
Responsive Table Risk
High
Reason
Dense account data may not translate directly to mobile.
Mitigation
Use account cards for small screens and preserve full tables on larger devices.
Onboarding Risk
Moderate
Reason
The product may appear empty before integrations are connected.
Mitigation
Provide a guided checklist, import options, and a clearly labeled sample workspace.
Chart Interpretation Risk
Moderate
Reason
Health and renewal data can be misunderstood without definitions and context.
Mitigation
Provide metric definitions, time ranges, comparisons, freshness indicators, and accessible summaries.
=== OPEN QUESTIONS ===
- What exact formula determines account health?
- Which risk drivers are visible to each role?
- How frequently does each integration synchronize?
- Can users customize KPI cards?
- Are filters shared across users?
- Can saved views be workspace-wide?
- Which roles can export customer data?
- Are playbook actions reversible?
- What happens when an account belongs to multiple workspaces?
- Which events require audit-log entries?
- What data is available during an integration outage?
=== KNOWN LIMITATIONS ===
- Final formulas require analytics and domain validation.
- Final permissions require security and backend validation.
- Final responsive behavior requires browser and device testing.
- Accessibility requires implementation testing.
- Production performance depends on dataset size, architecture, and API behavior.
- The architecture does not guarantee activation, retention, revenue growth, adoption, customer satisfaction, or reduced support volume.
=== FINAL IMPLEMENTATION NOTE ===
Treat this architecture as an implementation contract only after product, design, engineering, analytics, accessibility, security, and domain owners resolve the open questions and approve the assumptions.
Connects securely to your tools. The creator never sees your data.
About this skill
SaaS Dashboard UI Architect helps SaaS founders, UI/UX designers, frontend developers, startup teams, indie hackers, product managers, agencies, and design-system teams create clear, scalable, actionable, and implementation-ready dashboard experiences.
The skill transforms a SaaS concept, product requirement, workflow, dataset, business model, or existing interface into a complete dashboard architecture based on user jobs, business goals, data meaning, workflow priority, operational frequency, and technical constraints.
It defines the product context, target users, user roles, activation event, retention behavior, core entities, dashboard purpose, information hierarchy, application shell, sidebar structure, navigation model, route map, page inventory, primary actions, analytics modules, operational queues, recent activity, notifications, settings, permissions, and multi-tenant behavior.
The agent creates metric dictionaries, KPI card specifications, analytics panel structures, chart recommendations, filter systems, date-range controls, saved views, data-table requirements, search behavior, command palettes, notification centers, activity feeds, audit logs, user flows, bulk-action logic, onboarding systems, setup checklists, empty states, loading states, error states, permission states, plan-limit states, and upgrade experiences.
It supports analytics dashboards, admin panels, AI products, CRMs, customer-success platforms, finance operations, sales tools, marketing systems, project-management applications, support platforms, subscription products, developer portals, marketplaces, infrastructure tools, security dashboards, compliance applications, internal tools, and multi-tenant B2B software.
The skill also produces responsive behavior matrices, component inventories, semantic design-token recommendations, accessibility requirements, animation rules, analytics instrumentation plans, developer handoff notes, implementation sequences, acceptance criteria, QA checklists, dashboard audits, discrepancy reports, growth opportunities, and risk assessments.
The core commercial promise is: create clear, scalable, and conversion-aware SaaS dashboard architectures for real product workflows.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for UX & UI Design.
This skill creates SaaS product architecture, dashboard specifications, information hierarchies, workflow recommendations, component systems, developer handoff documentation, and QA requirements.
It does not directly create final Figma files, finished production code, verified database queries, validated analytics formulas, security certification, accessibility certification, regulatory compliance, legal approval, penetration testing, production deployment, or guaranteed business outcomes.
Recommendations depend on the accuracy and completeness of supplied product requirements, user research, metric definitions, permissions, data structures, technical constraints, and business assumptions.
The skill must not invent customer behavior, conversion rates, retention metrics, revenue impact, benchmark data, market demand, or analytics results. Unknown information should be labeled as an assumption or open question.
Final dashboard decisions should be validated through real user research, usability testing, analytics review, accessibility testing, security review, technical feasibility analysis, browser and device testing, and stakeholder approval.
The skill does not guarantee improved activation, retention, revenue, usability, adoption, customer satisfaction, marketplace performance, or development speed.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
Permissions
File Scopes
This skill uses file access to read user-provided product requirements, user personas, jobs-to-be-done notes, interview summaries, analytics-event lists, metric dictionaries, database entity descriptions, API examples, existing dashboard screenshots, Figma exports, wireframes, page inventories, user flows, role and permission matrices, product roadmaps, pricing plans, onboarding requirements, customer-support themes, churn reasons, feature-adoption notes, brand guidelines, design-system documentation, frontend framework notes, component-library documentation, accessibility requirements, localization requirements, browser-support requirements, performance requirements, mobile requirements, competitor observations, and stakeholder constraints. It uses write access to create structured Markdown, text, CSV-style, JSON-style, YAML-style, and code-oriented outputs such as SaaS dashboard architectures, application-shell specifications, navigation systems, route maps, page inventories, metric dictionaries, KPI card specifications, chart plans, filter systems, table requirements, workflow documentation, onboarding systems, empty states, loading and error states, permission matrices, responsive behavior matrices, component inventories, design-token recommendations, accessibility requirements, developer handoff reports, analytics instrumentation plans, acceptance criteria, QA checklists, dashboard audits, discrepancy reports, risk assessments, and SKILL.md files. Browser access is useful when the host environment permits public framework-documentation review, public accessibility-standard review, public component-library documentation review, public analytics visualization research, public browser-support research, or public SaaS product-pattern research. The skill should clearly distinguish: Observed: Directly supported by supplied product data, screenshots, requirements, or documentation. Inferred: Strongly suggested by the supplied material but not explicitly confirmed. Recommended: A proposed product or UI decision intended to resolve ambiguity or improve usability. Open Question: A decision requiring confirmation from product, design, engineering, analytics, legal, security, or another responsible stakeholder. The default safe setup does not require terminal access, production deployment access, unrestricted source-code access, private customer accounts, billing accounts, passwords, database administration, or server access.