Rust ownership and lifetime error diagnosis through design-first questioning.
Create detailed user stories, acceptance criteria, and feature specs
Example: Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example: Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example: Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example: Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Submit your Claude Code skill and start earning
epx add zhanghandong/rust-skills --skill m01-ownershipCompatible with
Supported agents
Covers seven critical error codes (E0382, E0597, E0506, E0507, E0515, E0716, E0106) with root-cause questions rather than quick fixes
Guides developers to ask \"who should own this data?\" before applying syntax solutions, distinguishing between symptom fixes and design restructuring
Provides decision trees for choosing between move semantics, borrowing, cloning, and smart pointers (Arc, Rc, Cow) based on d
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionm01-ownershipExecute the skills CLI command in your project's root directory to begin installation:
epx add zhanghandong/rust-skills --skill m01-ownershipFetches m01-ownership 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/m01-ownership
Restart Cursor to activate m01-ownership. Access via /m01-ownershipin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
premortem
parcadei/continuous-claude-v3 · Productivity · same category
travel-planner
ailabs-393/ai-labs-claude-skills · Productivity · same category
xauusd-trading
huynguyen03dev/xauusd-trading · Productivity · same category
reverse-engineering-tools
gmh5225/awesome-game-security · Productivity · same category
sports-betting-analyzer
onewave-ai/claude-skills · Productivity · same category
lua
mindrally/skills · Productivity · same category
m01-ownership fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: m01-ownership is focused, and the summary matches what you get after install.
m01-ownership has been reliable in day-to-day use. Documentation quality is above average for community skills.
m01-ownership is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
m01-ownership reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend m01-ownership for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
m01-ownership is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: m01-ownership is the kind of skill you can hand to a new teammate without a long onboarding doc.
m01-ownership has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: m01-ownership is focused, and the summary matches what you get after install.
showing 1-10 of 64