WithSeismic MCP
# ://CONTRIBUTING_TO_WITHSEISMIC-MCP
```
INITIALIZING CONTRIBUTION PROTOCOLS • LOADING GUIDELINES • ESTABLISHING PARAMETERS
```
## ://BEFORE_YOU_START
1. **SYSTEM_CHECK**: Ensure you have read the [README.md](README.md)
2. **NEURAL_SYNC**: Join our [Discord](https://discord.gg/withseismic) community
3. **PROTOCOL_REVIEW**: Check existing issues and PRs to avoid duplicates
## ://CODE_OF_CONDUCT
```
RESPECT • INCLUSIVITY • COLLABORATION • CONSTRUCTIVE FEEDBACK • CONTINUOUS IMPROVEMENT
```
We follow a strict code of conduct to maintain a positive and productive environment. See [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) for details.
## ://DEVELOPMENT_WORKFLOW
### LOCAL_SETUP
```bash
# Clone the repository
git clone https://github.com/d0ugwithseismic/withseismic-mcp.git
# Install dependencies
pnpm install
# Run tests
pnpm test
```
### BRANCH_STRATEGY
- `main` - Production-ready code
- `develop` - Development branch
- `feature/*` - New features
- `fix/*` - Bug fixes
- `docs/*` - Documentation updates
### COMMIT_MESSAGES
Follow the [Conventional Commits](https://www.conventionalcommits.org/) specification:
```
feat: add new tool for API integration
fix: resolve type inference in prompt generator
docs: update installation instructions
test: add coverage for error handling
```
## ://SUBMITTING_CHANGES
### PULL_REQUEST_PROCESS
1. Create a new branch from `develop`
2. Make your changes
3. Update documentation if needed
4. Add tests for new functionality
5. Run the test suite
6. Submit a PR against `develop`
### PR_TEMPLATE
Your PR description should include:
- What changes are included
- Why these changes are needed
- How to test the changes
- Screenshots (if applicable)
- Related issues
## ://ISSUE_REPORTING
### BUG_REPORTS
Include:
- Steps to reproduce
- Expected behavior
- Actual behavior
- Environment details
- Screenshots/logs if applicable
### FEATURE_REQUESTS
Include:
- Clear description of the feature
- Use cases
- Expected benefits
- Potential implementation approach
## ://STYLE_GUIDELINES
### CODE_STYLE
- Use TypeScript
- Follow existing patterns
- Document public APIs
- Write meaningful tests
- Use descriptive variable names
### DOCUMENTATION_STYLE
- Clear and concise
- Code examples where relevant
- Update README.md if needed
- Follow cyberpunk aesthetic
## ://CONTACT
- Discord: [Join our server](https://discord.gg/withseismic)
- Email: <hello@withseismic.com>
- Twitter: [@withseismic](https://twitter.com/withseismic)
```
CONTRIBUTION PROTOCOLS INITIALIZED • READY FOR NEURAL INTERFACE • AWAITING YOUR INPUT
```