Agent skill / pproenca
Comprehensive UX/UI design guide for Chrome Extensions, optimized for Manifest V3. Contains 42 rules across 8 categories, prioritized by impact to guide extension UI development and code review.
Core file
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionchrome-extension-uiExecute the skills CLI command in your project's root directory to begin installation:
Package manager
npx skills add https://github.com/pproenca/dot-skills --skill chrome-extension-uiFetches chrome-extension-ui from pproenca/dot-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate chrome-extension-ui. Access via /chrome-extension-uiin your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Copy the command for your terminal
Package manager
npx skills add https://github.com/pproenca/dot-skills --skill chrome-extension-uiWorks with
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
pproenca/dot-skills
anthropics/claude-code
mblode/agent-skills
sickn33/antigravity-awesome-skills
github/awesome-copilot
leonxlnx/taste-skill
chrome-extension-ui reduced setup friction for our internal harness; good balance of opinion and flexibility.
chrome-extension-ui has been reliable in day-to-day use. Documentation quality is above average for community skills.
chrome-extension-ui fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added chrome-extension-ui from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
chrome-extension-ui fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: chrome-extension-ui is the kind of skill you can hand to a new teammate without a long onboarding doc.
chrome-extension-ui has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in chrome-extension-ui — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: chrome-extension-ui is focused, and the summary matches what you get after install.
I recommend chrome-extension-ui for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 34