Glide Coding Standards
Battle-tested patterns for governed AI development. Community-driven. Free to use. Ready to enforce.
Standard Categories
AWS Well-Architected
Operational excellence, security, reliability, performance, cost optimization, sustainability.
Serverless Patterns
Lambda database connections, API Gateway CORS, cold start optimization, error handling.
Security Standards
Authentication, authorization, secrets management, input validation, audit logging.
Cost Optimization
ARM64 migration, pay-per-use defaults, right-sizing, cost analysis gates.
API Design
RESTful patterns, versioning, pagination, error responses, rate limiting.
Agent Orchestration
Permission boundaries, capability tokens, blast radius containment, audit trails.
Testing Standards
Unit testing patterns, integration tests, mocking strategies, coverage requirements.
Deployment
CI/CD patterns, blue-green deployments, rollback strategies, infrastructure as code.
Documentation
API documentation, code comments, architectural decision records, runbooks.
Sample Standards
A few examples from the library
Never fetch SSM parameters at Lambda runtime Serverless Cost
Use environment variables with SAM template resolution instead. Runtime SSM calls cost $25/month per million invocations and add latency.
Never use connection pools in Lambda Serverless Database
Lambda handles one request at a time. Use a single cached client that reconnects on error. Pools waste memory and connections.
Never use DefaultAuthorizer in API Gateway Security CORS
DefaultAuthorizer applies to ALL methods including OPTIONS preflight. This breaks CORS. Use explicit per-function Auth properties.
Agent permissions must be task-scoped and time-limited Agent Security
Never inherit full user permissions. Each agent task gets a capability token specifying exactly what it can access and for how long.
Contribute Standards
These standards are community-driven. If you've learned a pattern the hard way, share it so others don't have to.
All contributions are reviewed, tested, and refined before inclusion. Your name goes in the commit history. The community benefits forever.
Contribution Guide-
1
Fork the Repository
Create your own copy to work on
-
2
Add Your Standard
Follow the template format in /templates
-
3
Include Evidence
Why does this matter? What happens if ignored?
-
4
Submit PR
We'll review, discuss, and merge
Open Source License
All standards are released under Creative Commons Attribution-ShareAlike 4.0. Use them in your projects. Modify them for your needs. Share improvements back.