Rust naming, formatting, and best-practice guidelines covering 50 core rules.
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
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add zhanghandong/rust-skills --skill coding-guidelinesCompatible with
Supported agents
Covers naming conventions (no get_ prefix, iterator patterns, conversion methods), data types (newtypes, slice patterns, pre-allocation), and string handling (prefer bytes for ASCII, use Cow<str> when appropriate)
Error handling guidance includes ? propagation over try!() , meaningful lifetime names, and lock ordering for concurrency safety
Includes deprecation mappings (e.g., lazy_static! to OnceLock
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncoding-guidelinesExecute the skills CLI command in your project's root directory to begin installation:
epx add zhanghandong/rust-skills --skill coding-guidelinesFetches coding-guidelines from zhanghandong/rust-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:
.cursor/skills/coding-guidelines
Restart Cursor to activate coding-guidelines. Access via /coding-guidelinesin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
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.
frontend-design
anthropics/claude-code · Frontend · same category
high-end-visual-design
leonxlnx/taste-skill · Frontend · same category
senior-frontend
alirezarezvani/claude-skills · Frontend · same category
frontend-security
schalkneethling/webdev-agent-skills · Frontend · same category
tailwindcss
hairyf/skills · Frontend · same category
ubiquitous-language
mattpocock/skills · Frontend · same category
I recommend coding-guidelines for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in coding-guidelines — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
coding-guidelines has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: coding-guidelines is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend coding-guidelines for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: coding-guidelines is focused, and the summary matches what you get after install.
coding-guidelines has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: coding-guidelines is focused, and the summary matches what you get after install.
Keeps context tight: coding-guidelines is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend coding-guidelines for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 74