メニュー
Think from the user's perspective — understanding goals, frustrations, workflows, and the context in which people interact with the system. Applies wherever user value, journeys, stories, screens, or acceptance criteria are shaped or reviewed.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Design clear, versioned, backward-compatible interfaces and contracts between units, services, and external consumers. Applies wherever interfaces/contracts are designed or reviewed.
Evaluate software architecture for sound boundaries, intentional coupling, explicit trade-offs, scalability, deployability, operability, and failure behaviour. Applies wherever architectural decisions are designed or reviewed.
Identify and define the core domain concepts of a system — components, entities, relationships, ownership boundaries, and the language the system speaks. Applies wherever domain structure, entity ownership, or business capability boundaries are designed or reviewed.
Apply disciplined implementation practices across backend, frontend, infrastructure, configuration, and tests: write-test-verify, repository convention matching, integration boundary control, and appropriate test strategy.
AI-DLC workspace kickoff. Handles the welcome banner and workspace setup — creating the intent directory, state file, and audit file. Read by the orchestrator at the start of every new intent.
AI-DLC workflow orchestrator. Activate whenever the user states a fresh development intent — building, creating, implementing, fixing, migrating, refactoring, or adding a feature to a codebase. Use this skill for any free-form development prompt such as "build X", "add feature Y", "migrate Z to W", "fix the bug in V", "refactor U", or "create a new service for T".
| name | aidlc-user-empathy-skill |
| description | Think from the user's perspective — understanding goals, frustrations, workflows, and the context in which people interact with the system. Applies wherever user value, journeys, stories, screens, or acceptance criteria are shaped or reviewed. |
The ability to think from the user's perspective — understanding their goals, frustrations, workflows, and the context in which they interact with the system.
When applied at requirements-analysis: ensure requirements reflect real user needs not just technical capabilities, identify missing user-facing requirements by reasoning about user journeys, flag requirements that would create poor user experience.
When applied at user-stories: ground stories in personas, ensure acceptance criteria reflect what the user actually experiences, identify missing edge-case stories.
When applied at wireframes: validate that screen flows match user mental models, flag confusing navigation or information architecture.
