Skip to content

Commit e06e5a8

Browse files
klm-blzsclaude
andcommitted
JNG-6382 Add Code Instructions section to AGENTS.md
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 42a1b2f commit e06e5a8

1 file changed

Lines changed: 12 additions & 0 deletions

File tree

AGENTS.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22

33
## Project Overview
44

5+
56
**Repository:** BlackBeltTechnology/java-embedded-compiler
67
**License:** Apache License 2.0
78
**Java Version:** 11 (source and target)
@@ -13,6 +14,17 @@
1314
4. **Flexible classloading** — Composite classloaders, custom classloader wrapping, and compiled-bytecode classloaders enable loading compiled classes in complex classloader hierarchies
1415
5. **ServiceLoader discovery** — Compiler factories are discovered automatically via `java.util.ServiceLoader` in standard Java, or via OSGi DS `@Reference` in OSGi containers
1516

17+
## Code Instructions
18+
19+
1. First think through the problem, read the codebase for relevant files.
20+
2. Before you make any major changes, check in with me and I will verify the plan.
21+
3. Please every step of the way just give me a high level explanation of what changes you made.
22+
4. Make every task and code change you do as simple as possible. We want to avoid making any massive or complex changes. Every change should impact as little code as possible. Everything is about simplicity.
23+
5. Maintain a documentation file that describes how the architecture of the app works inside and out.
24+
6. Never speculate about code you have not opened. If the user references a specific file, you MUST read the file before answering. Make sure to investigate and read relevant files BEFORE answering questions about the codebase. Never make any claims about code before investigating unless you are certain of the correct answer - give grounded and hallucination-free answers.
25+
7. For implementation use TDD (Test-Driven Development): write or update tests first to define the expected behaviour, verify they fail, then write the minimal implementation to make them pass.
26+
8. Use DRY (Don't Repeat Yourself): extract reusable logic into separate classes, utilities, or components. If the same pattern appears in multiple places, refactor it into a shared helper.
27+
1628
## Directory Structure
1729

1830
```

0 commit comments

Comments
 (0)