@alire8za@guerriero_se@micka_design I plan to try borders (and shadows) soon to make it more card-like... we'll see if its able to play nice with extra elements used to make the shape
Cooked this up today for one of my apps :)
Inspired by @guerriero_se skewed folder tabs and @micka_design fluid functionalism motion / proximity hover🔥
@guerriero_se Looks so good! Are you willing to post a basic version of the code/CSS for this? I've been trying to create similar folder tabs but the angled version (which looks way better) is much tougher than straight vertical :/
things devs did today waiting for Fable 5 instead of touching any of the other 6 models they have access to:
- refreshed X and Claude 40 times
- "tested" if Opus 4.8 "feels different" now
- reread the export control statement
- refreshed again
@micka_design I threw a PR on the repo, whether just for inspiration/reference or actual use. If you find a shorter way to implement it, feel free - there were some edge cases I had to clean up using AI which left the components somewhat bulky
@micka_design I love the checkbox group animations in Fluid Functionalism, but the top-down expand animation when merging 2 groups (especially for large lists) always looked strange to me... so I gave it a shot at adding some merge/split animations that I think feel really smooth :)
@micka_design@base_ui@colmtuite Ok, I think I understand, but yeah maybe the problem section could be further expanded with examples or explanations (or a blog post).
Yeah your dark mode surfaces look incredible! I'm for sure implementing this system in my new app
@mattpocockuk Or maybe, good AX *is* having good DX?
…not relying only on brute force AI ability to search codebases, but having well architected context to enable efficient traversal (as humans we wouldn’t want to read every line of code every time we wanted to understand something either)
@KaiXCreator /grill-me skill by @mattpocockuk 😉
but seriously, probably the ability to build a vision and hold together many pieces in my head (discovering the bottleneck is how fast I can put it on paper/code and how concisely I can articulate it to others)
I’ve found that Composer 2 using /grill-me was able to one-shot major feature additions and refactors with much more thorough plans, as opposed to previously where I had to use more premium models to do the plan thinking (which still could miss things, and burned so much $$$)
@cursor_ai you should add a dedicated grill-mode with principles from @mattpocockuk ‘s /grill-me or /grill-with-docs skill to the IDE!
I not only find it much more effective than current plan mode which:
- even with thinking, only asks at most a couple clarifying questions before jumping to plan, way too eager
- and plan intent/language gets more and more messy with “corrections” as you iteratively try to modify it
I’m tired of repeatedly modifying plans with bullet points of corrections (which by definition limits my own imagination to only the factors brought up in the plan, rather than be forced to walk down the design tree and think through decisions).
My new workflow has become using agent/ask mode to grill me (which I actually enjoy ☺️ , and surfaces assumptions and clarifies intent so much more than I would have thought to give in my initial prompt)… and then use plan mode only as the final step before build now since it generates and enforces todos.
Wow, great timing! This is awesome because I was actually coming to this type of understanding on my own through heavy agent use that constantly had to relearn context and language. I was just about to implement something similar in my monorepo... like a colocated natural-language md file tree of design decisions and language that is quicker to traverse than reading all code AND theoretically easier to maintain / understand by both agents and humans...
...but now I get to use your version which I trust to be more robust, thanks haha🥳