Fetches perl-patterns from affaan-m/everything-claude-code and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/perl-patterns
Restart Cursor to activate perl-patterns. Access via /perl-patterns in your agent's command palette.
⚠
Security Notice
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.
Idiomatic Perl 5.36+ patterns and best practices for building robust, maintainable applications.
When to Activate
Writing new Perl code or modules
Reviewing Perl code for idiom compliance
Refactoring legacy Perl to modern standards
Designing Perl module architecture
Migrating pre-5.36 code to modern Perl
How It Works
Apply these patterns as a bias toward modern Perl 5.36+ defaults: signatures, explicit modules, focused error handling, and testable boundaries. The examples below are meant to be copied as starting points, then tightened for the actual app, dependency stack, and deployment model in front of you.
Core Principles
1. Use v5.36 Pragma
A single use v5.36 replaces the old boilerplate and enables strict, warnings, and subroutine signatures.
Use signatures for clarity and automatic arity checking.
usev5.36;# Good: Signatures with defaultssubconnect_db($host,$port=5432,$timeout=30){# $host is required, others have defaultsreturn DBI->connect("dbi:Pg:host=$host;port=$port",undef,undef,{ RaiseError =>1, PrintError =>0,});}# Good: Slurpy parameter for variable argssublog_message($level,@details){say"[$level] ". join(' ',@details);}# Bad: Manual argument unpackingsubconnect_db{my($host,$port,$timeout)=@_;$port//=5432;$timeout//=30;# ...}
3. Context Sensitivity
Understand scalar vs list context — a core Perl concept.
usev5.36;my@items=(1,2,3,4,5);my@copy=@items;# List context: all elementsmy$count=@items;# Scalar context: count (5)say"Items: ". scalar @items;# Force scalar context
4. Postfix Dereferencing
Use postfix dereference syntax for readability with nested structures.
usev5.36;my$data={ users =>[{ name =>'Alice', roles =>['admin','user']},{ name =>'Bob', roles =>['user']},],};# Good: Postfix dereferencingmy@users=$data->{users}->@*;my@roles=$data->{users}[0]{roles}->@*;my%first=$data->{users}[0]->%*;# Bad: Circumfix dereferencing (harder to read in chains)my@users=@{$data->{users}};my@roles=@{$data->{users}[0]{roles}};
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ 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.
Learning Path
1Basic: user stories, feature specs, status updates
