clients
└── index.ts # Package entry point
test/ # Main test suite (hooks, integration, utils)
docs/ # Documentation (ADRs, configuration, etc.)
```
### Architecture
TDD Guard is organized as a TypeScript project with integrated language-specific
contributors, maintainers, and skill developers.
## What This Is
A **Claude Code skill** - executable documentation that Claude loads to provide Terraform/OpenTofu expertise. It encodes terraform-best-practices.com patterns into Claude's context
Endpoints in `web/server.js`:
`GET /api/community/templates`, `POST /api/community/import` (engine-validated, saved to 我的工作流).
Contribution flow documented in CONTRIBUTING.md. Listing/de-listing needs only a website push, no release.
NOTE: manifest `relayPresets` that duplicate
Create high-quality academic papers, literature reviews, grant proposals, clinical reports, and other scientific documents backed by comprehensive research and real, verifiable citations.
**Default Format:** LaTeX with BibTeX citations unless
Never run the app. User will run and test visually
- When code changes affect documented behavior, public APIs, hooks, configuration, or workflows, update the related documentation accurately.
- If contributed using
generate strategy, architecture, delivery, and assurance artifacts. It transforms architecture governance from scattered documents into a systematic, template-driven process.
**Nine distribution formats** exist side-by-side in this repo
/README.ko.md) | [日本語](./README.ja.md) | [中文](./README.zh.md)
```
- Translated READMEs include a disclaimer at the top:
> This document was translated from the English README. Some phrasing may be unnatural.
- When updating `README.md`, update
facing interactive course content (distributed via GitHub Releases as a zip)
2. **website/** - Next.js documentation site (deployed to Vercel at ccforpms.com)
Students download course-materials/ as a zip, extract
test section of @.github/workflows/ci.yml)
### Comments
- Comments MUST only be used to:
1. Document a function
2. Explain the WHY of a piece of code
3. Explain a particularly complicated piece
content section wrapped in ` ` and ` `
- Screenshot of live application
- Description of products used with documentation links
### Technical Requirements
- **Package-lock.json**: Required for 80% faster module resolution
- **Tests**: Mandatory minimum
hostnames, private URLs, cookies, local profile paths, or absolute personal
filesystem paths.
- Do not document real `.env` locations, credential-file paths, secret store
values, or commands that write real credentials
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.