Shared commands for AI coding agents (Cursor, Claude, and more)
Generic AI Coding Agent commands for research, planning, implementation, and commits
Installation • Commands • Workflow • Troubleshooting • Contributing
- Features
- Quick Start
- Installation
- Workflow
- Commands
- Post-Installation
- Requirements
- Troubleshooting
- Contributing
- License
|
Understand codebase structure and patterns instantly with AI-powered analysis |
Create detailed implementation plans following best practices |
|
Execute plans with automatic migrations, tests, and validation |
Generate semantic commits that follow conventional commit standards |
- ✅ Multi-Agent Support - Works with Cursor, Claude, and more
- ✅ Zero Configuration - Interactive installer handles everything
- ✅ Project-Aware - Respects your project's rules and architecture
- ✅ Workflow Integration - Commands designed to work together seamlessly
- ✅ MIT Licensed - Free for personal and commercial use
Install commands with a single command:
npx @integral-de/agent-resources installThe installer will:
- ✓ Detect which AI agents you have installed (Cursor, Claude)
- ✓ Let you choose which agents to install for
- ✓ Automatically copy commands to the correct locations
- ✓ Create a configuration file to track your installation
- Node.js 18 or higher
- At least one supported AI agent installed:
- Cursor (installs to
~/.cursor/) - Claude (installs to
~/.claude/)
- Cursor (installs to
Simply run:
npx @integral-de/agent-resources installThe interactive installer will guide you through the process.
After installation, verify commands are available:
For Cursor Users:
- Commands appear as custom rules in your workspace
For Claude Users:
- Type
/integral:to see available commands
These commands work together in a natural development cycle:
graph LR
A[🔍 Research] --> B[📝 Plan]
B --> C[🚀 Implement]
C --> D[📦 Commit]
D --> A
style A fill:#e1f5ff
style B fill:#fff4e1
style C fill:#e8f5e9
style D fill:#f3e5f5
/integral:research-codebaseAnalyzes your codebase to understand domain architecture, business logic, and implementation patterns.
/integral:generate-plan TICKET-123 add user notificationsGenerates a detailed implementation plan with requirements, architecture decisions, and file changes.
/integral:implement-plan @docs/plans/TICKET-123-user-notifications.plan.mdExecutes the plan following project rules, generating migrations, tests, and validation automatically.
/integral:commit-and-pushCreates a conventional commit and pushes to remote with semantic versioning support.
Purpose: Research codebase structure and patterns to understand domain architecture, business logic, and implementation patterns.
Usage:
/integral:research-codebaseWhat It Does:
- 🔍 Analyzes project structure and architecture
- 📊 Identifies domain patterns and business logic
- 🏗️ Maps dependencies and relationships
- 📝 Generates synthesized findings with file references
Output:
docs/research/{topic}.research.md
Best For:
- New team members onboarding
- Understanding legacy code
- Planning large refactors
- Documenting system architecture
Purpose: Generate software implementation plans through structured requirement gathering.
Usage:
# Basic usage
/integral:generate-plan implement user authentication
# With ticket reference
/integral:generate-plan TICKET-456 add payment processing
# Complex feature
/integral:generate-plan TASK-789 multi-tenant support with data isolationWhat It Does:
- 📝 Gathers requirements interactively
- 🎯 Defines clear objectives and success criteria
- 🏗️ Plans architecture and file changes
⚠️ Identifies risks and considerations- ✅ Creates validation checklist
Output:
docs/plans/{ticket-id}-{feature-name}.plan.md
Plan Sections:
- Overview & Requirements
- Architecture Decisions
- Implementation Steps
- File Changes
- Testing Strategy
- Validation Checklist
Purpose: Execute implementation plans following project rules and guidelines.
Usage:
# Implement a plan
/integral:implement-plan @docs/plans/user-authentication.plan.md
# With optional research context
/integral:implement-plan @docs/plans/user-auth.plan.md @docs/research/auth-patterns.research.mdWhat It Does:
- 📖 Reads plan and optional research files
- 🏗️ Follows project architecture rules
- 🗄️ Generates database migrations automatically
- 🧪 Runs tests and linting
- ✅ Validates implementation against plan
- 📊 Reports progress and completion
Features:
- Smart Implementation - Follows your project's rules and patterns
- Auto Migrations - Generates Liquibase/Flyway migrations
- Test Integration - Runs relevant tests after changes
- Validation - Ensures all plan requirements are met
- Rollback Support - Guides you if issues occur
Best Practices:
- Run research before complex implementations
- Review generated migrations before applying
- Check validation report before committing
Purpose: Create a conventional commit for staged changes and push to the remote repository.
Usage:
/integral:commit-and-pushWhat It Does:
- 📊 Analyzes staged changes with
git diff - 📝 Generates conventional commit message
- 🎯 Determines commit type (feat, fix, chore, etc.)
- 💬 Creates meaningful commit description
- ✅ Asks for approval before pushing
- 🚀 Pushes to remote repository
Commit Types:
feat:New featuresfix:Bug fixeschore:Maintenance tasksdocs:Documentation changesrefactor:Code refactoringtest:Test additions/changesstyle:Code style changes
Example Output:
feat(auth): add user authentication with JWT tokens
- Implement JWT token generation and validation
- Add login and logout endpoints
- Create authentication middleware
- Add user session managementAfter installation, commands are immediately available in your selected agents.
Commands are available as custom rules in your workspace. Simply start typing /integral: to see available commands.
Available Commands:
/integral:research-codebase- Research codebase structure and patterns/integral:generate-plan- Create implementation plans/integral:implement-plan- Execute implementation plans/integral:commit-and-push- Generate conventional commits and push
Use commands with the / prefix in any conversation:
/integral:research-codebase
/integral:generate-plan TICKET-123 feature description
/integral:implement-plan @docs/plans/plan-file.plan.md
/integral:commit-and-push| Requirement | Version | Purpose |
|---|---|---|
| Node.js | ≥ 18.0.0 | Runtime environment |
| npm | Latest | Package installation |
| AI Agent | Any | Cursor, Claude, etc. |
Supported AI Agents:
- ✅ Cursor (Desktop app)
- ✅ Claude (CLI or Desktop)
- 🔜 More agents coming soon
Symptom: Installer says "No supported agents found"
Solutions:
- Ensure you have Cursor or Claude installed
- Check that the agent's directory exists:
- Cursor:
~/.cursor/ - Claude:
~/.claude/
- Cursor:
- Run the agent at least once to create its configuration directory
- Try running installer with verbose output:
DEBUG=* npx @integral-de/agent-resources install
Symptom: Installation script exits with error
Solutions:
- Check write permissions to your home directory:
ls -la ~/.cursor/ ls -la ~/.claude/
- Try running with elevated permissions (macOS/Linux):
sudo npx @integral-de/agent-resources install
- Check the error message for specific issues
- Clear npm cache and retry:
npm cache clean --force npx @integral-de/agent-resources install
Symptom: Commands don't appear after installation
Solutions:
- Restart your AI agent - Most agents require restart to load new commands
- Check that files were copied correctly:
- Cursor:
~/.cursor/commands/integral/ - Claude:
~/.claude/commands/integral/
- Cursor:
- Verify file contents are not corrupted:
cat ~/.cursor/commands/integral/research-codebase.md - Reinstall commands:
npx @integral-de/agent-resources install
Symptom: Commands run but fail during execution
Solutions:
- Ensure you're in a git repository (for commit-and-push)
- Check that plan files exist (for implement-plan)
- Verify your project has a
docs/directory - Check agent logs for detailed error messages
- Try running in a fresh terminal session
- 📖 Check the GitHub Issues
- 💬 Open a new issue with detailed error information
- 📧 Contact maintainers for support
We welcome contributions! Here's how you can help:
- 🐛 Report Bugs - Open an issue with detailed reproduction steps
- 💡 Suggest Features - Share ideas for new commands or improvements
- 📝 Improve Documentation - Fix typos, add examples, clarify instructions
- 🔧 Submit Pull Requests - Add features or fix bugs
-
Clone the repository:
git clone https://github.com/Integral-de/agent-resources.git cd agent-resources -
Install dependencies:
npm install
-
Test locally:
npm link integral-agent-resources install
-
Make your changes:
- Commands:
integral/commands/ - Installers:
src/installers/ - CLI:
bin/cli.js
- Commands:
-
Test your changes:
npm test -
Submit a pull request
- ✅ Use ES modules (
import/export) - ✅ Follow existing code style
- ✅ Add comments for complex logic
- ✅ Test with both Cursor and Claude
- ✅ Update README if adding features
- Create command file in
integral/commands/{command-name}.md - Follow existing command structure
- Add command to installer in
src/installers/ - Update README with command documentation
- Test with target AI agents
- Fork the repository
- Create a feature branch (
feat/amazing-feature) - Commit your changes (use conventional commits)
- Push to your branch
- Open a pull request with detailed description
All contributions go through code review. We look for:
- ✅ Code quality and readability
- ✅ Test coverage
- ✅ Documentation updates
- ✅ Compatibility with supported agents
MIT License - see the LICENSE file for details.
Made with ❤️ by Integral
If you find this project useful, please consider giving it a star ⭐