aiwg
Version:
Deployment tool and support utility for AI context. Copies agents, skills, commands, rules, and behaviors into the paths each AI platform reads (Claude Code, Codex, Copilot, Cursor, Warp, OpenClaw, and 6 more) so one source of truth works across 10 platfo
79 lines (45 loc) • 2.25 kB
Markdown
# Programming Guidelines Template
## Cover Page
- ``Project Name``
- `Programming Guidelines`
- `Version`1.0``
## Revision History
| Date | Version | Description | Author |
| --- | --- | --- | --- |
| ``dd/mmm/yy``|``x.x``|`<details>`|`<name>` |
## Ownership & Collaboration
- Document Owner: Environment Engineer
- Contributor Roles: Implementer, Integrator
- Automation Inputs: Language standards, static analysis rules
- Automation Outputs: `programming-guidelines.md` with sections 1–9
## 1 Introduction
> Outline purpose, scope, terminology, references, and organization of the programming guidelines.
### 1.1 Purpose
### 1.2 Scope
### 1.3 Definitions, Acronyms, and Abbreviations
### 1.4 References
### 1.5 Overview
## 2 Language and Framework Standards
> Enumerate supported languages, versions, frameworks, and compiler/interpreter settings.
## 3 Coding Conventions
> Provide naming conventions, formatting, documentation, and commenting rules.
## 4 Error Handling and Logging
> Describe standard patterns for exceptions, error codes, logging levels, and telemetry.
## 5 Security and Compliance Practices
> Define secure coding requirements, data protection rules, and compliance considerations.
## 6 Performance and Resource Management
> Provide guidance on performance optimization, memory management, and concurrency.
## 7 Testing Expectations
> Document unit testing standards, code coverage targets, and mocking or test harness conventions.
## 8 Code Review Checklist
> List criteria reviewers should apply to ensure adherence to these guidelines.
## 9 Tooling
> Identify IDE configurations, linters, static analyzers, formatters, and automation used to enforce guidelines.
## Appendices (Optional)
> Include snippets, templates, or references to style guides for specific languages.
## Agent Notes
- List formatting rules and static analysis configurations explicitly for agent tooling.
- Identify security and compliance requirements that code generators must respect.
- Verify the Automation Outputs entry is satisfied before signaling completion.
- Document formatting, linting, and static analysis rules for automation.
- Include security and compliance requirements code generators must follow.