AI コーディングの長すぎるプロンプトを圧縮する方法：コンテキスト整理と実用テンプレート

1
2
3
4
5
6

Goal: Fix failed login session refresh.
Scope: Start with src/auth/session.ts and tests/auth/session.test.ts.
Limit: First pass is analysis only; do not modify files; do not scan the whole repo.
Constraints: Do not change public API; do not delete files.
Validation: Give the smallest test command.
Output: List the 3 most likely causes and next steps.

1

I recently changed the login module. Users report that refreshing the page often logs them out. I suspect session expiry handling or cookie updates. Please look at it, avoid affecting other login logic, don't rewrite the architecture, maybe add tests, and check if similar problems exist elsewhere.

1
2
3
4
5

Goal: Diagnose login state lost after page refresh.
Scope: src/auth/session.ts, src/auth/cookie.ts, tests/auth/session.test.ts.
Limit: Do not change auth architecture; first pass analysis only.
Validation: List minimal reproduction and tests to add.
Output: 3 likely causes ranked by probability.

1
2
3
4

Background facts:
- Login has a legacy compatibility layer; do not remove it.
- Web and mobile share session logic.
- There was a previous cookie write issue; check cookie update paths first.

1
2
3
4
5

Forbidden:
- Do not change public API.
- Do not change database schema.
- Do not delete legacy compatibility logic.
- Do not do unrelated refactoring.

1
2
3
4

Phase 1: Diagnose the bug only; do not modify.
Phase 2: Fix the minimal code path.
Phase 3: Add the smallest related test.
Phase 4: Separately evaluate whether refactoring is needed.

1
2
3
4
5
6

Please read:
- src/auth/session.ts
- src/auth/cookie.ts
- tests/auth/session.test.ts

First pass: summarize relevant logic only. Do not modify.

1

Focus only on session refresh, cookie update, and logout branches.

1
2
3
4

Command: pnpm test -- auth
Failing test: refresh session keeps user logged in
Key error: Expected status 200, received 401
Stack: tests/auth/session.test.ts:42

1
2

Full log is in .tmp/auth-test.log.
Read only the last 80 lines first.

1
2

Follow project AGENTS.md.
Extra limit for this task: do not modify src/db/migrations.

1
2

- Search `src/components` before adding UI; prefer existing components.
- Do not create a generic component for a one-page change.

1
2
3
4
5
6

Goal:
Scope:
Symptom:
Key error:
Limit: First pass analysis only; do not modify files.
Output: 3 most likely causes + minimal validation steps.

1
2
3
4
5
6

Goal:
Allowed files:
Forbidden files:
Implementation requirements:
Validation command:
Output: changed files + validation result + risks.

1
2
3
4

Goal: Read-only review current diff.
Focus:
Limit: Do not modify files.
Output: List issues by severity; if none, say no high-risk issue found.

1
2
3
4
5
6

Goal: Diagnose login state lost after page refresh.
Scope: src/auth/session.ts, src/auth/cookie.ts, tests/auth/session.test.ts.
Background: There is old token compatibility; do not remove it.
Limit: First pass analysis only; do not modify; do not scan the whole repo.
Validation: Give minimal reproduction and test suggestions.
Output: 3 causes ranked by probability.

1

Run related tests.

1

Run `pnpm test -- auth`.

1
2
3
4
5
6
7
8
9

## Prompt Discipline

- Treat each task as a small work order.
- Prefer fields: goal, scope, limits, validation, output.
- Do not scan the whole repository unless explicitly requested.
- Ask before reading large logs or unrelated directories.
- Keep command output summarized; save full logs to files.
- Do not mix new feature work, refactor, docs, and cleanup in one task.
- Preserve exact paths, commands, error messages, and safety rules.