Pdd Context.prompt

---
agent: agent
description: "Write or update PDD context files (project.md, conventions.md, decisions.md)"
---

# Write PDD Context Files

This is the Copilot adapter for the shared `Context` workflow in `core/workflows/context.md`. Keep shared workflow behavior aligned there; this file exists to preserve Copilot-specific frontmatter, `#file:` references, and `/pdd-*` command wording.

## Purpose

Write or update the persistent project context layer so future prompts are grounded in real project constraints.

**Write what is true, not what you hope will be true.** Stale or aspirational context makes every later prompt worse.

## Use When

- Context files do not exist yet.
- The stack, constraints, or architectural decisions have changed.
- The user wants better prompt quality and consistency.
- You need to refresh context after research, planning, or a major implementation decision.

## Inputs

- What the project is
- who it is for
- the tech stack
- quality expectations
- hard constraints and anti-patterns
- current implementation state

## Detect Project Type First

Load the matching project-type reference file from `#file:references/` to get type-specific questions, conventions, and templates. Provider adapters may translate these paths into provider-specific syntax, but the underlying reference files should stay aligned.

| Type | Signals | Reference |
|---|---|---|
| Frontend / UI | React, Vue, Angular, Svelte, CSS, Tailwind | `#file:references/frontend.md` |
| Backend / API | Node, FastAPI, Django, Rails, REST, GraphQL, gRPC, databases | `#file:references/backend.md` |
| Mobile | iOS, Android, Swift, Kotlin, React Native, Flutter, Expo | `#file:references/mobile.md` |
| Data / ML / AI | Python, Jupyter, pandas, PyTorch, scikit-learn, pipelines | `#file:references/data-ml.md` |
| DevOps / Infra | Terraform, Docker, Kubernetes, CI/CD, AWS, GCP, Azure | `#file:references/devops.md` |
| Full-stack | Frontend + backend, Next.js, Nuxt, SvelteKit | `#file:references/fullstack.md` + `#file:references/frontend.md` + `#file:references/backend.md` |
| Library / Package | npm package, PyPI library, crate, gem, Go module, SDK | `#file:references/library.md` (+ domain flavor if applicable) |
| CLI / Developer Tools | CLI app, terminal tool, code generator, REPL, arg parsing, subcommands | `#file:references/cli-devtools.md` |
| Embedded / IoT | MCU, RTOS, bare-metal, Arduino, ESP32, STM32, Zephyr, FreeRTOS, firmware | `#file:references/embedded-iot.md` |
| Game Development | Unity, Unreal, Godot, Bevy, game engine, ECS, frame budget | `#file:references/game-dev.md` |
| Blockchain / Smart Contracts | Solidity, Vyper, Rust/Anchor, Hardhat, Foundry, EVM, Solana, DeFi | `#file:references/blockchain.md` |
| Security / Pentesting Tools | Scanner, fuzzer, exploit framework, SIEM, detection rules, pentest | `#file:references/security.md` |
| API Platform / SDK | Public API, developer platform, OpenAPI, SDK generation, rate limiting, webhooks | `#file:references/api-platform.md` |
| Desktop / Native GUI | Tauri, Electron, Flutter desktop, SwiftUI macOS, Qt, .NET MAUI, WPF | `#file:references/desktop-gui.md` |
| Compiler / Language Tooling | Compiler, interpreter, transpiler, linter, formatter, LSP server, parser, AST | `#file:references/compiler-lang.md` |
| Robotics / ROS | ROS, ROS2, robot, drone, autonomous vehicle, URDF, Gazebo, MoveIt, Nav2 | `#file:references/robotics.md` |

**Full-stack merge priority**: When `fullstack.md`, `frontend.md`, and `backend.md` are loaded together, `fullstack.md` conventions take precedence where they overlap. Fall through to the frontend or backend reference only for concerns `fullstack.md` does not address.

**Library is composable**: A project can be both a library and a domain type. When combined, `library.md` takes precedence for API surface, versioning, and distribution; the domain flavor takes precedence for implementation patterns.

If the project spans multiple types, load all relevant references. When conventions conflict, surface the conflict and record the decision in `pdd/context/decisions.md`.

## Produces

- `pdd/context/project.md`
- `pdd/context/conventions.md`
- `pdd/context/decisions.md`

## If Creating New Context Files

Ask these questions conversationally, not as a single long form:

1. What are you building, and who is it for?
2. What's the tech stack?
3. What does good output look like?
4. What should the AI never do or suggest?
5. What's already been built?

Then ask any type-specific questions from the matching reference file.

### `pdd/context/project.md`

Use this as the shared base template: