Open Source

Glide Coding Standards

Battle-tested patterns for governed AI development. Community-driven. Free to use. Ready to enforce.

Browse Standards Contribute
10+
Standards Documents
7
Categories
100+
Individual Rules
MIT
License

Standard Categories

🤖

AI Assistant Configuration

11 rules

CLAUDE.md templates, agent configuration patterns, context management, prompt engineering.

🛠

API Design

7 rules

RESTful patterns, versioning, error responses, rate limiting, documentation.

💰

Cost Optimization

7 rules

ARM64 migration, pay-per-use defaults, right-sizing, cost analysis gates.

💻

Development Principles

7 rules

Code organization, naming conventions, error handling, logging patterns.

📋

Testing Principles

6 rules

Unit testing patterns, integration tests, mocking strategies, coverage requirements.

🧠

Agent Memory

8 rules

Tiered memory systems, context management, hot/warm/cold transitions, vector optimization.

⚙

Serverless Patterns

15 rules

Lambda best practices, API Gateway configuration, SAM templates, connection patterns.

☁

AWS Well-Architected

12 rules

Six pillars coverage: operational excellence, security, reliability, performance, cost, sustainability.

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 the MIT License. Use them in any project—commercial or open source. No restrictions. No attribution required.

MIT License - Maximum freedom to use, modify, and distribute