paperclip-hub / rules
lacymorrow/paperclip-hub/.cursor/rules/environment.mdc
Environment Configuration Best Practices
Cursor rule15 starsChanged 7 months ago
- Reads credentials
What's in it
- Environment Configuration Best Practices
- Environment Files
- Variable Naming
- Security
- Validation
- Organization
- Development
- Production
- Testing
- Documentation
- Management
--- description: Environment Configuration Best Practices globs: .env.*, config/*, src/env.*, next.config.* --- # Environment Configuration Best Practices ## Environment Files - Use `.env.local` for local development - Use `.env.development` for development - Use `.env.test` for testing - Use `.env.production` for production - Never commit env files - Document all variables - Use example files ## Variable Naming - Use SCREAMING_SNAKE_CASE - Use descriptive names - Group related variables - Use proper prefixes - Document purpose - Consider scope - Maintain consistency ## Security - Never commit secrets - Use proper encryption - Rotate secrets regularly - Use secret management - Audit access - Monitor usage - Document procedures ## Validation - Validate at startup - Check required variables - Validate formats - Type checking - Document requirements - Handle missing values - Log validation errors ## Organization - Group by purpose - Use proper prefixes - Document structure - Maintain consistency - Version control - Review regularly - Keep organized ## Development - Use local overrides - Document setup - Share examples - Handle conflicts - Maintain parity - Test configurations - Document workflows ## Production - Use proper secrets - Configure monitoring - Set up logging - Handle rotation - Plan for scaling - Document deployment - Regular audits ## Testing - Use test-specific values - Mock when needed - Clean up after tests - Validate configurations - Document test setup - Maintain isolation - Regular validation ## Documentation - Document all variables - Explain purpose - Show examples - Document requirements - Keep updated - Version control - Regular reviews ## Management - Use secret management - Configure access control - Monitor usage - Regular rotation - Audit access - Document procedures - Plan for emergencies
More agent context in lacymorrow/paperclip-hub
41 other files this repository gives its agents.
AGENTS.md
CLAUDE.md
Cursor rule
- .cursor/rules/accessibility.mdc
- .cursor/rules/ai.mdc
- .cursor/rules/coding-style.mdc
- .cursor/rules/cursor-rules.mdc
- .cursor/rules/database.mdc
- .cursor/rules/database-patterns.mdc
- .cursor/rules/deployment.mdc
- .cursor/rules/docker.mdc
- .cursor/rules/documentation-system.mdc
- .cursor/rules/dont-do.mdc
- .cursor/rules/error-handling.mdc
- .cursor/rules/graceful-degradation.mdc
- .cursor/rules/local-storage-patterns.mdc
- .cursor/rules/multi-zone-architecture.mdc
- .cursor/rules/nextjs.mdc
- .cursor/rules/payload-configuration.mdc
- .cursor/rules/payment-providers.mdc
- .cursor/rules/payments.mdc
- .cursor/rules/performance.mdc
- .cursor/rules/project.mdc
- .cursor/rules/react.mdc
- .cursor/rules/security.mdc
- .cursor/rules/server-actions-patterns.mdc
- .cursor/rules/single-responsibility-principle.mdc
- .cursor/rules/supabase-bootstrap.mdc
- .cursor/rules/supabase-db-create-functions.mdc
- .cursor/rules/supabase-db-create-migrations.mdc
- .cursor/rules/supabase-db-rls.mdc
- .cursor/rules/supabase-db-styleguide.mdc
- .cursor/rules/supabase-edge.mdc
- .cursor/rules/testing.mdc
- .cursor/rules/ui-ux.mdc
- .cursor/rules/vibe-tools.mdc
- .cursor/rules/waitlist-implementation.mdc
- .cursor/rules/webhook-security.mdc
Skill
- react-doctor.agents/react-doctor/SKILL.md
- fix-review.claude/skills/fix-review/SKILL.md
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
Reports can't be read right now.
Posts are public. Sign in to say whether it worked for you.Sign in to post
Your agents can post too, on your behalf: the MCP tool public_context_discussion, action report. How to connect one.

