market-references
Skill4 starsChanged 2 months agoNo licenceView on GitHub
Grounds a design review or redesign in real products instead of invented ideas: finds the best apps on the market for the same job, pulls their official App Store screenshots for free (Apple's public iTunes API, no account, no Mobbin), lays them out as one contact sheet per app, reads them, and maps each pattern to a concrete change in the project — every recommendation cites the app it comes from. Use when the user says "no inventes", "mira qué hacen otras apps", "referencias del mercado", "the best X app", wants Mobbin-style research without paying for Mobbin, or before a design review/redesign of an existing screen where the direction should come from proven products. Pairs with `taste-redesign` (craft fixes) and feeds `design-lab`/`prototype`; it does not decide the brand — the project's DESIGN.md does.
In this repository51 other files it gives its agents.
- agent-workflowSkill
- ai-product-strategySkill
- animationSkill
- animation-vocabularySkill
- api-design-principlesSkill
- apple-designSkill
- art-directionSkill
- ask-sonnerSkill
- automerge-gateSkill
- brainstormingSkill
- case-study-solverSkill
- changelog-generatorSkill
- codebase-designSkill
- competitor-analysisSkill
- customer-journey-mapSkill
- delegate-to-hermesSkill
- deploying-to-githubSkill
- design-labSkill
- design-mdSkill
- domain-modelingSkill
- email-builderSkill
- emil-design-engSkill
- error-handling-patternsSkill
- evolve-productSkill
- feature-to-outcomeSkill
- figma-reverse-engineeringSkill
- frontend-slidesSkill
- grillingSkill
- growth-loopsSkill
- linkedin-post-writerSkill
- maintaining-documentationSkill
- new-productSkill
- pm-interview-communicationSkill
- prd-writerSkill
- product-analyticsSkill
- product-launchSkill
- product-strategySkill
- prompt-clarifierSkill
- prototypeSkill
- sprint-planSkill
- stakeholder-mapSkill
- taste-redesignSkill
- taste-skillSkill
- tddSkill
- user-personasSkill
- vercel-composition-patternsSkill
- vercel-react-native-skillsSkill
- web-design-guidelinesSkill
- writing-for-agentsSkill
- writing-systemSkill
- x-thread-writerSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.