From e06ebe86cfd96178fd9f1063c1831c2c8ee730d2 Mon Sep 17 00:00:00 2001 From: Muness Castle Date: Tue, 20 Jan 2026 15:40:31 -0500 Subject: [PATCH 1/3] Add OpenCode as 5th provider target - Add transformOpenCode() transformer for .opencode/ directory format - Commands: description-only frontmatter, $ARGUMENTS placeholders - Skills: Same SKILL.md format as Claude Code with reference files - Include install.sh script for easy installation - Add 21 tests for OpenCode transformer - Update DEVELOP.md with OpenCode documentation Co-Authored-By: Claude Opus 4.5 --- DEVELOP.md | 24 +- dist/opencode-prefixed.zip | Bin 0 -> 75616 bytes .../.opencode/commands/i-adapt.md | 189 +++++++++ .../.opencode/commands/i-animate.md | 184 +++++++++ .../.opencode/commands/i-audit.md | 120 ++++++ .../.opencode/commands/i-bolder.md | 126 ++++++ .../.opencode/commands/i-clarify.md | 173 ++++++++ .../.opencode/commands/i-colorize.md | 152 +++++++ .../.opencode/commands/i-critique.md | 112 +++++ .../.opencode/commands/i-delight.md | 311 ++++++++++++++ .../.opencode/commands/i-extract.md | 88 ++++ .../.opencode/commands/i-harden.md | 351 ++++++++++++++++ .../.opencode/commands/i-normalize.md | 61 +++ .../.opencode/commands/i-onboard.md | 236 +++++++++++ .../.opencode/commands/i-optimize.md | 262 ++++++++++++ .../.opencode/commands/i-polish.md | 195 +++++++++ .../.opencode/commands/i-quieter.md | 112 +++++ .../.opencode/commands/i-simplify.md | 131 ++++++ .../.opencode/commands/i-teach-impeccable.md | 67 +++ .../.opencode/skills/frontend-design/SKILL.md | 127 ++++++ .../reference/color-and-contrast.md | 132 ++++++ .../reference/interaction-design.md | 123 ++++++ .../reference/motion-design.md | 99 +++++ .../reference/responsive-design.md | 114 +++++ .../reference/spatial-design.md | 100 +++++ .../frontend-design/reference/typography.md | 131 ++++++ .../frontend-design/reference/ux-writing.md | 107 +++++ dist/opencode-prefixed/install.sh | 43 ++ dist/opencode.zip | Bin 0 -> 75512 bytes dist/opencode/.opencode/commands/adapt.md | 189 +++++++++ dist/opencode/.opencode/commands/animate.md | 184 +++++++++ dist/opencode/.opencode/commands/audit.md | 120 ++++++ dist/opencode/.opencode/commands/bolder.md | 126 ++++++ dist/opencode/.opencode/commands/clarify.md | 173 ++++++++ dist/opencode/.opencode/commands/colorize.md | 152 +++++++ dist/opencode/.opencode/commands/critique.md | 112 +++++ dist/opencode/.opencode/commands/delight.md | 311 ++++++++++++++ dist/opencode/.opencode/commands/extract.md | 88 ++++ dist/opencode/.opencode/commands/harden.md | 351 ++++++++++++++++ dist/opencode/.opencode/commands/normalize.md | 61 +++ dist/opencode/.opencode/commands/onboard.md | 236 +++++++++++ dist/opencode/.opencode/commands/optimize.md | 262 ++++++++++++ dist/opencode/.opencode/commands/polish.md | 195 +++++++++ dist/opencode/.opencode/commands/quieter.md | 112 +++++ dist/opencode/.opencode/commands/simplify.md | 131 ++++++ .../.opencode/commands/teach-impeccable.md | 67 +++ .../.opencode/skills/frontend-design/SKILL.md | 127 ++++++ .../reference/color-and-contrast.md | 132 ++++++ .../reference/interaction-design.md | 123 ++++++ .../reference/motion-design.md | 99 +++++ .../reference/responsive-design.md | 114 +++++ .../reference/spatial-design.md | 100 +++++ .../frontend-design/reference/typography.md | 131 ++++++ .../frontend-design/reference/ux-writing.md | 107 +++++ dist/opencode/install.sh | 42 ++ scripts/build.js | 10 +- scripts/lib/transformers/index.js | 1 + scripts/lib/transformers/opencode.js | 139 +++++++ scripts/lib/utils.js | 5 + scripts/lib/zip.js | 2 +- tests/lib/transformers/opencode.test.js | 389 ++++++++++++++++++ 61 files changed, 8254 insertions(+), 7 deletions(-) create mode 100644 dist/opencode-prefixed.zip create mode 100644 dist/opencode-prefixed/.opencode/commands/i-adapt.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-animate.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-audit.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-bolder.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-clarify.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-colorize.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-critique.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-delight.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-extract.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-harden.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-normalize.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-onboard.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-optimize.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-polish.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-quieter.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-simplify.md create mode 100644 dist/opencode-prefixed/.opencode/commands/i-teach-impeccable.md create mode 100644 dist/opencode-prefixed/.opencode/skills/frontend-design/SKILL.md create mode 100644 dist/opencode-prefixed/.opencode/skills/frontend-design/reference/color-and-contrast.md create mode 100644 dist/opencode-prefixed/.opencode/skills/frontend-design/reference/interaction-design.md create mode 100644 dist/opencode-prefixed/.opencode/skills/frontend-design/reference/motion-design.md create mode 100644 dist/opencode-prefixed/.opencode/skills/frontend-design/reference/responsive-design.md create mode 100644 dist/opencode-prefixed/.opencode/skills/frontend-design/reference/spatial-design.md create mode 100644 dist/opencode-prefixed/.opencode/skills/frontend-design/reference/typography.md create mode 100644 dist/opencode-prefixed/.opencode/skills/frontend-design/reference/ux-writing.md create mode 100644 dist/opencode-prefixed/install.sh create mode 100644 dist/opencode.zip create mode 100644 dist/opencode/.opencode/commands/adapt.md create mode 100644 dist/opencode/.opencode/commands/animate.md create mode 100644 dist/opencode/.opencode/commands/audit.md create mode 100644 dist/opencode/.opencode/commands/bolder.md create mode 100644 dist/opencode/.opencode/commands/clarify.md create mode 100644 dist/opencode/.opencode/commands/colorize.md create mode 100644 dist/opencode/.opencode/commands/critique.md create mode 100644 dist/opencode/.opencode/commands/delight.md create mode 100644 dist/opencode/.opencode/commands/extract.md create mode 100644 dist/opencode/.opencode/commands/harden.md create mode 100644 dist/opencode/.opencode/commands/normalize.md create mode 100644 dist/opencode/.opencode/commands/onboard.md create mode 100644 dist/opencode/.opencode/commands/optimize.md create mode 100644 dist/opencode/.opencode/commands/polish.md create mode 100644 dist/opencode/.opencode/commands/quieter.md create mode 100644 dist/opencode/.opencode/commands/simplify.md create mode 100644 dist/opencode/.opencode/commands/teach-impeccable.md create mode 100644 dist/opencode/.opencode/skills/frontend-design/SKILL.md create mode 100644 dist/opencode/.opencode/skills/frontend-design/reference/color-and-contrast.md create mode 100644 dist/opencode/.opencode/skills/frontend-design/reference/interaction-design.md create mode 100644 dist/opencode/.opencode/skills/frontend-design/reference/motion-design.md create mode 100644 dist/opencode/.opencode/skills/frontend-design/reference/responsive-design.md create mode 100644 dist/opencode/.opencode/skills/frontend-design/reference/spatial-design.md create mode 100644 dist/opencode/.opencode/skills/frontend-design/reference/typography.md create mode 100644 dist/opencode/.opencode/skills/frontend-design/reference/ux-writing.md create mode 100644 dist/opencode/install.sh create mode 100644 scripts/lib/transformers/opencode.js create mode 100644 tests/lib/transformers/opencode.test.js diff --git a/DEVELOP.md b/DEVELOP.md index 2ef211f..28678c7 100644 --- a/DEVELOP.md +++ b/DEVELOP.md @@ -10,7 +10,7 @@ This repository uses a **feature-rich source format** that transforms into provi Different providers have different capabilities: - **Cursor**: No frontmatter or argument support -- **Claude Code, Gemini, Codex**: Full support for metadata and arguments +- **Claude Code, Gemini, Codex, OpenCode**: Full support for metadata and arguments By maintaining rich source files, we preserve maximum functionality where supported while still providing working (if simpler) versions for all providers. @@ -98,6 +98,9 @@ source/ → dist/ codex/prompts/*.md (custom prompt format) codex/skills/*/SKILL.md (Agent Skills standard) + + opencode/commands/*.md ($ARGUMENTS placeholder) + opencode/skills/*/SKILL.md (Agent Skills standard) ``` ## Provider Transformations @@ -131,6 +134,16 @@ source/ → dist/ - Uses same SKILL.md format as Claude Code - Reference files in subdirectories +### OpenCode (Full Featured) +- Commands → `dist/opencode/.opencode/commands/*.md` + - Frontmatter uses `description` only (no `name`, no `args` array) + - Placeholders transformed from `{{argname}}` to `$ARGUMENTS` (single args string) + - Invoked as `/normalize`, `/polish`, etc. +- Skills → Agent Skills standard → `dist/opencode/.opencode/skills/{name}/SKILL.md` + - Uses same SKILL.md format as Claude Code + - Reference files in subdirectories +- Includes `install.sh` script for easy installation + ## Adding New Content ### 1. Create Source File @@ -157,7 +170,7 @@ Add frontmatter and content following the format above. bun run build ``` -This generates all 4 provider formats automatically. +This generates all 5 provider formats automatically. ### 3. Test @@ -189,6 +202,7 @@ The build system (`scripts/build.js`) is a single ~170-line Node.js script with: - `transformClaudeCode()`: Keeps full format - `transformGemini()`: Converts to TOML + modular skills - `transformCodex()`: Full format + modular skills +- `transformOpenCode()`: Description-only frontmatter + $ARGUMENTS placeholder ## Best Practices @@ -218,6 +232,9 @@ The build system (`scripts/build.js`) is a single ~170-line Node.js script with: - [Gemini CLI Skills](https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/gemini-md.md) - [Codex CLI Slash Commands](https://developers.openai.com/codex/guides/slash-commands#create-your-own-slash-commands-with-custom-prompts) - [Codex CLI Skills](https://developers.openai.com/codex/skills/) +- [OpenCode Commands](https://opencode.ai/docs/commands/) +- [OpenCode Agent Skills](https://opencode.ai/docs/skills) +- [OpenCode Configuration](https://opencode.ai/docs/config/) ## Repository Structure @@ -232,7 +249,8 @@ impeccable/ │ ├── cursor/ │ ├── claude-code/ │ ├── gemini/ -│ └── codex/ +│ ├── codex/ +│ └── opencode/ ├── scripts/ │ └── build.js # Build system (~170 lines, zero deps) ├── package.json # ESM project config diff --git a/dist/opencode-prefixed.zip b/dist/opencode-prefixed.zip new file mode 100644 index 0000000000000000000000000000000000000000..aadd8e24a8756f7d65428af3aed2cac945b69701 GIT binary patch literal 75616 zcmaf)Q*dtIw(Y;zcCzBE*tTukwrwXX_KI!WPQGx(wrz7I_kT{^s#E*c-Df|{S@UJ~ z8V_w$YyCI+P?P}!M+X1^&;WQ}R^7_9R(%an0Dukx0DuMj09e_(xEk5o(z{ryslouj zG>#pt{_An`gad$pKY;)M|NU>Q>W2LWBfQ^=M!oecnV21i&!1Tk5pDQ^PIt-qG9ya# zjJUA%B;s+q`ALmSH-k0?9KBI_b=z@$*C5ZaA(5yEs5#v;OM2Z2M5F2)EG@``Zb2#_ zuSf#fPAe7O+=i?)-4 zah#h+Q~2hQ3F|~sd*gCW3*6#2L^%C~`Yf7+t+lhFTguoVd;z zTMJ#Z3#MeY;WN%28J+HdPE*CUccJn+c)gEG-7cCjwVwl;T8_QtEz9Hei@-N3(>VnK z+?|kUf3#~=JiuBZ$w!AoMs?D0tBvoRDdM?T*|DgX)aFb^rl*A>$Zh{yrjPv_>h0Kx z;wi~nc}cA-zJT{QF19y&C$83^*4!dTztFY2DGqsYXOHvG0Y|~Ekg(#_wmOwZ!G^`c z%)#Vj&o&-Ta5j8>{tkD3lV+<$A9eZ3bA-+do54+=|Cc2>ve|_+)m%sDY*okz_<9CY zsC?D%vD>?}9W)@PM)x&KkVBr<@-xPb2PnUr`tV%rmBSM@o+6_F=qW~e!c+W5ny~*! z6Y$^C{O^zd`}!|w(mObs*_$|+nlb!u(){-|(Eg={iG!V;k-e$Qe=PPtdu5X|Q}QpO z&I9%5j}uG9F>QXSN=|fLs|XYttTLQs6dX==dTCbEInnd7oc!@*&%*dAhGzS_+5_u6 z8mY$q(xCWuwKhjuzlA$P`^uMaB*F;`twp*^IWgLg$gDdW6Dem6gN2h0Q=WsTeUBwb z+=8tl%GDT-^O{oCRJjRHI9nnT=9xRisghMJoxcB^Z6NR+|J+lSU|=RQ7z)c7;~2StB{Av)<-%H+qH%?4AXuM{a$W>Zl)}gF3vSMSGh| zs|I+@3EmdI2VelHuIajv>+>yDpgbP>4Ikd^j;XU(o3Exmy?s0Uq_o(Ma%D#^duN+e z24snl&+wG4o|k{)H5EzFW1(`yMWLDhaZ>zW>aE#`ek^S5)DSvjQwaq&UB0*a@!v^x zB@~GKf$u(YG1R$E#M0~9IkS%gZ44^dvu}*+T94?B>uBT7bfMY}smitox@tYi)~DtU zWeXdWR!}z}LD!^zKVAfCViSYLUkm4cO!=x&ZR{_9kWb-9riXVfUWgCCKN|4x-xW~$ z8(GqW-QhPohj2z#oC~sqA4gHMaz=@bs7t!!<0>0h+b&Svc?y3~WSzS>>-`XED3ck^ z$=2TUH>_pP@6yaGl-lv>T0$Tc08#ZsO(jhiatfRhS}ne-4(Xv!ty4uP$iOk!r_?QQ zf>g-+OfJ5C9W5wnGQ_t*)`e1I`=ZJ^^4Ih4{d;w7baxaK^q%VUV`!ti-1w@}8OS{Y1273>(?BvDf*gbW3$cfhG)(L|1REtZ zV`x)K9~~3P9b)Xt`?IN%c9;b2{D~!lUrA{bZk4ic4xw4>w;8f`!H7kU4XCj*Bz%XM zfY>z$88F3` zgs*`t_BXy1ut4HgmJsdnER6M&a0;TYR+zER&8)(4*dM{4L zKX^R%q;3aZ1ZD4B|$&{Sp05 zI;`>yST$Tho>)}P<={nAXji=1nIEuP_i6L5oU-Ncxo#NI&HXAmL}7Af9PozpH!PD9 zRXO_68sgVb(Tk?{NADL;_`0OGjG#aG@ZJ9E=gk>jk9xyT1=048mn9aFiiJ@(Jo~BS z(y+kK5)AzA84p5QN~?eaua7z$_hy%h>W8 z6R#L!>6gN;&<@?3>D7&&HToEo4&iPBHCDgiwMw6$Xkwl`{n?5pn}|5+6qc1ukU_w1 z1$e|?BVG}rV@M=d?L9;V-)EYgMfngniv6Z4eeOjXc#MK6pP1hiOFCn^#!Ef9(6Q9sXs{P&+q&KZ z9&dsWiW|5`$zfP~8O_SVmLazsF?@gs@lx<7YQiQYp8c(!M|dgiIiYkOrpIcGEOG*l_|4?=t+%c8fM&cdv?=Fe!3`q zRaHb+@!f@>zx>s`cpzodp~Yc%?6IX0fTRAsFwE3{dbEY;WPZ;g*eu%_Bb<;ZX6{qq zzwGmW9M5dsG#&pRM^?iG00{q`<2kumnYo%d{|CRz(Uf!9WJm3psS^aIrn0gXQC3X( zpB5(l1gighuQ#{Vh{Hx@5d}wO1z3ybJvXcQY^@X4_f7Sg8gKv*N8O(jLZne)SaG-h z>h~S{^5>;YV9B=$Z5*r8+7*dfwZ+yeOl0U+S5t+#?Mr>ghg8{dJbTL#%m7hI@g?s+mtU?p3U=CCvtXZglK zr@{+!{|s)qT(v!%is>dR^P6?EFzqj3QQ`y!z))F7=g8N%6-o2!x7IW@mLI~_N*{@o z1k(?zM@+a2VP9AkY1gTtI0}Zi#8D(;F$_<=T^+sMU+-x+eLK1Zd^z@Z_jZ+VFbs!< z9n1)IC)FQYe(#lFOiKIQC5PKcB#+m%qJ`Pw;vrkUwh&_h9o*Tnb;l{z*C>Y>^0MbNnGPr;ofrrm9%7FD%DC);tN?LZX! zj({jd>Jw7;w%kzzdAKy)TK-fh%G=sS3|gWC=c8+wAse`mgqG|C{fEQB0BEq`%hSt` zWt7|}sv!^RW5mR7);tj78l9 zXPn>(^K)B}ij<4YE^4VPkqq2MMjW>3(~KLsyW+)m3D;OeCx4*^(SSz%2!|uh(O3C- zaQ~Oy!grU6fTowIXKnU?D0^GA{FpEfh~Kkr9p8TLwk^wX4lOiiHtCbY7}<&9E+?gb zk+ks3xz*VfV-MJ`L{L zLm!SzpsWR=8WzFAPnL)`vkf)%Br>Y^ypCMf3q6v$GhtT2!_)RsJ#cCGXiKQs-OIzL zo-Cb(V&K393Eaym5!M66RFTpZUG-ZDsJL>k7;7PJICJN0oS_o(3sKFp|(!PEtz4?>=7#6K-rCnNR@~^!MTDGWoB5#>BJG^{b zA^CoJy`TQ!&px*qp;jU;?w@#`SZ5wpr^QB1w(rAjsYwcat01jeyB*f(M)WrV4z8dT z-sI2gJbkU7n*b+N%uX#P z?1q!bKF*!7SJI_=bDE(NTxU_0dC1{q3vF^zTcOKL9%8ca72ffigu~r!IU+<$8JyjT z*NI>xxzG^Hvkv>*_*99e-0TN>Yp6bQ(PV8%ZLg!el8Hefe zRjH3_E(atqr&?6!3H|o0h4ku6dm9UeuIKnteQ>EW_J8T2Av1~nXhz4$?xZhAKXoT% zSJ>qHD9UEdAX-6MnY@U8Frbv%={{rS9P&4;tjG@0DnHkflnZ>Yus?8XoaR=%q(Zhs z%DzYGu)uOuw24srC(L7B1x(s3pcYG|QfKP-8x*a$lDDn$eT?Y|c@h0p1?y5x1kqym zTkm#xeVD3KN@@0pwh6)m*{KFp7J`s32|_I7n@)=^j9QjmLFPBunV6`kkabj# zn3eXGTkuyla7KtG?_J6t2PXNyQ%X@&iG1>I8dGcI&Qalih{GkQm}VBAWNPZ%Ehv1y z#?uyPfBNIxKnB&41xpeGGCi^GU=89B1p=GVMyQf1$;31@h7mj?Ca zWk)J}f403&j*r8$VST^d9fn#!;imH%J&^{Yg-kn!pOYLl%?RTR@(bBR3lOrI&?H7V zp+GJof2v}7itXYL!qJ0~-diKuB!6n5Om_tE*j#9dTjJb}>lkPkLNI)h!QZ`|zOQQX z&Z88;Y5y1?1?i3~W_Q$vzvm|=f4uFaWwn$c*^*RG^5#54ohaYBhC#24n66+Q9s!|n z-zFm%q1{XlbH72P>CMS!;T9OlwQxIR zBRkY!fpgxYmjzrK%h3Cy4!Iz#&4`9K)Hd>pFPVSBIUKkx`qXAnJD&f;^q{{Zk-i45 zno=@+4hyn=^fMy)*-KYCVC1`eOU@Ye{2jU2Kw;Gp+2F*YWPL6&9sHcuz#id{=c)>Q zW>r(PW)A-Nuq+v9NbPcelEgmm{1^)vl4ME5g(V;+8o=UO&Us>(!?j)v$NTcSzOER= znnduEIXXAE9rw5h!}8~`7>*P?d+*ovw8$@oGS>9MoF^zro(iH$;A;+9RJU$w#lVu6 z;%g7Pgft$h*p@RZCfoaImlO>D8-~XqI_Xxk( zUU8U)xJng*)75EHEax9%6?A0La?vzVE#;#hiLnria40zAE*hQNfqx_mLQ@JV23wta5OQ?ibYRN%lc%OGUMgpBl;@^IdhW{l3eCywz4 z!Qgn0&_nbmQ&Gc)|~>!Gi`+_qV33){^f`OM>sN00CUlD=B9Y2t>`sIzb%_cNG#XUyGnmk9 zIqDD2DzgzFQSn+q0U)C(qRw{o8|+_Gr+3re8sUF9OZPvV<=>`GGf!7%BNNyEkUHHo z5>x?8a}ww+Pk}jVUhU3QG zJRgpyEL*hA!tOg3>}HoYBR>cS#(ANwU=wu?>}ud}QXDHEoHb}Zo2+V-$X`qP<@9h- zE~}Vdr9HH9f}Ka;?1C|Rt~MPfUiiz+=~^M^FM8DVS6f@?UB#i^TifXIlY~w#l^W#C zvZraX4PD9rqBS1!o&GsB31VrN&nD#}w3Ax1rgyZrid3YF4$PxNZoGgm?#v>Vu3F9K_E(DSLV^w~*{^pD8S_pz{lm^#KA`&Nt_UNuO|;a;MFv9Go+ zu=l8^M?V#1g!a^L^&{(alq}2c4fPmmrOUMCkEi~OWR-X>SiSRsMmkU*UR<=iTEias z5_P-Y4nnOQ6}X&}qX}0JZ;ki3m9V~-9e$p+C&se>Ebt`)0NlIpos`q&a@*&9bT8@_ zh_gHpYQP@_+I$5eKfXOc=y7=CE;xP|d;Zb-(oFHiQuk zL@YW}Fvc6ov9UiY5G9xqmfPdqq`sg~-rpOBC|cg|tBS^;#4L_iYJ$n^0&0sJ?O`}` zsGs*{G->R|wfibNDTG$V3e8JpP$?I|+qD2+r>{G4i zhXkg|6)6vV`Cu8s&Ww+5oZ{m-# zd#`a}9Jom;=TU=$QAv#a(v?c8WX$)D#O4i&@)SQ;xT3V*gZEqRTx`knAunk8OfSf+ zO~0eXzY%zA#-1sBiX(}6lOBD#p^immk-=G$;H(#&W_@p$ny}3+7Z~Ed`Fd;#^v8Bb zD?q)KxH)Gb$DHGr-TL^iAVwuqyVd8HlC^9uoqicK)kapFH3nQb2VD zMEd03YdtHJ4ZMlo8gq4G5B3?N9pGzus=D<=rRI*8ah@wGks8x0o$7)xu*d88lkjpD zj7xzi6079K^Y14(C&HSBk{?n^H|HLrCOoXk<%$qL%CB$}DUhKA7PPPP+HuI-Rlesy zuqZu-(063Zq)+n1uj6Sk&#$Z<`4(vff66FhN;OJtbAF%IXA2{LJ0&`1c4*WLp~K*= z2TebpYB;j@<(BGLjfGEE<>n|vyfEyCxDs0VfL=f&U8BYsLO(baP7N*n+RrWg|*+aFccqY{TDmYXxy zWGk;YvT$y>b0)|POTm<*G<1UP@@PqPpqh6!q{h#Ih#>evrSf*Fx(=bD&vM!!W#viT zoC*Yw83$K#Hfn}CMU-Z+8ab~`)?5syn1cg0YeVqTm#!hxICCpvz(skJ;X#ZZiHWo}q*2(J~QuZ z(Py{KSH(_?noFC6aTwPWJJdK2V$H)@VG!UdWvrWqv86t8#w3^gY26p7SDHh*nmM$SKv-8}UsHO+y0THUQ)K(c1%4wWzZC=Q{WDNwO{KxHSb{^wnZ1pd403Up2UXF5go9rD|N(Ryz;` zX>z`|Gk0zYCTRa_PL65Q5CP__()Vm!L;NAgH}QwC|Ha0Him}w(ZWjU;mv7YK6)Z=c zxZT%wYZ+(D$fT6^^Zenj@+O0W{ac``&NBR0JxPQOGZGjvCr!!HMbD~I_~l3WEtG|4 z^{SwEQ^BadW)Ib;?V~%n{ppfCkEeXyf>~oZ!kHvBUT^fFGEybFxtx*iMK)NtZ@Fsi zMpV$$C^Nj|1X_+umHX>WxP6}0FG-Qu7f~uGe(}u+{`bat!!HxVtW`q(wXfjqFTQcU^WyRA7Z<|Vj2vH@i3$^K&u{1k7chC$vdV75+D=dzc zy5GfgLolqlJd05x5NLs$tg#KfHHj*c-efCZ9#3R_IZ&VVL{a5s<>}XP>er!7e|L9X za)$hJqb)t3c6Uw5LOF*MZ^b&CQ*b=#?SqPA#JSEMBVOa zb5XEt&jd4`$D^J~O1VZ;T)+F?DQHO`wq%vHVSXd#%P2tV6H3s4MgB(ZmoP8$ta;IG z@U3KwMuLFUyZ|{z;wl`C$7XIq0$UMgkeXOr1gvms<)F(7SK@kV!@Gw#CuaT%rOq@o z5c#-t@CNUQ6FU3n*45+$cmf*u$`2TOMMg-mcA?E~JA7_Y@hwpS#qE(QgQHwWcJ6~B zYP|W(df+eI9P?ziJgI3?vm>TD*2Yfvh0 zbW6qC?J8C43hG(Rxz}+vU0Mm09tGfQHzP8`Ho@0oo?obykIG9R(;kCv|6rzaGE%sL zWh8=k27V^cAkH9MJd7eRF=eRCH(**3P2l0Olk|r_0NvT7ftg$+sCaJ}#5{IKh?CFP z<&&9`)gcqLIg}5D>!=s1Y7_91dWjBxthk;Ks@EV;lFv|U?{J;=aPf1Cn-EfZDXf@( z0|am9;x^8i0*-hB)@oLcA4T|7k`IK1ttBZcOU@HJxaTzTI5`puH%dN{!qd$Ms+7!+ ztem-Nq(c*eYre`|^_HSQ%e@>ZyvFgeX;5yzm%n?1l4=azgmxFyA2SCS3uh#reoN`s zM1d!o_aDTfhq;s=&Y6f;eBE#bJEs(e(<{)vgEFjx$LfU?k=K1%!)i@AWe&(R$BMblpPk{!fo ze;dKgPbSsX#gSnI1`ql%A?}y<6O43Njk@ik95rc4w&~cgrw#Ewp6~Ktj>%;60T@w- zKnW8R;UAR9j;Qr9rPF$$=c3(EP>mB7?ut4|U>U#$Uw%mgb#WG@c9_*`A|$rv-kh&r z?K?s-hUHB)x~aDUvA8DZow+;=W#Rf(pgV>SBzXR+A;Y#9uT~>}koN%%<|3@b zN!P^QE~8*;Lq()@eigkMKiTP>p`aiXr2MHgD&fg}Sq0~?DLZ>T*(>&#+v0cgc4wRD z_xCYS`QgK8?W8R7iowUbRr-}AZBZRi4;&blZ_akwU=-ANr`;SQSIl+Hfv*k$epGQ5 zqYi;SXxWEGz$%;{LKb@5RtU>D{%pFWb} z?F2G0-eoCayVy5@+e~695z=;F?NrJzt(~(aOBo+>8PzgEY^yssW>*|lL0=TAr67ME zFTqpTIuPThczOVg>3D6H0e?=w;fdajCNh#}r|E2ySq#`#F^qktp?djFBt8HNuaawE z--fzBWIp{$$WwrnOr(r-&o<0dIdXrfz7~NfNXs#khQ9dsKHNi`WJz#Ffu=#CL1tmJ z#P4#VqVP-=GNULui~CdM+z)B?katrHo<$H+z^dIRVNVoBRz*5I21%8kq1zsNuekax zg@;t%PTXY8FUL^PNmo%JJ&rd+&X zDV+pFHu*lEF-yam@#9htTV=O@HicANkf=8!$P}~>?=X176&L>WA&QMPzCF*7i~PXR zj)?3!9_7P@%3O#AA7GmFGvO@%5b}^kh4x5Nje1E|GT!nj;NcXU6jc?@@s*VoD^{ZL zJnOJ|hlhopl8h+#!f9@=vz)jjLDx@CkoJ;-xs{cav=;mO+s{8^1XBE_(KZA7XAF+G z0g{2UwmH@2OPH;2xd3Ioo5I-cE6&m$8if>xC=J`Ew{RK1`LHqCEi~veDodr|fi4p` zQ*VHJX6g`c3kYuUO;hxrbq{sXmNAi;QkY{Mi$+s|7g(Zrs_+)PSbCck#FPHnKE<@% z{3uGlP1&II&}GCXy?A0<1{Z1Qyk0j)!Wu}HzLdo*hN%!4lT|c`oea?9 ze@Rx85^sn_66^IVk_S2V|$U<{#-%3`kv-&ml%M)Mm6ZwjF23dU2zY!&+(J zA{M`5iBn8F@5q6&4w5;Kg#ljU)rZrh&_JmzhirE1>jE2jDjNf4?|+l9|I#nVJx?t_ zESy;5w}VVF4&7^)-SWj9lk*e|PlEHCrUp(rSHC8R{|KLQOt-$bcH@@mcMgIB0=z;T7QOX z1qO|X4S9S<l{W0qb&^EkYXX6I!9PRNA8OcdKi%<%yed36SZy8Yr1 zQXz|kVokc;f-vWi=!utmPX&MV`^9u0*FeKWSHX2U7A!Z?dByS?ri-9vruCyPX&K5+ zkjLya5FOZ}CwjB)<34W%lQMS@44gfjqrgn-47U?=9q`Eu%s(K;rhyMYWTiP4?u;O~ zryTLyGEQ6F6<<1XaUuuO&kgsiCaYm5<`?yvK`Chr<&|>_6??q!q-oM%_)97q*$s3- z=m}V!gO@p-m*jZBs#FA%%{fJu0o19EM8xauMW2GxZ4N%+{}f-Z{1Nb^b!$Q|7=1Gzurke|uB+5>!#-E(_rVn7e;{r8w(5pKqBtoEx* zs>umNN-#X)yJ4a>e($nfAI0s~eg{#qD~>7ZK`K~9LNX#)l&pON{(URwq-#J|2q~v368A{6bxrHB~
S|GH z!2%3OV+I;p|C$O-W4db&-|t ztaI6nRcGr0x%|17R4m{#1oCPqp;v2;9DFLk(q^!nwng0MXwtopXklgABPtdxz?6hO zR-ZxABTfM5R0sBTE#q7M9<_C7B>Sop@>IGK`thPU3r-MWtEPc%~QS0g=jyf-zN@$j-I@cr&_L-N-J zJ`ve{BP*#-SCMH@A+YLDNTax~fJmG)0>jT*EWccWQWV>V#{^0}8RynzgB?zkFTxF&L*=&Sc5l>3wcCtC35OEr2opwlaAY+zv}X@3V0@ z9_wQ5vS=H(2Th{`xl*Y#VqvPwZJ_puy>k^brR(h~ z;Zy4Xe|R2Iz(lR?3bc~qcm+LI;g0@>pRjf{6pGcr$nQ^o!^Bdh3W%RjBxiAoH(tv_kgf}2ril2*y9Y0J|dOZqnZ{s^O1RDG2H zlU}=!Dr9x(Pglw|7+DjgfJy*)!&tFJ9du?amWL+Lo%3qcnq3bfc&X%v9s%|alFkb6 zq+~;o#zwC{$u=XRu3f{6Bvuw!F^popFM}+m8EpZ3tiUS!{`;Jx z-4Oh+`vaC0pNpyY(6`9@ zp=@>P&c_a7tt3Vqym6Cr_j{S`*X8Rb`4r^0Yk%qa3$~qww0WK+qMO#j!aQ5gF!85d zPUUpm-m|q$W{Sdj>f$;WubC<9(YG!s3?-5eaIDlo`q zf(#M&+liQw6_?~SSe>3M^N7Ox*tiO|eG>u}FXjwa@7&2-W3f6}N;4!(@w6S2^+itA zBX3*ZW5=I(uaV3ewy}6%?5pD|qm-)7{yQdrI8Ad~CSaI?EF&vYoPcdoPYhRYFeqHf) zqdx}CL;FF9>dJxyb|u36Mjv|=hzZa^vjgwL#&A-SZVZSqpF@TQvDf)%qN>0y`VXy^ zodiycs-;Cj$JW?`v$W4zDp7^#ndg}B@dQ!}9GCQ4QSog`%A(Va^naHN?+m*$9d#fl z@yhs)XB{(s=tsBHJUJESid82<9WC_WWvRacX%;>AftUmxQJ5+w6z3m!FL@pnwi8)% zV6YjF^Kq%i#M@}@`m;hsYLXdPPw&mnUUX&lDTv$@3gBRDbbF?}ibrbNQ%prB+G4o_ z!>N~9j?(DWP^Ruc!JvCJWvqHGTGWNe{%}{v8*^IXv#3gkcod6z+KAEJH^1)(|O;btR9gE>N z2*H^WteD_h){AiS62v>ueq(L=K1fXqIlOm1nk`@pAPV9)?`B47PzSyT?xH0kuY>~q z5Vz~&sVSl}xA00xXq5h6R$_fPV~g_$vY~l6expl`CSlR=aXt|2GH8!hMZrVV*<@Zk z#$j^{CMF9|QnNuZ5aSkTqSe9sQp|Xbgs+JCxJwwNI6}=(6xz}x#LhU*4Au`1bqo5}2U3|7~j@bgU=Vv+xuSv*qX>RY~gaD2=5W&2b6Cmsv6#N_ImN||; zSixJh`iQ=N-I#*fb>=qC2%Nr0X?Q0(aYl1HC6fBotOt@__#?aKoQ!!e6Kq{8Q3!I= z`$vL-+Y0`&#jeDNZAg*$ilwh9Br2TO?^38$5+=ME*>5uPFmk5+JtF$Y{2(xAu-{0& z$S-Sadh_`njKM`sZI(@`>ISrVCtTrb30sKcQnL}RY6BN$P)QhpQHKiR4&6?Mg@Iq9QiVa;8RQ~-Zrk_Ko=!Feg4a~M+~*BydHxRY$48*O?{lNo z$T;w4;S>H;BwDSZ?PmP&V-4idgarxl7l9hCFHZ_iE@x6!`w2MD+Wft9m!o@ioRot;Sve*GuHUmpEVsRC`>}d7T zp8Jq`IipATjo{XTNXM&48(}vllpb;?Y1ID2m2^q(NnL0j~j%P z!HpdB&!jrr!QBe6;d%d2@(UZ$v;xztdnZf5kG5lGNt3yPt6!_fjZ!C{*u2ovh_9Gg zCch!ABPd)&vR>*;1>>;)Sl+_d8+7cWMeYijr_lH`R-BmGqkZp#S0!h4Xg4(RnkM`J z$F-v4rt?9YN{E^NGG5~Cfd|@tsjgzH2DvYlZRBQZ^&d}DHEkR=+EM@38VEJ_*Ic#W z7b9JgXd3R3%h}i_9g}zH>7rv%(#@fwNG&F*{&-p0VG%jsGkpNInp&HCnjiluz>F44 zqWZ19YF$mOdi5BB+BnsWWlrOI)gV|Z{kb)v{Lzz8!8W}|qc(jO zTbkuE2hP$czoh#rtkyYwBD|bYKfy+>8D^5RB6Fv;G$CF0Z5-4`+J0TTz2~8F@TxhUole!8Fn6*@gZSI2i3#+1 zL(^_o<6G2}iJ*~4<(`tG#2Yh|ljRAIq4mAN$B>vgxm9x?2MNS8bbvu-8$|Uultb7Y z2QWyUw05bhb7Jui4I(T%#c61Pyj@u%0Z?rA(95u+I}lBCFUhR|HGFz3izOzYe;+>C zIF*{|<4GiJmNp`C;@kIyP#(5e%P3%qmC|SjPUVn|-zonwuX36In!5RR=S`cho>FP$ zx67jvJMv}akT}xh#2e0*UN06!oOtG;T4%rNbsP9|a$%xfo@w|lY^zr-H8;8ZI!W|w z=+vqk8_S$XoDXbQtAO58q%M6D9Lk3eW9v7em+nyd*=scCMcq1moM+v~G;dy*hQxjH znRqt6gsJ6H{vlg7j|T?_*g9;d4*QL_I+>Ca{V@&uyztoSpybaM^!MocJ{YXlST!sO zCxd~N-EaYvPem;Lr?ZBX50XZPKhX}QNrn=Ot@ce~(DY}eC=TxFk*T?M|kVbUR;8t`fMjRAcqY%`hE zfan1tMhTe%B(4a*1;?bGQ2Dfl1YOkX58$e7wDe*{TchA=Y@S;8Z&B>HyhU$1m~Rdi z!LTVVdieVL8Mdiuy?b*6>B1O#%irdA_}l8onO@ap@F(nnJfGnSyv*p+x}_Z`78%LbIyGlorSyu-4`#ljNMbAL=%883PX2r)Ccc6oWR zl*Lm$rjtW8{KNAQsMU#%HL@8|(S%vciomX%<`^MU>pCYnd`xWZ91VFAHKgvORoFpe zk|o>~g*{>{FrkxEc&UsF-?4<_-*nk8x;ogG6_+Bp#`b4m6%&nfT}68JTh|aN_Z^Yk z$j(Iju^rGa%Wi0T3k7fJ)|A&6bDFSU5Phn+?ueo~oxP!!Bu_k!`Xr@FYsg}=-c9); z1W{6wgbfpq0I9mGvuuGOInSU~%sa=DoXJ@(it&eMdbkcWvC5l1Md7!~JTGY?S=*{B zG~H>cJZ_=nDDF`>P%A0BFkExsY4EPY^T4)faVoBI+H0e`6{5h6QQS zeoiNMzC5iw&xY*95)O$%@K*syz>n4)8~kG036IpxvE3rz9LU~b5zJKs?R}g zyK9u%p|Y>4_pz19OI46tp2vTbubRlwbs@~bq4}Efl zhFer)g<@8)tT3oF?MCDm&t7D`hJyze%4VH4w+Dllo^MpBsd$rN#6Y7 zl#BgIv~6{9i+lN^Dc5)IYr0qiIej-;Y>xmYfQZEj((Z^_Ao}|I3B64m@m^?PAD+N zlotU8wb#ghAryeU+GuRUfM0A`nn=9)WGKmp$|zD?M?yPd^;JfiPS(LpnU7D65Yx%> zoC_p?{+<77D+_5mrd|1}t0#mLSY-VP!(GET7@UtNO(oA#J+zxo@IY3Wy^ew(291~% z3vcH#B=pE(J>esH}$`?GpNdBwK$E`JbK>T9d>s4t*| z!Y*szkDQmktd!51J6k4xS_?rB#ODK2MAxs_lS^=82VVs={VliVN@EePutvJ|iI-5) zTvw2MFy!-1nod+%`U2S0g4w;aSG~U>bgPOnM^uNRWh#e=UyOV`-ebCiWcT4v(*r(g zeHzg5ZP(niJ32?ameQsx5OcI|*N+0hW*uaK`vEBtp#duravlMXgrBa1uAoXhVx+9%0-NAk@WhUtK>P?%yG%^RP&wG3ezaj zB&4Q6hyr<0w@LN<-k;AP`Mn~W=y7{g{(*Q>Wj5kTUg%Iq#_>#BR5^xMNXuyDOTD-< zpOjna$Neapu0C~m*_*~Q_B=|AQclck_1OoO6?XVIJ&>iyr#%cIr-y_GQnWh(m+g8k8713c)Y&CZ~m>Cmy zI>0cuIOQtTWQOsY7I|;gQ{FiUOz&dnWUA6b?@$AoD^I$DH*y7KxoO`yuujFc^~7E% zvm&A8Ibkkc3LZUkyN-Ea{sNRkj#S~pJgxh^z0vi{D$}%`V`noumUb%l?Aem2<-u*4 z+d}@r+cgijle|dGBxc30gmYJWO>~WWySvgr)1zL{dVA`${0gs17LIe*T*TAcTVa|u zDpx;bQ)xd>&U0iX!kbY{27xm!Kh_dy{O#Gd*G378l*F)dd+J2;>@vc#x`UbW{;JMLo^9twF zthR4zwSLBH0q-nP36$Rq{H2E-fzZO!w-twAfjVvTblYYMZC4gzJ!TdLfts zxV}l%4rY+If$vbdQW5K*Gs<5>+pZWL7AJ$yT9nL+fdv7E=%K^oqvKjwJoIpI5vHR?nM%eFA<8idGx2e8%P#}T zPMKJ@+1OC#?!M2uerrqVK%QgV_bUe5Oz;nrg;aN&3%>q3B~}-)OINOoIa@np^|KgP z>R{%zhOpfj(xopfiN9Do-*Nt7%yJzjC##%wn&pvv;DtjXokF{JXFhx6fd+*ty842^ zrZrnNbE^}HWIC8!Fm`=Dkj%9K^_dlgPgv}S=)VF4_~USc@pkd1S7I&Cg<3xE)!K&! zIt4>cujf)J6(3*AWJlJ+qRTIO-*pmK91NdXSYHSWnma6s`D+>q%BLAvs<6x3d(w3o z6ghhev}iit(iBx^*jyN!3L@VT$Q_KdH2nb7RA2;X`d* zPf7>4Jpy`qrk{_7m@gVo!Q;m;E5_L@tTwAQ>Ejy?1`pZrixX6viRFJ;$dgNwpw80P zjnlNG<~N!Ot{)u1f9M49>g;w9?mLLuS1q%EW@Mz|ij=U}c5naL8yMC>;fnD_7ts_% z0YnCNrr0=`?q*Onw#H?{cz9vMnzqv9Bx{4kE{B0gHUte6^o6yq(`uA3=)01zN9SC8 zinXUopXA+c-KJ!qR};o?)HdTxdfd)OY(=t*;o`#|jTq71Kye(}QW>5i?Y|sdA1})TTp!C=xc+K$ zwI6cLa{LY*i0I}2XOJ}T>oN!TChnMF_4-EO?BvtGe+$X4o23tT-om-i%a7Biw@gKb}Osp ziry2xB!${a>IWlnu8t=13gxF}=_T5$qWaIBfNzAOpQPMUdlnt2=|aLX*`~8}#U?~2 z+#uh?IQO9!?x3e#|A(-1Y7PX@vUP0RPCB-2+qP}n>Daby+qP}nPNwU=%~aiUe#Nf6 z@GZa^AK)J1Y{$BW-Zy*Q2s^?g7fyeF`DreVfaXwroWGIwNiNw?ncDFBl~iu!cuQe} zu|l3?r@Rbo*|qk>2H$+Y1+6QAud9ETX|!MEGx|ZW?6!m$PF8khqX*(Tp zSBV6l>f6{u73;OezqGPCdo%r(wwT)c=2z|Z)NH1~*f2az0liGMwTaD$qJPkUn)$Du z20@9v+5|&b9M-xWGirYwXJ=WRn zQ%cTk*F}VJ$ke7po`ei*?myP5MqvY?UlmE)HWIymf+j$(D%R*%L1LfXyu3d zF@)&nhZ6 z+wZ*&dmE8|6>S#ztrABl!jilKs*4-2@VlV)WzttEFndZ1@*`h0Qf^<{`hd{ax3|K{ zIwwta*S;9jv9ll()hs#7I~`X^JHQGE&K)aca(`Wz+3=DQ%Yt@2sHGHYOj#@gs5o~`y&$< zaOXW18EW69bbcb>aT|j0-E`^NB9o@-JxB&LX%M(y0Y{qI_y%O)74rBz+A5z$M?hjS zoYNVxn#yW<;JyF5sY;hZ|Q@JClP;)b-nB0QFTsalj>#q}TOV*_Ervm1> zD-{*3zUoO|4U>dggnO&(5w#Qp&KA>y8)J^g9um`%UNh*bExq-<3pYEK?p(~1^=*g6 zTHr=y8>}^p(DvD^`rt$LHlv~o6DgQe6WzxQXh$1) z?03q8B+0($1V_~zKMRG&pgmA!SYGP|RLC>|s?u>$45%{mGHZ>C_U}Rd%n7H3eqA!B zR8GFcr2MjKjEO_GYV<=|Nv@g$CSmVK{#^(x`(qQPu*yB~)Z1xCl>g60;U#n?Hb|)Z z(0;y{mN3^FWLk(I0I5jy&^$+~2UR3&H;^Y>Y=UU$50gNuc#liYlB(E(m|g<|%G3H(~uFm8E7vHTC! z!9S(z)WJVybn)>Fu#u4z%IHyoiM7<6Gy9GUpC`8P-P)T%j3#`^NL!8~qbH|@; zyWQm`KPb^LGOVNsJ1Mt_JWiB8+^S{>Wy^ZYe< zn~d?Qp(z-uT`x^6^cO}FHj!HiuM^D2typ}uY(Zv8y9U${+b+SEzwp+uWPQw~Mx?Ld z?hiN0I%rzF9SY+-D%ESn=?cFdC*B7Hj^0&;oo#xp1p5Vd33r@-02`(Y=Yx*e$d3@_ zd#j;fhM2R)Qn358fCTS#UFrCrda{e7LB;)2d01@2#dJkfRZz-NvT6?s4y5tb+O?~0vE85bAof{LI9 z&Gx-97&uw0v7+B-URluY6P`@{cXvw4OPJYut#J|R#sw_zh;^2Bo?B9KfOQeso9%Y^ zT=9sZg6qVRs08Qhz460C@f&+DXC_^(U2k~i=40mjwYP_dkBFS^U!~gwU-5(Pp_%|{ z{49@pYx^!}WJAs@>7F-P^7E|G_3k*sX?pKxs(P04dmW@`iMx3`S~!6JG9Lg=b}?-4<#G`66N+=0O!5yaUOE9>7dVjonhpg082RM}q`ExsVl{iHN;jVoK-xY6u&xVrRLzpAm5MnGq$ zvSNayKt@B^=uYb-+1ZruA$bHEwKb_IM#U6ianLEzP5?!b_Oy7BA~k{5G$pmXpHb&ZpCe{`x-y#Seh`W*Pz38a1xm5EUy&p+ zw73`EObLA9D=c< z=?=4L#fE^M<)_P3by}#^Uoy+7l%MT0&}LF{urmy!q|JO4oy8AVgc09)4ba-!BYV!+;2Y zdgB|>HlVu{cQyn?KIKuAT`TB8to8;Lbk_I@PeFNQcp|b&h zM80DSQb0dQ4ajf;bJ+!fI+pXJN|qrD-@873cyRs+2#gySQ&{)sIOl0E=)wUJ%N|5? zz#5e2@x4+z^ZCo@S-hxfH40|}Hbxn02*A1zb8}f6JG@Hkc%Omd1YJ;Os$*{y@Nf{X zpC&C^-VL15T?DY~1Q|qnZ`=(`cSHi}S=@4#R>)8AmagptPMae>3}R^LGypc!JI`*! zw6*iv4zyG($Re*rx->bmzA)X`ysmYbNO3Apr~%$nj6->h*3F`_AKdax=mHnEa$g?J z`%aDso8~7I*9Rl$`+k4&;mXmgd1JIwDCuA)ZzPX^vYN{!G#``jiP#nb67ibM@0Uz1 z8&M>3HzsaLs^M_#%U>Y-RTOr1B>wUpJ#%*SiIv!<+&`*rna>Cz zKw|5j+PRzd=QNKXG45B`17w{>9Y>OYa+h&N|A}d22_SBY zV`7k8t(l!9I$HHLzg-8g48oDHvtQPCIk$-rJ^_LEIi<*l;h6XfMTkP zun+DZzZsX%L5q~f#hyAmIS*QiBbD&ppF_QvgR$Bm5g;7;GNuXB4@TZuV(6zhQWQFY zQX)SlD+Y=@5lqr5;ZF&_;ur!$D%4}BOKE7RJy!o|q|o$$vo_$OpJU#ro$FPxyAZq> z(!mLW0(%RZ%`~NB;M))F3h%!B^7MiMM&;^cOLA@HzvT_|REv#mrCF-N@ajbD5(;DS z&#M^Ng4U!$HB+O?N>Ffrnw2No+3Aaqkh=QhnKm;hS-v%nyM-kZdkT@Q>Q^9=Zi!}j zVN`S68YVMm1RIDWI-{xVM@#kL%oowvM7IsBE07~mzr+s_6+wF+`XlvjCu`W5(pWkL zC;9YcZ{(VY4(viJhN;|)6vdShc{GeNrE&Nw_C_+R{;91a#!Y6;8NG0n@fIp(A#2dW z4s#R!j-L9?Ye>&5ZRSj=w0#yu-IkDJj(KI#fMc*-lwQ#5q_Z-R)%}2uNE#5Go39@d zs^>UUi1@GVLrFOtT>u$+*CrG2ju0|=ODK|9guqs{k~fF*>>tj+d2(+e%jPa(=RFI9 z*Asa-X}fZ%k84VudfV8u+;4GfmSh7PNh_J9`HofdxKUm$S!l3D;bhaBj2bxuu(ALG z3l#8&a0>$~N|uK)w&s0xj<62~z)se}i^v9YV7k=iw5rk0R=9d~R&=tDZ2l4J32+f= z73fBLJri{^iRdJS`Hc3LvISg{oylC9=Z-Se;t;0`SWIO2Lh>KM_uEj#Q{r|6hc}D`&DWOx`p;NLA_v{`%UJL^mvI(-j}wn2MJ0q>ialCE zQgb5QPshBFBg^pOynm!T_}dYun6Y07LH4<|+(Op+XHn(Qnl3R(*Ut?Zw)xhY#sotL z!qDys64=|Aqu1c?+;mh4!2#^hj}}0C@ku@Q}TowS|-Ue|Zc3pYbD#^w0Q_CRKquCbHmiaIO4GIG9ka`fF`LI#RP; zUHyQ75oZKT4`E6GHK;Qee(ET#GHR-ja_ZGQ^vGu zUix#^+~^=*4JS}7bIesZu+ma(!wOy1&L&_mTv9HBY)0AC(U+M{>5Xh1UP2L?z93UB ziQMcm5jtliwRKSzXyH;?sDOPdrQ*_~nmKdUmNrE=b@cwov>EdD^^X1QMZacfE)&Ew z$w4xlO}V9ciW01NF0i>?Qddn}ZeMO&klo5Dy2xU{kglB$7im?jVpBlldHR`0shWfu zrHjgmrd4+IHXy&KNA#Jfc5f~#Y@V=-!kz0CMshEYvaax zt77?hbJ9Mc#TSg04+M?jb5hf-x9mJjPVE8?f~%WwTLm=yW9G{-;T14x0XrocO@Gp> zSIGq)Sy&63wVEJ=ClOy_@(~GP%~E_e8SDm}hi@GK5~WN3)_(=W!;N@`A}8L5^*miZ z(9I=-P?EsTIddob!`1y`%k3DfWuA~D`nM!KbU5`W&9dRc4FJE1AT8fsx$;0lk$)sbz(p=n=vvna`2 z#`sZV*4(>qW3d&G2LnG8JE{DbwGV~W?i|CeSyQSPeXdE|pF|F87f@gOM>GYqzwUim z%HD2f9fY=!Xl4Nc7g`U^GGB{D-Nb}-k3OvSAvnu}L_A?_?`dUONdf!Vs zj}6GY7Y!z`vA23DdR~2!aISweucEfC3o|wXo0o$uVFH)cROlP#N`s(;d;=?wzpRio z6VMPD3wSz?EMkp>&c{d^Ltl4Vc32tiG;8tzXXXvzdxD%P`AW5~(2H}M2x0;ow|(|sciAV$`X+clbjOeddbl?^KZlqqeHV3yNY z!m#jqKIpZ@->Fhtr;ha}&qO*WpY1+&ldXr7-MBGF@^E0{viz0)n5n&^Hv8>zLM}}* z|LS>C@Qk-BOp4>+)Pyy&)ZSX%ES;R%@Y?u{z_sfouJC7=U$(uPIO!BW!lOKiv3iL) ze{z_qhj-`q%7d-qfWg7Em>;yQU2yY^ny`=wk9~=oz#14PI0Qyd$(t@QS;4?+d=cz< zbVZ58MmE(g3xZ4|DdzI%8H5I}ag#6gu1JaVcrBVpAYmJd4obbJs(Z}u0O$x5Vq74y zeN-Ho{94LLYCxOFDBQ^y{jh}S^ZO~2Qj2(W#MW>%NslL^YiEbgUB2JKNhGuCLa7EK zrh~Eb$>B-0JF6tT4-y4%8(U+&!1apelziFiuvJKAPZ0QKXe(fhkFd zNf&2gQko>5;3oHBcBLKhicI=qs?6Q3YoXL{hB^%rnjXYIo>r8wnuHqt`SI;pJ5pH) ze)Y-1ZgUb6M3oegEXW(V^<%!N-JBXHY)n-=IFi;b^oR{0K?~_vqm9}6`d`+7tdpJz zRWc8Y5~VX}t#k#puR!5vtO$!K4MS&egez~RybHQ*#|Va#^vofWX}GvAF_d7M50D@_ zj4TKjg@S>p+fP?Pfsnr%&$MQ)SNYm^fX7pKqj^x2k{t3CISuTMQ06&-vs=UrT9Qoc zj)bP)`jIpENqNF=($z1dQV5;f_WO*KCNKANBFJkk>-H?h3Oe%rUIZL_%s$VLlkakL zdMgo;qD}sawD}^We7@-%S4?6m>%-`NPY73_LoZWFu*(S<6^}r^Biu{W35&J+E96}q z6ofa{fbihNFu`1|aq`eT*zvC_Y)L%Jdb+AMDe2A`gz8&y$p|*ZUI3vvZ>(?!)WlG= zK4dTOx_`MVvVcXLFN5Nt;E=rH*_Po=^Z<$ncdW>4Y zN|4f|uc@8fdHZ0~b1a|W5zsm~+{U;NLj>GGjtGPNiZWKcW=e%91MU+O+J}ZwQ9HVW zr-PFGLuWn52M8lDk053yt%7Q7H`vb5Lvj`ht9uSj%XlTM)x=4%R>#!#5$6cuW{wcz z9^$nGLt7V`U8XKrnp2Rn)PKc|k}x1q+G8YRjBwVkM?uF>SqC>`p|sYgVoBi7A1Y~w z@W}z2+P6+Wv$=PmXQBT7d|CkftXOQPEh3HHWj9nGxfabONy&R4H5OD>9!NJ!$h%%D zGm-3qUlZRx(JUu9uf)Epqm=~`*tC{SoY>XQ^uJ{1U(LR-3t=?yU>Ua>$3io13w<`q zc9BN_Agqs+NUsJdlVjo~yyeV0wWsd!(X&{F@P|Ot`PgYoF@FsmB_wMiP zvznEN?ygS{R&71|f%jtKHht0timOyxVvlAfG!4Er=)@Sn z$*0xb4iIYJF?ZPtb@0Wp6WeLj$!4?!#d)z{Do;=j#R`d|fQB_%fQXoNdrIJNED;4} z{9>$M`xF1ib(I2jP&R|IZeVW*#Vu7uWcW=;$;$)A8=G>4&0LhqU@5R7+PF`sm!c6E z@~BWZK_i2+b)%L>MI!!1Y-Nx2L-lL%F-yb^o0vOy* zap)o;b7~4(cz=kRn@T9I(Aj#4iWB_v_$O*%#q9+C@W8Xw5A(b`8;E z?tR;xXUM#MP(r_5IjsaS7ik926u{rho@Zu&1p(UjHXTa zV713Kxu)#8;Bo2c>EOgz8zcI%H29y=BMGQ%b!CRcg4`v4gIrCpr3xn5K2H|&$r{zk z+BUBp&cH>`3rhZxIUSx=P^##c+P+1S9#^SXKy^zV$EGp0Q1uDRvljQNfmP;-f>)?W zdR+yHAS+iq9xhW(Lm>X`8`A*)S~cZSq^RMkcy#$5MY~qw;R(|;|L0smTZ`F?Z3{^;YprcBWnL7NW*)Oml6R0G zuv|mJ2Yy=d!&N}d$NTksyIERhQRMtFr5Nxdaqtn+M+iWMF!mW2UDe_#hB~`PpZ+gj zHwpgPxKjyYRP%ntHI6U8u_X#Sn#vSf1OskgIj>?*jClMIs_h<)v<&gin4U=)?HDoN zUQmaC!YJ8`yiGWjqYWTZ16wX;|+x6em_NqT8Xq4^ZPGtP{gwto>_ zP_B8AG~9S%STCgOQ$RTQP8O9+#v?a9%qi!^8pNhFhvM>mE9|>C35;wSfEj(>q>A_r zWU;?A@n!3Y?Qyr%6Ry0{$3|R3o~4k|V+>!+{Zb7ReLAK&_W=Iq5S!vkxy6(ScCc!D z;;BkXFSlbw0eVB0*;!aSTD5PcB?u##M6bv|M?GaJYy4U3p4ZoR_Dmp zytc&_OZlEHEhAq`TL_QJo(6z60~Bbv5)QYqAmP~2ukSgmK@i2qaRbhs)^NlJ=}7#d$wlHOd>z!=*Zhr^l|M} zTE@cHE~MJr53`kAW;@Ae5iyfoZtqdg%olRr>g) zu)Urt)6UGX?uitW%cQfyRQgf6{VVJ&N23A=G;d|!U9n3Fl=R5>89JcbSaxI(kE z>TJH`YF>HGTF1D;Xxc3&s`0DKh48h9(mrQ>wcvt_z4A*40#Wsng${=dWmfB(5}FB zR_Qp=C{01z%t-^+asE?>FkNcFi3kpbd^+G{O^lrej?HNqf1y5X;N=t(!kyew%TeK|btqQwTZmM;syt`c4Y>qW z5RXThsI#pKCW@M$@Y+vqe+;ko?}84@4I*SEQ`3U+D+{#ItD!Tvl5FgeYTee!yu>zP z#WuU({rD?HTZV=!#i^++bB`>Jp3$c*BsCgO)YYr7q1f4X^t{xQ( zQ98~DS?mecI!?dMI+>l{lG~8fcg&zt0;3QHgr*k5x$!3`WSNO<7STUaDt|?5xzZlQ z%_k{jdn10Qo=rH_ajbUco%tN!CYCH9Nt0g>M3$;m8%$!`8KmHNTcO!kL2*9!$`A~e z?f9oW`O_q6R3Ct~1p8QY1Zpv;&BFsauRIF`qVV3~(!ADF+!q!?M;92@t(RhOdOw5I z&n`W23cjRw-~qm*e?;~@V?I*#e_XNCoh)c_80bfEDOH)(z4MIpnnE?ax_@nWyiuVv z<#Is;7Ud+EB%oDhp%=KlK|Kd%<8SN>?k%*lR)uIo5YwCK0WU2WK&$Ccz z&JHt^lfN2iC^Pt1Uc zH}o0s=~;lzT6#9xps7QI|BV3JRS=@UwXTYW=;Kykwp6(QJhh07e#Dc+L`P!9J2a@) zABVeJ(-I$22kpdj3?*?~OO0@yEW65cGCJ=(m4WUU^K{F?BH|Ce@QzwCaD}w#VEB~c zq5z-+feL8VXYB>(92&0@o{@W2v<&k(-i#x^sv>71D#IJk`wIdL_GXJR7@e$htlBks0S0 z00ME)8oE75g>V{9cR^{j$H8`CRfxi^bSf)^)yDyb%y?WfalYh1ZY&1*k;Idh@=^fh z>F~W}tggc!VIcPFKz>2Z=`Z)c0ubZP--ZXWq7D7`;@Rtuxy8m6CGj}}Rq3Ls-FH7z z?P8I_={bz{2Bhf|qY0#fkhZ$^N96iMD9VE_T83 z`nYkb-Gv+`CM9s2PlF4!o?0TZX!{6K`FQrcBmENNgY{4!GS z`|+iiCyBo2<9ng)$3kdKp&y5__=Xetax2hF-G}{R{p8~Y2pXs4-)DR;n{V5GcgvhL zi62MfIZP?d&M3QaPT4+A%!P^ zF3x7o1QWvDpjSouj8YD?G?qJ))9|Ue8DfI5Vc)3DkKN&;dba@_&WHgeF!pi4#m4Zm z14d_}e14g8zMeNwGBrP8EiPSuGiv1-Gin;|q*EM*&NctxqAwABM%wW2>C%zv#>@B! zAyewzQxg{9CwWYf#{<;K!}~^2m>4b)8~dlE9`eL53%yP4X%HI?b2JAJftXhQYOq#E zue#}zX4?d?3da={D8xaN9H1YGG@x%1rn=-&gmA||O46?+9UhSE?-R?p!yb$T8OI{k z;aR5y`Zkgw3B^Z5=9I-aSo9xu9UgyPR%UiS!n-MwO17Yy^2#EuiKJvvrQoKg7UT3R4}&cs z?};T|l~ug0t(Fryc=UbuD)g?+5idq>Nv7F4j|T}7f{m6X_$rGHRc!?DQcgk;4G8ys zZqG}7xIkX$9RA@3FDG@mM8KG`f&74jx*LrwdZWgl<~T#=&PlXLM8zzB4)nOoQ%@j| zrrevaAV%dkF29m%L{Y~i0now` zbA};@k@ym9CEf`HN6@dNq$McFKhb+<*cfgsI%p7aY#5G{0+sG2v%AC~&2t_6f@p%F zxau`y9K)P*QaJ|~-*B}8!XsatqA`QO{m`~KP$+t|k5vrQpfgy7NEoe#mGlLKLHME& z2!l^N<~n)tc`@q*hC+L>$7=LX>zcm~pRrlJGSaVJNeUYWaL^E^jj#Zu<6|urQnw(< zKA#uK60(l=;luPR`N=N)ITXh^nWSBSWGjvXG9dMmTrv7Fx#*U8*<3 zs#0`@P9z5~kvM+zZx#ZTu=H3a8{nJK1Cr*j^K**BPQ+P|Hx&9yIa9^*&MkH0dBz(} z(I@zs^cWM`aS+};g+816i|kQDt5#K6%pDaOljt@gDT;G0E~r)lowTM`&KKlyCC(g& z(X}bc(?dGk5GF$lCbsxuot9bQoe^quo*E7^$E~+dZ74(LO7}*)@eKfBSW25qn|I=0 zPXN$j1oN7m+5f4)R0tw;T;dc#anT!RYJJ2Sf0uXQFt*_gpvt`FzJ$hkBEd`WlbWtE zoC5|$YjGu3A)QBN-B42GhUc$_h5ypyB}~GN1!#qZG|3Ar$C-Q#5Nhp9#O`+8lZ~W- zt;+F?e$#6z=6Ciad= zin?IDj7$#j#=jDkqHL0+rzWl*cvOF6N~94@jn{tYx`_?(M#XC|y;Q*6fU&OK}CF)bDzc@0|A!oYQo!36tRb9Vk!d-)*8 z7uoPwRBRBrITk^5JoPjeKUJGWKOV#_GO3*1Mr1h<9iJZ#WDwQRVsDSv%KRA<`bqf* zdh{#tGHA`Woh{jDN6`DJ`fdEppRhX2d>`gr z3N5B=K!|YU)AZqR+Qauh#A+5yF9(toA7O`*L=m&#mf8)9{&5K+vMSX1N8vfZ>#As2pS zH6C_YU0W8IEf(yL7aF)fH*=PH!$sgV=(oVrNubGe!;*rkzFz-|8+6>_Nl^+mJdIF_ z9rX59S6K1|yBU)>@^eRgtdX^l z<71ZzjzAKo{w(IuRJ@))7%T6_j2jEvGQ%Fq%-cM_PEa+;guT#1@4bP#b~#w7%g6dd>i^D zr(i2~ZQ$P}ENfguky#E{^}Fj0{9OE49~%8btk++8i50V?*b?9)M>P>vH%n2*XbDs4 zz}vJYCgwAMo%P|gU?eW-J{BDMken@Ix2cS#ec!))Y07*yX`w{1!0@9*dUqya7Zv_E^pvDcv~mw-3oabA z{o81WSuwbe{S{4tl?wVT{K{2ztRQe>P%N&-k}M`&vgumIw4B+JYl-~3dqdJtNcE8; zyCKbnD`zn&erFMrREkb>9(|;g4xwa_E_l>s6Zb6Y{L&HG(oiA$-~5j+7a z)QbNlUAoJj>}V3DJ-h4rZ5bFy1Kjm*69~3HoV>6#M^-bz%D5Q-dBUNqz2LB2tT?Ow z7yA$A<=cjg0sG0h(?7iuIqrH+ub14ZN>aglnrA8`~N1(g#0T={#(lO$*tvA!Q*x`Eh2GU*Q(fXq)5mvJBU=x zAZfN6h)W|>CFuvq6Fr1qgI|-|qFZ;uA_+?>m=2mWLIS|vE|tr*rTfQ3vlTqCL9VWp zTh^$_EV~=Cz0506;yS%en(2ZTICgDh*jZ9A2xDl5dZ~njrtWRU^fRuBIUzhqeXO8x z*<#lVF?#NSt7Z$h4T6pTlNL7OZgnyBRJv>R#idr#)4H>aiWYLXjs!N7pl|}HWz+3r zm>r;^(ezrf#n;@#CPDMN@zrlw-wP{h!ik~I@Ogsmf_BG50&c-6m5ts(Ez`}?xL)gG z>mA-Pvs^Q$usm`ka6Y*4Wa`J6>ElbIWaB z8r0y!zlWO!zInB>^7itRouQXzkFHbbYWgkf<7lNdkT3IiW9}RdmtRfN2YA_~kURtX z;=AN)#c5{GWM_R@5`DV_jyvSW!gF~s?%>P`PbpQUs&P3Q-sUI!|iQI(8k3CD;s{(4haZi?2H8tj{6AAU!9y_Ihm$b1_z*!B6M))v7cs(IA>!$ zTBl6DBir*C+0}-%xO%$oa5b;>5TKIo87W@RHoF7faXsXtuz5XuBPD|(pcFfGpOT|$ zopI;CJaIOf2-1vd_`{s^;cOR5r4|sTo@NA8J zz@yNJxhJKt0*>YUcDxdfU#t=Hz{RJ%gPZSDTr7G4J*Qkp`PUK{QXsV`g){*c|J6Ua z`t~gtlJkJ_1RsCdbaj+zeh?LijrSX@?yqTQ?(_^|KfACWM@I_Oc7YP!y-aRTp;D;T z@9XaGx$a~#??pH8*JmufsZ?I;PRf`3x@sF<9PAlDWQFCVdFnaG%D1U^QyYCy!Z@jz zRnYXbW4GReUDfwo%CV!_qx#-fg#(L)N0+Y=K7gVIV%?7zdSRs~1ZM59h^+g~84H~g z#4zeO^mU(sEY(bInjHwE?iVKH?)Q zm3v(swR|CV@jX2au&IHvxii==w78NZk7Hl5o7NU#UR%C*NR=~nk!6llXb6zEk^L`E zZ>LHIM{YXty19T3qPOTyRnzVtfPb7={W~UnzJhsATv_K7j@(4$q1cee_!Qt4OIk1^ zA=4mCJtaLFxc&;O#MX6;KY=|+NCY<)n0H>S zYM?~IJw}SI=fnI!OP1RQ@_}~VBVb=yj5ee$rU@2&x2roR7g6l-V?3#*mD!h$63Gv| zBqX6pzJdtkwA)w?Bn-P}SmMZ9xgY>my!lZOafL0#9j&J5NV3bVlsrcghV=b)D^;*{ zUdnk(T>^db(?plxZ{*dh)XAtQkoen8lIWmIm>iNb1{^DFIMLX#A z0En!hX$8ISTNVL>)O~mVZ^`0uJ?Eq$O0lFc`jbN30%-2@RJx`&z&M zLc~GEN1U9=QLh}!-V(~%)cH&M;p9PB&tElFK-<<8X?}rKCxKjqA#%BT)Z&Bj;x>)O z%^@a-&A47X)A=E`O6ZVQIOk~9EFP~hSA7*D3mrk@Gim2ynzo8)o05u%rE(?2d%NvF ztMc<-Tn;FvHLN!s@5#;m`vteoOX@P+9d(aqk=J3%CCQDiT3XimFM{|aB`;6p#$yE9 z=M?_fu)EjqxP{Q_kOjrVC`NMru$&WROu(0131Emu%Zkr+6cl9vR4#^qq;z@Xsj4M8 zTOn{Z(TBG>Yn7KLuo)(nBjlH>I>OCslW&5f-tLQ9xQJ_$rc=2DZ1L zb9l0M!G>XU*NTT9Vtm`KAQ5;xdi(QQ-8yt8SwFJv`ivqK@ zu`{67ktmRI7;I%@+^v(&FP`?G;M++`4U%X@Su8kO#P8GCTdI*1hvNaPd1&Z7a5%6# zGVkPJ5aB_fU<0GRkSk1WMRl8%YShY@uPp;l@G)X?e$CE6pAIOyR>R+hq=pR2Emz_r zq#tjx*=2_9bl)p?`#iF7fB$si>y97B9Lu5R)TY{Y6 z(`<&&KVgSiW3&Qi)U%eSS zR?f4->2(V-50Xv>FJ-$r8xrqErR&FiLm%~J{VV$Ih;pEKc zkW_yHow|ItxznJ(cg?rO&aAiUxc1rIb|*P4P1W_#0Y`fZ(2~D9>n&J)|0D5;`|&K1 z8oqRAXvGp$gE2;x;?GR(y+j|A;e|JJE`G9}bT3lIK8%sYXaOVMpIg(TT|2{DYpfsq z6X#_w=z#$UhaA9S32t&7(yqtB>^4d%Q_25m!vTZ9sX}6zrWH?>C4wgf{q)oNx|*$e zh)YtI*)o$LE~LZ$COmx|>eM4Cicwd%;1&wcE*$T@4>9}1rsfwm@Ok z5MHkADX%)A{UjKQHV+{Su>?#J^_=#CnHUVh`$h_xvMN-f{cmQytNF6GVh&jbdfcbOuhfAjT*b}6c0Y<=(=9n0} zbPir{kRI}yqce76Ou%tUW%s?F7sl7SseI6x$g>-eg=WcPUkCL0zTdOa0Ur99cb9kP z^*EI4Dm62NvvMAJ%{$*WtkeN3KEtQoqp3e8v~mCayz1)Ubs;ModVkGF@{lm%ln5aP zZ7Jka*elGF}KO-?(~6~}uJE>ARGKyccW{7AWV~+;wnJ z)XxFK#$)F_j{L^f7^PBRW|4ZpW0CRGGzzo#xI}02UpmqmCiX8TlYo6ck%n)FKNwZ~ zYN|VuU z>zGL{_p!Gb8TnG)J{Nm%M;ohl4$Upd;+}^`PGy;Rj%2EHyiR($ys|FEn1n)Tjsr?V z2q3tFZM|Ook$2Aqu&thmSc~J=T&+YE)Ex3+DbZJNBU$M*F=~0Z{099Dzf|+-zJ=*6 z_RNWL@NaQ(<(LbMXb;}~;4>P~N=qW)en0suf_{Q<*~q4q^w=t5S@ziRNYL(M*=@vW zj^hi4L+g#?Y)H<-2L=`>Q_EFf>#AcIzJ=_lvetRbQ%-F~rGpz;jOkkIhX!y7HgJi( z5cpnfB6AKZt#F=?Jtz0YV-U0MmE88VxQ@=y_KcNH*^F5!k+*^AImOcP>o7VX`B9(p zZ$M7AGnlhD+8c+j>KG3R=nIUsH6jiYO8=PFXqvdmOkCOXgnfqVtWReCQOx?XVlMsg zEJiI&dG*LdnnU1zya_wyUoGO{I%i#Ta4ra43rgfKX&S5=?sqCOeCa4zxl?>QeB0C1 zTa35%CCJ85$};PJC^R{W+zPq!grmqQM7XQviRLbvOljt%wvkpDBV0q<1~Dk!l-n@H zRmCRUWCl-P=8Q;|;^ei0XW2liO+-6&6&f*db$jLnMTe3F+f@g=PdxcW+eT%zda3hp@A-$- z_S$33IeMqKRioBlYn@so`e!u>l9_@c--zf*YR^ncMgI<*lC!?UvOpm8BrlVD*&o*7xl~J2LXg+O{6Tm;f!u` z$G_p{)9L+Vz-?bM-NDLm&jb=G>1P~lSz5u=6?F4=L_v~Qp89KvH z2PT*ySa+!qh2}G#qch8^oI*p6(JkCjXKhvr703a_HGW4lv5Eui$*D;bN&E^(C*7Ki zpL?6V;!`DEhL?Hiy~q?@;51@a3H)K#v5A+#fWbWX{g727e#aKW47~zWvaE)AM#z42j38TB(4FmsmUE}BQ&tn2aGmG}-Ht!DW*8aO=X?J3g{$RCj}1KHtW#--h)pmKz6GIDN6 z35Hf^A^>p7V9-s5Li`Mt>ApdyDv=WSLdqI{`CfNrP?42Fdx*Fae5I!82=LJyz%=9A zPbh`bJad(NktnaRy{Le;5v<8Ph&U%XbXNSR!-&v!A&Ma{UeT`l^W{bthK9Wl%^S#i zQL5KCFqM&$)yZ|)48IpJg%XHR2h<#>=KM*WEL0(+#xb)zOC#18kiCVO0)I8%VHkbv z4bhlB02p~hX5T^=?ybZDvvHcJE!9{GZg}mZQYRuOLC<3Q2r0Tt(;7n1Pm3R&D;EjT70Yq0mClz3IJ+dM<3y%@OM|PFM*Qid zqT#!(aYRC8U*9-I*#pB%6jAmp7*u|m1BOri>eO&jngdLDB90wd1{;dOgi@*gzDbxm zMpQ_GF-xx)=ijkr*ZEQvx~H?JFa4l=JQ;E21m1Rx^!hyqJ%9`(8eapHN?$d72H8pg z9dTLEM5-<}?u0=>GL856x&ACx&5SBW1H2Pb%X1u+$Z}ajpvGbjY$!LH%r;~Ta@BUU z4TEjOS)E?sH3+?vHy8=vHS-7nU zMHH3j`AC#FYO;m+F)9lw8(^aW@cap4JM#dN3@4f5l^o^5AQ`igfbF4f6usC(DJZUiC{)zN+T!=!m5RZmsYI)A5~UxCEjbw|9beTu@Xq%>UK} zyNIIIw-6!&qKRM<&9os??FN}Y$*`^>4UMGH&A#Iqz|R@hMz!d}J?Zm+ZR8)ba0!yQ zRxzePrX(-Y&%{-0rO`}`Y;~vQyQNbF1IG{NM6{vA1$(f=0e_{Q2%YlCs5+t5uUr~_ znpDo6!sC#_PCR=}r&;53O=Bl7TAh$VK}v{*KZ?BK!B=9m61VW;`Cz1_+mQO}I{UW6 z*8evM>X4vA{d__x+k0X8A0#f3pwi$fFQ-d#t%f zIbQkzOQ56BxK4Rv(Uu3TIZs)fTZ4Yd-$GsChGG67Y<2lMT|AFkm~1blHM6@!=^MuF zmOGte2sO{%)Q6?#JjyC)+fHX}y{5Ag%0=C?7Fp`N9jKM>OltA0r{@}T-_qmW!HKw9 zcw@@lNG>zf^An+vrXM}gNiu2e#Po{7156R5v-wo=f+6jk=F6livGam$*Td*rP9ySm zgBbE8y*~+4RvXie;4GHjikpUk%>oIXo)?0hMFf?3vm{@|+M$3EkJ76~3mA*uMGy^BFripa3EAU*9X|U*GG0l<(Tx8QB{; znf#Z+SB>Vi-R3yzcU@V!>Rii})XWW-XcS8MKF5sMwoiLPl0kz80kIQ_tc+7T&O+k{ zjITeReqQnE7G~mMOwi9czA%~j&6fA+mNS351`S!qy{7TyO6Ns|mtFU^+9c~_s_UU$ zjMMVQIa%AXnk`h@tF!53CojeB#mXMP?y;3I_AZ^4HrBG|B89Vh)@UXb^N&goi|F-n zhr0HnlksAv&O6p&maL%c)N2>TbSrB)xm>wqCFth_BNyYs@>b3} z4v0m~lgZ9{KXxO} zElyd}-^%4zD!0v4x{wLVE$mixRXav!VNnzL8%N++8E+xnrt`eWK@wSoAUB^z z%-Y(jYmDkGo4}HdzO_=`<_}GW;K9kYEp3^5BQJlurjWFFa2B9f`#H@oat2b^JbL-c zd#vs7P)N=~@}xHxWF$V3V{5qlzhrpd?cRK|_0;AwO9#)}{BeDtB*9&kJ9ypn+m(z; z9Z5%4N?U5IX8`heeNzGdYOmrD*gpjOdE2qIGWn|T>@ivy{H^stuzYJ^la%oF3}IK0 zHFsHZ2=LHxGOx0SVeuQFFhlWS!@Pq3-MB!byRPv&e`!VrvM|N+f1<9HxT=LFK4q!D zm(g8p;1D&+Jju=0>DJbxr=QUum}F`EnsF7SOUJ24O&9p&qk3<0+u3wAJgIc54?I%_ zP;jP@IClo0CGEawc!o+gbsjRHTmqY)MDMK6SJEcUg+c1BXvto1 z6Nni}T{s3a+VLi=v<>nGyHc_9RpZzl@E3In0getNhfoA`V>n~I(WKRWZiO?i!d%N& zQlHl!L-?I6&Q2KfzGH8dQz<4MroJ2u;B5Af{fB>GX>jWtT%nvW?c||~#7HT&Q^iZ( zRQEvFC82sTc<;9k%f?rx2^Q!X6FseZq^9wnZ?DuvkvsJeUP^7T)-uAu$;jwDhSiC3 z_j|j6Clo#^^#>+=r}sEu1GLm=U2v$Hv2Wop2r33X^=b)#MOew~Y7M$Pa~Gci?V%sU zenyL10;NFX;Dj-U6MA`a$Lb63ci7kMDS%yb$|zQs1eZ+i$aHf}v8_Q&%BI$edXgF) zN@>e=*W>;wl;of+f1P>55|n*nv4T{M8np8q8d6>99C?4qOEj=t3sf($4MClaZl4G8 z;t_vGjIGP?=+^K+`NCsSYM{rtGzbv!RPO5z%AN+tB zba0ry`-(<@HtEY_W~v9`Xw733qc!UmF4)g-azI$2paH=*s99(w*3=u$VL0K8Gq+Eq zUV43z|7l$cpt1RcIjy#)e_4qrUWy(b8)a zc|h=|gDNxFh{VNM!bdmh^kBQy=6Ov-2A_j{yakpSXK+2ml693?M;5Uw;>F;Mzm^|P zxKukz=_y-O>{Cs}@~g`@az{iwl)AAM7^7=(TR^550|k6P=m+WYUqmy-uFk`l=nbYB zt>gtCsbzW@!xf?T^>jgV>pgOd>2#5c7NA1^{m5uxU1HB(2$rJU*RA4S)l<(s^-RQc zQ_?9R>Qo6+2jFX+p(6IlRW4yQQM?`gYe)L2};v2;t$ouWZiGQ<8GJ75UDi2qN>!ZqF zaj8E9xJ0d56tKT6iIu>A2xSm5jFHk-??gPg-btO}c{Ykc=j)cv(onO~6qcShzNt1K zHo~sv9-aCpJ@0bKE)>q0XhXh2&eDiSXC|;qGacf9;>U{@$e|2%w+T>9VPiPDhJirkzf!_ zPgOy^CPjiQ&ZN7x2^+4o1e|}ns>e3cw}ii2*g4;W%5H@tCSeA4 ziy@!{y~mvFHqUSf`dz0VhW|noX-I$U=oUjyHofp!9+>XJqwWRv9^N5r;YS}S<224!a?w>TIh z(1#(Q4Pq%YB9HztBYDV>Vmb_SVI@iH6MP3~)?@@=p&$n3^XM9pRX#+gy9D7UA&6BF z8ekW2WV^o1&9y3RH1L|{8vgKO8(>$wdE%gK@ZI~X(}vYS{^Fr0cPU-0czd}f#}i%o zYHSKsedGsN<4q26X5_RYn^$r(c=m5|KwF~%Y66hv*Un;NqZvuV4q?b_>=HJTlqI#C zLs;_(l}0eErAs;uESa1Po^qt-oZx&IIS%Mi7DB+1fff1o!=HO&<7^bwpj89-W$Il! zxB$+SkqhDL2D%DLL^t$@uZXC-_q6&IH$a7%YQpts&64aa%}$u90b|ry1eQ zQ8;Mbonv3kyBbQa{6b+I9F#xDSBVW-Y3Z;w*rQhhx4J%9DIFbuiR+2JN&feJweQad ziTh|T24w;m1%Mz=MIsd$8wv$X@rEQ=63{_!LK@cz@g;@}6a9Y1#FIG_Xd+debvcor z{)NovHMrY!ov@UW71K9=GM1v72=C^WYI+nL>3C14F(vHvEi^phzqjK9kwTnmR!uV1 zbP`6rMH>uhiL6NSf&*xj?AH2Z(zWbfM7;bE?cj!Cd4+qK?+3-Us}gildRC&d)pHG# zP-zQzSNU9DMBH|<9z)AIk~FC<)Py3ldfPHyUP|1JY&(R^%Njm3!-a7vVk@V~qG#1| zt$6qO4eW}Rv4S}o5>k@@8+P&4LwG|cOsP47Cs=%s7cLY`pfJ2GjhXj5I4U&+XnnAZ z-c7p<3a73F|HCT`@|hqr$2|OC;x?7+{(nAPVc9@aHT2f(!8B%}rqZe+abI--Zr?V2DTQ49z5w4_4IfA}x8alHyB4#yN1{LD?!*yY$u zaucZVAidxU7=I{0U8mU9)h@7qh!D$rs{n>pw zx!tJ$uBzMb>gM%zl-^6S`)_&KUoG5Zw3uTp^Yw}2h9b$5I@ zywfrCL$8_$kKsVK4my^z;+0~U2Y*SHEuEPTH8wjpR2 z@@rf%E;+9p>s$Q=@J1WWkN~34e5{4c)Av6r9*qK)u^a@J=jW+}1s<#%q`X2O-&Deg zU2#weXDg-%!aXM;hXY=|+Lyd#A5${l#;!}PHm4oxMHE}hcZZZiM@kS>Az;u#wUOLJ z#y+)}FqP29fH(}YeA}kN-1;s`T7Ncik_AG69_CAc=_Js79@;{rN_hG3;tb^GWr=;C z6#?kV9?h3}cD#N3=~8{DQLvYo`Nmvkv*Eoxl{v&)DOS>Va$uX18+5Wn%p9*ejmalt zQ9cCePK}dnTK%YJGprpD4ZbrrTlE`vR_8zes<1&hTUa_{b|gAZ8N=L8iJ3%2Zr*sr)CQ& zx0d@o-TK~#XDVx$HX8$4Vj{jY;xll@$(sf5Mc_+*2ftk)D>`5N1^Um3*I7c02>mbO zh5eJ*|BpxyBYPVYQ>Xuu@cuuAeeOogVWJH=a}$3@JIdyvqv}^vYvK|PArcZJ7-T2_ zEpu7VjW51Io^7tlKOq*cLrcW3$$2o2v&wd6_2P zE-kpXYEoA>T#}Wasn*~}N2XM$UUL`W*`BpH2Q|vFg6>*qMH{zGs$$(1C_m-W zGpJfGrq7@$cTSdD?k1ORs*EmkxL2NGtYqFAXSV2_axa0+J|SghlH*v(DyKVeWca-1 zbY|-3O{25_qh@S&J#M~l`#5?!%i8xUm*JIqL|zCD$=LLMGuNS|z+RC5V~IF1y^p;9 z-y&HNRnLNzELXYyx00<*wGX~(3BIMdv4hdvc0N=Bmudk$Rf(hSb`31uR$6u1Mi_b# zZL>G0X_8B6u;O&JLDy}suA9EbJ;evuN@3Z_yo+%4nayFKq?jy}nr}^0k8BxRuRE#A zu;84zadwdH31enw3<{Ms8vrOYNDY_%qPXglt~nM>IYAT2EJ`nnv_-^r9Rf8qYd=qk zy`D%*k6*zJ zI(u8UKp6N6%*urdV3Xd0`1#$+flC@zULY7nN7YbgrbJB!&Y`cB8+MVBvbyPPMO*8C)U^$C5t5BVF{=_Yn z4P^xo(J+c{ar_8h=dkc0J5+!EjGbP1b5qtOI`pJ77?A}JyhK61obu6*I4&#^E+VTB zn~`ubgG4s0MVsDUC$$KZwSP(t2$MgV;x3gdPoiJ9Y%+}#PB=Y&=^J*=qDx_;hkcP zx@nnpPFr7)Cj}Z8?g9GeL@wY0qAF%7dngmZEvfW+pqp-ylSgD5C9VLvHvAXj@#xWU zTR)Aqh>%XNO|QbsRk^_#w+KLXqWjMgL~ixDi@Hh>4h2`EY9Nt}X?cb9j~o*Ag1OLy zm&09dBv2h{eBvH{&OIWZAK}k86tDc!&uslXl$b#408r(%uJ4=U=$*4!5*frtl;EAV9Ml{d}S&h?1Zk&ajpRLeuf;faZu_z&H2>BO1LW z&87}9VJgvC;H5M%DqxVFP!a|lXoq4hG6pGpGq<($b@T=b0PEk}DlsG5U#Tcx8X2KV zc{~&QXiK^6PMzXW(oG9JQ81w9Dt3w<6M?sz_-Y{fm19pI@;p|KDy>sO3Q`zJ3iCqGV(a=j#~ ze?Cw9?mavLRv~NQmvcOu&5BNLckae#c|_P6--ca_4H7 zp%{_iUNP+LakpqxP?AL(pOP^kY6~dBi!|Yt-jOB0$ZBYKCK*Vf{L=ykfx%TT8-#Ge zIbcwcGfFTZE+MO|){s1%py?~JE*~op^idFpC(I@MCJyY}%gcv3lSv2EKPFZ@Vkaj9 zTncA$G>haUi*x31!5soXLdY+od9=Ls4<0R#c{^YvcKlK21>MmoTdt%P_>koNiL;ZR zhGUQ(XaFJF1n}Ei$*-El1d#DIC;lM5JOA5Iv>aP12Bxf6OO2;P$&)i z0)6k{_aaP-NK0l-Q*UE;k9vO&1aSf>W~lJS09EX780_A~EOvM>IOxl0R*d;bVM{I* zU|J+5-0M)@2QVE-ick@s=1G%Wc|4mFJr$OKP)j@pLd<6ul13B0Oc0^Hy61UX`zm$q z#84K2VpuJYu~S{Em>g7URm`nw+kij$gNVHuyfO(&+B}nIWDbCCyf25@e=qzd&Whby zp*{ZdWBGE394m_D*bFXNs~*PB7ttK2la`12pl!?j{Caq((xmL_+v7{X^dkg+HVr>E zMswjSoS=>nwqZzyk6^P!MQR6x+;1`zt4K9BsA8QD=FgG-0AT>?%_Rl+F2vE$Vo420Z5@>wI83h$%wx;|}Ja_dddT%Pz~^W}Z@yT*R2u4fS?QM+w*$es#EDo`rALr{WD>K?4@ zwZ=~(s`%=vLv>Eb+2%DCWN>!egx`D>83YdC2E*X2y=I<}6G7$sO)3s9_pJ_?K>akQv*x|!o6!;(@P zbHpwya|hVDF4Dcb$dp)R-V~ibn>L_wJ2|@HkckbM5Byr`5mCdEO@RTB63H%8J%ig# z9~WOPAoK=#d^MZkz~$jOya$otpCG>e^VHjFa1D#@JGqrkLRVYc>S0R!VtJ0VK>7w= zBCQhXK1d=YHSvM_s&xD&5}XGLWPe6vXP9K%1LC?7pcj-Y0aZ!(Oceen$tBru5@ z=W$(3l$kB-xft4(A_0nEc1D`RB>PrtH^7Uixi2OX&M=Ymk0y;^xSsq(9?`(|6dA+G zoxkAXY9T-CwE!>|R(XuVDEb$4JU)Q6x@P0!{Y#3bumtQiz)<= zlImag9-%Vjf;zBYg!f)?TcXQy*{V{M1oP)*lqxf+|8NL^;=y80{3J@b5&q#p5%Aj$K24D_ZL@lr!s|0ez_z0+DP%u0x z%<13r(ZUv|srq5KT1j3Lw7l|g7``kgl?I{9)-#Wyu)WnlkU@z*%#CP%Kmv>|1^zea`=2bw57FJL3XKpQ!0)CokoC%8A zmSKra(gM|2a%nLfdz)i3PM;sUTvnX-?ExuX+lex0(1l)^`bJ-T|FR-aT0KmP;wxm zqb?kmoXMd)rrx7V*;yPycx5QN>K;%+KW!HzX2^-u=rc6e>mPytO4?PMekIGPE_f)N zvXKeE3yrRwfUUF0&y$)rRK94+@WS^ow#!jWqoJaDTgEKdBNRMfV=c!ATEGGcL_y*F zc9#rnz3%mErHQFU2jRc#2JbssW{0$BWY$=&L4gZx&zpPP2S(CIW>fy=NkYbMVWw`8 z67${G7ff+nNzHnQp?OMdYkGKRlC9|QDj}k2Nm=0Z-Y=$kZHi0YSqKZhiN@|G7*~7(~ewT zuZ#qhYP-jWXKKpm%j91{&6>^vYbkdi=+;1tYky^zYC|T z-i2gi#>$yYGt#UInn+sKyUVW5;xe366^}}8Dedig2Gx#frqydS--I(v>{P0A6s2>{ zJ2W$=UYA39+3cJfl}-6-vQJUtsVa;T8L49AR=(vx=DCseGi`3r$*k)Zoo$(EY+@aG z5z&5+Ei+1UT&(^a^C!F37D~DxwaOQ%>Xk-R;+QDYv1QQN-Z=cZUPeK#O_7D6WseB_ zxZ-jCmOI_FUv3yOlfWj+o5AD~N!G#fjoHBkpOBBLd zn+{$@c*M}e&)&*(1fy?%`#=Ubj+H#mwfJyNG__OhxBlD2P3}hJIdXI^3FB$*Smng- zUCNL)ExG6&ozL{qIA)F$@ZkC4{RAgMfy=5;)>!Wpjn9)wzp&98XlZzBUsA??UBU+L z(+lAwZ#hn3#!HezQ^*dw=v@s-?eiN)1j8JR#382fj`#~FQD>DZOoH!nm%3f}12*(( z;OTm}RL*a+QNQiABwDPJIp8QI$r zHOAKM+qWBnaoqqoq~qBda#OauH~1|BIZ0*(E*6q?jB6x-P2dph-v{eW+f`KX**L}} zZb`m`4yuv;#$gA`Dle6nh$|*)Dbyu zhK72v7q8m+fF96kanE{CP?T#x_1>tII$xP_zBAK!)zTK6UK*Qasy+6RuB9CXn|V5V zzLna^Uo$sayclto874Ygv>KZObYoVZ%1r1EQOhQ4Ehg3{?is|*wJk#DIl6ykSlZES zl5bc>i!W-U;9Y3rQ|MWIEK(gT_5Kms?hIe#2awt5C2y1CIGe?r9q~x5^1?s_Kiwl| z3a^II;)wg^4qY|r$YK%s{b3jC$lIX;eI0VpiH&# z&fK~cu>}WrCYmkx{!H`sfoCWH^kUeTs=DDu#-#&s*vd-njz~aZ{|q~KpCsd^j2>1O z!nLu4Kn>z7Z1-`lye(UE28G}6*}f&{oahJzmGN6bUvLU^U!E+r9b@dZ$&NMyKymJ> zvpt8?_u@>VeID%bw?{bpx7$CJtDbV)J6+Sj*r;vu1yn2Z1K--@@d3T?9xNUW{45r#*iQ8{{AHkJ85XEr}5vI z`mt_Oc{g8$A6ONBC45oXih zp_~!*62bSJg+P!$Cb~#rz@p_9f%lGiK{1ct%VfKsvTmQn_RUu+-1ytb16fSVg>%UI z7PQwUW+TcU&5YNdkz<`*WKlcvZm%CqZBab-`MNedSkbvKaG~H~`ubVvXUFG3)_G6j zzIt7nG%BW_Yj{`C6s~?bgU4=%0xEa7`j`3`9{ipiRb2X+Nn+q}@SpNO1YzHHOG$Yx z;@!a1+eYrMDQ@UM7kl&@(%kreUO8u~rvB{HAo`Wt$Hp#6d~05J>VmGj_4#xM0hz=a z0MczLanrhX-0W>++rDiyuBP#J25>|UwV4W5C>AT2hQv8h2A(RH9@+yf7euXy=x8*& zeVGV$FtB#k5<2oywT!#&1{fE#3#r|gYk{~>@NWf%ufbG{A*WD5C1rr@{vqj84cH_; zHZWbCK_Tlmr=)Jl=27^OZJ86(NzkE!fy`MLPPSdmnI$?Z60d|#;y=tlC%Shws=Ls< z|3bZh@#j`xopv2mX|6Ld9d`;bnY)j$^q)%l-#JgY?RQQMI>zkW5&p(SARhLK!<@a8f2b| zR@&dIf}2l*9ksgEWru+uvs?nmqKw-wCa?n`95=LZAQyoa3P0qKicDHAz_|u#^0X&! z*lYvUp{2{SFG;+H1E(pJ(d``ld zJjaO^GFPHD4B0}YFxX8X3IJcOC2K>W`1&fZZQ2eI2c^4KG2Nb;CJzUPrVPTVf+g20 z*mqYm=NkfeB3y`j06&8 zXLCLPN!f8iNldJ0u`q97rhEX(n8$cc+sgSZK65kiyIxyR9}q++mVe% z>|l$7U5W$Wf*EL2&?@l&1%TN?)Cn!kkOB`7f|VGltf&YrIgu8@w^9p;V@6m|p`j|e z05q@D9rw)xEH$R$738PdqN<&f#2vc~rNJ=~!&(*AOMJn*sY#B=4n_gFL?PY+5bnt^ z41=za3%Cj^Nk2Ase?OlGFw+Pk^nAJt!VaWCk4V6es-{2j!4%W1w##i!In? z7SX({JVI19y7u|kIq@Q!yAsIlDk`(Hr~I@z4*j5uJmv9S?FJDKAcHI!aPpI>qE=4b z>-uG_UBq!9v!V;TjZX08l7*LTh*pU_jqU1s0U9-*K$PtoC(9S=BDC2gcV_z}Yd9EK zwQaq}ZfcNzai+#SyEYip*bhhq?2!>pjvWz3qopi6gc}V)#v=^hTuNX z*=|r8yW^%i@y827AQF0ffetDc)}!eZyVeay`2lVQ{!c}hR&fRXlvm~@689xGw|&Pl z-f`Hh zpI`Ld1Vu|ix|797(Rfvce>i|r{}`va@I%}^&8QgkOvR+<7ZvufXFw}`{@Q$*E~0t` zeWX3>T8W?t=25hTR^-{F0u(GA>~xdSrWn{P!} zwS*u9S(^SXpwdqC?Wk)3*zvT>;SFq)o2ctkvkfy;Zej?nfh)pXh>Ip2okoK%NEcL;Y5`BPyZp76cLTbs(%6d?j5%Wfem(Nm{#~#h6nMoBW266 zfY}L(K8W^o(+fTcy&&rYv%1VK^Oe>s4nWxUbVb&@$n&{eTzFaI*JaaBOg72EIsg1{ z)mwY8oegc7nDqq`eqF%anSetgv-yF?st_td1=)A4^V$1|=Z8q5-IL5@^0Fe>08?AJ z6@ReYgpb2EW{9`@X|Gv-?hZUcAfF&iu?N%hNX;mow(|oGX20wZz6=M^9R1d>yZfJ< zTGXC7YZW=lg{34Bv^lC-!X6)bDJbKMO)}3zYZ8uU2Az|IixK>Ua>oFY1Yo&~xHMZ#`%cWS$Ucp^usieb&*HU03`W)N68(U~n)?}v%lKPxcX@Uekk>~R06Tj8m zw*+}I>C!KW=lpTeu-tMO8RokV($&DeP?yfDE#5kZa&}qAEJ7jcLyFx~(ve@>iv&*^ z;}&696`5^^Qf0Kk%jfJ;C6TtCeA`EEhW@1B9AE;lS3^CL?%gajPYzJe4iN z?5kU@I{D+&Ra2Hc5#1(VK#_G$ot`R-?D}^C#B7o@nO$$|7ymyKzr{=089f{T05HM- zvNvmJXK8EbV)|bqe~#w1)8;5@@2Rp)lBLW%2q|Yn78N=a?Ru=zB{@=#%uO>0+L0Ck z+Bzu7e2$CPGWgjO zvRcQy>tW1-X{k)dlBrd4&2mmnTBViGao|K2P~5fD;yi;Ib(UA!S|giY**!Z~uhUZ) zlc(JRSGiY(wW)fFdz%=m;H<6TC2L;1|nV?Gl#H=6RsY_9OXFbX|aNV)4Zz1^YwcdH^29$ z&UPPX#-8jMxtZCsiPMYm{mxIVp2g<{k8#x@<1#a8>?Q4}ziwbbdAdbPx~a8l89}np zor1nD&My_#RxL|yE{!Y|kb<8rQlb|cA!NE#u-wi1>00MxO`$TFL=LQ;M&>Z8LC<7C z;ddaJ+D@wqf-r&^u?<53Y@ zW#aB^=?#sZ-sv<}5LJbZhfR8@Co3qE$48Sm07oFuR;Emw)n_$>+nBq`-*Hwr_(?&2 zmNN0tR}hqrR8R0ahADme@9<;f0Q@rpA&d&A7RQqq{z;XS zl^}ETv>cuPDtQ!_CTwf{w6_$@=N~1*P|CDwC{Dtj%Est`!`OHQU6r~36-=p<%%@1a za^+k#zxveiE}}bi!K5B9s*;l;noVyIW(gKUBU_?k?ay@B$Nvu1ySR5r=VNwPqJv?8 zQH@Rt_uOc>uZA&!T6I5^B7Ep=MA~-=0npM2Ca0m%+$@sLuf0S$aes+Go}9D|>((5- z-T{`V727Aiw-SSZhWWd%f{HfklYR7p(V)dlhhLsOsii|6C;o}_S96NTJTp+%uIwNr zbN3TS7BFjl7Asd!s*bvrXE@Z{6X*5fQyGf-jmpeJT4;Fcp15N($>CDbOmbMkFVs?; z*>w(wTs0Oh{Q0OBzuf-|hq}%}>cwfgBeOhaky=N$>l>I9_G8QCx zJh3~~nFo8vuY1q-5Cen}lcr6RnNaf*3Ao?8Ar)aOc0Rl>$+D;CbH1u%xMlirr5N*_ZO(bqDKSZjofmlppSkA`1<;i_?_lm zC7=gnHUIY*E8n+PNN`W|J8!emT^t{k<@}TJ z)dR$&FlOxox;XYAp`6GX-kv~;m8)W8h=WDv-w0Tdx}MhwYTwYYjBatn?u1nl>73%n zfI$>HuW7;}Fkl|0M)HgKv^?<7o~l#k+s_js>OE^+N#x7Lt-r?&cd|>|Wu~Vt#)zE% zEV(y5($^_zc1|ZyuE5A-MV$Tx3@;cL8r5wmDUPBpp8`M28#z=zH>qHeifl=!cT!)k zO5gY8t`+_PLph+ue1Xpo?;ZfW;&QVoC9K&pia+XUx(Va*SFdEv2f1m8(ReI}LS2q{ zNhFp%mOrCs0+V9$P!p(@GT#rem1?P}Q@7RywlJqrxBHoPf&&8tK}P{TN37=0 z8It3}6fN43mH!(VwvB9?lvA{y=leTr>&)SWbaPCAuEVvRp$28GHwYren z>qziP@X+3lx_;lT_TD*FgNR+sSmjx6o?2uP=U^CJ`wUc`C#@q}^OQ9@2Bf+0Q+olj z;D7t7KvBsoDE$ykKS%JUj5C3=CmZ6@q&rXMwS()A?wpN z`F~1q7b&k{T89lsVMMr;lu2OBEr!vQ*!vXhAzN`{_|6>S!s9Y9PfL6M`N=I|vztXE zX`A>4t8>Ns2Ys*D;V8^B6nv*M5Fq1l*i?J!QFZTGdVhO50fi#U^fmm zoHA3|(xtyy%r4#|S&>Qz0*P;?R(MC%v1z3Qz2di$%%VH=Vm zg-|aHDb;7QsjaA|pdNfsVjWNUsS2jZ5BQSPKuwTold@m;CM=L-k!8|mK@pn|2_Ak# zqM~AwW0krEn}!1f35-fAR=QH)5~u1E4IZZjQ_#6+BC_6M8a`-TQ&`u{nc~NCgp1{= zP?CkRO>;n^DW$b6+szu1JD|XJIsXXPMSgD3ov37j4m?&?u6~Oo9Rvtxu442YfL}A* zvTb#^gmXs{b3f}~e+gMCuewEf5H<>?HRH5>RVf7(@irfRbgZ|23~4Csy;#H--HXie$G z&ZnLQtv^hi5t__wRIFtx$?o5r`1>;K-Ba4p!(F(DLYjU#71@c! z8MvBMw@IvPz6Lx|kKN)vuGEn65GNLINSuX&6< z;WGy#vx~Sc|>K|=ZYez{C%hUMd@O^^utN$}brY)*a3%Te3x0}fww#ET(=lNK@-T2`F zRrmFRxyy;0xs-nXGPoE4o0Yh#18h(rN%QoTC7|3 zb4*|FC*#CS*t5DZ{JY(a7~%;m3KoFQWAC^bDs>^gCvac0^DP(X=-!VsnfV)}|Iyxl zifil%ftfW%JIo-yyV!<0FyoOkQ6#dH8gX;KD+(U+K``Ik-^LBJ;CJi;{;tkKdy0cf2$P34g^oYaO3~%+&pW=u^9SMioXh4W>xvwj>$cqZ${De< z4j}D8Kw-Wo8EM%e{I-IUR9WhZF&)H&T<0e^J zqv=WQiTIHB7(Uj{IUE=>a;pc<%>GG(##oFV4uA`7g;0g_$&$G44o?EBBR_cCnAUVg ztLpbU)+u^BbIQlz#jBbyt7sr~6YsYp=cbT0Sf(wfV8#*omI} zY$&@?E(s@xMQ64qLYdHuP-8i-u6&i_>}s@?rf=CHgEqZ#i`-vf8^j>>&uHGT8_`=s zqQPK?naT*-qplPGr?@w?MzsbF90-W*#}b9&|1Yo4$;80Ooc1Tp+r-Goz|i`?D@bir zbz;}q5WH4u)d>XXc>mF@3F&BqU-0@^aP&i6*_EbgI%34kEA^lB_B)G9(2^IHw;ON}X zy57gR66#sOn~nv@6rBzaAFViN)8JT34#B(RQnHq4fN=^mTga@-#e9&7);TuoB}$H# z)!`#8;ggmsqxQZ92CJcv!!UFH$-aVx370h&lMNjd*C5DK)~m|p%<3HE_-M>e32k$A z4jE{+Wvo!yt90#%ekmK6U4(R#?j#pFgx=HHG+zn`QfJ1>(B##ufn7cUc_O?CfD)Q( zs5rKFdigqj-pyoAs$4p?c52UGy4A~dyZXoLzQP60C}TsYFbnS&lo72o{;7cDT&SMs zZrUAM*`fLLns%6e^M6!@Kiz~adbGAWV1j-40J1D9h@V)l>bi4FUf7bhYdZHZn@h;D zP448klB+c|rq>SAwFm-zob8BK`*a~NqVyM#cHJ2`R*~@dO z0^>19F;jtOFBQ1F!Z|SEVC2Nz3>;i@b%k&RSENM6D@0T7vBcCnMv5SjzZ0Z{wH#Bd zYo-~R61fJl`>+;UErC0(GJi8MQQ>h;gum|o*UVDGonSJ0^4s$&3Aop|sgrwQrBPB2>S#ZADpeHX2TJ|@?nlH3N zdG+PckIk8@j%=-%0zLRL@*BqBtlVj{IJ~vj8do1eeP+(S!VrwR{(h_}cUY4m0-B6h z&ad6IT3eY4H$d+vL9M?Yinb8{2*;InO?tnofT=n}xOX7~yj$!SU#XeKuycGDtltz` zj_5=?CTVN`88AqU$E^}&(I`xC9-f(s)t=w`mpy>%Kq@GaX=iz8v$*GzQhU%N*jx|r zLtfs%UV(vtBS+FGZ-+9$HJ#lP#2f4GC=6_%4HGaemoWB5c9%6tDeScq14iZ<|6(wY zm=j<6ykCJfO<(GZ5DGF-U{8HOg3UU#t;|lP6wYD%_(Bq&A#{O0ex8ctczYrzSc+Nr z``T|{T5&B+n_sSBIW>3oIWwPWv9dsYi%r5)t4zvsZ(;Jr^Odr<9l?A24oupP<{#ps zvn7XaKouKq50dDdMyh2_^$dkyQIgP{5ZBGzh$?-+`jTKOh(EP0N?a@?nAt`eM-2R3 zF~e6~qt_Sf39*sw4A7c1PCq9IQ$xU|d#D(d6Tj6ahhq^*SU~8ft7m1C9X)LAw6kwG zmp9~uopj}1$aV2|Geilj-}M7MVi~$4c$o`qyRYfx#70(=dOOHx#{z6sw8FE)qm2Z< zrcOu>nO7Oq$C=HraMSfe5`>lGP_~Qhjg(*g{j7&z0KdAv=60%u&{_KBZzfdmMw3YB ziA|Qvn*;gE_zP$w3_fzZCky+2BPI9SMN}IXk)^P*P5o*ktij^9K(+gX_p9zbJvkh) znu7C~v*O2v=eBXsCYWW_-7(EIUG zJ+ytvs{Ex7i(8S=>WcYE>&JK(gE0f-NQChF6+M@jKu#{&|lBXIb0XB#*7 z{%daj=O_Dfz|6NBb3u|jfdKG0TAW*dE!1Qvm!+H? zu~QrLYAd}8YC9*Eih9De=BTIXN#$dmrBpAys?M58j==ht-PCp#K^q(G$|jv^l?+wy zb7z}<+nR2O!o4*JRJP`tB^Mjb4;y9tC^atYfCyPy4=puIE3^tHnPbg`VZY?Z@tx48 zIYU(UJ&=?^diZS@9UCc`fqv~zea(FXPkGYkI2zX`I4dQC`3TXIvWM&j6?y8IAIr;5 z)itm*WE;#Q^0b*oVA=KyCn)Tm+@7?`6)t_~m5K?rny&MotV|qFMw_3n!6@YOY47Ux z;I^Y`D*AD3`Y~QS{3sGYk+prER)1{9q8)~|ef4ei>8bsrRr*h@OvjaLGrQfkeT~Jw zy5A!#=pK8$Cc%-!=ctO>~8M>BRF3B-RLK4On$c z_&UM_-*bi|32aTWrJ2W$HRralz32M#Y9q7QMkW|z$)n}s{Qks6#D+aAquknQ>+G#_ zj`|ZOWa@4&?SA9DS^%qtX7hEt6~fA)cqiqya{-7$^{>rRC`BR=_b5s9w$>!>L|eNK zwjBc?+fSyEyQvBoi2kSh(iFyWLx0BV^_sfJMMrM1_+g0QN1qjXm8D>rEo< z_~#atiOwTh9n9lxImxOOGVk_C%dShGrmUeDu!~?~j}&mkBTc&tqXROKCyDWtvh;NDhMlsO^^cGIo8uWNryF06V=1P z=|9E3B0e$kob^i8CSF<3wnhxBxrZ0jv|R?Yv5{F1zy;|{z{k~H6JRe}f%jtFD~;d9 zL;~%8aofGY)VVp|{uYs9H!Wp~SWhyy?~`t#D>3s=l86A3SYy=r#l$KW0d@bHhG#xh zZ#TihD*9nAM4v{UVhj)Oul1AoNE6lS;0H)lcj0I?#($gctLvwYk=ZK(pd=b$Hm>W3pDI)O{kxHtHI2i;f72vWQ}7WN*TBv{9lJ zgvn+Vc9$(%MU+8*U?tpH)p8j*vsef%zGR`}Rw2mYeKcCBy3&vX?D!D9^uXQWh|~t= z{)I`Dl-i}TY8M532CL>KH`%tE?U(Xf@>dzjTN)J@z_L-^E8WT>b|#J%k`z+CA;BM! z;OB0^lW`1Ini(L|1Ldr297}I<=r2z#lD3(Z@Hq?Yp>Ov8H2_$Gpl23~M)ltYMO*2d zj7}!*oaR}6!tAuT;KkS~$?!yj8fB^V!a*nBme#o$z?*);Mg+vFiVGB(FJo*y+K`fN z7B2UJ!d#FP+S!n-QLgym2%{1#sT5y1ZI(U|gO~~f(*E+L@S5X>n_OKskd^VV!=%J{8o8Fj<5jRib=ijP?U(CJG&T*M5oVDs2Cr( z#3~yYICOZ0g*o@Abp6N0_Go#x{+)m>{ycK(EraVB=rV z%Q3~l4lRMG^H(3KPVrw+t=7PAcE2*2vaHr)MAz}svEqa=3Pt&&(kPV^d0cSFG^+57 z-l^j%*jjlpg*r-4uleW~U{WE7BS4(SCG-Qg&Z7(w_R(+}6D6o>)4C+D)R7#qyC#=f z?l^-mb7TSw8|o{GXNC5pBdtfRE6!*3+ixUpNpA$~B#BSAyW`Y0R19R_!#N89#TwT? zn?;S}oCNfBW=ZJ$%7wz~>2(YCL$ZZp?9PBqfO3L5a)SaD!x``zG-7R0C)B4+IrQe~ojU($>p1P0RtT zh`4i5AB{7m^twJ*_JKLaPLVd)0xac*BGgPyv1QlJ+o&6e3^Z6}5BrgM#`b}~8q>Pn zT`x)+e||S<3;Aw1EUlmcp_uty2`dC#>DGu3*Ob`6Rv>;&W<#?n+Ja|l+Fms0v&=-6KLVRMU zSLcqj>zJy1OQi?L7M83U)%8!Vo^9rx)flYvPCf>uds&)CV<-&OH10VwxF$Y6)ltM= zsa?8xP$9cqF=(v?DPOEKkk0T~r+6$h*{4YZYn* z*7o+e2R>md=*X)^C&7NYjZT4$OU16ijYeFQivUFzj@t2jvauT{XhD{!q~ucGn%lJhnDeVsSg)`xiFu4;H!>oL z);td;!nzp|)7adQKz1-74@G9O$znEbG4ECCUqY#*7-}e|2W8-7?^w2(8EQWB;_9+0 zq9&g=4|Wo0Q@h@3NY0IBCwuv2x`+Nv zzlvCWshrnI2Tf^CX}@gLz@(4UB7?!7D&u$p~A)zD8#ZnXJVG^d#i zF(68@;rYZA@D4*3XCh&4I!}}#)%jZ8>0Dd@zZ=p6mD5=ZWiFM-|f+ckY;J2D1{oTwYVK6G-$M znkcv~O;RkdSAbQUaN(#BwqBqXHI4qHM7!DEt0foSi=t572FR`h0$(fb_G~_1hQq*X zZ7PrduEu7{-P=t&xQa7}cB+sV9K~%$`J77oc4q!Q+A8rw?5CEsBw3dHelSfx2+s4! z^J@w~+1=f~o~!L#V`B33!nTgcdXZB4uuq05r9?Xm`aH`vUt-15a(n1>Y%F@0vYCcT zR|ef)L-mf}Pnqtb8cvh2a;caZN-gYM@~xAhdF zM@+{gv{(=;>7YMP_CWV#B{ZwNoxW`oE%5kH=&F>_fsLs&eK6#~P9Evx&rq(WL|jM+ zN}+zMA)XOs^KB(r8u-!|GTkTXm-PHh&b=ZRM(|fqj^wPFIKZWIuVD1sc>Pj}dyFPH zc8KSjUtTV2m8Bg+gY$}T2tZ}@G5A~^MY=1dd2wxTCm~8Xu-QZ1+nJ?~PNV15f>JtW z1}VQxh=2L`&+yWZ0lz-O|Dn{+) zt4>+vE4nHc0<&ysTF(00Se&~pNRHl$r@=NKp`r{?9|n?u=m^t^(+>6c%WE2t(D&jEj#o_5NtR}nN3!)KL&@{6mr5ttc4VOY`vn( zs!v((vs&jyBRZK8;T`RiR4TQ>qlZiD7gpc=O>sm%Mbtge5&SYE(LKB>3UM7dYj(k^ zOZbt)-ThxC3@`LY4UOcuxUdq~Y3338y7*}eLMKO`oDfG`tNM2l81NaWd_Y+cN$R-#W58KF37l|`#~B`cMX@1o;LP;eJZAv~kX zj9ccISyZL!H#*@SZ>l7+Xd6AnH_IAD_aVhcW9c*6P*sFEl$Zr3DBfS4#=l}U{5M8~ z4dJzBQi8)(xYHDQZ z=w$i!VkNIUq$Q+PQouLkXb=)@zzv*Mr|%zIm^VbiF!mez1qiq^p0Yg8 zo1t);Gi?^=@OwgBn}B4oa36e*CZI8Zn3Qy9f_+$mta!+fJx`&lr89`Q8O;W$W4p0Z=e}Ar4{7mR)TF_t zYdJLnd?V670DnE;O5~CIM@4dptw7b2U%LIJLG^_%$8I(W^ja~=&ySh1imXLM>ZIS<1*3kT5{OuoVHKz+xYH~J1G~<#ujRurr)Yo^~X1;ua(gaNCX0P*S zK*9*Qj&C`f-ewB)`z6$**hh(cmcL&6gOb^TwXoTAuqGAvl*|-YMHg^)2NQ-3tIz80 zvL33O?^;H8yrc1u(BH;JcZfYzg3de7hmI}EX}u|K-@#Je)hzjR(ObVpi??@r z$@Z*yh}Sel+)cq))6AHq*tJa@?Cl^Kbz%Z z9GW?{h1%>&Q0r7F->uO?ct`x?4%VAcn&0TrL6TOUkV0WMC6grOs6-&GEOWpCv5E@D z&umEtZu0sV^hGm9R0GjOmmlhT2|pH1WNZ?mhB(oCNpzKEyj)zxJ((QALJm1`5w^6h zbMf#)0SU72AO1`xR^z0SrG61U-_O2f1OmV4!|2eF^Xr~X*K9(}DP9VJyTgW(tFBfG z8yiF@d7~utC3^3S0A}B_Hki$1K~Uf1$qDM^3>bEiXRNO|CCrrLLboh+Q8=nk8cQ zgV}`uTa{zy@(k0-`kNArF^51unPbb%1>@vn_&JBGwWX{WxhYfDY^6|wmI}-l^U$gT z_R51(%fdI*Q~18hh{+616LvS)D{dW@gn>qwvDuu~x$3JVvsCN&iV_80_(Yr}IO3xm zOBKF01O#t0=f`^ZSXSbC)9h{4Z=9@D?m>!)0I3vDRi6R~ySt_*$A0hXHMtsFx_93C zmga?1Dh~72$I*Z-CdF!MG44w%W;ZID%F?Zq=??JCbW`&Vbg+b~V( zBHdze44vqN2^DY}`6KS7a9ohN-oG_KhFy568hF#za0&VATk5~^^4mB1cg`P{|5(`1 zOA))fhtfcIPt6v3T%FUrPh?;~VSCdaT1UA%AQ5x+UBo<=JoOQi=;M8qqmGx9@eN9J zv4Ypg>DWi%$LwUt$l!+#TNUMAv3fZLeA9HWZw9A^V2n8lT+DDZFyczBu7iZ@nyxap zkFh*R|JuUhaOHYS=OcbUhFNvQ`)hUtB-LuAfg0(rkn<_bjQc ziHV$ha~u_}`_|8hXpZsOiH-wP<#Q+weHzmI2L^_X{p1z9DPVA1?T3Mwk2y3=Y@Ay4 zZJUMW0*Q?$^R3w{ow#Mma=`(|?rFES!iGXBLYRfw}f zq|0NrYE1@2={MAXRDg@4b7)u2l_Jhy%f;y_(V`q^3WndU`qiHwdl7P(1zq%;&yIf+ z6rIkLUbh1JfzTpX|4%8++Xq^0aJMfIr4<3y#9n)2Ya{JP8JZYeoT)rql3<>UIT8!0 zjZr2pK@{CnAZkYRpnAx?^olriD-37qCRSN9s46w>pvthSQZb1(aJOSC6&I2)(I#OP zFrqyW#fc(#MVeAxqFWh8hd?$O8r~}GF(GXks0)+2HQPJMC%Bd|j|U(}lzSv}750I~ zI%(8H*5?8atgLp#{bmj>SnOWeBT|Nq>7(4CKdX zQF+dX_4kWZnk%T3GVnAsEb4UcSn#qnqypfu?~YVy)B-3kFr6Z3FHpk*SXy;J%dXwEpF zwp5$cK4ttdjZq)QZB~wm}i# z{Sc#vZ2oko;UC^(+@(i+SN}3aA=To7a&tTAN`=rHQXoJt(U?D^y6w3VwuxJ{j4Ow( zpz;R>w>e0b&kS0RVYdgX&MAS8qE3yR;CF!89aLQ)r#B*}KjCJh^~^+*Y6A!hw4+Qj zS_xxk^{zPMZFiFcOVmSthC4F;_QwH5E|4MVqpNmrNW>v3Tmvyk5t1Xr@?a6tSSXxD zM*!`Yt)Mjovcc=EZ7otBgIejAq6+zU7XM`LpS8PynRsrM2a-2`Ia_jCrKX}UWx+5a zWO7$Db5-R?lG6#v4zWQht-IU$EDYr3Kxzwn7H#{Xmp4`#6x80i_2HE>Yx_VeZPCIqUwB z?sRCOujCPd9Rn=&c_AJQ^fX{2!M^ZXlM~%gcZpsU5)gY=ngj|>P{iamsCnj)ZCbi0 z4gty|WWwb2>Nyqt1S0_n!o3-g2WSc{W0J{)zFTl_WjR3(;I%;3B((5MYmu0bv^`gH z@OTNO<-sQsYQ8Dk(!MB%U7GaC{ym26Y|f@CE^QO`d23V`w%{4Di08Rrq62x7DIZ$2UmbDHOVQi!*Noepbd&I)(30vi^O zzhtFL?ZaA@J-Q@u_2Sg=gFk!fM91z?-`+@bp}I_k(GtJRSy#zgSxgh$i{a2lP$_u| ztfHy;V5%ZqnL8GaaQ=PbRo}knS>*Wv&r_H3qrEipSA~ui?un1R-o^K4YHA%59`X3z zfzxuxEyg>22Z9Rv>Ypa%Ls~rV?GZ?Jt6HHnd8f+cC1k2>5dqQwJqyW{oIa%KOj;c= zRA*g3`;+J^4+pEwzi?)S8ggZST-TI#k_oZ>{r8;g4#b+Ay?N>#bW^6)IG(`9%966> z50@ZB=WQ=&bgx|XoaQQP7K^wRj-s{}w1UH`l~6ydu1C+gt7+cxqejs2rFnE~?DGJ^uQeO_H-vwYv49-a>@zrZ40iZh|{=!&WwJ*?u!AjLZq6}!(qvrX-4b)HF( zv^0Q#Js3s)rQSkq5cOQHbu5DkLh|2-4cW%`hn-v~OBSn;>LWyALhAP z9_3aIbHVR26HJ^VnS-1VLQZ*U$9*iu4a@nlE<+nm$0DJ!rOnyAV|og~anl($k5#Kw zUG>=SXkqK3Q@3}Xg^1tnk-U)BK;Ytel=oWnzD1(O=hP;;&P55P(a`j^;PbxVoHEiB5VmZS)8BqH(XfU$V=*w^(Xh1EQX zL;OW`EGv;AL@A~W|56BH@Zc`!c^ncmX23vKJN`}Ym9*i~nVYp*#15~#DVc9Nv%#5r zInASRVWs-&dp~~IS)7q|6gikR3p{`_+jOsw;^-A^h3M+)(`4#q@n(SBjIa6-4lD%`TA z;;Sc;EoIW8)DEH+3~?>K;#?1QMtF258^*zPdduq>7cRJt6+Lkx^U((r$FP+^5dauc z2?g1-#_4(_5XXl@_;y`caNhUOnrp*A>DRx5N&}-s>JP<<-PBAbv%THwgN6rUyI=oj ze{BIX3+*%)8!iFNVluHsmVi`a-WWHJcnY@^V=_R|G;Vk(qaqx=8XyjR&1N9muqGvz zv*_b*35m^!Y$^q*A8$=x#$*qRQNmo zp?+n|(J>z#vV_LY8Bd7Z4o|NBet2^K+BfE8-tMZ5+eoX1!p# z6SoMJUOB5J25|C4P;a9q$F4D1rNE?u^}H*I5LLCDyR}M-Ol9leO1zVPU}&G;NQAeH zJH!{UdLTiVfNNv1WD)S9-$o$2rJ!4BcRC|JUlntxQc1rOhrt%ZOoEU&=1Y$)5Xzx1 z5XD8$*&9w70bOX_oOI3r8cLX#eAm+AJJe4{flzQqvN%cfPp(|ol})q2+~8k+|F~%g zO!{heqyiZS5AR+%e!QdVzD88lMCTB=3Pcx0bQOwF?>mi1zJA4fp-EL!8%@rVGn0x1Sh`bO;(5m()Kd0j<;a|t zMYz3|?r_O@TuP@&wq^UC(1hnxI^52KNV8OrwTRny<0-}OHGv`;X=*xBb;Pb#Z!@s< z07`WJYEE;ySPhS5JO}yoP-V^6whwf}e#* zqFNf{FEuSNGHwZTc^qf@ZYVp(J@3qM;5y~INsTw9&U&xozV*;pN5Fcqnjf4fR22c_ zW`2uXf7LrlCx5X`On);q_BGeNLOb^eBY3>Y^d;kf_Z<;14336^qiLYUT;>kr3IOfB zeCTjT;Wc@h>KmquXfC&Oe-m7@65++9fP8e~!>2H6_6h+{qz{s@vhwH2^e0sL$$aui!e+t-BKF9#MAM3~uXW)Cp?Mg6~5FEJ!v^hu#I%cK7Q zKRZN5UxL{=-V+0X5+j_qY+TU`14&=`4t=UrEFf{eivxryup0^iSCY=ox842T2zoCf zxfL<}?kj=Vt*1t~kxlw{nQpbDcNUm7haboUJG7A}#5XkRva_9r-slp{FHMV$xarHY zwSf9W27m0cp%FY)>m3i=%V0dk3 zKy6OGW1vU!36{Q7yGnW_hjbN$R(coVwgWgm6myWE35DTQ8%L3}nzPJ*@J_8>pSg~7{i#8a?6=&&cLQxeASpC^7wfoAx_pG6raj_6f@hktPT>S5Gggi4 zjhFW3paOnVr`BVe93S7SK%B){83hU*avdyYZ=YTZ=n34>x*%>#XK=w|Y{7YyDLDW| z#NXs&*MB0~tVie3aB!45ud9*fdKF)lbj0rFowH|5_53jW9eJwzPAe*b3T}^SEoN7L z#0gtQLQCJK6o3{rzoclI!H>5$2GT-9sqyye9kuZj8cTZcZl!p{&}?T1WN@SIWN)skaPf5Kzhs*KO90uE$wkxhL(=-9 z{>MEcCwF^0GY12EbNBy-E{XmDUF)O&1-e>yEHw}hQwL8~`cR#{oD+y-1O8da<3O8> z&<#b4({*$-R&}79lz#aY^xXJJ zx0fY9lWl92JWn^aomyVHj}X5Vy7V1Xl>Ay^Q=T$^AYbRMkg05t%v3=gRco$=(X@n4 zE-Ajtcv}XesxG`|w>xo}-QiBobYU%AA*HqXTby?dqB6cqQ`wuvhXpmnM|(|zw+$n1tUi_A%5f-F*~$K7YN?)yzT}m4j<#v( z`MAtA46=k#sLGe)l!?F!Uf)So*InzTz3H(ro1<21KCwDH!LnohjL^lrOqy7&X1D)s zi)~&y{F1lqA={@(VcjCX*l+M7q(r6)cKn0ZGii1H+LJt79y3hN;44XPcK4qC@db~b zF$Le#uDpP5Z_JAG>z*tzR$k={?qM*IjZAq_eZ-}yj}qTB5h{B@WB7W^&U+Sai%?$P z+&fS8ynjZlkp7`>&qt3#&=9E(`DRi~+rFqLs@wQ3@$16pDd%tK6;Dx&Sr4Bh#~F+< z_ftu(Vzt`rgq9bvRyX#OwpE%IMN4sPZRz4k9s&rd7U@{`ti;BPVXD+ejqYvc>ZwKu zk7UN1NwJE5RXnK5pPu&`pD4J})rHo3R9y!;L;OAcQ18O$=0rE{?w;I8A1wAWW(OYS zVN~(S#MMM{Ir9w*wX>{+9@qSY$A&HyCBr|W*D~FrF;-(dvgpW)mfn6)mKK)C&Ei$m z)n3;R=7V^82TQ*#C#3!yimN08E}5RhfYHZvvFNd!Q*ERXD>!+%0}MU+AO`3aqTtd8-DL`0Gl}^AxUrtqsl%Hp)wl7T|5H<7q$&bw$1JK#7 zu{R<7>G!;vnjt9a_@1g-suPTvyLllEKgKJtDC;hEPZMSeq63s7x~NAQ6l9ibBvy1I z`NBV7a5*G&H9IO2?ZlVVEm0%uiA6EBffofyK`Mu+A11cH1rwp@x&Nx+FsDoZed&fU z{1&WE7W&+#?>QH;=r_KT*K)E|e1Q26COP@TdTgXY@uUMnTo(T54&NEwFnWCRT&F+`Gp zq{;^z7&7h7+g=+4AiT)mUJ5WGMES|1q&OQn6Qg|GHJJ9P%&Z?7VF& zh+#uz$}Lb|fRkuNM_wzU+pYCn;JZ`X@$jgK>0hG2CX{=U{AC#TaXt zaf2sGx!hFya38U3W21ALd4NTjK#*;5Is>s<7gdi9Qe?B2fiN9Pd9arY;2Cj{83_B( z`q}Ya$6qh-$1CJrQLUfDl4cP!u;_+}dilplbb&m!M`Om*p4N~Qz^8b!sZE_9prr=va4+29nE(d`53l zw+t{>hd(edXzif4h@88?)JvC8Il_I}SqMc2AASg()WLWBfgGPRe3@6pd?QflK}E^a z+L=uy`0gG3{=Rr>giby_PL02z9wsp5&&urh-wT;8IY?d@uQ}5>S>uBTP-i(kvT#Dv zxX@r?>CA@|nSPZD%ICHNy!*~#?3OD|hsEP5&%{z^D`1WYTti{T&K1G>Wo3%2qA8)l zR3RGkFVM|eu=8M;pN0&Akh`gw6?QEc@S*}c;QIrrw}~})7XliI6F5Yq7vk@A0c1XD zOfZ$fEq=kv6^VoqF_`?k|8PxZd!Yz~!@~71*In5=i;oR)t5!CgbRP%>qUL~X6leu4 zOU!c!*fUNcg|2KD4>*xVBTQ~QP0e^h+T((D(?TzSyC>ef$@ z{sE-LJUjO|tAOU0Q+BzX`<-EA@dB%^^#z4-bCgN(va6$O@qiYhHOCL;pQaKXAxRH7 zp>1`VemBOAGwY6nw0OL6lHFJT#@wd|OV=cnt4?$rw<={zY#h4J0xIax2Z9S- z(+LhJKvl_ndlZ}3Im~O5~ue6+eIyMf-@UKZ> z$hS!({Bp>UR;gz_Wh{B_KhZ?e76|S>ALg^J8&L}L{yraIbQ=@{ytOCK1ct~fQW|JQ z98n@Y&;I0$6ON5?$c^%0b0^i7tq#i+s1Lk1Az+wkqzzFGT>IEG@*}5=QwuN${OleZ z{K?#GqqN|!ayhpr;j6V*Fxgj#K)z*FFQ@+8y-qvk3!erwO?#Rl;no5=3!5=i z*g3~}RvmQQbxUb1g>x`nO-$zGKB&iTSav@xxi6V|A2yytuy9XC=~9LE3}7%$zCb*mMy3KLwn;e9R2#HVJR3Zl@E#Uf?pG|u7K&+PDpDUpmwCU<#KIt z=4_Cg)I?Zn^09Fz>&NN~iQhCW-mFtpHuTi3Jff)1;!JW^*6c=cvdk;3Hia!4=|G1h z0WyNNN|c(;?(rt{5};kP+tiyoGj?Q79Ey1Jj7AEDe%9v+406%Dr! zD3&Gho$zrba+0uiRTe2pbYBNM)!Lr+drY^#Sgf^+PTC8&`sR$-V^tGbBi%%U8>W@Y zZsyNl`cQQcaD5jt+myO-TDEArDy&dt1Y!8(Zqqm)+}QYGH5atCo}K0^(L2 zL^v05yn!v43e4DNNLlS7cT7 zFm>%qnR(9 za%8$9Hp!Hn#73Q{P~bQCnpU0sv2!goH+z=TY=-YycG==nvWHD=x*On0r5oo&mf?AA z?Md$#B08Y}vBvGQ&++}YE*k}mVay4ltqPldf{Nw!^0kM{FrU_5DM6bo$R&}yjfySd zjV(*yoYND^{+DS8+V0sf4sC0RyCC5yl;e0tIHk?SO~~244Eh=b+Tv1+1l?otr9JdC zc=j;c>h7J>auYn}*#D0Lrxw!(ihw)L7}YHB&1bIfCpJnOux_BGR<(cx98D9hA9s_S zB{CTPI?D{5h&|J~JHzjW&*ADZZ>ZI_%h|shAMtukH_YScKT*{(LZ8|vDTr=@)zG_8 zyisU=N)zhYQQ}^tQ{MP_8XPd@x)?TnM^Vlhly=H7<0xB`&YatmtyIyXrt*x!N~NY} ztETK!vU1l37&cQZt4$YmEUi1VB;5o`EA1>C^#lypRoRt>L;f^Lg2o=g+W|k8CVz3d zI{LLGgs5j{u{v{h|Lw74711xE4l?G^B zPjNKu^>xUs)MLVS`}8#HtRo(MNcT~-dJKbZ1RBRh8l~{hWMQsy7o`$SDvjid7e=+p z)cGQvS?EMPG>%I|vvcPgqqAy62)_ZtrBbVX7e8)if@Fq5jkx8$ZVNe%F6}Sqx}k^| zu7dJa5Is*Z6l767Mjiw5X2qyWHR`m3D?U+>>Fv56G^U}H&L9iNzxt$G7L_10>nitF zD@yAj775i1+0u0rSok#-nmG)}% z65(3#Joq@}~ z5PTJL?&p8W*KOnQq`P!2%CiGDd1N-d1h+Hh^L=X}Ak3%aus+IU{Z+TKmZ%NxS(SA}pXb9LPRa_Z{zaS%&*&j!=yyo_T z5lq_`zSdqxwiU0H=Q#L@IHW+V#!WK*An|>IC6vMJpCQgkC2$dq>F5qn>U$zEHR`Wg z2wz<3ovTa%A1wmkRFdg$yYOc__Q3}^gDLpzOh&w1H|!MYXpR;KT82%SuG3?;IHM1M zuwT1!{7ACJobePiYCluYQ8V;M=Ha$EM~AYqdsizK4kO|5=RYiIVFa?En|D3>5lbd+ zccY<$$nB2yLlfX_CvLZ>`R;IVIyvTs5pFrlqoJTm{JA`gwIKS`0C&-1R*nh0T&`5Ce^dMuEewGt8e74bd^@Bx>*pPU*>YdjVqac0?{Aefi=g|6&se+ce zLy2m&`o(bwb-E_VZFZ!3FKit@E{247ydES`F=`?wW1$*ZTGwDnJv;Pu-0Dl1JeSP1 z-;W&=^6i3T!#kp0m|4cF(fgF+hsMb7afgwdk31-jPjeM8x(qGn(EU@6B~7Pm=?UHl zNRpXcawG(kC{%YKEuU-(o~6Nt2Z4?~$%@8BeJ*Q~z#^}P;sYeJhoQe_@c9~Nh!>eJ zS?lp_dtU6n+hGu2lMXjlyEac#*H7I5WwTAy_d8err@4jHZ*h~WpRQ@;4^H_HL5Y!_ zwVea4!OzgN(a-R-gMp*df5YMhs~gy1vm<@}v`*{dRTYbyj7QppL-z={Eo@jMKquPr zAfeONiW{q3Qawr3>g~G+yxZ~ZTlN0wIoOHUkZ{}3;~QF}GUH5ly5E->wJ!$$Kb4(j zSd`lq$A>N{=?3XWq@|=wLL^jbgrPg6B?Y9VQ$R|(LsD8gB?akD8M^Lxy!RgP$a!Es z@yv(yTWjsTXK&WK-v8zT_-F3z>KgLg}Sc1B4u4Rit{Fcx{tI|?>&k|T61-H> zJq5ldV8;>Ruta2|DQ%jXc$~eq&Y%*zVCLYi(pK;M1uzu_ZB{lX<@={HSI3_6)aZU( z{Rc`iQw|s+5sMWr+gZ=?45nHRODE6Yp=;r5ki%#Ulg&rvwC10jAw6a`vlC6%lC^fC zlxvN(4O5(Pq!{?>9@rK4bTdr%jY*)Tj9RUC{&c1*C2_m60af`FEjKohKCswPWN@2i z2x09Ad{Pz}5u5IIYzvzNlU+&~-5IJ~JFSBm1GwudayMi)KmvzAbiF!5hL?SM-HR^G zX5fdXZq=KB7b?85{mx^63%E%_B^wbz4)@Uk#56cVAREl;AQR=I^4N#&48Ak3Ehw|Q zV494e`!LH63}}7Hol%9RvQWRyg#;Ft>lak&4}E}x-{Q0nS?G(LAjPj8CklFzie|AR z9b>)R7~3eX>G4t2g-&nf#}t|A`@mN4hn7wiejwY4*W?REvWE2GmT<%bxm~EQ60C}f z+I|;!O=t&ZcXl-=PR(JbXaI32L_5AeC}NliaZQ{!EHq>xohecobTUEMpJDO1zD7Qd zG-q;;kPVJp9574EMO#~cByrj|59vLNk0Lk4w6VThK}| z43&u5+rD_O>Asg2qQllSE(xFTMOsdJ|KrGpZjJamUz$4Ans#_%!XAtJq3u6-=HHPu z^e~2#UIMNw?S2grM$^0?Ad`t>N(ddO)3CCg8zkz_VUftG?*W{1)$}wgEF2;jH-O0J zDzo{M*5onGj}P9N@nSmU;EzWpK{QFMV4UM&WO5gjF#2a5&0 zE9uu4M^TX;r_<4x^ZNV@Q1zMW+in*{Iy_maaJybMKNl_{s67piE;n*PTGa>yDqf1l z!^h^ASUC|@*i`?dCfm5uF!6JiwW;~PFYi&6UpFCSflJ?T>H*Sz4RF2iQ#Hd?xH_0 zH};Rg1+a6K2euOb7Y2h*u4CTz^^?QjY6j_Rl_MGA2i#%@^4Mfo_Pb9(jBYz{TCBF^ z)GUCC$JT-bb6ZJ=ZZ*!Gq)nZhhalGr)ZV$B-DA=+hGJ6H_eXpEXt-nr0vCW`oDs2f z58U@G&ILIXJ%QrLO0taFzzVSh_pN3ev;V7qJ=H0uB1i;=QU3?2mWC~{W zqMm}EpQ1mQ3K=^7?BhHrk!akcfcC-Lr;7$ruj>?i1EVjbmSM?*30mnjvl!FMM;eHg-=H}{lB>kTP)u}lTx zvX2pqLBu6YmbMKUgq(*lFy=;8W)CsO?sr|3bo1F?oRv1 zYE?sNnigSoIYZH7dZ``Sx7gw9FuinHV#)Vhy8U7O(6Sj)Ht(QfQL8d?U|M3Jj2RpMUF4%-NWq*P~n#iG0h|iABkL zI(>c0)45f}(D%1F0>~_5O{Q`=Mv6MgQZGA0$JoFdf^fpuXyhu7So$Bjm zm-FNRGiHWQ-)n*u?#gY3lfnni=<63fV;7v0Zu-W&<9Ijzm~k7Prs-i~dz8eiT2(nY zm*faea`V_7c;JG9PDUSgz2)$_#E{hhRfA|dsay;)2Apvbz!^v`{Ou#COd09X`i6j) z+yNASEE>8(Mgvo0P;cC$5)n2y1vyma(|y+JNOR2b-R4bh<7x)5I+4st#9N=L9li=- z`qV{4wDXRQAOoPtF24iwoTkDi>GLfD04PAAZVcTU5gq+|_KE)734iEP1=_|+b$DxL z(@v*B&F)N|QS_SSm$JJXV=oBx%&>d9?Y-ajkGuAGV~OIr{FtDeT3$9dcJ?*o2`q2g z+4@F~Hj+?oA}<+YPUFJKJ8P29Aqn1?Nj&X4HZ?eN@C~l0N1{KlL!|#s%gz@kdgo44 zHBw??NMq~B%o0vU_);on!I@;`{$cP4qhe2FSg3#z+S%+2msF&CglR$)=S9Mfyh{%B z>icL!9<#nn@6Y*5#I4*a=i5VwO@LL-54Vj(zTZcicnRd%!GO(lU>y}=lNZ3qsTK0^aLnvf+GV)r4$_(%Jz2<0ScUxTqb?EE%cX&nUM#fM_JYz zd+CuMzh$3KHRXTWu1@Nh`gZa#E1yP*_kqHAC0ya2lxJJg=j3>I%Q*u-~^zEm9jj`&~NbG{DmA`0+B8 zQkg@zmt)5qN1^SE9it4DaH5M^j-weONb4iRt`JxZK66tm98u92S!Ug&nkFKdvErG>eT(JRo+I`mv2z4b)AcU`v%=y=d|ji|@aierU!iE@f) zVPU!?yCALg>-5DhqM)|wc$kaLbNN&s@X5QntR=#rKV^tZ{EN8A{Ykaml8}?K_mp zIcmkrtCgx`G_9rI%@6R^w_(ZWwI*0eHM2T-OQG_3xmEmF(pSul9y1`FRZ3VXug@gUxFeyyT(F=^TUqxPK6I+-f|^g91K*HBsh;e zF0TqdG2H@oMrNWrVX6$>cE8;9(Bn1hYu4r_oR@rvOFXqYVbeozq6H$P7u=3{oKa~D z6vDCYRUSS&LY1TKltOwfRuq4xeK5T?KJ1uGzBK#Uj4x(scgo-`M^DK#ce@X&u*ien zBnk2Jksa(uf$z1(oC&hWoYxW;xI?rojVA@8XR)Sq)>`+RC>n7dD+lDTcg**3iK*hq zQIF820alT9MWZ_c+iW_5mI#C;$BR?E=Xx5wOFGh|Eu+KWIt3N8#HioubGRv)WWccn zx1Iw4K=R}q*j|t(c9KTR)RPyK4)e+sOpM%tTHyQ=95uR>3O0e2nGvaZ9Ff2t-@49G z^L||gLyb?X_tQVHg0Yj6!lmH6AE+Q2_%GQ+1oWdLcrqgRaj7bpB!mc zL3iqz;`7N9)-F`|EQ5B6Mb@NJ3`~|_A!0m!Sjq>7T{aJn+%RbeU0vOZ2bM~|)?ldv zT_ok;%|JR1u{i8VTsD{my1M?mwt6Z}c#>WN{cJX@!2`|pUzB-6E|3DDL^|YPbei!D z!VP*@WExugLBR+B-s$3ypmCj#ec$_S6`J>uMH-@k`10B<0TAUnJ4SN4_nu$7;iWyn zEtnD&@pTUc63@oXgMU!SX?&qos&WZuMY`CeQE010t95?uvR@?>9YWF*t~8SpkUA%D z)cppwuP51Kka={m;E>U?+FoZ!J~{f+dxf_^dkbL{W`^vDaxjhIsCN588^i4ALz0NCFumq z_~P24Pm(#et41HxvUqt8H?9_oK4r)CnO!6|w6YNhwapoQ~9GGd~&KMGwd3grY2m4O} zsAl{2Z%>mDJ`>$fkEMqrDo;q!k#u&KlD})HHS~}Pe9#NN_k3R(U8;+Rn2%QzMBJtS z05LIXeU8X!#$b<*vEc*sW7%=0$!x#jibtW=spU@L!62TcbXXhLaITc+oH;C3BibK- z82h4sM32|ps5wU!K*^OtgChFW9U;`f&rOqx%%l4m)?P(xOP_=E`&)G>L4@oH58%rFCq$hdn(=@-qIXrEGtkFZPb)xCl7ITPCQgyzJr zw3~xapSD-|P7nnT98v|iGn3t)I^MbCOw=;xW??Xs@Hcaa6z`kyhHXeoJ zPxVANutxKT2Q~qlWkl&Y){D64WN=>LChWmkL!;`{%Bl{*kO|Ojih;<$R;9!kA;qIu zz(TwX#9D~a_C-DP4EOCZT48a*FuJ@Q65oP~ACY6cJauae?&3iC&bkn`$z>C2+l{nfH+4bXZvuEmd?6C4q_>>zsonN3A1Qz%8n}6QiBEnm?6@n$N>Dmgz_NjcYrjH zpMM&e+t>n4O<8OVRi48AQpx*=Lf%h%f7ZzRpFIEo1F-QZ9ztQUu!Lv_Sm^y!54gQO ztpED=%ii}Z_H-@G%pgUipK^ZxX87;GzwyLLMMI7fAc*Q7#g)LBU@klQf5S%1<`&jw zKvN^9U$U$>!+^&1Vn`tAQNjIr{mA9~l0v@yJ0F)YR(3`p$b-7S%3wExIF+2`i9lkh zfy8nZ5&;SLj}VXpq}HbUtJZci$fBb&V!<5%poJI!Aioj`E73KOziNB8%a^cfNaGVo zC6Ns4cM1>Pb(Eh15mt7$8I^7m@3S=sWf{_KNOC2X`TN&UfOdLDw@DZLSFE9*$JDPR zzXw9Ye+|OI($>iAcIkp<$8f1f0RWN+f2SbITtl&e$P1eq>Hlh$yxGvt?6ElTKw`lo z{dsHd=Aq{yv9`bgyCPflQ4I3~w_i-49|XC?M&o zAozXUW$dnj0QG>Dw?W7z~9u5ZbrW}45-DNLuv2NwXpUZdGIROVb4FB92$pG_^6RSSq&;Mxt0~7`LhyVZp literal 0 HcmV?d00001 diff --git a/dist/opencode-prefixed/.opencode/commands/i-adapt.md b/dist/opencode-prefixed/.opencode/commands/i-adapt.md new file mode 100644 index 0000000..70eb740 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-adapt.md @@ -0,0 +1,189 @@ +--- +description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments. +--- + +Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases. + +## Assess Adaptation Challenge + +Understand what needs adaptation and why: + +1. **Identify the source context**: + - What was it designed for originally? (Desktop web? Mobile app?) + - What assumptions were made? (Large screen? Mouse input? Fast connection?) + - What works well in current context? + +2. **Understand target context**: + - **Device**: Mobile, tablet, desktop, TV, watch, print? + - **Input method**: Touch, mouse, keyboard, voice, gamepad? + - **Screen constraints**: Size, resolution, orientation? + - **Connection**: Fast wifi, slow 3G, offline? + - **Usage context**: On-the-go vs desk, quick glance vs focused reading? + - **User expectations**: What do users expect on this platform? + +3. **Identify adaptation challenges**: + - What won't fit? (Content, navigation, features) + - What won't work? (Hover states on touch, tiny touch targets) + - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop) + +**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context. + +## Plan Adaptation Strategy + +Create context-appropriate strategy: + +### Mobile Adaptation (Desktop → Mobile) + +**Layout Strategy**: +- Single column instead of multi-column +- Vertical stacking instead of side-by-side +- Full-width components instead of fixed widths +- Bottom navigation instead of top/side navigation + +**Interaction Strategy**: +- Touch targets 44x44px minimum (not hover-dependent) +- Swipe gestures where appropriate (lists, carousels) +- Bottom sheets instead of dropdowns +- Thumbs-first design (controls within thumb reach) +- Larger tap areas with more spacing + +**Content Strategy**: +- Progressive disclosure (don't show everything at once) +- Prioritize primary content (secondary content in tabs/accordions) +- Shorter text (more concise) +- Larger text (16px minimum) + +**Navigation Strategy**: +- Hamburger menu or bottom navigation +- Reduce navigation complexity +- Sticky headers for context +- Back button in navigation flow + +### Tablet Adaptation (Hybrid Approach) + +**Layout Strategy**: +- Two-column layouts (not single or three-column) +- Side panels for secondary content +- Master-detail views (list + detail) +- Adaptive based on orientation (portrait vs landscape) + +**Interaction Strategy**: +- Support both touch and pointer +- Touch targets 44x44px but allow denser layouts than phone +- Side navigation drawers +- Multi-column forms where appropriate + +### Desktop Adaptation (Mobile → Desktop) + +**Layout Strategy**: +- Multi-column layouts (use horizontal space) +- Side navigation always visible +- Multiple information panels simultaneously +- Fixed widths with max-width constraints (don't stretch to 4K) + +**Interaction Strategy**: +- Hover states for additional information +- Keyboard shortcuts +- Right-click context menus +- Drag and drop where helpful +- Multi-select with Shift/Cmd + +**Content Strategy**: +- Show more information upfront (less progressive disclosure) +- Data tables with many columns +- Richer visualizations +- More detailed descriptions + +### Print Adaptation (Screen → Print) + +**Layout Strategy**: +- Page breaks at logical points +- Remove navigation, footer, interactive elements +- Black and white (or limited color) +- Proper margins for binding + +**Content Strategy**: +- Expand shortened content (show full URLs, hidden sections) +- Add page numbers, headers, footers +- Include metadata (print date, page title) +- Convert charts to print-friendly versions + +### Email Adaptation (Web → Email) + +**Layout Strategy**: +- Narrow width (600px max) +- Single column only +- Inline CSS (no external stylesheets) +- Table-based layouts (for email client compatibility) + +**Interaction Strategy**: +- Large, obvious CTAs (buttons not text links) +- No hover states (not reliable) +- Deep links to web app for complex interactions + +## Implement Adaptations + +Apply changes systematically: + +### Responsive Breakpoints + +Choose appropriate breakpoints: +- Mobile: 320px-767px +- Tablet: 768px-1023px +- Desktop: 1024px+ +- Or content-driven breakpoints (where design breaks) + +### Layout Adaptation Techniques + +- **CSS Grid/Flexbox**: Reflow layouts automatically +- **Container Queries**: Adapt based on container, not viewport +- **`clamp()`**: Fluid sizing between min and max +- **Media queries**: Different styles for different contexts +- **Display properties**: Show/hide elements per context + +### Touch Adaptation + +- Increase touch target sizes (44x44px minimum) +- Add more spacing between interactive elements +- Remove hover-dependent interactions +- Add touch feedback (ripples, highlights) +- Consider thumb zones (easier to reach bottom than top) + +### Content Adaptation + +- Use `display: none` sparingly (still downloads) +- Progressive enhancement (core content first, enhancements on larger screens) +- Lazy loading for off-screen content +- Responsive images (`srcset`, `picture` element) + +### Navigation Adaptation + +- Transform complex nav to hamburger/drawer on mobile +- Bottom nav bar for mobile apps +- Persistent side navigation on desktop +- Breadcrumbs on smaller screens for context + +**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect. + +**NEVER**: +- Hide core functionality on mobile (if it matters, make it work) +- Assume desktop = powerful device (consider accessibility, older machines) +- Use different information architecture across contexts (confusing) +- Break user expectations for platform (mobile users expect mobile patterns) +- Forget landscape orientation on mobile/tablet +- Use generic breakpoints blindly (use content-driven breakpoints) +- Ignore touch on desktop (many desktop devices have touch) + +## Verify Adaptations + +Test thoroughly across contexts: + +- **Real devices**: Test on actual phones, tablets, desktops +- **Different orientations**: Portrait and landscape +- **Different browsers**: Safari, Chrome, Firefox, Edge +- **Different OS**: iOS, Android, Windows, macOS +- **Different input methods**: Touch, mouse, keyboard +- **Edge cases**: Very small screens (320px), very large screens (4K) +- **Slow connections**: Test on throttled network + +Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-animate.md b/dist/opencode-prefixed/.opencode/commands/i-animate.md new file mode 100644 index 0000000..e77485f --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-animate.md @@ -0,0 +1,184 @@ +--- +description: Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. +--- + +Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight. + +## MANDATORY PREPARATION + +### Context Gathering (Do This First) + +You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone (playful vs serious, energetic vs calm), and performance constraints. + +Attempt to gather these from the current thread or codebase. + +1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and ask the user directly to clarify what you cannot infer. whether you got it right. +2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST ask the user directly to clarify what you cannot infer. clarifying questions first to complete your context. + +Do NOT proceed until you have answers. Guessing leads to inappropriate or excessive animation. + +### Use frontend-design skill + +Use the frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts. + +--- + +## Assess Animation Opportunities + +Analyze where motion would improve the experience: + +1. **Identify static areas**: + - **Missing feedback**: Actions without visual acknowledgment (button clicks, form submission, etc.) + - **Jarring transitions**: Instant state changes that feel abrupt (show/hide, page loads, route changes) + - **Unclear relationships**: Spatial or hierarchical relationships that aren't obvious + - **Lack of delight**: Functional but joyless interactions + - **Missed guidance**: Opportunities to direct attention or explain behavior + +2. **Understand the context**: + - What's the personality? (Playful vs serious, energetic vs calm) + - What's the performance budget? (Mobile-first? Complex page?) + - Who's the audience? (Motion-sensitive users? Power users who want speed?) + - What matters most? (One hero animation vs many micro-interactions?) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: Respect `prefers-reduced-motion`. Always provide non-animated alternatives for users who need them. + +## Plan Animation Strategy + +Create a purposeful animation plan: + +- **Hero moment**: What's the ONE signature animation? (Page load? Hero section? Key interaction?) +- **Feedback layer**: Which interactions need acknowledgment? +- **Transition layer**: Which state changes need smoothing? +- **Delight layer**: Where can we surprise and delight? + +**IMPORTANT**: One well-orchestrated experience beats scattered animations everywhere. Focus on high-impact moments. + +## Implement Animations + +Add motion systematically across these categories: + +### Entrance Animations +- **Page load choreography**: Stagger element reveals (100-150ms delays), fade + slide combinations +- **Hero section**: Dramatic entrance for primary content (scale, parallax, or creative effects) +- **Content reveals**: Scroll-triggered animations using intersection observer +- **Modal/drawer entry**: Smooth slide + fade, backdrop fade, focus management + +### Micro-interactions +- **Button feedback**: + - Hover: Subtle scale (1.02-1.05), color shift, shadow increase + - Click: Quick scale down then up (0.95 → 1), ripple effect + - Loading: Spinner or pulse state +- **Form interactions**: + - Input focus: Border color transition, slight scale or glow + - Validation: Shake on error, check mark on success, smooth color transitions +- **Toggle switches**: Smooth slide + color transition (200-300ms) +- **Checkboxes/radio**: Check mark animation, ripple effect +- **Like/favorite**: Scale + rotation, particle effects, color transition + +### State Transitions +- **Show/hide**: Fade + slide (not instant), appropriate timing (200-300ms) +- **Expand/collapse**: Height transition with overflow handling, icon rotation +- **Loading states**: Skeleton screen fades, spinner animations, progress bars +- **Success/error**: Color transitions, icon animations, gentle scale pulse +- **Enable/disable**: Opacity transitions, cursor changes + +### Navigation & Flow +- **Page transitions**: Crossfade between routes, shared element transitions +- **Tab switching**: Slide indicator, content fade/slide +- **Carousel/slider**: Smooth transforms, snap points, momentum +- **Scroll effects**: Parallax layers, sticky headers with state changes, scroll progress indicators + +### Feedback & Guidance +- **Hover hints**: Tooltip fade-ins, cursor changes, element highlights +- **Drag & drop**: Lift effect (shadow + scale), drop zone highlights, smooth repositioning +- **Copy/paste**: Brief highlight flash on paste, "copied" confirmation +- **Focus flow**: Highlight path through form or workflow + +### Delight Moments +- **Empty states**: Subtle floating animations on illustrations +- **Completed actions**: Confetti, check mark flourish, success celebrations +- **Easter eggs**: Hidden interactions for discovery +- **Contextual animation**: Weather effects, time-of-day themes, seasonal touches + +## Technical Implementation + +Use appropriate techniques for each animation: + +### Timing & Easing + +**Durations by purpose:** +- **100-150ms**: Instant feedback (button press, toggle) +- **200-300ms**: State changes (hover, menu open) +- **300-500ms**: Layout changes (accordion, modal) +- **500-800ms**: Entrance animations (page load) + +**Easing curves (use these, not CSS defaults):** +```css +/* Recommended - natural deceleration */ +--ease-out-quart: cubic-bezier(0.25, 1, 0.5, 1); /* Smooth, refined */ +--ease-out-quint: cubic-bezier(0.22, 1, 0.36, 1); /* Slightly snappier */ +--ease-out-expo: cubic-bezier(0.16, 1, 0.3, 1); /* Confident, decisive */ + +/* AVOID - feel dated and tacky */ +/* bounce: cubic-bezier(0.34, 1.56, 0.64, 1); */ +/* elastic: cubic-bezier(0.68, -0.6, 0.32, 1.6); */ +``` + +**Exit animations are faster than entrances.** Use ~75% of enter duration. + +### CSS Animations +```css +/* Prefer for simple, declarative animations */ +- transitions for state changes +- @keyframes for complex sequences +- transform + opacity only (GPU-accelerated) +``` + +### JavaScript Animation +```javascript +/* Use for complex, interactive animations */ +- Web Animations API for programmatic control +- Framer Motion for React +- GSAP for complex sequences +``` + +### Performance +- **GPU acceleration**: Use `transform` and `opacity`, avoid layout properties +- **will-change**: Add sparingly for known expensive animations +- **Reduce paint**: Minimize repaints, use `contain` where appropriate +- **Monitor FPS**: Ensure 60fps on target devices + +### Accessibility +```css +@media (prefers-reduced-motion: reduce) { + * { + animation-duration: 0.01ms !important; + animation-iteration-count: 1 !important; + transition-duration: 0.01ms !important; + } +} +``` + +**NEVER**: +- Use bounce or elastic easing curves—they feel dated and draw attention to the animation itself +- Animate layout properties (width, height, top, left)—use transform instead +- Use durations over 500ms for feedback—it feels laggy +- Animate without purpose—every animation needs a reason +- Ignore `prefers-reduced-motion`—this is an accessibility violation +- Animate everything—animation fatigue makes interfaces feel exhausting +- Block interaction during animations unless intentional + +## Verify Quality + +Test animations thoroughly: + +- **Smooth at 60fps**: No jank on target devices +- **Feels natural**: Easing curves feel organic, not robotic +- **Appropriate timing**: Not too fast (jarring) or too slow (laggy) +- **Reduced motion works**: Animations disabled or simplified appropriately +- **Doesn't block**: Users can interact during/after animations +- **Adds value**: Makes interface clearer or more delightful + +Remember: Motion should enhance understanding and provide feedback, not just add decoration. Animate with purpose, respect performance constraints, and always consider accessibility. Great animation is invisible - it just makes everything feel right. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-audit.md b/dist/opencode-prefixed/.opencode/commands/i-audit.md new file mode 100644 index 0000000..de58622 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-audit.md @@ -0,0 +1,120 @@ +--- +description: Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations. +--- + +Run systematic quality checks and generate a comprehensive audit report with prioritized issues and actionable recommendations. Don't fix issues - document them for other commands to address. + +**First**: Use the frontend-design skill for design principles and anti-patterns. + +## Diagnostic Scan + +Run comprehensive checks across multiple dimensions: + +1. **Accessibility (A11y)** - Check for: + - **Contrast issues**: Text contrast ratios < 4.5:1 (or 7:1 for AAA) + - **Missing ARIA**: Interactive elements without proper roles, labels, or states + - **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps + - **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons + - **Alt text**: Missing or poor image descriptions + - **Form issues**: Inputs without labels, poor error messaging, missing required indicators + +2. **Performance** - Check for: + - **Layout thrashing**: Reading/writing layout properties in loops + - **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform/opacity + - **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change + - **Bundle size**: Unnecessary imports, unused dependencies + - **Render performance**: Unnecessary re-renders, missing memoization + +3. **Theming** - Check for: + - **Hard-coded colors**: Colors not using design tokens + - **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme + - **Inconsistent tokens**: Using wrong tokens, mixing token types + - **Theme switching issues**: Values that don't update on theme change + +4. **Responsive Design** - Check for: + - **Fixed widths**: Hard-coded widths that break on mobile + - **Touch targets**: Interactive elements < 44x44px + - **Horizontal scroll**: Content overflow on narrow viewports + - **Text scaling**: Layouts that break when text size increases + - **Missing breakpoints**: No mobile/tablet variants + +5. **Anti-Patterns (CRITICAL)** - Check against ALL the **DON'T** guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy). + +**CRITICAL**: This is an audit, not a fix. Document issues thoroughly with clear explanations of impact. Use other commands (normalize, optimize, harden, etc.) to fix issues after audit. + +## Generate Comprehensive Report + +Create a detailed audit report with the following structure: + +### Anti-Patterns Verdict +**Start here.** Pass/fail: Does this look AI-generated? List specific tells from the skill's Anti-Patterns section. Be brutally honest. + +### Executive Summary +- Total issues found (count by severity) +- Most critical issues (top 3-5) +- Overall quality score (if applicable) +- Recommended next steps + +### Detailed Findings by Severity + +For each issue, document: +- **Location**: Where the issue occurs (component, file, line) +- **Severity**: Critical / High / Medium / Low +- **Category**: Accessibility / Performance / Theming / Responsive +- **Description**: What the issue is +- **Impact**: How it affects users +- **WCAG/Standard**: Which standard it violates (if applicable) +- **Recommendation**: How to fix it +- **Suggested command**: Which command to use (e.g., `/normalize`, `/optimize`, `/harden`) + +#### Critical Issues +[Issues that block core functionality or violate WCAG A] + +#### High-Severity Issues +[Significant usability/accessibility impact, WCAG AA violations] + +#### Medium-Severity Issues +[Quality issues, WCAG AAA violations, performance concerns] + +#### Low-Severity Issues +[Minor inconsistencies, optimization opportunities] + +### Patterns & Systemic Issues + +Identify recurring problems: +- "Hard-coded colors appear in 15+ components, should use design tokens" +- "Touch targets consistently too small (<44px) throughout mobile experience" +- "Missing focus indicators on all custom interactive components" + +### Positive Findings + +Note what's working well: +- Good practices to maintain +- Exemplary implementations to replicate elsewhere + +### Recommendations by Priority + +Create actionable plan: +1. **Immediate**: Critical blockers to fix first +2. **Short-term**: High-severity issues (this sprint) +3. **Medium-term**: Quality improvements (next sprint) +4. **Long-term**: Nice-to-haves and optimizations + +### Suggested Commands for Fixes + +Map issues to appropriate commands: +- "Use `/normalize` to align components with design system (addresses 23 theming issues)" +- "Use `/optimize` to improve performance (addresses 12 performance issues)" +- "Use `/harden` to improve i18n and text handling (addresses 8 edge cases)" + +**IMPORTANT**: Be thorough but actionable. Too many low-priority issues creates noise. Focus on what actually matters. + +**NEVER**: +- Report issues without explaining impact (why does this matter?) +- Mix severity levels inconsistently +- Skip positive findings (celebrate what works) +- Provide generic recommendations (be specific and actionable) +- Forget to prioritize (everything can't be critical) +- Report false positives without verification + +Remember: You're a quality auditor with exceptional attention to detail. Document systematically, prioritize ruthlessly, and provide clear paths to improvement. A good audit makes fixing easy. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-bolder.md b/dist/opencode-prefixed/.opencode/commands/i-bolder.md new file mode 100644 index 0000000..5f1638e --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-bolder.md @@ -0,0 +1,126 @@ +--- +description: Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. +--- + +Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences. + +## MANDATORY PREPARATION + +### Context Gathering (Do This First) + +You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and everything else that a great human designer would need as well. + +Attempt to gather these from the current thread or codebase. + +1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and ask the user directly to clarify what you cannot infer. whether you got it right. +2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST ask the user directly to clarify what you cannot infer. clarifying questions first to complete your context. + +Do NOT proceed until you have answers. Guessing leads to generic AI slop. + +### Use frontend-design skill + +Use the frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts. + +--- + +## Assess Current State + +Analyze what makes the design feel too safe or boring: + +1. **Identify weakness sources**: + - **Generic choices**: System fonts, basic colors, standard layouts + - **Timid scale**: Everything is medium-sized with no drama + - **Low contrast**: Everything has similar visual weight + - **Static**: No motion, no energy, no life + - **Predictable**: Standard patterns with no surprises + - **Flat hierarchy**: Nothing stands out or commands attention + +2. **Understand the context**: + - What's the brand personality? (How far can we push?) + - What's the purpose? (Marketing can be bolder than financial dashboards) + - Who's the audience? (What will resonate?) + - What are the constraints? (Brand guidelines, accessibility, performance) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. + +**WARNING - AI SLOP TRAP**: When making things "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the OPPOSITE of bold—they're generic. Review ALL the DON'T guidelines in the frontend-design skill before proceeding. Bold means distinctive, not "more effects." + +## Plan Amplification + +Create a strategy to increase impact while maintaining coherence: + +- **Focal point**: What should be the hero moment? (Pick ONE, make it amazing) +- **Personality direction**: Maximalist chaos? Elegant drama? Playful energy? Dark moody? Choose a lane. +- **Risk budget**: How experimental can we be? Push boundaries within constraints. +- **Hierarchy amplification**: Make big things BIGGER, small things smaller (increase contrast) + +**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration. + +## Amplify the Design + +Systematically increase impact across these dimensions: + +### Typography Amplification +- **Replace generic fonts**: Swap system fonts for distinctive choices (see frontend-design skill for inspiration) +- **Extreme scale**: Create dramatic size jumps (3x-5x differences, not 1.5x) +- **Weight contrast**: Pair 900 weights with 200 weights, not 600 with 400 +- **Unexpected choices**: Variable fonts, display fonts for headlines, condensed/extended widths, monospace as intentional accent (not as lazy "dev tool" default) + +### Color Intensification +- **Increase saturation**: Shift to more vibrant, energetic colors (but not neon) +- **Bold palette**: Introduce unexpected color combinations—avoid the purple-blue gradient AI slop +- **Dominant color strategy**: Let one bold color own 60% of the design +- **Sharp accents**: High-contrast accent colors that pop +- **Tinted neutrals**: Replace pure grays with tinted grays that harmonize with your palette +- **Rich gradients**: Intentional multi-stop gradients (not generic purple-to-blue) + +### Spatial Drama +- **Extreme scale jumps**: Make important elements 3-5x larger than surroundings +- **Break the grid**: Let hero elements escape containers and cross boundaries +- **Asymmetric layouts**: Replace centered, balanced layouts with tension-filled asymmetry +- **Generous space**: Use white space dramatically (100-200px gaps, not 20-40px) +- **Overlap**: Layer elements intentionally for depth + +### Visual Effects +- **Dramatic shadows**: Large, soft shadows for elevation (but not generic drop shadows on rounded rectangles) +- **Background treatments**: Mesh patterns, noise textures, geometric patterns, intentional gradients (not purple-to-blue) +- **Texture & depth**: Grain, halftone, duotone, layered elements—NOT glassmorphism (it's overused AI slop) +- **Borders & frames**: Thick borders, decorative frames, custom shapes (not rounded rectangles with colored border on one side) +- **Custom elements**: Illustrative elements, custom icons, decorative details that reinforce brand + +### Motion & Animation +- **Entrance choreography**: Staggered, dramatic page load animations with 50-100ms delays +- **Scroll effects**: Parallax, reveal animations, scroll-triggered sequences +- **Micro-interactions**: Satisfying hover effects, click feedback, state changes +- **Transitions**: Smooth, noticeable transitions using ease-out-quart/quint/expo (not bounce or elastic—they cheapen the effect) + +### Composition Boldness +- **Hero moments**: Create clear focal points with dramatic treatment +- **Diagonal flows**: Escape horizontal/vertical rigidity with diagonal arrangements +- **Full-bleed elements**: Use full viewport width/height for impact +- **Unexpected proportions**: Golden ratio? Throw it out. Try 70/30, 80/20 splits + +**NEVER**: +- Add effects randomly without purpose (chaos ≠ bold) +- Sacrifice readability for aesthetics (body text must be readable) +- Make everything bold (then nothing is bold - need contrast) +- Ignore accessibility (bold design must still meet WCAG standards) +- Overwhelm with motion (animation fatigue is real) +- Copy trendy aesthetics blindly (bold means distinctive, not derivative) + +## Verify Quality + +Ensure amplification maintains usability and coherence: + +- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over. +- **Still functional**: Can users accomplish tasks without distraction? +- **Coherent**: Does everything feel intentional and unified? +- **Memorable**: Will users remember this experience? +- **Performant**: Do all these effects run smoothly? +- **Accessible**: Does it still meet accessibility standards? + +**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects." + +Remember: Bold design is confident design. It takes risks, makes statements, and creates memorable experiences. But bold without strategy is just loud. Be intentional, be dramatic, be unforgettable. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-clarify.md b/dist/opencode-prefixed/.opencode/commands/i-clarify.md new file mode 100644 index 0000000..9183cd5 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-clarify.md @@ -0,0 +1,173 @@ +--- +description: Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use. +--- + +Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. + +## Assess Current Copy + +Identify what makes the text unclear or ineffective: + +1. **Find clarity problems**: + - **Jargon**: Technical terms users won't understand + - **Ambiguity**: Multiple interpretations possible + - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file" + - **Length**: Too wordy or too terse + - **Assumptions**: Assuming user knowledge they don't have + - **Missing context**: Users don't know what to do or why + - **Tone mismatch**: Too formal, too casual, or inappropriate for situation + +2. **Understand the context**: + - Who's the audience? (Technical? General? First-time users?) + - What's the user's mental state? (Stressed during error? Confident during success?) + - What's the action? (What do we want users to do?) + - What's the constraint? (Character limits? Space limitations?) + +**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets. + +## Plan Copy Improvements + +Create a strategy for clearer communication: + +- **Primary message**: What's the ONE thing users need to know? +- **Action needed**: What should users do next (if anything)? +- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?) +- **Constraints**: Length limits, brand voice, localization considerations + +**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words. + +## Improve Copy Systematically + +Refine text across these common areas: + +### Error Messages +**Bad**: "Error 403: Forbidden" +**Good**: "You don't have permission to view this page. Contact your admin for access." + +**Bad**: "Invalid input" +**Good**: "Email addresses need an @ symbol. Try: name@example.com" + +**Principles**: +- Explain what went wrong in plain language +- Suggest how to fix it +- Don't blame the user +- Include examples when helpful +- Link to help/support if applicable + +### Form Labels & Instructions +**Bad**: "DOB (MM/DD/YYYY)" +**Good**: "Date of birth" (with placeholder showing format) + +**Bad**: "Enter value here" +**Good**: "Your email address" or "Company name" + +**Principles**: +- Use clear, specific labels (not generic placeholders) +- Show format expectations with examples +- Explain why you're asking (when not obvious) +- Put instructions before the field, not after +- Keep required field indicators clear + +### Button & CTA Text +**Bad**: "Click here" | "Submit" | "OK" +**Good**: "Create account" | "Save changes" | "Got it, thanks" + +**Principles**: +- Describe the action specifically +- Use active voice (verb + noun) +- Match user's mental model +- Be specific ("Save" is better than "OK") + +### Help Text & Tooltips +**Bad**: "This is the username field" +**Good**: "Choose a username. You can change this later in Settings." + +**Principles**: +- Add value (don't just repeat the label) +- Answer the implicit question ("What is this?" or "Why do you need this?") +- Keep it brief but complete +- Link to detailed docs if needed + +### Empty States +**Bad**: "No items" +**Good**: "No projects yet. Create your first project to get started." + +**Principles**: +- Explain why it's empty (if not obvious) +- Show next action clearly +- Make it welcoming, not dead-end + +### Success Messages +**Bad**: "Success" +**Good**: "Settings saved! Your changes will take effect immediately." + +**Principles**: +- Confirm what happened +- Explain what happens next (if relevant) +- Be brief but complete +- Match the user's emotional moment (celebrate big wins) + +### Loading States +**Bad**: "Loading..." (for 30+ seconds) +**Good**: "Analyzing your data... this usually takes 30-60 seconds" + +**Principles**: +- Set expectations (how long?) +- Explain what's happening (when it's not obvious) +- Show progress when possible +- Offer escape hatch if appropriate ("Cancel") + +### Confirmation Dialogs +**Bad**: "Are you sure?" +**Good**: "Delete 'Project Alpha'? This can't be undone." + +**Principles**: +- State the specific action +- Explain consequences (especially for destructive actions) +- Use clear button labels ("Delete project" not "Yes") +- Don't overuse confirmations (only for risky actions) + +### Navigation & Wayfinding +**Bad**: Generic labels like "Items" | "Things" | "Stuff" +**Good**: Specific labels like "Your projects" | "Team members" | "Settings" + +**Principles**: +- Be specific and descriptive +- Use language users understand (not internal jargon) +- Make hierarchy clear +- Consider information scent (breadcrumbs, current location) + +## Apply Clarity Principles + +Every piece of copy should follow these rules: + +1. **Be specific**: "Enter email" not "Enter value" +2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity) +3. **Be active**: "Save changes" not "Changes will be saved" +4. **Be human**: "Oops, something went wrong" not "System error encountered" +5. **Be helpful**: Tell users what to do, not just what happened +6. **Be consistent**: Use same terms throughout (don't vary for variety) + +**NEVER**: +- Use jargon without explanation +- Blame users ("You made an error" → "This field is required") +- Be vague ("Something went wrong" without explanation) +- Use passive voice unnecessarily +- Write overly long explanations (be concise) +- Use humor for errors (be empathetic instead) +- Assume technical knowledge +- Vary terminology (pick one term and stick with it) +- Repeat information (headers restating intros, redundant explanations) +- Use placeholders as the only labels (they disappear when users type) + +## Verify Improvements + +Test that copy improvements work: + +- **Comprehension**: Can users understand without context? +- **Actionability**: Do users know what to do next? +- **Brevity**: Is it as short as possible while remaining clear? +- **Consistency**: Does it match terminology elsewhere? +- **Tone**: Is it appropriate for the situation? + +Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-colorize.md b/dist/opencode-prefixed/.opencode/commands/i-colorize.md new file mode 100644 index 0000000..eb3f386 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-colorize.md @@ -0,0 +1,152 @@ +--- +description: Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive. +--- + +Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality. + +## MANDATORY PREPARATION + +### Context Gathering (Do This First) + +You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and especially existing brand colors. + +Attempt to gather these from the current thread or codebase. + +1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and ask the user directly to clarify what you cannot infer. whether you got it right. +2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST ask the user directly to clarify what you cannot infer. clarifying questions first to complete your context. + +Do NOT proceed until you have answers. Guessing leads to generic AI slop colors. + +### Use frontend-design skill + +Use the frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts. + +--- + +## Assess Color Opportunity + +Analyze the current state and identify opportunities: + +1. **Understand current state**: + - **Color absence**: Pure grayscale? Limited neutrals? One timid accent? + - **Missed opportunities**: Where could color add meaning, hierarchy, or delight? + - **Context**: What's appropriate for this domain and audience? + - **Brand**: Are there existing brand colors we should use? + +2. **Identify where color adds value**: + - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue) + - **Hierarchy**: Drawing attention to important elements + - **Categorization**: Different sections, types, or states + - **Emotional tone**: Warmth, energy, trust, creativity + - **Wayfinding**: Helping users navigate and understand structure + - **Delight**: Moments of visual interest and personality + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. + +## Plan Color Strategy + +Create a purposeful color introduction plan: + +- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals) +- **Dominant color**: Which color owns 60% of colored elements? +- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%) +- **Application strategy**: Where does each color appear and why? + +**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more. + +## Introduce Color Strategically + +Add color systematically across these dimensions: + +### Semantic Color +- **State indicators**: + - Success: Green tones (emerald, forest, mint) + - Error: Red/pink tones (rose, crimson, coral) + - Warning: Orange/amber tones + - Info: Blue tones (sky, ocean, indigo) + - Neutral: Gray/slate for inactive states + +- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.) +- **Progress indicators**: Colored bars, rings, or charts showing completion or health + +### Accent Color Application +- **Primary actions**: Color the most important buttons/CTAs +- **Links**: Add color to clickable text (maintain accessibility) +- **Icons**: Colorize key icons for recognition and personality +- **Headers/titles**: Add color to section headers or key labels +- **Hover states**: Introduce color on interaction + +### Background & Surfaces +- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`) +- **Colored sections**: Use subtle background colors to separate areas +- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue) +- **Cards & surfaces**: Tint cards or surfaces slightly for warmth + +**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales. + +### Data Visualization +- **Charts & graphs**: Use color to encode categories or values +- **Heatmaps**: Color intensity shows density or importance +- **Comparison**: Color coding for different datasets or timeframes + +### Borders & Accents +- **Accent borders**: Add colored left/top borders to cards or sections +- **Underlines**: Color underlines for emphasis or active states +- **Dividers**: Subtle colored dividers instead of gray lines +- **Focus rings**: Colored focus indicators matching brand + +### Typography Color +- **Colored headings**: Use brand colors for section headings (maintain contrast) +- **Highlight text**: Color for emphasis or categories +- **Labels & tags**: Small colored labels for metadata or categories + +### Decorative Elements +- **Illustrations**: Add colored illustrations or icons +- **Shapes**: Geometric shapes in brand colors as background elements +- **Gradients**: Colorful gradient overlays or mesh backgrounds +- **Blobs/organic shapes**: Soft colored shapes for visual interest + +## Balance & Refinement + +Ensure color addition improves rather than overwhelms: + +### Maintain Hierarchy +- **Dominant color** (60%): Primary brand color or most used accent +- **Secondary color** (30%): Supporting color for variety +- **Accent color** (10%): High contrast for key moments +- **Neutrals** (remaining): Gray/black/white for structure + +### Accessibility +- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components) +- **Don't rely on color alone**: Use icons, labels, or patterns alongside color +- **Test for color blindness**: Verify red/green combinations work for all users + +### Cohesion +- **Consistent palette**: Use colors from defined palette, not arbitrary choices +- **Systematic application**: Same color meanings throughout (green always = success) +- **Temperature consistency**: Warm palette stays warm, cool stays cool + +**NEVER**: +- Use every color in the rainbow (choose 2-4 colors beyond neutrals) +- Apply color randomly without semantic meaning +- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead +- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication +- Use pure black (`#000`) or pure white (`#fff`) for large areas +- Violate WCAG contrast requirements +- Use color as the only indicator (accessibility issue) +- Make everything colorful (defeats the purpose) +- Default to purple-blue gradients (AI slop aesthetic) + +## Verify Color Addition + +Test that colorization improves the experience: + +- **Better hierarchy**: Does color guide attention appropriately? +- **Clearer meaning**: Does color help users understand states/categories? +- **More engaging**: Does the interface feel warmer and more inviting? +- **Still accessible**: Do all color combinations meet WCAG standards? +- **Not overwhelming**: Is color balanced and purposeful? + +Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-critique.md b/dist/opencode-prefixed/.opencode/commands/i-critique.md new file mode 100644 index 0000000..8174c91 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-critique.md @@ -0,0 +1,112 @@ +--- +description: Evaluate design effectiveness from a UX perspective. Assesses visual hierarchy, information architecture, emotional resonance, and overall design quality with actionable feedback. +--- + +Conduct a holistic design critique, evaluating whether the interface actually works—not just technically, but as a designed experience. Think like a design director giving feedback. + +**First**: Use the frontend-design skill for design principles and anti-patterns. + +## Design Critique + +Evaluate the interface across these dimensions: + +### 1. AI Slop Detection (CRITICAL) + +**This is the most important check.** Does this look like every other AI-generated interface from 2024-2025? + +Review the design against ALL the **DON'T** guidelines in the frontend-design skill—they are the fingerprints of AI-generated work. Check for the AI color palette, gradient text, dark mode with glowing accents, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells. + +**The test**: If you showed this to someone and said "AI made this," would they believe you immediately? If yes, that's the problem. + +### 2. Visual Hierarchy +- Does the eye flow to the most important element first? +- Is there a clear primary action? Can you spot it in 2 seconds? +- Do size, color, and position communicate importance correctly? +- Is there visual competition between elements that should have different weights? + +### 3. Information Architecture +- Is the structure intuitive? Would a new user understand the organization? +- Is related content grouped logically? +- Are there too many choices at once? (cognitive overload) +- Is the navigation clear and predictable? + +### 4. Emotional Resonance +- What emotion does this interface evoke? Is that intentional? +- Does it match the brand personality? +- Does it feel trustworthy, approachable, premium, playful—whatever it should feel? +- Would the target user feel "this is for me"? + +### 5. Discoverability & Affordance +- Are interactive elements obviously interactive? +- Would a user know what to do without instructions? +- Are hover/focus states providing useful feedback? +- Are there hidden features that should be more visible? + +### 6. Composition & Balance +- Does the layout feel balanced or uncomfortably weighted? +- Is whitespace used intentionally or just leftover? +- Is there visual rhythm in spacing and repetition? +- Does asymmetry feel designed or accidental? + +### 7. Typography as Communication +- Does the type hierarchy clearly signal what to read first, second, third? +- Is body text comfortable to read? (line length, spacing, size) +- Do font choices reinforce the brand/tone? +- Is there enough contrast between heading levels? + +### 8. Color with Purpose +- Is color used to communicate, not just decorate? +- Does the palette feel cohesive? +- Are accent colors drawing attention to the right things? +- Does it work for colorblind users? (not just technically—does meaning still come through?) + +### 9. States & Edge Cases +- Empty states: Do they guide users toward action, or just say "nothing here"? +- Loading states: Do they reduce perceived wait time? +- Error states: Are they helpful and non-blaming? +- Success states: Do they confirm and guide next steps? + +### 10. Microcopy & Voice +- Is the writing clear and concise? +- Does it sound like a human (the right human for this brand)? +- Are labels and buttons unambiguous? +- Does error copy help users fix the problem? + +## Generate Critique Report + +Structure your feedback as a design director would: + +### Anti-Patterns Verdict +**Start here.** Pass/fail: Does this look AI-generated? List specific tells from the skill's Anti-Patterns section. Be brutally honest. + +### Overall Impression +A brief gut reaction—what works, what doesn't, and the single biggest opportunity. + +### What's Working +Highlight 2-3 things done well. Be specific about why they work. + +### Priority Issues +The 3-5 most impactful design problems, ordered by importance: + +For each issue: +- **What**: Name the problem clearly +- **Why it matters**: How this hurts users or undermines goals +- **Fix**: What to do about it (be concrete) +- **Command**: Which command to use (`/polish`, `/simplify`, `/bolder`, `/quieter`, etc.) + +### Minor Observations +Quick notes on smaller issues worth addressing. + +### Questions to Consider +Provocative questions that might unlock better solutions: +- "What if the primary action were more prominent?" +- "Does this need to feel this complex?" +- "What would a confident version of this look like?" + +**Remember**: +- Be direct—vague feedback wastes everyone's time +- Be specific—"the submit button" not "some elements" +- Say what's wrong AND why it matters to users +- Give concrete suggestions, not just "consider exploring..." +- Prioritize ruthlessly—if everything is important, nothing is +- Don't soften criticism—developers need honest feedback to ship great design \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-delight.md b/dist/opencode-prefixed/.opencode/commands/i-delight.md new file mode 100644 index 0000000..898e628 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-delight.md @@ -0,0 +1,311 @@ +--- +description: Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. +--- + +Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences. + +## MANDATORY PREPARATION + +### Context Gathering (Do This First) + +You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality (playful vs professional vs quirky vs elegant), and what's appropriate for the domain. + +Attempt to gather these from the current thread or codebase. + +1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and ask the user directly to clarify what you cannot infer. whether you got it right. +2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST ask the user directly to clarify what you cannot infer. clarifying questions first to complete your context. + +Do NOT proceed until you have answers. Delight that's wrong for the context is worse than no delight at all. + +### Use frontend-design skill + +Use the frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts. + +--- + +## Assess Delight Opportunities + +Identify where delight would enhance (not distract from) the experience: + +1. **Find natural delight moments**: + - **Success states**: Completed actions (save, send, publish) + - **Empty states**: First-time experiences, onboarding + - **Loading states**: Waiting periods that could be entertaining + - **Achievements**: Milestones, streaks, completions + - **Interactions**: Hover states, clicks, drags + - **Errors**: Softening frustrating moments + - **Easter eggs**: Hidden discoveries for curious users + +2. **Understand the context**: + - What's the brand personality? (Playful? Professional? Quirky? Elegant?) + - Who's the audience? (Tech-savvy? Creative? Corporate?) + - What's the emotional context? (Accomplishment? Exploration? Frustration?) + - What's appropriate? (Banking app ≠ gaming app) + +3. **Define delight strategy**: + - **Subtle sophistication**: Refined micro-interactions (luxury brands) + - **Playful personality**: Whimsical illustrations and copy (consumer apps) + - **Helpful surprises**: Anticipating needs before users ask (productivity tools) + - **Sensory richness**: Satisfying sounds, smooth animations (creative tools) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: Delight should enhance usability, never obscure it. If users notice the delight more than accomplishing their goal, you've gone too far. + +## Delight Principles + +Follow these guidelines: + +### Delight Amplifies, Never Blocks +- Delight moments should be quick (< 1 second) +- Never delay core functionality for delight +- Make delight skippable or subtle +- Respect user's time and task focus + +### Surprise and Discovery +- Hide delightful details for users to discover +- Reward exploration and curiosity +- Don't announce every delight moment +- Let users share discoveries with others + +### Appropriate to Context +- Match delight to emotional moment (celebrate success, empathize with errors) +- Respect the user's state (don't be playful during critical errors) +- Match brand personality and audience expectations +- Cultural sensitivity (what's delightful varies by culture) + +### Compound Over Time +- Delight should remain fresh with repeated use +- Vary responses (not same animation every time) +- Reveal deeper layers with continued use +- Build anticipation through patterns + +## Delight Techniques + +Add personality and joy through these methods: + +### Micro-interactions & Animation + +**Button delight**: +```css +/* Satisfying button press */ +.button { + transition: transform 0.1s, box-shadow 0.1s; +} +.button:active { + transform: translateY(2px); + box-shadow: 0 2px 4px rgba(0,0,0,0.2); +} + +/* Ripple effect on click */ +/* Smooth lift on hover */ +.button:hover { + transform: translateY(-2px); + transition: transform 0.2s cubic-bezier(0.25, 1, 0.5, 1); /* ease-out-quart */ +} +``` + +**Loading delight**: +- Playful loading animations (not just spinners) +- Personality in loading messages ("Herding pixels..." "Teaching robots to dance...") +- Progress indication with encouraging messages +- Skeleton screens with subtle animations + +**Success animations**: +- Checkmark draw animation +- Confetti burst for major achievements +- Gentle scale + fade for confirmation +- Satisfying sound effects (subtle) + +**Hover surprises**: +- Icons that animate on hover +- Color shifts or glow effects +- Tooltip reveals with personality +- Cursor changes (custom cursors for branded experiences) + +### Personality in Copy + +**Playful error messages**: +``` +"Error 404" +"This page is playing hide and seek. (And winning)" + +"Connection failed" +"Looks like the internet took a coffee break. Want to retry?" +``` + +**Encouraging empty states**: +``` +"No projects" +"Your canvas awaits. Create something amazing." + +"No messages" +"Inbox zero! You're crushing it today." +``` + +**Playful labels & tooltips**: +``` +"Delete" +"Send to void" (for playful brand) + +"Help" +"Rescue me" (tooltip) +``` + +**IMPORTANT**: Match copy personality to brand. Banks shouldn't be wacky, but they can be warm. + +### Illustrations & Visual Personality + +**Custom illustrations**: +- Empty state illustrations (not stock icons) +- Error state illustrations (friendly monsters, quirky characters) +- Loading state illustrations (animated characters) +- Success state illustrations (celebrations) + +**Icon personality**: +- Custom icon set matching brand personality +- Animated icons (subtle motion on hover/click) +- Illustrative icons (more detailed than generic) +- Consistent style across all icons + +**Background effects**: +- Subtle particle effects +- Gradient mesh backgrounds +- Geometric patterns +- Parallax depth +- Time-of-day themes (morning vs night) + +### Satisfying Interactions + +**Drag and drop delight**: +- Lift effect on drag (shadow, scale) +- Snap animation when dropped +- Satisfying placement sound +- Undo toast ("Dropped in wrong place? [Undo]") + +**Toggle switches**: +- Smooth slide with spring physics +- Color transition +- Haptic feedback on mobile +- Optional sound effect + +**Progress & achievements**: +- Streak counters with celebratory milestones +- Progress bars that "celebrate" at 100% +- Badge unlocks with animation +- Playful stats ("You're on fire! 5 days in a row") + +**Form interactions**: +- Input fields that animate on focus +- Checkboxes that bounce when checked +- Success state that celebrates valid input +- Auto-grow textareas + +### Sound Design + +**Subtle audio cues** (when appropriate): +- Notification sounds (distinctive but not annoying) +- Success sounds (satisfying "ding") +- Error sounds (empathetic, not harsh) +- Typing sounds for chat/messaging +- Ambient background audio (very subtle) + +**IMPORTANT**: +- Respect system sound settings +- Provide mute option +- Keep volumes quiet (subtle cues, not alarms) +- Don't play on every interaction (sound fatigue is real) + +### Easter Eggs & Hidden Delights + +**Discovery rewards**: +- Konami code unlocks special theme +- Hidden keyboard shortcuts (Cmd+K for special features) +- Hover reveals on logos or illustrations +- Alt text jokes on images (for screen reader users too!) +- Console messages for developers ("Like what you see? We're hiring!") + +**Seasonal touches**: +- Holiday themes (subtle, tasteful) +- Seasonal color shifts +- Weather-based variations +- Time-based changes (dark at night, light during day) + +**Contextual personality**: +- Different messages based on time of day +- Responses to specific user actions +- Randomized variations (not same every time) +- Progressive reveals with continued use + +### Loading & Waiting States + +**Make waiting engaging**: +- Interesting loading messages that rotate +- Progress bars with personality +- Mini-games during long loads +- Fun facts or tips while waiting +- Countdown with encouraging messages + +``` +Loading messages rotation: +- "Waking up the servers..." +- "Teaching robots to dance..." +- "Consulting the magic 8-ball..." +- "Counting backwards from infinity..." +``` + +### Celebration Moments + +**Success celebrations**: +- Confetti for major milestones +- Animated checkmarks for completions +- Progress bar celebrations at 100% +- "Achievement unlocked" style notifications +- Personalized messages ("You published your 10th article!") + +**Milestone recognition**: +- First-time actions get special treatment +- Streak tracking and celebration +- Progress toward goals +- Anniversary celebrations + +## Implementation Patterns + +**Animation libraries**: +- Framer Motion (React) +- GSAP (universal) +- Lottie (After Effects animations) +- Canvas confetti (party effects) + +**Sound libraries**: +- Howler.js (audio management) +- Use-sound (React hook) + +**Physics libraries**: +- React Spring (spring physics) +- Popmotion (animation primitives) + +**IMPORTANT**: File size matters. Compress images, optimize animations, lazy load delight features. + +**NEVER**: +- Delay core functionality for delight +- Force users through delightful moments (make skippable) +- Use delight to hide poor UX +- Overdo it (less is more) +- Ignore accessibility (animate responsibly, provide alternatives) +- Make every interaction delightful (special moments should be special) +- Sacrifice performance for delight +- Be inappropriate for context (read the room) + +## Verify Delight Quality + +Test that delight actually delights: + +- **User reactions**: Do users smile? Share screenshots? +- **Doesn't annoy**: Still pleasant after 100th time? +- **Doesn't block**: Can users opt out or skip? +- **Performant**: No jank, no slowdown +- **Appropriate**: Matches brand and context +- **Accessible**: Works with reduced motion, screen readers + +Remember: Delight is the difference between a tool and an experience. Add personality, surprise users positively, and create moments worth sharing. But always respect usability - delight should enhance, never obstruct. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-extract.md b/dist/opencode-prefixed/.opencode/commands/i-extract.md new file mode 100644 index 0000000..61f4209 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-extract.md @@ -0,0 +1,88 @@ +--- +description: Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. +--- + +Identify reusable patterns, components, and design tokens, then extract and consolidate them into the design system for systematic reuse. + +## Discover + +Analyze the target area to identify extraction opportunities: + +1. **Find the design system**: Locate your design system, component library, or shared UI directory (grep for "design system", "ui", "components", etc.). Understand its structure: + - Component organization and naming conventions + - Design token structure (if any) + - Documentation patterns + - Import/export conventions + + **CRITICAL**: If no design system exists, ask before creating one. Understand the preferred location and structure first. + +2. **Identify patterns**: Look for: + - **Repeated components**: Similar UI patterns used multiple times (buttons, cards, inputs, etc.) + - **Hard-coded values**: Colors, spacing, typography, shadows that should be tokens + - **Inconsistent variations**: Multiple implementations of the same concept (3 different button styles) + - **Reusable patterns**: Layout patterns, composition patterns, interaction patterns worth systematizing + +3. **Assess value**: Not everything should be extracted. Consider: + - Is this used 3+ times, or likely to be reused? + - Would systematizing this improve consistency? + - Is this a general pattern or context-specific? + - What's the maintenance cost vs benefit? + +## Plan Extraction + +Create a systematic extraction plan: + +- **Components to extract**: Which UI elements become reusable components? +- **Tokens to create**: Which hard-coded values become design tokens? +- **Variants to support**: What variations does each component need? +- **Naming conventions**: Component names, token names, prop names that match existing patterns +- **Migration path**: How to refactor existing uses to consume the new shared versions + +**IMPORTANT**: Design systems grow incrementally. Extract what's clearly reusable now, not everything that might someday be reusable. + +## Extract & Enrich + +Build improved, reusable versions: + +- **Components**: Create well-designed components with: + - Clear props API with sensible defaults + - Proper variants for different use cases + - Accessibility built in (ARIA, keyboard navigation, focus management) + - Documentation and usage examples + +- **Design tokens**: Create tokens with: + - Clear naming (primitive vs semantic) + - Proper hierarchy and organization + - Documentation of when to use each token + +- **Patterns**: Document patterns with: + - When to use this pattern + - Code examples + - Variations and combinations + +**NEVER**: +- Extract one-off, context-specific implementations without generalization +- Create components so generic they're useless +- Extract without considering existing design system conventions +- Skip proper TypeScript types or prop documentation +- Create tokens for every single value (tokens should have semantic meaning) + +## Migrate + +Replace existing uses with the new shared versions: + +- **Find all instances**: Search for the patterns you've extracted +- **Replace systematically**: Update each use to consume the shared version +- **Test thoroughly**: Ensure visual and functional parity +- **Delete dead code**: Remove the old implementations + +## Document + +Update design system documentation: + +- Add new components to the component library +- Document token usage and values +- Add examples and guidelines +- Update any Storybook or component catalog + +Remember: A good design system is a living system. Extract patterns as they emerge, enrich them thoughtfully, and maintain them consistently. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-harden.md b/dist/opencode-prefixed/.opencode/commands/i-harden.md new file mode 100644 index 0000000..899f8e8 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-harden.md @@ -0,0 +1,351 @@ +--- +description: Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. +--- + +Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. + +## Assess Hardening Needs + +Identify weaknesses and edge cases: + +1. **Test with extreme inputs**: + - Very long text (names, descriptions, titles) + - Very short text (empty, single character) + - Special characters (emoji, RTL text, accents) + - Large numbers (millions, billions) + - Many items (1000+ list items, 50+ options) + - No data (empty states) + +2. **Test error scenarios**: + - Network failures (offline, slow, timeout) + - API errors (400, 401, 403, 404, 500) + - Validation errors + - Permission errors + - Rate limiting + - Concurrent operations + +3. **Test internationalization**: + - Long translations (German is often 30% longer than English) + - RTL languages (Arabic, Hebrew) + - Character sets (Chinese, Japanese, Korean, emoji) + - Date/time formats + - Number formats (1,000 vs 1.000) + - Currency symbols + +**CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. + +## Hardening Dimensions + +Systematically improve resilience: + +### Text Overflow & Wrapping + +**Long text handling**: +```css +/* Single line with ellipsis */ +.truncate { + overflow: hidden; + text-overflow: ellipsis; + white-space: nowrap; +} + +/* Multi-line with clamp */ +.line-clamp { + display: -webkit-box; + -webkit-line-clamp: 3; + -webkit-box-orient: vertical; + overflow: hidden; +} + +/* Allow wrapping */ +.wrap { + word-wrap: break-word; + overflow-wrap: break-word; + hyphens: auto; +} +``` + +**Flex/Grid overflow**: +```css +/* Prevent flex items from overflowing */ +.flex-item { + min-width: 0; /* Allow shrinking below content size */ + overflow: hidden; +} + +/* Prevent grid items from overflowing */ +.grid-item { + min-width: 0; + min-height: 0; +} +``` + +**Responsive text sizing**: +- Use `clamp()` for fluid typography +- Set minimum readable sizes (14px on mobile) +- Test text scaling (zoom to 200%) +- Ensure containers expand with text + +### Internationalization (i18n) + +**Text expansion**: +- Add 30-40% space budget for translations +- Use flexbox/grid that adapts to content +- Test with longest language (usually German) +- Avoid fixed widths on text containers + +```jsx +// ❌ Bad: Assumes short English text + + +// ✅ Good: Adapts to content + +``` + +**RTL (Right-to-Left) support**: +```css +/* Use logical properties */ +margin-inline-start: 1rem; /* Not margin-left */ +padding-inline: 1rem; /* Not padding-left/right */ +border-inline-end: 1px solid; /* Not border-right */ + +/* Or use dir attribute */ +[dir="rtl"] .arrow { transform: scaleX(-1); } +``` + +**Character set support**: +- Use UTF-8 encoding everywhere +- Test with Chinese/Japanese/Korean (CJK) characters +- Test with emoji (they can be 2-4 bytes) +- Handle different scripts (Latin, Cyrillic, Arabic, etc.) + +**Date/Time formatting**: +```javascript +// ✅ Use Intl API for proper formatting +new Intl.DateTimeFormat('en-US').format(date); // 1/15/2024 +new Intl.DateTimeFormat('de-DE').format(date); // 15.1.2024 + +new Intl.NumberFormat('en-US', { + style: 'currency', + currency: 'USD' +}).format(1234.56); // $1,234.56 +``` + +**Pluralization**: +```javascript +// ❌ Bad: Assumes English pluralization +`${count} item${count !== 1 ? 's' : ''}` + +// ✅ Good: Use proper i18n library +t('items', { count }) // Handles complex plural rules +``` + +### Error Handling + +**Network errors**: +- Show clear error messages +- Provide retry button +- Explain what happened +- Offer offline mode (if applicable) +- Handle timeout scenarios + +```jsx +// Error states with recovery +{error && ( + +

Failed to load data. {error.message}

+ + +)} +``` + +**Form validation errors**: +- Inline errors near fields +- Clear, specific messages +- Suggest corrections +- Don't block submission unnecessarily +- Preserve user input on error + +**API errors**: +- Handle each status code appropriately + - 400: Show validation errors + - 401: Redirect to login + - 403: Show permission error + - 404: Show not found state + - 429: Show rate limit message + - 500: Show generic error, offer support + +**Graceful degradation**: +- Core functionality works without JavaScript +- Images have alt text +- Progressive enhancement +- Fallbacks for unsupported features + +### Edge Cases & Boundary Conditions + +**Empty states**: +- No items in list +- No search results +- No notifications +- No data to display +- Provide clear next action + +**Loading states**: +- Initial load +- Pagination load +- Refresh +- Show what's loading ("Loading your projects...") +- Time estimates for long operations + +**Large datasets**: +- Pagination or virtual scrolling +- Search/filter capabilities +- Performance optimization +- Don't load all 10,000 items at once + +**Concurrent operations**: +- Prevent double-submission (disable button while loading) +- Handle race conditions +- Optimistic updates with rollback +- Conflict resolution + +**Permission states**: +- No permission to view +- No permission to edit +- Read-only mode +- Clear explanation of why + +**Browser compatibility**: +- Polyfills for modern features +- Fallbacks for unsupported CSS +- Feature detection (not browser detection) +- Test in target browsers + +### Input Validation & Sanitization + +**Client-side validation**: +- Required fields +- Format validation (email, phone, URL) +- Length limits +- Pattern matching +- Custom validation rules + +**Server-side validation** (always): +- Never trust client-side only +- Validate and sanitize all inputs +- Protect against injection attacks +- Rate limiting + +**Constraint handling**: +```html + + + + Letters and numbers only, up to 100 characters + +``` + +### Accessibility Resilience + +**Keyboard navigation**: +- All functionality accessible via keyboard +- Logical tab order +- Focus management in modals +- Skip links for long content + +**Screen reader support**: +- Proper ARIA labels +- Announce dynamic changes (live regions) +- Descriptive alt text +- Semantic HTML + +**Motion sensitivity**: +```css +@media (prefers-reduced-motion: reduce) { + * { + animation-duration: 0.01ms !important; + animation-iteration-count: 1 !important; + transition-duration: 0.01ms !important; + } +} +``` + +**High contrast mode**: +- Test in Windows high contrast mode +- Don't rely only on color +- Provide alternative visual cues + +### Performance Resilience + +**Slow connections**: +- Progressive image loading +- Skeleton screens +- Optimistic UI updates +- Offline support (service workers) + +**Memory leaks**: +- Clean up event listeners +- Cancel subscriptions +- Clear timers/intervals +- Abort pending requests on unmount + +**Throttling & Debouncing**: +```javascript +// Debounce search input +const debouncedSearch = debounce(handleSearch, 300); + +// Throttle scroll handler +const throttledScroll = throttle(handleScroll, 100); +``` + +## Testing Strategies + +**Manual testing**: +- Test with extreme data (very long, very short, empty) +- Test in different languages +- Test offline +- Test slow connection (throttle to 3G) +- Test with screen reader +- Test keyboard-only navigation +- Test on old browsers + +**Automated testing**: +- Unit tests for edge cases +- Integration tests for error scenarios +- E2E tests for critical paths +- Visual regression tests +- Accessibility tests (axe, WAVE) + +**IMPORTANT**: Hardening is about expecting the unexpected. Real users will do things you never imagined. + +**NEVER**: +- Assume perfect input (validate everything) +- Ignore internationalization (design for global) +- Leave error messages generic ("Error occurred") +- Forget offline scenarios +- Trust client-side validation alone +- Use fixed widths for text +- Assume English-length text +- Block entire interface when one component errors + +## Verify Hardening + +Test thoroughly with edge cases: + +- **Long text**: Try names with 100+ characters +- **Emoji**: Use emoji in all text fields +- **RTL**: Test with Arabic or Hebrew +- **CJK**: Test with Chinese/Japanese/Korean +- **Network issues**: Disable internet, throttle connection +- **Large datasets**: Test with 1000+ items +- **Concurrent actions**: Click submit 10 times rapidly +- **Errors**: Force API errors, test all error states +- **Empty**: Remove all data, test empty states + +Remember: You're hardening for production reality, not demo perfection. Expect users to input weird data, lose connection mid-flow, and use your product in unexpected ways. Build resilience into every component. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-normalize.md b/dist/opencode-prefixed/.opencode/commands/i-normalize.md new file mode 100644 index 0000000..f68dc77 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-normalize.md @@ -0,0 +1,61 @@ +--- +description: Normalize design to match your design system and ensure consistency +--- + +Analyze and redesign the feature to perfectly match our design system standards, aesthetics, and established patterns. + +## Plan + +Before making changes, deeply understand the context: + +1. **Discover the design system**: Search for design system documentation, UI guidelines, component libraries, or style guides (grep for "design system", "ui guide", "style guide", etc.). Study it thoroughly until you understand: + - Core design principles and aesthetic direction + - Target audience and personas + - Component patterns and conventions + - Design tokens (colors, typography, spacing) + + **CRITICAL**: If something isn't clear, ask. Don't guess at design system principles. + +2. **Analyze the current feature**: Assess what works and what doesn't: + - Where does it deviate from design system patterns? + - Which inconsistencies are cosmetic vs. functional? + - What's the root cause—missing tokens, one-off implementations, or conceptual misalignment? + +3. **Create a normalization plan**: Define specific changes that will align the feature with the design system: + - Which components can be replaced with design system equivalents? + - Which styles need to use design tokens instead of hard-coded values? + - How can UX patterns match established user flows? + + **IMPORTANT**: Great design is effective design. Prioritize UX consistency and usability over visual polish alone. Think through the best possible experience for your use case and personas first. + +## Execute + +Systematically address all inconsistencies across these dimensions: + +- **Typography**: Use design system fonts, sizes, weights, and line heights. Replace hard-coded values with typographic tokens or classes. +- **Color & Theme**: Apply design system color tokens. Remove one-off color choices that break the palette. +- **Spacing & Layout**: Use spacing tokens (margins, padding, gaps). Align with grid systems and layout patterns used elsewhere. +- **Components**: Replace custom implementations with design system components. Ensure props and variants match established patterns. +- **Motion & Interaction**: Match animation timing, easing, and interaction patterns to other features. +- **Responsive Behavior**: Ensure breakpoints and responsive patterns align with design system standards. +- **Accessibility**: Verify contrast ratios, focus states, ARIA labels match design system requirements. +- **Progressive Disclosure**: Match information hierarchy and complexity management to established patterns. + +**NEVER**: +- Create new one-off components when design system equivalents exist +- Hard-code values that should use design tokens +- Introduce new patterns that diverge from the design system +- Compromise accessibility for visual consistency + +This is not an exhaustive list—apply judgment to identify all areas needing normalization. + +## Clean Up + +After normalization, ensure code quality: + +- **Consolidate reusable components**: If you created new components that should be shared, move them to the design system or shared UI component path. +- **Remove orphaned code**: Delete unused implementations, styles, or files made obsolete by normalization. +- **Verify quality**: Lint, type-check, and test according to repository guidelines. Ensure normalization didn't introduce regressions. +- **Ensure DRYness**: Look for duplication introduced during refactoring and consolidate. + +Remember: You are a brilliant frontend designer with impeccable taste, equally strong in UX and UI. Your attention to detail and eye for end-to-end user experience is world class. Execute with precision and thoroughness. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-onboard.md b/dist/opencode-prefixed/.opencode/commands/i-onboard.md new file mode 100644 index 0000000..e99d178 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-onboard.md @@ -0,0 +1,236 @@ +--- +description: Design or improve onboarding flows, empty states, and first-time user experiences. Helps users get started successfully and understand value quickly. +--- + +Create or improve onboarding experiences that help users understand, adopt, and succeed with the product quickly. + +## Assess Onboarding Needs + +Understand what users need to learn and why: + +1. **Identify the challenge**: + - What are users trying to accomplish? + - What's confusing or unclear about current experience? + - Where do users get stuck or drop off? + - What's the "aha moment" we want users to reach? + +2. **Understand the users**: + - What's their experience level? (Beginners, power users, mixed?) + - What's their motivation? (Excited and exploring? Required by work?) + - What's their time commitment? (5 minutes? 30 minutes?) + - What alternatives do they know? (Coming from competitor? New to category?) + +3. **Define success**: + - What's the minimum users need to learn to be successful? + - What's the key action we want them to take? (First project? First invite?) + - How do we know onboarding worked? (Completion rate? Time to value?) + +**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible. + +## Onboarding Principles + +Follow these core principles: + +### Show, Don't Tell +- Demonstrate with working examples, not just descriptions +- Provide real functionality in onboarding, not separate tutorial mode +- Use progressive disclosure - teach one thing at a time + +### Make It Optional (When Possible) +- Let experienced users skip onboarding +- Don't block access to product +- Provide "Skip" or "I'll explore on my own" options + +### Time to Value +- Get users to their "aha moment" ASAP +- Front-load most important concepts +- Teach 20% that delivers 80% of value +- Save advanced features for contextual discovery + +### Context Over Ceremony +- Teach features when users need them, not upfront +- Empty states are onboarding opportunities +- Tooltips and hints at point of use + +### Respect User Intelligence +- Don't patronize or over-explain +- Be concise and clear +- Assume users can figure out standard patterns + +## Design Onboarding Experiences + +Create appropriate onboarding for the context: + +### Initial Product Onboarding + +**Welcome Screen**: +- Clear value proposition (what is this product?) +- What users will learn/accomplish +- Time estimate (honest about commitment) +- Option to skip (for experienced users) + +**Account Setup**: +- Minimal required information (collect more later) +- Explain why you're asking for each piece of information +- Smart defaults where possible +- Social login when appropriate + +**Core Concept Introduction**: +- Introduce 1-3 core concepts (not everything) +- Use simple language and examples +- Interactive when possible (do, don't just read) +- Progress indication (step 1 of 3) + +**First Success**: +- Guide users to accomplish something real +- Pre-populated examples or templates +- Celebrate completion (but don't overdo it) +- Clear next steps + +### Feature Discovery & Adoption + +**Empty States**: +Instead of blank space, show: +- What will appear here (description + screenshot/illustration) +- Why it's valuable +- Clear CTA to create first item +- Example or template option + +Example: +``` +No projects yet +Projects help you organize your work and collaborate with your team. +[Create your first project] or [Start from template] +``` + +**Contextual Tooltips**: +- Appear at relevant moment (first time user sees feature) +- Point directly at relevant UI element +- Brief explanation + benefit +- Dismissable (with "Don't show again" option) +- Optional "Learn more" link + +**Feature Announcements**: +- Highlight new features when they're released +- Show what's new and why it matters +- Let users try immediately +- Dismissable + +**Progressive Onboarding**: +- Teach features when users encounter them +- Badges or indicators on new/unused features +- Unlock complexity gradually (don't show all options immediately) + +### Guided Tours & Walkthroughs + +**When to use**: +- Complex interfaces with many features +- Significant changes to existing product +- Industry-specific tools needing domain knowledge + +**How to design**: +- Spotlight specific UI elements (dim rest of page) +- Keep steps short (3-7 steps max per tour) +- Allow users to click through tour freely +- Include "Skip tour" option +- Make replayable (help menu) + +**Best practices**: +- Interactive > passive (let users click real buttons) +- Focus on workflow, not features ("Create a project" not "This is the project button") +- Provide sample data so actions work + +### Interactive Tutorials + +**When to use**: +- Users need hands-on practice +- Concepts are complex or unfamiliar +- High stakes (better to practice in safe environment) + +**How to design**: +- Sandbox environment with sample data +- Clear objectives ("Create a chart showing sales by region") +- Step-by-step guidance +- Validation (confirm they did it right) +- Graduation moment (you're ready!) + +### Documentation & Help + +**In-product help**: +- Contextual help links throughout interface +- Keyboard shortcut reference +- Search-able help center +- Video tutorials for complex workflows + +**Help patterns**: +- `?` icon near complex features +- "Learn more" links in tooltips +- Keyboard shortcut hints (`⌘K` shown on search box) + +## Empty State Design + +Every empty state needs: + +### What Will Be Here +"Your recent projects will appear here" + +### Why It Matters +"Projects help you organize your work and collaborate with your team" + +### How to Get Started +[Create project] or [Import from template] + +### Visual Interest +Illustration or icon (not just text on blank page) + +### Contextual Help +"Need help getting started? [Watch 2-min tutorial]" + +**Empty state types**: +- **First use**: Never used this feature (emphasize value, provide template) +- **User cleared**: Intentionally deleted everything (light touch, easy to recreate) +- **No results**: Search or filter returned nothing (suggest different query, clear filters) +- **No permissions**: Can't access (explain why, how to get access) +- **Error state**: Failed to load (explain what happened, retry option) + +## Implementation Patterns + +### Technical approaches: + +**Tooltip libraries**: Tippy.js, Popper.js +**Tour libraries**: Intro.js, Shepherd.js, React Joyride +**Modal patterns**: Focus trap, backdrop, ESC to close +**Progress tracking**: LocalStorage for "seen" states +**Analytics**: Track completion, drop-off points + +**Storage patterns**: +```javascript +// Track which onboarding steps user has seen +localStorage.setItem('onboarding-completed', 'true'); +localStorage.setItem('feature-tooltip-seen-reports', 'true'); +``` + +**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals. + +**NEVER**: +- Force users through long onboarding before they can use product +- Patronize users with obvious explanations +- Show same tooltip repeatedly (respect dismissals) +- Block all UI during tour (let users explore) +- Create separate tutorial mode disconnected from real product +- Overwhelm with information upfront (progressive disclosure!) +- Hide "Skip" or make it hard to find +- Forget about returning users (don't show initial onboarding again) + +## Verify Onboarding Quality + +Test with real users: + +- **Time to completion**: Can users complete onboarding quickly? +- **Comprehension**: Do users understand after completing? +- **Action**: Do users take desired next step? +- **Skip rate**: Are too many users skipping? (Maybe it's too long/not valuable) +- **Completion rate**: Are users completing? (If low, simplify) +- **Time to value**: How long until users get first value? + +Remember: You're a product educator with excellent teaching instincts. Get users to their "aha moment" as quickly as possible. Teach the essential, make it contextual, respect user time and intelligence. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-optimize.md b/dist/opencode-prefixed/.opencode/commands/i-optimize.md new file mode 100644 index 0000000..2e701f0 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-optimize.md @@ -0,0 +1,262 @@ +--- +description: Improve interface performance across loading speed, rendering, animations, images, and bundle size. Makes experiences faster and smoother. +--- + +Identify and fix performance issues to create faster, smoother user experiences. + +## Assess Performance Issues + +Understand current performance and identify problems: + +1. **Measure current state**: + - **Core Web Vitals**: LCP, FID/INP, CLS scores + - **Load time**: Time to interactive, first contentful paint + - **Bundle size**: JavaScript, CSS, image sizes + - **Runtime performance**: Frame rate, memory usage, CPU usage + - **Network**: Request count, payload sizes, waterfall + +2. **Identify bottlenecks**: + - What's slow? (Initial load? Interactions? Animations?) + - What's causing it? (Large images? Expensive JavaScript? Layout thrashing?) + - How bad is it? (Perceivable? Annoying? Blocking?) + - Who's affected? (All users? Mobile only? Slow connections?) + +**CRITICAL**: Measure before and after. Premature optimization wastes time. Optimize what actually matters. + +## Optimization Strategy + +Create systematic improvement plan: + +### Loading Performance + +**Optimize Images**: +- Use modern formats (WebP, AVIF) +- Proper sizing (don't load 3000px image for 300px display) +- Lazy loading for below-fold images +- Responsive images (`srcset`, `picture` element) +- Compress images (80-85% quality is usually imperceptible) +- Use CDN for faster delivery + +```html +Hero image +``` + +**Reduce JavaScript Bundle**: +- Code splitting (route-based, component-based) +- Tree shaking (remove unused code) +- Remove unused dependencies +- Lazy load non-critical code +- Use dynamic imports for large components + +```javascript +// Lazy load heavy component +const HeavyChart = lazy(() => import('./HeavyChart')); +``` + +**Optimize CSS**: +- Remove unused CSS +- Critical CSS inline, rest async +- Minimize CSS files +- Use CSS containment for independent regions + +**Optimize Fonts**: +- Use `font-display: swap` or `optional` +- Subset fonts (only characters you need) +- Preload critical fonts +- Use system fonts when appropriate +- Limit font weights loaded + +```css +@font-face { + font-family: 'CustomFont'; + src: url('/fonts/custom.woff2') format('woff2'); + font-display: swap; /* Show fallback immediately */ + unicode-range: U+0020-007F; /* Basic Latin only */ +} +``` + +**Optimize Loading Strategy**: +- Critical resources first (async/defer non-critical) +- Preload critical assets +- Prefetch likely next pages +- Service worker for offline/caching +- HTTP/2 or HTTP/3 for multiplexing + +### Rendering Performance + +**Avoid Layout Thrashing**: +```javascript +// ❌ Bad: Alternating reads and writes (causes reflows) +elements.forEach(el => { + const height = el.offsetHeight; // Read (forces layout) + el.style.height = height * 2; // Write +}); + +// ✅ Good: Batch reads, then batch writes +const heights = elements.map(el => el.offsetHeight); // All reads +elements.forEach((el, i) => { + el.style.height = heights[i] * 2; // All writes +}); +``` + +**Optimize Rendering**: +- Use CSS `contain` property for independent regions +- Minimize DOM depth (flatter is faster) +- Reduce DOM size (fewer elements) +- Use `content-visibility: auto` for long lists +- Virtual scrolling for very long lists (react-window, react-virtualized) + +**Reduce Paint & Composite**: +- Use `transform` and `opacity` for animations (GPU-accelerated) +- Avoid animating layout properties (width, height, top, left) +- Use `will-change` sparingly for known expensive operations +- Minimize paint areas (smaller is faster) + +### Animation Performance + +**GPU Acceleration**: +```css +/* ✅ GPU-accelerated (fast) */ +.animated { + transform: translateX(100px); + opacity: 0.5; +} + +/* ❌ CPU-bound (slow) */ +.animated { + left: 100px; + width: 300px; +} +``` + +**Smooth 60fps**: +- Target 16ms per frame (60fps) +- Use `requestAnimationFrame` for JS animations +- Debounce/throttle scroll handlers +- Use CSS animations when possible +- Avoid long-running JavaScript during animations + +**Intersection Observer**: +```javascript +// Efficiently detect when elements enter viewport +const observer = new IntersectionObserver((entries) => { + entries.forEach(entry => { + if (entry.isIntersecting) { + // Element is visible, lazy load or animate + } + }); +}); +``` + +### React/Framework Optimization + +**React-specific**: +- Use `memo()` for expensive components +- `useMemo()` and `useCallback()` for expensive computations +- Virtualize long lists +- Code split routes +- Avoid inline function creation in render +- Use React DevTools Profiler + +**Framework-agnostic**: +- Minimize re-renders +- Debounce expensive operations +- Memoize computed values +- Lazy load routes and components + +### Network Optimization + +**Reduce Requests**: +- Combine small files +- Use SVG sprites for icons +- Inline small critical assets +- Remove unused third-party scripts + +**Optimize APIs**: +- Use pagination (don't load everything) +- GraphQL to request only needed fields +- Response compression (gzip, brotli) +- HTTP caching headers +- CDN for static assets + +**Optimize for Slow Connections**: +- Adaptive loading based on connection (navigator.connection) +- Optimistic UI updates +- Request prioritization +- Progressive enhancement + +## Core Web Vitals Optimization + +### Largest Contentful Paint (LCP < 2.5s) +- Optimize hero images +- Inline critical CSS +- Preload key resources +- Use CDN +- Server-side rendering + +### First Input Delay (FID < 100ms) / INP (< 200ms) +- Break up long tasks +- Defer non-critical JavaScript +- Use web workers for heavy computation +- Reduce JavaScript execution time + +### Cumulative Layout Shift (CLS < 0.1) +- Set dimensions on images and videos +- Don't inject content above existing content +- Use `aspect-ratio` CSS property +- Reserve space for ads/embeds +- Avoid animations that cause layout shifts + +```css +/* Reserve space for image */ +.image-container { + aspect-ratio: 16 / 9; +} +``` + +## Performance Monitoring + +**Tools to use**: +- Chrome DevTools (Lighthouse, Performance panel) +- WebPageTest +- Core Web Vitals (Chrome UX Report) +- Bundle analyzers (webpack-bundle-analyzer) +- Performance monitoring (Sentry, DataDog, New Relic) + +**Key metrics**: +- LCP, FID/INP, CLS (Core Web Vitals) +- Time to Interactive (TTI) +- First Contentful Paint (FCP) +- Total Blocking Time (TBT) +- Bundle size +- Request count + +**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative. + +**NEVER**: +- Optimize without measuring (premature optimization) +- Sacrifice accessibility for performance +- Break functionality while optimizing +- Use `will-change` everywhere (creates new layers, uses memory) +- Lazy load above-fold content +- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first) +- Forget about mobile performance (often slower devices, slower connections) + +## Verify Improvements + +Test that optimizations worked: + +- **Before/after metrics**: Compare Lighthouse scores +- **Real user monitoring**: Track improvements for real users +- **Different devices**: Test on low-end Android, not just flagship iPhone +- **Slow connections**: Throttle to 3G, test experience +- **No regressions**: Ensure functionality still works +- **User perception**: Does it *feel* faster? + +Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-polish.md b/dist/opencode-prefixed/.opencode/commands/i-polish.md new file mode 100644 index 0000000..7184572 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-polish.md @@ -0,0 +1,195 @@ +--- +description: Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues that separate good from great. +--- + +**First**: Use the frontend-design skill for design principles and anti-patterns. + +Perform a meticulous final pass to catch all the small details that separate good work from great work. The difference between shipped and polished. + +## Pre-Polish Assessment + +Understand the current state and goals: + +1. **Review completeness**: + - Is it functionally complete? + - Are there known issues to preserve (mark with TODOs)? + - What's the quality bar? (MVP vs flagship feature?) + - When does it ship? (How much time for polish?) + +2. **Identify polish areas**: + - Visual inconsistencies + - Spacing and alignment issues + - Interaction state gaps + - Copy inconsistencies + - Edge cases and error states + - Loading and transition smoothness + +**CRITICAL**: Polish is the last step, not the first. Don't polish work that's not functionally complete. + +## Polish Systematically + +Work through these dimensions methodically: + +### Visual Alignment & Spacing + +- **Pixel-perfect alignment**: Everything lines up to grid +- **Consistent spacing**: All gaps use spacing scale (no random 13px gaps) +- **Optical alignment**: Adjust for visual weight (icons may need offset for optical centering) +- **Responsive consistency**: Spacing and alignment work at all breakpoints +- **Grid adherence**: Elements snap to baseline grid + +**Check**: +- Enable grid overlay and verify alignment +- Check spacing with browser inspector +- Test at multiple viewport sizes +- Look for elements that "feel" off + +### Typography Refinement + +- **Hierarchy consistency**: Same elements use same sizes/weights throughout +- **Line length**: 45-75 characters for body text +- **Line height**: Appropriate for font size and context +- **Widows & orphans**: No single words on last line +- **Hyphenation**: Appropriate for language and column width +- **Kerning**: Adjust letter spacing where needed (especially headlines) +- **Font loading**: No FOUT/FOIT flashes + +### Color & Contrast + +- **Contrast ratios**: All text meets WCAG standards +- **Consistent token usage**: No hard-coded colors, all use design tokens +- **Theme consistency**: Works in all theme variants +- **Color meaning**: Same colors mean same things throughout +- **Accessible focus**: Focus indicators visible with sufficient contrast +- **Tinted neutrals**: No pure gray or pure black—add subtle color tint (0.01 chroma) +- **Gray on color**: Never put gray text on colored backgrounds—use a shade of that color or transparency + +### Interaction States + +Every interactive element needs all states: + +- **Default**: Resting state +- **Hover**: Subtle feedback (color, scale, shadow) +- **Focus**: Keyboard focus indicator (never remove without replacement) +- **Active**: Click/tap feedback +- **Disabled**: Clearly non-interactive +- **Loading**: Async action feedback +- **Error**: Validation or error state +- **Success**: Successful completion + +**Missing states create confusion and broken experiences**. + +### Micro-interactions & Transitions + +- **Smooth transitions**: All state changes animated appropriately (150-300ms) +- **Consistent easing**: Use ease-out-quart/quint/expo for natural deceleration. Never bounce or elastic—they feel dated. +- **No jank**: 60fps animations, only animate transform and opacity +- **Appropriate motion**: Motion serves purpose, not decoration +- **Reduced motion**: Respects `prefers-reduced-motion` + +### Content & Copy + +- **Consistent terminology**: Same things called same names throughout +- **Consistent capitalization**: Title Case vs Sentence case applied consistently +- **Grammar & spelling**: No typos +- **Appropriate length**: Not too wordy, not too terse +- **Punctuation consistency**: Periods on sentences, not on labels (unless all labels have them) + +### Icons & Images + +- **Consistent style**: All icons from same family or matching style +- **Appropriate sizing**: Icons sized consistently for context +- **Proper alignment**: Icons align with adjacent text optically +- **Alt text**: All images have descriptive alt text +- **Loading states**: Images don't cause layout shift, proper aspect ratios +- **Retina support**: 2x assets for high-DPI screens + +### Forms & Inputs + +- **Label consistency**: All inputs properly labeled +- **Required indicators**: Clear and consistent +- **Error messages**: Helpful and consistent +- **Tab order**: Logical keyboard navigation +- **Auto-focus**: Appropriate (don't overuse) +- **Validation timing**: Consistent (on blur vs on submit) + +### Edge Cases & Error States + +- **Loading states**: All async actions have loading feedback +- **Empty states**: Helpful empty states, not just blank space +- **Error states**: Clear error messages with recovery paths +- **Success states**: Confirmation of successful actions +- **Long content**: Handles very long names, descriptions, etc. +- **No content**: Handles missing data gracefully +- **Offline**: Appropriate offline handling (if applicable) + +### Responsiveness + +- **All breakpoints**: Test mobile, tablet, desktop +- **Touch targets**: 44x44px minimum on touch devices +- **Readable text**: No text smaller than 14px on mobile +- **No horizontal scroll**: Content fits viewport +- **Appropriate reflow**: Content adapts logically + +### Performance + +- **Fast initial load**: Optimize critical path +- **No layout shift**: Elements don't jump after load (CLS) +- **Smooth interactions**: No lag or jank +- **Optimized images**: Appropriate formats and sizes +- **Lazy loading**: Off-screen content loads lazily + +### Code Quality + +- **Remove console logs**: No debug logging in production +- **Remove commented code**: Clean up dead code +- **Remove unused imports**: Clean up unused dependencies +- **Consistent naming**: Variables and functions follow conventions +- **Type safety**: No TypeScript `any` or ignored errors +- **Accessibility**: Proper ARIA labels and semantic HTML + +## Polish Checklist + +Go through systematically: + +- [ ] Visual alignment perfect at all breakpoints +- [ ] Spacing uses design tokens consistently +- [ ] Typography hierarchy consistent +- [ ] All interactive states implemented +- [ ] All transitions smooth (60fps) +- [ ] Copy is consistent and polished +- [ ] Icons are consistent and properly sized +- [ ] All forms properly labeled and validated +- [ ] Error states are helpful +- [ ] Loading states are clear +- [ ] Empty states are welcoming +- [ ] Touch targets are 44x44px minimum +- [ ] Contrast ratios meet WCAG AA +- [ ] Keyboard navigation works +- [ ] Focus indicators visible +- [ ] No console errors or warnings +- [ ] No layout shift on load +- [ ] Works in all supported browsers +- [ ] Respects reduced motion preference +- [ ] Code is clean (no TODOs, console.logs, commented code) + +**IMPORTANT**: Polish is about details. Zoom in. Squint at it. Use it yourself. The little things add up. + +**NEVER**: +- Polish before it's functionally complete +- Spend hours on polish if it ships in 30 minutes (triage) +- Introduce bugs while polishing (test thoroughly) +- Ignore systematic issues (if spacing is off everywhere, fix the system) +- Perfect one thing while leaving others rough (consistent quality level) + +## Final Verification + +Before marking as done: + +- **Use it yourself**: Actually interact with the feature +- **Test on real devices**: Not just browser DevTools +- **Ask someone else to review**: Fresh eyes catch things +- **Compare to design**: Match intended design +- **Check all states**: Don't just test happy path + +Remember: You have impeccable attention to detail and exquisite taste. Polish until it feels effortless, looks intentional, and works flawlessly. Sweat the details - they matter. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-quieter.md b/dist/opencode-prefixed/.opencode/commands/i-quieter.md new file mode 100644 index 0000000..bc9f92d --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-quieter.md @@ -0,0 +1,112 @@ +--- +description: Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact. +--- + +Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness. + +## MANDATORY PREPARATION + +### Context Gathering (Do This First) + +You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and everything else that a great human designer would need as well. + +Attempt to gather these from the current thread or codebase. + +1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and ask the user directly to clarify what you cannot infer. whether you got it right. +2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST ask the user directly to clarify what you cannot infer. clarifying questions first to complete your context. + +Do NOT proceed until you have answers. Guessing leads to generic design. + +### Use frontend-design skill + +Use the frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts. + +--- + +## Assess Current State + +Analyze what makes the design feel too intense: + +1. **Identify intensity sources**: + - **Color saturation**: Overly bright or saturated colors + - **Contrast extremes**: Too much high-contrast juxtaposition + - **Visual weight**: Too many bold, heavy elements competing + - **Animation excess**: Too much motion or overly dramatic effects + - **Complexity**: Too many visual elements, patterns, or decorations + - **Scale**: Everything is large and loud with no hierarchy + +2. **Understand the context**: + - What's the purpose? (Marketing vs tool vs reading experience) + - Who's the audience? (Some contexts need energy) + - What's working? (Don't throw away good ideas) + - What's the core message? (Preserve what matters) + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. + +## Plan Refinement + +Create a strategy to reduce intensity while maintaining impact: + +- **Color approach**: Desaturate or shift to more sophisticated tones? +- **Hierarchy approach**: Which elements should stay bold (very few), which should recede? +- **Simplification approach**: What can be removed entirely? +- **Sophistication approach**: How can we signal quality through restraint? + +**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision. + +## Refine the Design + +Systematically reduce intensity across these dimensions: + +### Color Refinement +- **Reduce saturation**: Shift from fully saturated to 70-85% saturation +- **Soften palette**: Replace bright colors with muted, sophisticated tones +- **Reduce color variety**: Use fewer colors more thoughtfully +- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule) +- **Gentler contrasts**: High contrast only where it matters most +- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness +- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead + +### Visual Weight Reduction +- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate +- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness +- **White space**: Increase breathing room, reduce density +- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely + +### Simplification +- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose +- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes +- **Reduce layering**: Flatten visual hierarchy where possible +- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows + +### Motion Reduction +- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing +- **Remove decorative animations**: Keep functional motion, remove flourishes +- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback +- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic +- **Remove animations entirely** if they're not serving a clear purpose + +### Composition Refinement +- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling +- **Align to grid**: Bring rogue elements back into systematic alignment +- **Even out spacing**: Replace extreme spacing variations with consistent rhythm + +**NEVER**: +- Make everything the same size/weight (hierarchy still matters) +- Remove all color (quiet ≠ grayscale) +- Eliminate all personality (maintain character through refinement) +- Sacrifice usability for aesthetics (functional elements still need clear affordances) +- Make everything small and light (some anchors needed) + +## Verify Quality + +Ensure refinement maintains quality: + +- **Still functional**: Can users still accomplish tasks easily? +- **Still distinctive**: Does it have character, or is it generic now? +- **Better reading**: Is text easier to read for extended periods? +- **Sophistication**: Does it feel more refined and premium? + +Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-simplify.md b/dist/opencode-prefixed/.opencode/commands/i-simplify.md new file mode 100644 index 0000000..c8ac2e4 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-simplify.md @@ -0,0 +1,131 @@ +--- +description: Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. +--- + +Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification. + +## MANDATORY PREPARATION + +### Context Gathering (Do This First) + +You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), and understanding what's truly essential vs nice-to-have for this product. + +Attempt to gather these from the current thread or codebase. + +1. If you don't find *exact* information and have to infer from existing design and functionality, you MUST STOP and ask the user directly to clarify what you cannot infer. whether you got it right. +2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST ask the user directly to clarify what you cannot infer. clarifying questions first to complete your context. + +Do NOT proceed until you have answers. Simplifying the wrong things destroys usability. + +### Use frontend-design skill + +Use the frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts. + +--- + +## Assess Current State + +Analyze what makes the design feel complex or cluttered: + +1. **Identify complexity sources**: + - **Too many elements**: Competing buttons, redundant information, visual clutter + - **Excessive variation**: Too many colors, fonts, sizes, styles without purpose + - **Information overload**: Everything visible at once, no progressive disclosure + - **Visual noise**: Unnecessary borders, shadows, backgrounds, decorations + - **Confusing hierarchy**: Unclear what matters most + - **Feature creep**: Too many options, actions, or paths forward + +2. **Find the essence**: + - What's the primary user goal? (There should be ONE) + - What's actually necessary vs nice-to-have? + - What can be removed, hidden, or combined? + - What's the 20% that delivers 80% of value? + +If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer. + +**CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. + +## Plan Simplification + +Create a ruthless editing strategy: + +- **Core purpose**: What's the ONE thing this should accomplish? +- **Essential elements**: What's truly necessary to achieve that purpose? +- **Progressive disclosure**: What can be hidden until needed? +- **Consolidation opportunities**: What can be combined or integrated? + +**IMPORTANT**: Simplification is hard. It requires saying no to good ideas to make room for great execution. Be ruthless. + +## Simplify the Design + +Systematically remove complexity across these dimensions: + +### Information Architecture +- **Reduce scope**: Remove secondary actions, optional features, redundant information +- **Progressive disclosure**: Hide complexity behind clear entry points (accordions, modals, step-through flows) +- **Combine related actions**: Merge similar buttons, consolidate forms, group related content +- **Clear hierarchy**: ONE primary action, few secondary actions, everything else tertiary or hidden +- **Remove redundancy**: If it's said elsewhere, don't repeat it here + +### Visual Simplification +- **Reduce color palette**: Use 1-2 colors plus neutrals, not 5-7 colors +- **Limit typography**: One font family, 3-4 sizes maximum, 2-3 weights +- **Remove decorations**: Eliminate borders, shadows, backgrounds that don't serve hierarchy or function +- **Flatten structure**: Reduce nesting, remove unnecessary containers—never nest cards inside cards +- **Remove unnecessary cards**: Cards aren't needed for basic layout; use spacing and alignment instead +- **Consistent spacing**: Use one spacing scale, remove arbitrary gaps + +### Layout Simplification +- **Linear flow**: Replace complex grids with simple vertical flow where possible +- **Remove sidebars**: Move secondary content inline or hide it +- **Full-width**: Use available space generously instead of complex multi-column layouts +- **Consistent alignment**: Pick left or center, stick with it +- **Generous white space**: Let content breathe, don't pack everything tight + +### Interaction Simplification +- **Reduce choices**: Fewer buttons, fewer options, clearer path forward (paradox of choice is real) +- **Smart defaults**: Make common choices automatic, only ask when necessary +- **Inline actions**: Replace modal flows with inline editing where possible +- **Remove steps**: Can signup be one step instead of three? Can checkout be simplified? +- **Clear CTAs**: ONE obvious next step, not five competing actions + +### Content Simplification +- **Shorter copy**: Cut every sentence in half, then do it again +- **Active voice**: "Save changes" not "Changes will be saved" +- **Remove jargon**: Plain language always wins +- **Scannable structure**: Short paragraphs, bullet points, clear headings +- **Essential information only**: Remove marketing fluff, legalese, hedging +- **Remove redundant copy**: No headers restating intros, no repeated explanations, say it once + +### Code Simplification +- **Remove unused code**: Dead CSS, unused components, orphaned files +- **Flatten component trees**: Reduce nesting depth +- **Consolidate styles**: Merge similar styles, use utilities consistently +- **Reduce variants**: Does that component need 12 variations, or can 3 cover 90% of cases? + +**NEVER**: +- Remove necessary functionality (simplicity ≠ feature-less) +- Sacrifice accessibility for simplicity (clear labels and ARIA still required) +- Make things so simple they're unclear (mystery ≠ minimalism) +- Remove information users need to make decisions +- Eliminate hierarchy completely (some things should stand out) +- Oversimplify complex domains (match complexity to actual task complexity) + +## Verify Simplification + +Ensure simplification improves usability: + +- **Faster task completion**: Can users accomplish goals more quickly? +- **Reduced cognitive load**: Is it easier to understand what to do? +- **Still complete**: Are all necessary features still accessible? +- **Clearer hierarchy**: Is it obvious what matters most? +- **Better performance**: Does simpler design load faster? + +## Document Removed Complexity + +If you removed features or options: +- Document why they were removed +- Consider if they need alternative access points +- Note any user feedback to monitor + +Remember: You have great taste and judgment. Simplification is an act of confidence - knowing what to keep and courage to remove the rest. As Antoine de Saint-Exupéry said: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/commands/i-teach-impeccable.md b/dist/opencode-prefixed/.opencode/commands/i-teach-impeccable.md new file mode 100644 index 0000000..c5904b6 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/commands/i-teach-impeccable.md @@ -0,0 +1,67 @@ +--- +description: One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines. +--- + +Gather design context for this project, then persist it for all future sessions. + +## Step 1: Explore the Codebase + +Before asking questions, thoroughly scan the project to discover what you can: + +- **README and docs**: Project purpose, target audience, any stated goals +- **Package.json / config files**: Tech stack, dependencies, existing design libraries +- **Existing components**: Current design patterns, spacing, typography in use +- **Brand assets**: Logos, favicons, color values already defined +- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales +- **Any style guides or brand documentation** + +Note what you've learned and what remains unclear. + +## Step 2: Ask UX-Focused Questions + +ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase: + +### Users & Purpose +- Who uses this? What's their context when using it? +- What job are they trying to get done? +- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.) + +### Brand & Personality +- How would you describe the brand personality in 3 words? +- Any reference sites or apps that capture the right feel? What specifically about them? +- What should this explicitly NOT look like? Any anti-references? + +### Aesthetic Preferences +- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.) +- Light mode, dark mode, or both? +- Any colors that must be used or avoided? + +### Accessibility & Inclusion +- Specific accessibility requirements? (WCAG level, known user needs) +- Considerations for reduced motion, color blindness, or other accommodations? + +Skip questions where the answer is already clear from the codebase exploration. + +## Step 3: Write Design Context + +Synthesize your findings and the user's answers into a `## Design Context` section: + +```markdown +## Design Context + +### Users +[Who they are, their context, the job to be done] + +### Brand Personality +[Voice, tone, 3-word personality, emotional goals] + +### Aesthetic Direction +[Visual tone, references, anti-references, theme] + +### Design Principles +[3-5 principles derived from the conversation that should guide all design decisions] +``` + +Write this section to opencode.json in the project root. If the file exists, append or update the Design Context section. + +Confirm completion and summarize the key design principles that will now guide all future work. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/skills/frontend-design/SKILL.md b/dist/opencode-prefixed/.opencode/skills/frontend-design/SKILL.md new file mode 100644 index 0000000..d49fe3c --- /dev/null +++ b/dist/opencode-prefixed/.opencode/skills/frontend-design/SKILL.md @@ -0,0 +1,127 @@ +--- +name: frontend-design +description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics. +license: Apache 2.0. Based on Anthropic's frontend-design skill. See NOTICE.md for attribution. +--- + +This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. + +## Design Direction + +Commit to a BOLD aesthetic direction: +- **Purpose**: What problem does this interface solve? Who uses it? +- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction. +- **Constraints**: Technical requirements (framework, performance, accessibility). +- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember? + +**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work—the key is intentionality, not intensity. + +Then implement working code that is: +- Production-grade and functional +- Visually striking and memorable +- Cohesive with a clear aesthetic point-of-view +- Meticulously refined in every detail + +## Frontend Aesthetics Guidelines + +### Typography +→ *Consult [typography reference](reference/typography.md) for scales, pairing, and loading strategies.* + +Choose fonts that are beautiful, unique, and interesting. Pair a distinctive display font with a refined body font. + +**DO**: Use a modular type scale with fluid sizing (clamp) +**DO**: Vary font weights and sizes to create clear visual hierarchy +**DON'T**: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults +**DON'T**: Use monospace typography as lazy shorthand for "technical/developer" vibes +**DON'T**: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated + +### Color & Theme +→ *Consult [color reference](reference/color-and-contrast.md) for OKLCH, palettes, and dark mode.* + +Commit to a cohesive palette. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. + +**DO**: Use modern CSS color functions (oklch, color-mix, light-dark) for perceptually uniform, maintainable palettes +**DO**: Tint your neutrals toward your brand hue—even a subtle hint creates subconscious cohesion +**DON'T**: Use gray text on colored backgrounds—it looks washed out; use a shade of the background color instead +**DON'T**: Use pure black (#000) or pure white (#fff)—always tint; pure black/white never appears in nature +**DON'T**: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds +**DON'T**: Use gradient text for "impact"—especially on metrics or headings; it's decorative rather than meaningful +**DON'T**: Default to dark mode with glowing accents—it looks "cool" without requiring actual design decisions + +### Layout & Space +→ *Consult [spatial reference](reference/spatial-design.md) for grids, rhythm, and container queries.* + +Create visual rhythm through varied spacing—not the same padding everywhere. Embrace asymmetry and unexpected compositions. Break the grid intentionally for emphasis. + +**DO**: Create visual rhythm through varied spacing—tight groupings, generous separations +**DO**: Use fluid spacing with clamp() that breathes on larger screens +**DO**: Use asymmetry and unexpected compositions; break the grid intentionally for emphasis +**DON'T**: Wrap everything in cards—not everything needs a container +**DON'T**: Nest cards inside cards—visual noise, flatten the hierarchy +**DON'T**: Use identical card grids—same-sized cards with icon + heading + text, repeated endlessly +**DON'T**: Use the hero metric layout template—big number, small label, supporting stats, gradient accent +**DON'T**: Center everything—left-aligned text with asymmetric layouts feels more designed +**DON'T**: Use the same spacing everywhere—without rhythm, layouts feel monotonous + +### Visual Details +**DO**: Use intentional, purposeful decorative elements that reinforce brand +**DON'T**: Use glassmorphism everywhere—blur effects, glass cards, glow borders used decoratively rather than purposefully +**DON'T**: Use rounded elements with thick colored border on one side—a lazy accent that almost never looks intentional +**DON'T**: Use sparklines as decoration—tiny charts that look sophisticated but convey nothing meaningful +**DON'T**: Use rounded rectangles with generic drop shadows—safe, forgettable, could be any AI output +**DON'T**: Use modals unless there's truly no better alternative—modals are lazy + +### Motion +→ *Consult [motion reference](reference/motion-design.md) for timing, easing, and reduced motion.* + +Focus on high-impact moments: one well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions. + +**DO**: Use motion to convey state changes—entrances, exits, feedback +**DO**: Use exponential easing (ease-out-quart/quint/expo) for natural deceleration +**DO**: For height animations, use grid-template-rows transitions instead of animating height directly +**DON'T**: Animate layout properties (width, height, padding, margin)—use transform and opacity only +**DON'T**: Use bounce or elastic easing—they feel dated and tacky; real objects decelerate smoothly + +### Interaction +→ *Consult [interaction reference](reference/interaction-design.md) for forms, focus, and loading patterns.* + +Make interactions feel fast. Use optimistic UI—update immediately, sync later. + +**DO**: Use progressive disclosure—start simple, reveal sophistication through interaction (basic options first, advanced behind expandable sections; hover states that reveal secondary actions) +**DO**: Design empty states that teach the interface, not just say "nothing here" +**DO**: Make every interactive surface feel intentional and responsive +**DON'T**: Repeat the same information—redundant headers, intros that restate the heading +**DON'T**: Make every button primary—use ghost buttons, text links, secondary styles; hierarchy matters + +### Responsive +→ *Consult [responsive reference](reference/responsive-design.md) for mobile-first, fluid design, and container queries.* + +**DO**: Use container queries (@container) for component-level responsiveness +**DO**: Adapt the interface for different contexts—don't just shrink it +**DON'T**: Hide critical functionality on mobile—adapt the interface, don't amputate it + +### UX Writing +→ *Consult [ux-writing reference](reference/ux-writing.md) for labels, errors, and empty states.* + +**DO**: Make every word earn its place +**DON'T**: Repeat information users can already see + +--- + +## The AI Slop Test + +**Critical quality check**: If you showed this interface to someone and said "AI made this," would they believe you immediately? If yes, that's the problem. + +A distinctive interface should make someone ask "how was this made?" not "which AI made this?" + +Review the DON'T guidelines above—they are the fingerprints of AI-generated work from 2024-2025. + +--- + +## Implementation Principles + +Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. + +Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices across generations. + +Remember: the model is capable of extraordinary creative work. Don't hold back—show what can truly be created when thinking outside the box and committing fully to a distinctive vision. \ No newline at end of file diff --git a/dist/opencode-prefixed/.opencode/skills/frontend-design/reference/color-and-contrast.md b/dist/opencode-prefixed/.opencode/skills/frontend-design/reference/color-and-contrast.md new file mode 100644 index 0000000..77aaf03 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/skills/frontend-design/reference/color-and-contrast.md @@ -0,0 +1,132 @@ +# Color & Contrast + +## Color Spaces: Use OKLCH + +**Stop using HSL.** Use OKLCH (or LCH) instead. It's perceptually uniform, meaning equal steps in lightness *look* equal—unlike HSL where 50% lightness in yellow looks bright while 50% in blue looks dark. + +```css +/* OKLCH: lightness (0-100%), chroma (0-0.4+), hue (0-360) */ +--color-primary: oklch(60% 0.15 250); /* Blue */ +--color-primary-light: oklch(85% 0.08 250); /* Same hue, lighter */ +--color-primary-dark: oklch(35% 0.12 250); /* Same hue, darker */ +``` + +**Key insight**: As you move toward white or black, reduce chroma (saturation). High chroma at extreme lightness looks garish. A light blue at 85% lightness needs ~0.08 chroma, not the 0.15 of your base color. + +## Building Functional Palettes + +### The Tinted Neutral Trap + +**Pure gray is dead.** Add a subtle hint of your brand hue to all neutrals: + +```css +/* Dead grays */ +--gray-100: oklch(95% 0 0); /* No personality */ +--gray-900: oklch(15% 0 0); + +/* Warm-tinted grays (add brand warmth) */ +--gray-100: oklch(95% 0.01 60); /* Hint of warmth */ +--gray-900: oklch(15% 0.01 60); + +/* Cool-tinted grays (tech, professional) */ +--gray-100: oklch(95% 0.01 250); /* Hint of blue */ +--gray-900: oklch(15% 0.01 250); +``` + +The chroma is tiny (0.01) but perceptible. It creates subconscious cohesion between your brand color and your UI. + +### Palette Structure + +A complete system needs: + +| Role | Purpose | Example | +|------|---------|---------| +| **Primary** | Brand, CTAs, key actions | 1 color, 3-5 shades | +| **Neutral** | Text, backgrounds, borders | 9-11 shade scale | +| **Semantic** | Success, error, warning, info | 4 colors, 2-3 shades each | +| **Surface** | Cards, modals, overlays | 2-3 elevation levels | + +**Skip secondary/tertiary unless you need them.** Most apps work fine with one accent color. Adding more creates decision fatigue and visual noise. + +### The 60-30-10 Rule (Applied Correctly) + +This rule is about **visual weight**, not pixel count: + +- **60%**: Neutral backgrounds, white space, base surfaces +- **30%**: Secondary colors—text, borders, inactive states +- **10%**: Accent—CTAs, highlights, focus states + +The common mistake: using the accent color everywhere because it's "the brand color." Accent colors work *because* they're rare. Overuse kills their power. + +## Contrast & Accessibility + +### WCAG Requirements + +| Content Type | AA Minimum | AAA Target | +|--------------|------------|------------| +| Body text | 4.5:1 | 7:1 | +| Large text (18px+ or 14px bold) | 3:1 | 4.5:1 | +| UI components, icons | 3:1 | 4.5:1 | +| Non-essential decorations | None | None | + +**The gotcha**: Placeholder text still needs 4.5:1. That light gray placeholder you see everywhere? Usually fails WCAG. + +### Dangerous Color Combinations + +These commonly fail contrast or cause readability issues: + +- Light gray text on white (the #1 accessibility fail) +- **Gray text on any colored background**—gray looks washed out and dead on color. Use a darker shade of the background color, or transparency +- Red text on green background (or vice versa)—8% of men can't distinguish these +- Blue text on red background (vibrates visually) +- Yellow text on white (almost always fails) +- Thin light text on images (unpredictable contrast) + +### Never Use Pure Gray or Pure Black + +Pure gray (`oklch(50% 0 0)`) and pure black (`#000`) don't exist in nature—real shadows and surfaces always have a color cast. Even a chroma of 0.005-0.01 is enough to feel natural without being obviously tinted. (See tinted neutrals example above.) + +### Testing + +Don't trust your eyes. Use tools: + +- [WebAIM Contrast Checker](https://webaim.org/resources/contrastchecker/) +- Browser DevTools → Rendering → Emulate vision deficiencies +- [Polypane](https://polypane.app/) for real-time testing + +## Theming: Light & Dark Mode + +### Dark Mode Is Not Inverted Light Mode + +You can't just swap colors. Dark mode requires different design decisions: + +| Light Mode | Dark Mode | +|------------|-----------| +| Shadows for depth | Lighter surfaces for depth (no shadows) | +| Dark text on light | Light text on dark (reduce font weight) | +| Vibrant accents | Desaturate accents slightly | +| White backgrounds | Never pure black—use dark gray (oklch 12-18%) | + +```css +/* Dark mode depth via surface color, not shadow */ +:root[data-theme="dark"] { + --surface-1: oklch(15% 0.01 250); + --surface-2: oklch(20% 0.01 250); /* "Higher" = lighter */ + --surface-3: oklch(25% 0.01 250); + + /* Reduce text weight slightly */ + --body-weight: 350; /* Instead of 400 */ +} +``` + +### Token Hierarchy + +Use two layers: primitive tokens (`--blue-500`) and semantic tokens (`--color-primary: var(--blue-500)`). For dark mode, only redefine the semantic layer—primitives stay the same. + +## Alpha Is A Design Smell + +Heavy use of transparency (rgba, hsla) usually means an incomplete palette. Alpha creates unpredictable contrast, performance overhead, and inconsistency. Define explicit overlay colors for each context instead. Exception: focus rings and interactive states where see-through is needed. + +--- + +**Avoid**: Relying on color alone to convey information. Creating palettes without clear roles for each color. Using pure black (#000) for large areas. Skipping color blindness testing (8% of men affected). diff --git a/dist/opencode-prefixed/.opencode/skills/frontend-design/reference/interaction-design.md b/dist/opencode-prefixed/.opencode/skills/frontend-design/reference/interaction-design.md new file mode 100644 index 0000000..10a7756 --- /dev/null +++ b/dist/opencode-prefixed/.opencode/skills/frontend-design/reference/interaction-design.md @@ -0,0 +1,123 @@ +# Interaction Design + +## The Eight Interactive States + +Every interactive element needs these states designed: + +| State | When | Visual Treatment | +|-------|------|------------------| +| **Default** | At rest | Base styling | +| **Hover** | Pointer over (not touch) | Subtle lift, color shift | +| **Focus** | Keyboard/programmatic focus | Visible ring (see below) | +| **Active** | Being pressed | Pressed in, darker | +| **Disabled** | Not interactive | Reduced opacity, no pointer | +| **Loading** | Processing | Spinner, skeleton | +| **Error** | Invalid state | Red border, icon, message | +| **Success** | Completed | Green check, confirmation | + +**The common miss**: Designing hover without focus, or vice versa. They're different. Keyboard users never see hover states. + +## Focus Rings: Do Them Right + +**Never `outline: none` without replacement.** It's an accessibility violation. Instead, use `:focus-visible` to show focus only for keyboard users: + +```css +/* Hide focus ring for mouse/touch */ +button:focus { + outline: none; +} + +/* Show focus ring for keyboard */ +button:focus-visible { + outline: 2px solid var(--color-accent); + outline-offset: 2px; +} +``` + +**Focus ring design**: +- High contrast (3:1 minimum against adjacent colors) +- 2-3px thick +- Offset from element (not inside it) +- Consistent across all interactive elements + +## Form Design: The Non-Obvious + +**Placeholders aren't labels**—they disappear on input. Always use visible `