Claude Code configured for PMs to ship faster.

# CLAUDE.md

> Memory file. Claude reads this on every session start. Keep it under 500 lines.
> Replace the bracketed TODOs with details about your team and product.

## Product

[TODO] One paragraph: what you're building and who it's for.

Example: *We build a payments API for marketplaces with 1–50 sellers. Our buyer is the marketplace's founding engineer. Our anti-buyer is enterprise procurement.*

## Team

- **PM:** [TODO — your name + handle]
- **Eng lead:** [TODO]
- **Design:** [TODO]
- **Anyone else with commit access:** [TODO]

…

# DESIGN.md

> Brand spec template. Fill in your brand values and Claude reads them every session.
> Reference this file from `CLAUDE.md` so the design system is always in context.
>
> For the deeper version (used by Claude when generating artifacts), see `skills/your-brand/SKILL.md`.

## At a glance

| Element | Spec |
|---|---|
| Primary color | [TODO `#xxxxxx`] |
| Logo | [TODO file path + dark/light variants] |
| Headline type | [TODO size/weight/letter-spacing/color] |
| Body type | [TODO size/line-height/color] |
| Voice | [TODO one sentence — e.g. "Short, declarative, period-ending. One idea per sentence."] |

## Colors
…

---
description: PRD authoring rule. Invoke when the user wants a new feature spec.
globs:
alwaysApply: false
---
# Rule: Generating a Product Requirements Document (PRD)

## Goal

To guide an AI assistant in creating a detailed Product Requirements Document (PRD) in Markdown format, based on an initial user prompt. The PRD should be clear, actionable, and suitable for a junior developer to understand and implement the feature.

## Process

1. **Receive Initial Prompt:** The user provides a brief description or request for a new feature or functionality.
2. **Ask Clarifying Questions:** Before writing the PRD, the AI *must* ask clarifying questions to gather sufficient detail. The goal is to understand the "what" and "why" of the feature, not necessarily the "how" (which the developer will figure out). Make sure to provide options in letter/number lists so the user can respond easily with selections.
3. **Generate PRD:** Based on the initial prompt and the user's answers, generate a PRD using the structure outlined below.
4. **Save PRD:** Save the generated document as `tasks/[feature-name]/task.md`.
5. **Seed sessions log:** Create `tasks/[feature-name]/sessions.md` with a single starter entry: today's date, status "Not started", and any open questions noted.
…