shop-management-system

Turns a finalized architecture and UX-foundations into an executable, sequenced build plan. Reads the architecture document and the UX-foundations document, then decomposes the system into epics and vertical feature slices (each mapped to the screens it touches and the building blocks/endpoints it needs), defines the walking skeleton, orders the work by dependency and risk, specifies the first vertical slice, and lists the engineering foundations to stand up. Use this in the planning phase — after software-architecture and ux-foundations, before scaffolding or coding — whenever a designed application needs to become a backlog and a build order. Trigger on phrases like "plan the implementation", "break this into epics and features", "what do we build first", "create the build plan", "turn the architecture into a roadmap", or "sequence the work". It stops at the plan; per-feature detailed design and code are separate downstream steps.

Establishes the UX and design foundations for an application before feature work begins — the "architecture of the UI." Reads a finalized architecture document, then produces a shared design core (brand, design tokens, accessibility, voice) plus a per-surface profile (users, information architecture, navigation, key user flows, screen inventory, surface-specific components) for each UI surface such as an admin portal, public website, or mobile app. Use this in the design phase, as a sibling to software architecture and before implementation planning, whenever a new application with one or more user interfaces is being designed. Trigger on phrases like "design the UX foundations", "set up the design system", "what should the UI look like", "plan the screens and navigation", "create the design language", or any point after the architecture is settled and the UI structure needs defining.

Designs the software architecture for a new application, service, or major feature through a structured interview, then produces an architecture document (arc42-style, with C4 diagrams in Mermaid and Architecture Decision Records). Use this whenever the user is starting a greenfield system or a significant new feature and would benefit from thinking through structure, quality attributes, tech stack, and trade-offs before writing code. Trigger on phrases like "design the architecture for", "I'm building a new app", "help me architect", "set up a new project/service", "what should the architecture be", "create an architecture doc/diagram", or any greenfield system-design discussion — even when the user does not say the word "architecture" explicitly but is clearly about to start building something new. Prefer this skill over answering from memory whenever real architectural trade-offs are in play.