# App Guide — [Project Name]

<!-- Copy this template to your client plugin's guide/ directory and
     fill in each section. The plugin's /guide skill reads this file
     to answer "how does the app work?" questions using your vocabulary
     instead of improvising from code.

     Four sections, each with a different job:
     - Overview: the 30-second mental model
     - Data Model: what the nouns mean and how they relate
     - Workflows: step-by-step for the things people actually do
     - Page Reference: what each screen is for
-->

## Overview

<!-- One paragraph. What does this app do, who is it for, and what's
     the core mental model? Write this so someone who has never seen the
     app can orient in 30 seconds.

     Example: "CasePipeline is a mass-arbitration platform for law firms.
     You set up Campaigns (a Target company + Legal Theory pair), generate
     public intake funnels, and manage Claimants through e-signature and
     filing. Think of it as a pipeline: prospects enter through campaigns,
     become claimants, and flow toward filed arbitration demands." -->


## Data Model

<!-- Define the domain terms your app uses. These become the canonical
     vocabulary — the /guide skill uses these definitions, not code-level
     names. For each term: what it is, how it relates to others.

     Format:
     - **Term** — definition. Relationship to other terms.

     Example:
     - **Target** — a company being pursued. Has one or more Legal Theories.
     - **Legal Theory** — the legal basis for claims against a Target.
     - **Campaign** — a Target + Theory pair that creates a public intake funnel.
     - **Claimant** — a person who entered through a Campaign's funnel.
     - **Claim** — a Claimant's filed arbitration demand against a Target. -->


## Workflows

<!-- Step-by-step instructions for the tasks people actually do. Each
     workflow has a title, who does it, and numbered steps. Use the
     vocabulary from the Data Model section.

     Example:
     ### Setting up a new campaign
     **Who:** consultant
     1. Create a Target (the company)
     2. Create a Legal Theory for that Target
     3. Link them as a Campaign — this generates a landing page URL
     4. Review the landing page content and publish

     ### Processing new claimants
     **Who:** consultant
     1. Check the pipeline dashboard for new sign-ups
     2. Review each claimant's intake data for completeness
     3. Send e-signature request for incomplete profiles
     4. Move completed claimants to "ready to file" -->


## Page Reference

<!-- What each screen in the app does and when you'd use it. For each
     page: its name, what it shows, and when to go there.

     Example:
     - **Dashboard** — overview of all campaigns, claimant counts, and
       conversion rates. Go here first each session.
     - **Campaign Detail** — deep view of one campaign: target info,
       theory, landing page, and all associated claimants.
     - **Claimant Profile** — individual claimant's intake data,
       e-sign status, and timeline. Go here to review or fix a
       specific person's record.
     - **Pipeline** — funnel view across all campaigns showing
       prospects → signed → filed progression. Weekly reporting
       pulls from this view. -->