Agent neutral instructions

This commit is contained in:
Kovid Goyal
2026-07-06 11:18:16 +05:30
parent 4e01ab48cc
commit fab7ce90db
2 changed files with 7 additions and 5 deletions

4
.gitignore vendored
View File

@@ -8,7 +8,7 @@
*_generated_test.go *_generated_test.go
*_generated_test.s *_generated_test.s
*_generated.h *_generated.h
/.dmypy.json *.local.md
/dependencies /dependencies
/tags /tags
/build/ /build/
@@ -24,11 +24,9 @@ __pycache__/
/docs/_build/ /docs/_build/
/docs/generated/ /docs/generated/
/tools/simdstring/simdstring.test /tools/simdstring/simdstring.test
/.mypy_cache
/.ruff_cache /.ruff_cache
.DS_Store .DS_Store
.cache .cache
bypy/b bypy/b
bypy/virtual-machines.conf bypy/virtual-machines.conf
_codeql_detected_source_root _codeql_detected_source_root

View File

@@ -1,4 +1,7 @@
# Claude System Instructions & Project Context initialize_command: make debug
copy_resource: fonts
# System Instructions & Project Context
## Project Architecture & Stack ## Project Architecture & Stack
This is a multi-language repository. Adhere strictly to the idiomatic styling, patterns, and type safety of each respective language ecosystem present in the codebase. Do not mix patterns across language boundaries. This is a multi-language repository. Adhere strictly to the idiomatic styling, patterns, and type safety of each respective language ecosystem present in the codebase. Do not mix patterns across language boundaries.
@@ -41,9 +44,10 @@ To run a Go test named TestMyFunction, use:
``` ```
## Verification Pipeline ## Verification Pipeline
Before declaring a task complete, you must follow this exact verification lifecycle: Before declaring a task complete, you must follow this exact verification lifecycle:
1. Run the local **Build Command** to guarantee zero compilation or compilation-stage type errors. 1. Run the local **Build Command** to guarantee zero compilation or compilation-stage type errors.
2. Run the local **Test Command** targeted at the modified module to prevent regressions. 2. Run the local **Test Command** to run the full test suite
3. If errors occur, analyze the stdout logs completely before writing a fix. Do not guess. 3. If errors occur, analyze the stdout logs completely before writing a fix. Do not guess.
4. If the change you have made is user facing, update the docs/changelog.rst 4. If the change you have made is user facing, update the docs/changelog.rst
file with a brief description of your changes file with a brief description of your changes