← ClaudeAtlas

backoffice-workflow-uxlisted

Generate enterprise backoffice workflows with route-based capability pages, scalable lists, task flows, filters, actions, and role-aware UX.
authenticfake/clike · ★ 1 · AI & Automation · score 70
Install: claude install-skill authenticfake/clike
# Backoffice Workflow UX Skill ## Intent Backoffice software is operational software. This skill prevents CLike from generating a single superficial dashboard when the requirement describes multiple capabilities, task workflows, search-heavy archives, validation operations, export actions, AI assistance, or enterprise operator journeys. ## Use when Use this skill when a REQ touches: - backoffice; - admin console; - operator console; - task inbox; - workflow; - validation; - archive/search; - export; - document management; - approvals; - configuration; - AI assistant page; - enterprise dashboard; - internal tools. ## Do not use when Do not use this skill for landing pages, pure marketing pages, simple static forms, or backend-only modules with no operator/user workflow. ## Required UX shape When this skill is selected, generated frontend should prefer: - one route/page per major capability; - a shared shell/navigation; - clear page title and purpose; - list/detail or master/detail patterns for operational data; - server-side filters and pagination for large datasets; - loading, empty, error, permission-denied, and success states; - role-aware navigation and actions; - confirmation for destructive or irreversible actions; - audit/provenance visibility where relevant; - API client boundaries instead of hidden fetches inside presentation components. ## Capability page expectations For a backoffice MVP, prefer explicit pages such as: - `/ingest`; - `/validation`; - `