What is sapstack-symptom-context?

A symptom-matching guide for SAP problems in ECC and S/4HANA, two major SAP product generations. It maps user descriptions, synonyms, and spoken transaction codes to likely known symptoms and initial checks.

Use it to identify possible SAP symptoms, normalize business terms and transaction codes, and present likely causes and read-only checks.

It helps an agent interpret informal reports such as a failed transaction without immediately guessing at a fix.

How BoxLogoDev/sapstack configures Kiro

Reuse

Borrowing it

Nothing to install: this file belongs to BoxLogoDev/sapstack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/BoxLogoDev/sapstack/main/.kiro/steering/sapstack-symptom-context.md

Clone the repo

git clone --depth 1 https://github.com/BoxLogoDev/sapstack

Made for: Kiro.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/boxlogodev/sapstack/sapstack-symptom-context/github.svg)](https://agentmods.dev/instructions/boxlogodev/sapstack/sapstack-symptom-context)

Your own site

<a href="https://agentmods.dev/instructions/boxlogodev/sapstack/sapstack-symptom-context"><img src="https://agentmods.dev/badge/instructions/boxlogodev/sapstack/sapstack-symptom-context/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/boxlogodev/sapstack/sapstack-symptom-context"><img src="https://agentmods.dev/badge/instructions/boxlogodev/sapstack/sapstack-symptom-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 931 This file is loaded in full into every session.

When invoked 931 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00931	$0.00931
Opus 5.5	$0.00372	$0.00372
Sonnet 5.5	$0.00186	$0.00186
Haiku 4.5	$0.00093	$0.00093

Measured 1mo ago against content hash cddb61b6eb02, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sapstack-symptom-context 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 1mo ago.

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.

.kiro/steering/sapstack-symptom-context.md · 85 lines

What it actually says

sapstack Symptom Context

이 steering은 사용자가 SAP 증상을 언급할 때만 자동 로드됩니다. 평소에는 토큰 컨텍스트를 차지하지 않고, description에 매칭되는 발화가 감지되면 20개 증상 인덱스 + synonym 사전이 주입됩니다.

원본 Symptom Index (실시간 참조)

#[[file:data/symptom-index.yaml]]

원본 동의어 사전

#[[file:data/synonyms.yaml]]

원본 T-code 발음 사전

#[[file:data/tcode-pronunciation.yaml]]

이 steering이 활성화되면 Kiro가 다음을 수행합니다

1. 증상 매칭 우선순위

사용자 증상을 받으면 다음 순서로 처리:

symptom-index.yaml에서 fuzzy 매칭 — symptom_ko, symptom_ko_variants, typical_causes 전체 대상
synonyms.yaml로 토큰 정규화 — "코스트센터" → cost_center로 canonical 통일
tcode-pronunciation.yaml로 발음 → 코드 변환 — "에프백십" → F110
상위 3-5개 매칭 결과 제시 — 신뢰도 내림차순, typical_causes 요약

2. 매칭 결과의 형식

매칭된 symptom이 있으면 답변 시작부에 반드시 표시:

## 🎯 매칭된 증상

**[sym-f110-no-payment-method]** F110 돌리는데 벤더 하나만 No valid payment method 뜨는 경우 (신뢰도: 87%)

관련 모듈: FI, TR
초기 체크 T-code: F110, XK03, FBZP, SE16N

### 전형적 원인 (likely)
1. 벤더 마스터에 ZWELS(페이먼트 메소드, LFB1) 비어있음 — 제일 흔함
2. 최근 CDHDR 변경 이력 확인 필요
3. FBZP 뱅크 디터미네이션에 페이먼트 메소드 누락

3. 매칭 실패 시 행동

symptom-index에 매칭 없으면:

즉답 금지 — 환경 컨텍스트 질문 (Universal Rule #2)
Evidence Loop 세션 시작 제안: /sap-session-start "<증상>"
또는 MCP 툴 resolve_symptom 호출

4. 로컬라이제이션 우선순위

사용자 국가가 확인되면(kr/de/us/jp) 해당 localized_checks 반드시 언급:

🇰🇷 KR: 한국 특화 — 전자세금계산서, K-SOX, 4대보험, KEB/국민/신한 은행
🇩🇪 DE: SEPA, DATEV, ELSTER
🇺🇸 US: 1099, ACH/Wire, SOX
🇯🇵 JP: 源泉徴収, 電子帳簿保存法

연관 MCP 툴 호출

이 steering이 활성화되면 다음 MCP 툴을 자동 호출 권장:

resolve_symptom(query="<사용자 원문>", language="ko", country="kr", top_n=5)

MCP 서버가 연결되어 있으면 sapstack이 synonym 확장까지 포함한 정확한 매칭을 반환합니다. 연결 안 된 경우에도 이 steering에 주입된 symptom-index 본문으로 Kiro가 직접 매칭 가능.

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.

1mo ago First seen · 85 lines · 931 tokens per session scan A cddb61b6eb02

Subscribe to this mod's changes

sapstack-symptom-context is an instructions file published in the GitHub repository BoxLogoDev/sapstack (20 stars, last pushed 19d ago), licensed MIT. It adds 931 tokens to every session, about $0.0037 per session on Opus 5.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-09-15.

Claude Code Debugging abap ai-agents developer-tools erp llm-skills

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

sapstack: Instructions file for Kiro