tech/sxchnge
1
0 Fork 0
Code Issues 6 Pull Requests 1 Actions Packages Projects 1 Releases Wiki Activity

Build exchange workspace with clear money movement #29

Merged
tech merged 7 commits from workspace-28 into limits-22 2026-09-12 10:10:34 +00:00
Conversation 0 Commits 7 Files Changed 52
+17
2 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 52b7135eda - Show all commits

No files matched your search

docs/implementation.md
+11
View File
@@ -184,3 +184,14 @@ Documentation only; no runtime tests were run.
- Validation passed: all 91 frontend tests, analyze app and sxchnge_kyc, - Validation passed: all 91 frontend tests, analyze app and sxchnge_kyc,
format check of all 9 affected Dart files, web build and diff checks. format check of all 9 affected Dart files, web build and diff checks.
- Delivery: [PR #23](https://git.sendico.io/tech/sxchnge/pulls/23), unmerged. Merge #21 first and retarget #23 to main. - Delivery: [PR #23](https://git.sendico.io/tech/sxchnge/pulls/23), unmerged. Merge #21 first and retarget #23 to main.
## UX simplicity preference
Task [#26](https://git.sendico.io/tech/sxchnge/issues/26), delivered in
[PR #27](https://git.sendico.io/tech/sxchnge/pulls/27) on `skills-26`, makes
simplicity an explicit preference in the UX Design skill and its review checklist.
Prefer fewer concepts, choices, and controls when they serve the same need; retain
essential information, accessibility, and recovery. Documentation only.
Validation: skill-creator `quick_validate.py` passed in an isolated environment
with PyYAML (the system Python lacked it); `git diff --check` passed. No runtime
tests were needed. The PR is not merged.
skills/ux-design/SKILL.md
+6
View File
@@ -10,6 +10,10 @@ before reporting it complete. Rendering correctly is only one part of completion
## Establish the flow ## Establish the flow
- Prefer the simplest interface that lets users complete their task confidently.
When options meet the same need, choose fewer concepts, choices, and controls.
Add complexity only for a concrete user need; preserve essential information,
accessibility, and recovery rather than hiding them to make a screen look minimal.
- Identify the user's primary task, successful outcome, and shortest appropriate - Identify the user's primary task, successful outcome, and shortest appropriate
path to that outcome before choosing layouts or controls. path to that outcome before choosing layouts or controls.
- Inspect comparable product flows, components, navigation, terminology, and - Inspect comparable product flows, components, navigation, terminology, and
@@ -95,6 +99,8 @@ performed and any gaps; do not mark applicable unmet criteria as complete.
- [ ] Are interactive elements recognizable, and can the user tell what is - [ ] Are interactive elements recognizable, and can the user tell what is
happening and what will happen next? happening and what will happen next?
- [ ] Are steps appropriate, with unnecessary interaction and cognitive load removed? - [ ] Are steps appropriate, with unnecessary interaction and cognitive load removed?
- [ ] Is this the simplest usable solution, with each added concept, choice, or
control serving a concrete user need?
- [ ] Does the flow follow existing product patterns and consistent terminology, - [ ] Does the flow follow existing product patterns and consistent terminology,
with a concrete reason for any departure? with a concrete reason for any departure?
- [ ] Can users recover from errors, with input and context preserved where appropriate? - [ ] Can users recover from errors, with input and context preserved where appropriate?