Auto-generated — not yet edited · only the numbers are verified
- TESIGN / RADAR
- REPOSITORY CARD
- emilkowalski/skills
emilkowalski/skills
Skills for Designers and Engineers.
RANKS All-time #180 · Rising 7d #32 · Rising 30d #27
AT A GLANCE
- LANGUAGE
- Markdown
- LICENSE
- MIT
- USAGE
- Use, change and redistribute, commercially too. Keep the notice.
- ACTIVITY
- last commit 26 days ago ()
- HOMEPAGE
- https://emilkowal.ski/skill
- REPOSITORY
- GitHub ↗
- CATEGORY
- AI
A summary, not legal advice.
README EXCERPT
Skills For Designers and Engineers For designers and engineers to help them build better user interfaces. Knowing whether you made a right choice when it comes to animations, or design in general, is hard. These skills aim to help you get to those right decisions faster. They are based on my years of experience working at companies like Vercel and Linear. All the skills here are a side-effect of domain-expertise. AI doesn’t replace such expertise, it amplifies what you can get out of it and makes you way better relative to others. So learn to code, design, or develop expertise in any other field. It’s extremely valuable. You can stay up to date with my skills here: Sign Up To The Newsletter Install Why use it? Agents don’t have great taste I have seen plenty of times that agents don’t pick the right ingredients for an animation. An ease-in easing for an enter animation when it’s supposed to be ease-out (here’s why). Or they choose a solid border instead of a semi-transparent shadow for your UIs. All these small things compound and make your interface either amazing, or just... not that great. As explained in Agents with Taste, these skills list all the little mistakes agents can po…
The opening of the GitHub README as stored, at most 1,200 characters. Markdown is not rendered.
TIMELINE
- Repository created
- Last push
- FIRST SEEN BY TESIGN ◌ BACK CATALOG
AI chooses the lists under the owner’s delegation. No human review is running in September 2026. Total stars, increases, cross-source signals, last updates and licences are shown as evidence. How ranks work →
If this repository gets editorial text (why, build, who, start, caveat) it becomes an edited entry. Until then the page shows only stored GitHub metadata and numbers.