agentmods.dev

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

A set of guardrails for building and testing Angular frontend code, including rules for test-first development and accessible interfaces.

In plain words
What is it for?
Writing failing tests before implementation, limiting edits to task-scoped files, structuring Angular components and services, checking user-input errors, testing rollback behavior, and validating changed UI code.
Why use it?
It helps prevent untested UI changes, unsafe shortcuts, inaccessible controls, and frontend validation gaps.

Instructions file for GitHub Copilot

57 2mo ago A scan 255 tokens original MIT
View the source file loiane/specs-driven-development-spring-angular
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/frontend-code
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: GitHub Copilot.

Per session 255 This file is loaded in full into every session.
When invoked 255 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.00255 $0.00255
Opus 5 $0.00128 $0.00128
Sonnet 5 $0.00051 $0.00051
Haiku 4.5 $0.00026 $0.00026

Measured yesterday against content hash 66597779a0e9, 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 frontend-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/frontend-code.instructions.md · 35 lines

What it actually says

Frontend code guardrails (Angular)

These rules apply when a task includes files under src/**.

Build-phase rules (TDD)

  • Test-first: write/extend failing tests before implementing behavior.
  • Edit only files listed in the active task's Files in scope.
  • Never skip frontend tests to force green.
  • Never remove assertions from existing tests.

Angular implementation rules

  • Prefer standalone components and typed interfaces/models.
  • Keep smart/container logic separate from presentational components where practical.
  • Avoid hardcoded API URLs in components; route all calls through services.
  • Keep templates accessible: semantic buttons/inputs, labels, and keyboard-operable controls.

Test rules

  • Add/maintain component/service tests for new behavior.
  • Every user-input validation rule needs a negative-path test.
  • For optimistic-update flows, test both success and rollback paths.

Validate/review rules

  • During /validate and /review, never modify production code or tests.
  • Missing frontend validation outputs (lint/test/build for changed UI scope) is an error.
  • Any waiver must reference an ADR.
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 · 35 lines · 255 tokens per session scan A 66597779a0e9

Subscribe to this mod's changes

specs-driven-development-spring-angular frontend-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 255 tokens to every session, about $0.0013 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.

FrontendTestingWriting and docsangulargithub-copilotjavaspec-driven-developmentspring-boottdd
Related

Other instructions, from other repositories

atmosphere AGENTS.md

Instructions for Atmosphere/atmosphere, covering build system: maven, commands, module build, build only atmosphere-runtime (cpr) and build only spring-boot-starter.

Atmosphere/atmosphere · 7,963 tokens

plugins CLAUDE.md

Instructions for ihub-pub/plugins, covering project knowledge base, project structure, plugin id 速查表, version compatibility and commands（build / lint / test）.

ihub-pub/plugins · 6,974 tokens

featherspec constitution.instructions.md

FeatherSpec constitution editing rules (thin loader).

GregorBiswanger/featherspec · 87 tokens

featherspec knowledge-records.instructions.md

FeatherSpec knowledge record rules — observation, rationale, provenance (thin loader).

GregorBiswanger/featherspec · 99 tokens

featherspec memory-bank.instructions.md

FeatherSpec Memory Bank writing rules (thin loader).

GregorBiswanger/featherspec · 91 tokens

featherspec plans.instructions.md

FeatherSpec plan-file craft rules (thin loader).

GregorBiswanger/featherspec · 89 tokens