indentation, `crlf` line endings, and `latin1` charset — avoid non-ASCII characters in source files.
- **Documentation**: The project provides documentation on [Microsoft Learn](https://learn.microsoft.com/windows/win32/dxmath/directxmath-portal) with additional wiki pages available
ASCII characters in source files. HLSL files have separate indent/spacing rules defined in `.editorconfig`.
- **Documentation**: The project provides documentation in the form of wiki pages available at [Documentation](https://github.com
Security Considerations**
- Scripts should be reviewed for security implications
- External dependencies should be clearly documented
- No malicious patterns (unexpected network calls, unauthorized file access)
### Common Issues to Flag
- **Missing
file with YAML frontmatter containing `name` and `description` fields. The description serves as both documentation and trigger condition.
### Skill File Structure
All skill files must include YAML frontmatter:
```yaml
---
name
security issues not mentioned in PR description
- Breaking changes that weren't highlighted
- Documentation that needs updating due to code changes
### What NOT to Comment On
- Changes that are clearly
body]
[optional footer(s)]
```
### Types
- **feat**: A new feature
- **fix**: A bug fix
- **docs**: Documentation only changes
- **style**: Changes that do not affect the meaning of the code (white-space
code patterns and conventions
3. **Test**: Add comprehensive test cases with edge cases
4. **Document**: Update both code comments and user documentation
5. **Validate**: Test on multiple platforms and with
platform behavior, feature gates, wire compatibility, and failure semantics.
## Before changing code
- Read the documentation for the affected subsystem. Start with the references below rather than inferring behavior from names
supabase-swift
## Instructions for Code Review
- Check for breaking API changes
- Check if documentation is up to date
- Check if examples are up to date
- Check if tests are comprehensive
uses a modern Python build system with hatch, and includes comprehensive testing, linting, and documentation.
## Working Effectively
### Environment Setup
- **Python Requirements**: Python 3.10 or higher (tested with 3.9-3.13)
- **Network
Variables in PascalCase pass spell-checking; inconsistency fails the spell check.
### Comments and Documentation
- Use `#` for single-line comments
- Use `<# #>` for block comments (especially for complex logic)
- Use `.SYNOPSIS`, `.DESCRIPTION
separate migration)
│ └── promptyjs/ # Hand-written JS runtime (separate migration)
├── vscode/prompty/ # VS Code extension
└── web/ # Documentation site
```
---
## Python Package Layout
All source code lives under `runtime/python/prompty/prompty/`. The package is organized
into
variant analysis
Do not turn the repository into general iOS architecture guidance or product documentation.
## Agent Skill Requirements
- Every skill directory must contain a `SKILL.md` with valid `name` and `description
converted before merging into `main`.
---
### Version Header Format
```md
## [vX.Y.Z] - YYYY-MM-DD
```
---
## Documentation Consistency (Mandatory)
Documentation must always reflect the **current, shipped** implementation.
Whenever a change in this repository
Atlas.
- `create`: Creates resources, like a collection or a cluster.
- `delete`: Deletes resources or documents, like collections, documents or clusters.
- `update`: Modifies resources or documents, like collections, documents or clusters