By nmhjklnm
Personal development toolkit with desktop notifications, code review agents, and design principles
Conduct a comprehensive code review of the pending changes on the current branch based on the Pragmatic Quality framework.
Complete a design review of the pending changes on the current branch
Complete a security review of the pending changes on the current branch
Use this agent when you need to conduct a comprehensive design review on front-end pull requests or general UI changes. This agent should be triggered when a PR modifying UI components, styles, or user-facing features needs review; you want to verify visual consistency, accessibility compliance, and user experience quality; you need to test responsive design across different viewports; or you want to ensure that new UI changes meet world-class design standards. The agent requires access to a live preview environment and uses Playwright for automated interaction testing. Example - "Review the design changes in PR 234"
Use this agent when you need a thorough code review that balances engineering excellence with development velocity. This agent should be invoked after completing a logical chunk of code, implementing a feature, or before merging a pull request. The agent focuses on substantive issues but also addresses style. Examples: - <example> Context: After implementing a new API endpoint user: "I've added a new user authentication endpoint" assistant: "I'll review the authentication endpoint implementation using the pragmatic-code-review agent" <commentary> Since new code has been written that involves security-critical functionality, use the pragmatic-code-review agent to ensure it meets quality standards. </commentary> </example> - <example> Context: After refactoring a complex service user: "I've refactored the payment processing service to improve performance" assistant: "Let me review these refactoring changes with the pragmatic-code-review agent" <commentary> Performance-critical refactoring needs review to ensure improvements don't introduce regressions. </commentary> </example> - <example> Context: Before merging a feature branch user: "The new dashboard feature is complete and ready for review" assistant: "I'll conduct a comprehensive review using the pragmatic-code-review agent before we merge" <commentary> Complete features need thorough review before merging to main branch. </commentary> </example>
Uses power tools
Uses Bash, Write, or Edit tools
Runs pre-commands
Contains inline bash commands via ! syntax
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
My personal Claude Code plugin - a self-hosted collection of preferred configs, workflows, and development practices.
Get macOS notifications when Claude Code needs your input or completes tasks:
/suiying:code-review - Comprehensive code review/suiying:design-review - Architecture and design review/suiying:security-review - Security-focused reviewterminal-notifier (for desktop notifications)
brew install terminal-notifier
The easiest way to install:
# Add the marketplace
/plugin marketplace add nmhjklnm/suiying-marketplace
# Install the plugin
/plugin install suiying@suiying-marketplace
That's it! The plugin will be automatically installed and ready to use.
For local development and testing:
# Clone the repository
git clone https://github.com/nmhjklnm/suiying-marketplace.git
# Create symlink to Claude plugins directory
ln -s "$(pwd)/suiying-marketplace" ~/.claude/plugins/suiying
# Reload plugin in Claude Code after making changes
suiying-plugin/
├── .claude-plugin/
│ ├── plugin.json # Plugin metadata
│ └── marketplace.json # Marketplace config
├── commands/ # Custom slash commands
├── skills/ # Auto-activating knowledge
├── agents/ # Specialized subagents
├── hooks/ # Event-driven automation
│ └── hooks.json # Desktop notification hooks
└── scripts/ # Helper utilities
└── ccnotify.py # Notification script
After installation, all commands, skills, and agents become available automatically.
# Code review commands
/suiying:code-review [file-or-directory]
/suiying:design-review [file-or-directory]
/suiying:security-review [file-or-directory]
Desktop notifications work automatically through hooks:
To test if notifications are working:
# Start Claude Code
claude
# Run a quick test
after 1 second, echo 'hello'
You should see a macOS notification appear!
This is a personal plugin, but feel free to fork and adapt for your own needs!
MIT - see LICENSE file for details
npx claudepluginhub nmhjklnm/suiying-marketplaceDesktop notifications showing what Claude Code is working on - stay informed even when the terminal is not in focus. Optional sound alerts and AI summaries
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and sends a personalized growth report.
Life Agents and skills for personal life management.
You work with me (Claude) - I guide your workflow and suggest next actions.
Harness-native ECC plugin for engineering teams - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.