magento-feature-developer
Implements business requirements as scalable, maintainable Magento 2 features. Use when developing custom functionality, implementing business logic, creating integrations, or building complex features. Masters service contracts, repository patterns, and enterprise-grade feature implementation.
- Installs
- 190
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/maxnorm/magento2-agent-skills --skill magento-feature-developer- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads magento-feature-developer automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Magento 2 Feature Developer
Expert specialist in translating business requirements into robust, scalable technical solutions within the Magento ecosystem following Adobe Commerce best practices.
When to Use
- Implementing new business features
- Developing custom functionality
- Creating integrations with third-party systems
- Building complex business logic
- Extending existing Magento functionality
Feature Development Process
1. Discovery & Planning
- Requirements Analysis: Break down business requirements into technical specifications
- Stakeholder Interviews: Gather comprehensive requirements from business users
- Technical Analysis: Assess existing system capabilities and constraints
- Impact Assessment: Evaluate effects on performance, security, and scalability
- Resource Planning: Estimate development timeline and requirements
2. Architecture Design
- System Design: Create high-level architecture diagrams and component relationships
- Database Design: Plan entity relationships, indexes, and data migration strategies
- API Design: Define service contracts and data transfer objects
- Integration Points: Identify touchpoints with existing modules and third-party systems
- Performance Planning: Design for scalability and optimal response times
3. Implementation Strategy
- Module Structure: Organize code following Magento's module conventions
- Service Contracts: Implement clean API interfaces for feature contracts
- Repository Pattern: Build data access layers using Magento's repository pattern
- Configuration Management: Implement admin configuration options where appropriate
- Error Handling: Build robust error handling and logging mechanisms
4. Quality Assurance
- Unit Testing: Write comprehensive PHPUnit tests for business logic
- Integration Testing: Test feature integration with core Magento functionality
- Performance Testing: Ensure features don't degrade system performance
- Security Review: Validate security compliance and data protection
Common Feature Types
E-commerce Features
- Custom Product Types: Implement specialized product configurations
- Pricing Rules: Build complex pricing and discount logic
- Inventory Management: Create advanced inventory tracking and allocation
- Order Processing: Implement custom order workflows and fulfillment
- Customer Features: Build loyalty programs, wishlists, and customer dashboards
Administrative Features
- Reporting & Analytics: Create custom reports and data visualization
- Bulk Operations: Implement mass actions and data import/export
- Workflow Automation: Build automated business processes
- Content Management: Create custom content types and management interfaces
- User Management: Implement role-based access and permission systems
Integration Features
- Third-party APIs: Connect with external services and platforms
- Data Synchronization: Build real-time or batch data sync processes
- Webhook Integration: Implement event-driven integrations
- File Processing: Handle document uploads, processing, and storage
- Notification Systems: Build email, SMS, and push notification features
Development Patterns
Service Contracts
- Create interfaces in
Api/directory - Implement clean API interfaces
- Use data transfer objects (DTOs) for data exchange
- Maintain backward compatibility
Repository Pattern
- Separate data access from business logic
- Use repositories for all data operations
- Implement proper error handling
- Support transactions where needed
Event/Observer Pattern
- Dispatch events for extensibility
- Implement observers for loose coupling
- Use proper event naming conventions
- Document event data structure
Plugin System
- Use plugins to extend functionality
- Prefer before/after plugins over around plugins
- Document plugin execution order
Best Practices
Code Organization
- Modular Design: Keep features self-contained within dedicated modules
- Interface Segregation: Use small, focused interfaces
- Dependency Injection: Leverage Magento's DI container
- Configuration Management: Use XML configurations for flexibility
- Namespace Organization: Follow PSR-4 autoloading standards
Performance Considerations
- Lazy Loading: Implement lazy loading for expensive operations
- Caching Strategy: Utilize appropriate cache types
- Database Optimization: Use efficient queries and proper indexing
- Frontend Optimization: Minimize JavaScript/CSS footprint
- Resource Management: Monitor memory usage and execution time
Security
- Input Validation: Implement comprehensive input validation
- Output Escaping: Ensure proper output sanitization
- CSRF Protection: Implement form key validation
- Access Control: Enforce proper permission checking
- Data Encryption: Handle sensitive data appropriately
Maintenance & Extensibility
- Backward Compatibility: Ensure features work across Magento version upgrades
- Extension Points: Provide hooks for other developers to extend features
- Configuration Options: Allow customization without code modifications
- Migration Scripts: Provide smooth upgrade paths
- Documentation: Maintain comprehensive technical and user documentation
Testing Strategy
- Unit Tests: Test individual classes and methods
- Integration Tests: Test module integration with core
- Functional Tests: End-to-end test scenarios
- Performance Tests: Validate performance under load
- Security Tests: Test authentication, authorization, and data protection
References
Focus on creating features that meet immediate business needs while providing a foundation for future growth and customization.
FAQ
What does the magento-feature-developer skill do?
Implements business requirements as scalable, maintainable Magento 2 features. Use when developing custom functionality, implementing business logic, creating integrations, or building complex features. Masters service contracts, repository patterns, and enterprise-grade feature implementation.
How do I install magento-feature-developer?
Run npx skills add https://github.com/maxnorm/magento2-agent-skills --skill magento-feature-developer in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/magento-feature-developer/ (personal) or .claude/skills/magento-feature-developer/ (project).
Which AI agents can use magento-feature-developer?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is magento-feature-developer safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains magento-feature-developer?
It is published by maxnorm in maxnorm/magento2-agent-skills. It has 190 recorded installs.
More from maxnorm/magento2-agent-skills
magento-hyva-specialist
maxnorm/magento2-agent-skills
Develops high-performance Magento 2 storefronts using Hyvä theme framework. Use when working with Hyvä themes, Alpine.js, Tailwind CSS, or modern frontend development. Masters Alpine.js architecture, Tailwind CSS styling, and performance optimization for blazing-fast e-commerce experiences.
magento-code-reviewer
maxnorm/magento2-agent-skills
Reviews Magento 2 code for quality, security, performance, and compliance with PSR-12 and Magento coding standards. Use proactively when reviewing code, before commits, during pull requests, or when ensuring code quality. Enforces strict type declarations, proper dependency injection, security best practices, and performance optimization.
magento-module-developer
maxnorm/magento2-agent-skills
Creates robust, maintainable, and extensible Magento 2 modules following enterprise architecture patterns. Use when developing custom modules, implementing new functionality, creating extensions, or building Magento 2 components. Masters dependency injection, service contracts, repository patterns, and module architecture.
magento-performance-analyst
maxnorm/magento2-agent-skills
Conducts comprehensive Magento 2 performance analysis and optimization. Use when analyzing performance bottlenecks, profiling applications, optimizing database queries, or improving system scalability. Masters profiling tools, database optimization, and enterprise-scale performance tuning.
magento-frontend-developer
maxnorm/magento2-agent-skills
Creates comprehensive Magento 2 frontend solutions. Use when developing frontend features, working with layout XML, templates, JavaScript, or responsive design. Masters layout XML, template development, JavaScript integration, and performance optimization across all Magento frontend technologies.
magento-xml-specialist
maxnorm/magento2-agent-skills
Creates XML configurations for Magento 2 including layout XML, dependency injection, system configuration, and module definition. Use when working with XML configuration files, layout XML, di.xml, or system.xml. Masters XML schema design, validation, and configuration management.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.