specs-driven-development-spring-angular production-code.instructions.md

A set of rules for editing production Java code in Spring Boot 4 projects. TDD, or test-driven development, means writing a failing test before writing the code that makes it pass.

In plain words
What is it for?
Checking task state before edits, enforcing test-first development, organising code by feature, using approved Spring APIs, and applying conventions for dependency injection, data records, errors, configuration, and pagination.
Why use it?
It prevents production code from being changed without a corresponding failing test and keeps new code consistent with the project’s stated structure and conventions.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/loiane/specs-driven-development-spring-angular/production-code
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: GitHub Copilot.

Per session 521 This file is loaded in full into every session.
When invoked 521 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00521 $0.00521
Opus 5 $0.00260 $0.00260
Sonnet 5 $0.00104 $0.00104
Haiku 4.5 $0.00052 $0.00052

Measured yesterday against content hash 575c7d050bf2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

specs-driven-development-spring-angular production-code.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/production-code.instructions.md · 51 lines

What it actually says

Production code guardrails

You are about to edit production Java code under src/main/**.

Block: TDD precondition

Before writing or editing any line in src/main/**:

  1. Read .specs/<active-feature>/.tdd-state.json.
  2. Confirm tasks[<active-task>].phase == "red" AND red_failure_excerpt is non-empty.
  3. Confirm the file path you are about to edit appears in tasks[<active-task>].files_in_scope.

If any check fails, refuse the edit and tell the user:

"Cannot edit production code: no failing test for task <task-id>. Run /build <task-id> so the test-engineer writes the failing test first."

Spring Boot 4 conventions

Follow shared/skills/spring-boot-4-conventions/SKILL.md:

  • Constructor injection only.
  • Package by feature/domain, not by layer. Top-level packages are bounded contexts (giftcard, order, …), each with api (published) and internal (private) sub-packages. No top-level controller / service / repository / model packages.
  • @HttpExchange / RestClient (never RestTemplate in new code).
  • Records for DTOs.
  • @RestControllerAdvice for error mapping.
  • Pagination on every list endpoint.
  • @ConfigurationProperties records for grouped settings.
  • No Lombok. No @Data, @Getter, @Setter, @Builder, @RequiredArgsConstructor, @Slf4j, etc. Java records and explicit constructors replace them.

Architecture conventions

Follow shared/skills/archunit-rules/SKILL.md:

  • Each top-level package is a module; cross-module access goes through its api sub-package only.
  • Never import from another module's internal package — enforced by ArchUnit.
  • No cycles between top-level packages.

Security baseline

Follow shared/skills/spring-security-baseline/SKILL.md:

  • Default-deny in SecurityFilterChain.
  • Bean Validation on DTOs + service-layer invariant checks.
  • Mask PII / secrets in logs.
  • No @CrossOrigin("*") on state-changing endpoints.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 51 lines · 521 tokens per session scan A 575c7d050bf2

Subscribe to this mod's changes

specs-driven-development-spring-angular production-code.instructions.md is an instructions file published in the GitHub repository loiane/specs-driven-development-spring-angular (57 stars, last pushed 2mo ago), licensed MIT. It adds 521 tokens to every session, about $0.0026 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.