--- name: design-ui-window description: Redesigns any Avalonia .axaml view/window to best-in-class UI/UX quality. Enforces consistent layout, spacing, typography, interaction, accessibility and visual hierarchy. Only changes visuals, layout and styles — never business logic, bindings or public view-model API. Reusable by updating target_view_path. metadata: keywords: - redesign - ui - ux - avalonia - axaml - window - view - layout - consistency - accessibility - animation - feedback - refactor - style - xaml --- You are an expert Avalonia UI/UX designer and refactor specialist. Follow these instructions **exactly** and in order. Do not skip steps, do not add business logic changes, do not break existing bindings or view-model public API. Redesign every control in the target window to achieve best in class UI and UX quality. Make layout spacing alignment typography and interaction behaviour consistent across the entire window. Keep the prompt reusable by changing the target view path in one place only. src\XerahS.UI\Views\AfterCaptureWindow.axaml The target window is the view referenced by target_view_path. All changes must be confined to this view file and any new/updated styles/resources that are introduced for consistency. Visual consistency across the entire window. Uniform spacing margins and alignment. Controls aligned to a clear grid. Controls use available space appropriately. Predictable control placement. Clear visual hierarchy with one primary action per view. Minimal visual noise with purposeful whitespace. Clear affordances. Controls look interactive. Immediate feedback for every interaction. Smooth animations that explain state changes. Animations never block user intent. Touch targets sized for comfort and accuracy. Text always readable. Consistent typography and scaling. Colour used sparingly and meaningfully. Colour never carries meaning alone. Strong contrast for accessibility. Icons simple recognisable and consistent. Platform conventions followed. Behaviour consistent across similar controls and screens. No surprise interactions. State always visible. Error prevention first. Errors clear human and actionable. Progressive disclosure of complexity. Sensible safe defaults. Performance feels instant. Do not change business logic. Do not change command bindings. Do not change view model public API. Do not break keyboard navigation. Do not break screen reader semantics. Do not break localisation readiness. Do not remove existing controls or features. Only reorganise and restyle unless a control is provably redundant. Use a consistent grid based layout. Use consistent spacing tokens. Avoid ad hoc pixel values. Align related controls. Keep labels and inputs aligned. Use stretch only where it improves scanability and reduces empty awkward gaps. Primary action must be visually dominant and placed predictably. Every interactive control must provide clear hover pressed focused and disabled states. Every action must provide immediate feedback. Use progress indication for long running tasks. Confirm destructive actions. Provide undo where feasible without changing core logic. All controls must have accessible names. Focus order must follow visual order. Minimum hit target size must be appropriate for touch and pointer use. Contrast must be sufficient for common accessibility expectations. Prefer existing app styles resources and theme tokens. Introduce new reusable styles only when they reduce duplication. Keep code behind changes minimal. Prefer XAML changes. Execute the following steps in order. Think step-by-step and show your reasoning after each major step. Only edit files that are necessary. 1 Open the target view and inventory every control. Record type purpose binding and current layout container. 2 Define the intended information hierarchy. Identify the primary action secondary actions and supporting options. 3 Redesign the layout using a grid based structure. Group related controls into clear sections. Use consistent spacing and alignment. 4 Fix sizing and stretching so controls use available space appropriately. Avoid cramped areas and avoid large dead zones. 5 Standardise typography. Apply consistent font sizes weights and line heights using shared styles. 6 Standardise control styling. Ensure consistent padding corner radius icon sizing and state visuals across the window. 7 Ensure accessibility. Add or fix accessible names. Verify focus order. Verify keyboard navigation for all controls. 8 Review micro interactions. Ensure feedback for all actions. Add progress indication where needed without changing the underlying workflow. 9 Remove visual noise. Reduce unnecessary borders separators and duplicated labels. Use whitespace and section headers instead. 10 Refactor styles. Extract repeated styling into reusable styles and resources. Keep styles consistent with existing app theming. 11 Build and run. Verify the window at common sizes and DPI settings. Verify localisation expansion by simulating longer text. 12 Document the changes briefly in a UI audit note. Include before and after screenshots if available. The redesign is considered successful when: All validation_rules pass with no exceptions. No regressions in behavior. All existing functionality works as before. Primary action is visually dominant and immediately clear to users. Window is usable at all sizes and DPI scales without layout issues. No arbitrary pixel values outside defined spacing and sizing tokens. All controls are aligned to a consistent grid. No misaligned edges within a section. Spacing is consistent across the window. No arbitrary spacing values outside defined tokens. Primary action is obvious within 2 seconds of first view. Secondary actions are present but visually quieter. All interactive controls have visible hover pressed focused and disabled states. Keyboard only navigation can reach every control. Focus order matches visual order. Screen reader has meaningful names for every interactive control. No bindings are broken. No runtime binding errors in logs. Window remains usable at different sizes. No clipped content at typical minimum size. UI remains readable at different DPI scales. No regressions in behaviour. Commands trigger the same actions as before.

summary

control_inventory

layout_changes

style_changes

accessibility_checks

screenshots_or_notes

files_changed

After completing all steps, output your final answer strictly in the structure above.

sharex-workflow-and-versioning

Scan your own AI components