initial commit

This commit is contained in:
2026-03-16 19:54:53 -04:00
commit bfe0e01254
3341 changed files with 483939 additions and 0 deletions

View File

@@ -0,0 +1,83 @@
# Project Info: {{project_name}}
**Created:** {{date}}
**Project Type:** {{project_type}}
**Design Experience:** {{design_experience}}
**Status:** In progress
---
## Team
**Project Lead:** {{user_name}}
**Communication Language:** {{communication_language}}
**Document Output Language:** {{document_output_language}}
---
## Project Configuration
**Output Folder:** `{{output_folder}}/`
**WDS System Folder:** `{{wds_folder}}/`
Configuration stored in: `{{wds_folder}}/config.yaml`
---
## Quick Navigation
**Product Brief (Phase 1):**
- [01 — Product Brief](01-product-brief.md)
- [02 — Content Language](02-content-language.md)
- [03 — Visual Direction](03-visual-direction.md)
- [04 — Platform Requirements](04-platform-requirements.md)
**Trigger Map (Phase 2):**
- [00 — Trigger Map Overview](../B-Trigger-Map/00-trigger-map.md)
**UX Scenarios (Phase 4):**
- [UX Scenarios Guide](../C-UX-Scenarios/ux-scenarios-guide.md)
**Design System (Phase 7):**
- [00 — Design System Overview](../D-Design-System/00-design-system.md)
---
## Project Timeline
| Phase | Status | Completed |
|-------|--------|-----------|
| 1 — Product Brief | Not started | — |
| 2 — Trigger Map | Not started | — |
| 3 — Platform Requirements | Not started | — |
| 4 — UX Design | Not started | — |
| 5 — Design System | Not started | — |
| 6 — Design Deliveries | Not started | — |
| 7 — Testing | Not started | — |
---
## Technical Stack
**Frontend:** TBD
**Backend:** TBD
**Hosting:** TBD
**Languages:** {{document_output_language}}
---
## WDS Agents
To activate agents, tell Claude:
```
Read and activate the agent in `{{wds_folder}}/agents/[agent-name].md`
```
**Available:**
- **Saga** — Product Brief, Trigger Mapping & Platform Requirements
- **Freya** — UX Design, Design System, Testing & Product Evolution
---
*Generated by Whiteport Design Studio installer*

View File

@@ -0,0 +1,245 @@
# Content & Language: {{project_name}}
> Tone of Voice & Content Guidelines
**Created:** {{date}}
**Author:** {{user_name}}
**Related:** [Product Brief](./product-brief.md)
---
## Brand Personality
{{brand_personality_summary}}
### Personality Attributes
| Attribute | Description | Expression |
|-----------|-------------|------------|
{{#each personality_attributes}}
| **{{this.attribute}}** | {{this.description}} | {{this.expression}} |
{{/each}}
---
## Tone of Voice
### Core Tone
**Primary Tone:** {{primary_tone}}
{{tone_description}}
### Tone Spectrum
| Dimension | Our Position | Example |
|-----------|--------------|---------|
| Formal ↔ Casual | {{formal_casual}} | {{formal_casual_example}} |
| Serious ↔ Playful | {{serious_playful}} | {{serious_playful_example}} |
| Technical ↔ Simple | {{technical_simple}} | {{technical_simple_example}} |
| Reserved ↔ Enthusiastic | {{reserved_enthusiastic}} | {{reserved_enthusiastic_example}} |
### We Say / We Don't Say
**We say:**
{{#each we_say}}
- {{this}}
{{/each}}
**We don't say:**
{{#each we_dont_say}}
- {{this}}
{{/each}}
---
## Language Strategy
### Supported Languages
| Language | Priority | Coverage | Notes |
|----------|----------|----------|-------|
{{#each languages}}
| {{this.language}} | {{this.priority}} | {{this.coverage}} | {{this.notes}} |
{{/each}}
### Translation Approach
{{translation_approach}}
### Localization Notes
{{#each localization_notes}}
- **{{this.language}}:** {{this.note}}
{{/each}}
---
## Content Types
### UI Microcopy
*Buttons, labels, error messages, system feedback*
**Guidelines:**
{{#each microcopy_guidelines}}
- {{this}}
{{/each}}
**Examples:**
| Context | ✅ Do | ❌ Don't |
|---------|-------|---------|
{{#each microcopy_examples}}
| {{this.context}} | {{this.do}} | {{this.dont}} |
{{/each}}
### Marketing Content
*Headlines, feature descriptions, value propositions*
**Guidelines:**
{{#each marketing_guidelines}}
- {{this}}
{{/each}}
### Informational Content
*Service descriptions, about pages, FAQs*
**Guidelines:**
{{#each informational_guidelines}}
- {{this}}
{{/each}}
---
## SEO Strategy
### Page-Keyword Map
| Page | URL Slug | Primary Keyword (SE) | Primary Keyword (EN) | {{#if has_german}}Primary Keyword (DE) |{{/if}}
|------|----------|---------------------|---------------------|{{#if has_german}}---------------------|{{/if}}
{{#each page_keyword_map}}
| {{this.page}} | {{this.slug}} | {{this.keyword_se}} | {{this.keyword_en}} | {{#if ../has_german}}{{this.keyword_de}} |{{/if}}
{{/each}}
### URL Structure
**Pattern:**
```
{{url_primary}} → {{primary_language}}
{{url_secondary}} → {{secondary_language}}
{{#if url_tertiary}}
{{url_tertiary}} → {{tertiary_language}}
{{/if}}
```
### Primary Keywords (by language)
{{#each seo_keywords_by_language}}
**{{this.language}}:**
{{#each this.keywords}}
- {{this}}
{{/each}}
{{/each}}
### Local SEO
{{#if is_local_business}}
| Property | Value |
|----------|-------|
| **Business Name** | {{business_name}} |
| **Address** | {{business_address}} |
| **Phone** | {{business_phone}} |
| **Email** | {{business_email}} |
| **Opening Hours** | {{business_hours}} |
| **Google Business Profile** | {{google_business_status}} |
| **Business Category** | {{business_category}} |
{{else}}
*Not a local business — skip this section*
{{/if}}
### Structured Data Plan
| Page Type | Schema Type | Key Properties |
|-----------|-------------|----------------|
{{#each structured_data_plan}}
| {{this.page_type}} | {{this.schema_type}} | {{this.properties}} |
{{/each}}
### Keyword Usage Guidelines
{{keyword_usage_guidelines}}
---
## Content Structure Principles
### Structure Type
{{structure_type}}
### User's Vision
{{users_vision}}
### Content Priorities
**Must be prominent (visible immediately):**
{{#each must_be_prominent}}
- {{this}}
{{/each}}
**Important but secondary:**
{{#each secondary_content}}
- {{this}}
{{/each}}
### Navigation Principles
{{#each navigation_principles}}
- {{this}}
{{/each}}
### Not Included
{{#each not_included}}
- {{this}}
{{/each}}
### Clarity Level
{{clarity_level}}
---
## Content Ownership
| Content Type | Owner | Update Frequency |
|--------------|-------|------------------|
{{#each content_ownership}}
| {{this.type}} | {{this.owner}} | {{this.frequency}} |
{{/each}}
---
## Writing Checklist
Before publishing any content, verify:
{{#each writing_checklist}}
- [ ] {{this}}
{{/each}}
---
## Next Steps
- [ ] **Visual Direction** — Establish visual style and brand
- [ ] **Phase 2: Trigger Mapping** — Connect content to user psychology
- [ ] **Phase 4: UX Design** — Apply tone to interface copy
---
_Generated by Whiteport Design Studio_

View File

@@ -0,0 +1,297 @@
# Project Contract
**Project**: {{project_name}}
**Date**: {{date}}
**Client**: {{client_name}}
**Contractor**: {{contractor_name}}
**Contract Language**: {{contract_language}}
**Governing Law/Jurisdiction**: {{governing_jurisdiction}}
---
> **Contract Philosophy**: This contract is designed to be simple, fair, and clear - providing reliable terms that support a long-lasting working relationship between both parties.
---
## 1. Project Overview
### The Realization
{{realization}}
### Recommended Solution
{{recommended_solution}}
---
## 2. Business Model
**Selected Model**: {{business_model}}
{{business_model_description}}
{{business_model_terms}}
---
## 3. Scope of Work
### The Path Forward
{{path_forward}}
### Deliverables
Based on the path forward, the following deliverables will be provided:
{{deliverables_list}}
### In Scope
The following work is explicitly included in this contract:
{{in_scope}}
### Out of Scope
The following work is explicitly NOT included in this contract:
{{out_of_scope}}
**Note**: Any work outside the scope defined above requires a written Change Order (see Section 10: Not to Exceed Clause).
---
## 4. Our Commitment
{{our_commitment}}
---
### Payment Terms
**Total Contract Amount**: {{total_amount}}
**Payment Structure**: {{payment_structure}}
**Payment Schedule**:
{{payment_schedule}}
**Background**: Clear payment terms protect both parties and ensure fair compensation.
**What it does**: Defines when and how payments will be made.
**Purpose**:
- Ensures supplier receives fair compensation for work
- Provides client with clear payment expectations
- Protects both parties from payment disputes
- For fixed-price contracts, upfront payment is fair since supplier assumes cost overrun risk
**Payment Terms Details**:
- **Payment Method**: {{payment_method}} (check, wire transfer, credit card, etc.)
- **Payment Due Dates**: {{payment_due_dates}}
- **Late Payment**: {{late_payment_terms}} (e.g., interest charges, work suspension)
- **Payment Conditions**: {{payment_conditions}} (e.g., payment required before work begins, payment tied to deliverables)
**For Fixed-Price Contracts**:
This is a fixed-price contract, meaning the contractor commits to deliver specified work for the agreed price, regardless of actual costs. Since the contractor assumes the risk of cost overruns, upfront payment (50-100%) is standard and fair. This demonstrates client commitment and enables the contractor to deliver quality work without cash flow concerns.
---
## 5. Timeline
{{timeline}}
*Note: Timeline is based on the work plan outlined above and may be adjusted based on project requirements.*
---
## 6. Why It Matters
{{why_it_matters}}
---
## 7. Expected Outcomes
### The Value We'll Create
{{value_we_create}}
---
## 8. Risks and Considerations
### Cost of Inaction
{{cost_of_inaction}}
---
## 9. Confidentiality
### Confidentiality Clause
**Background**: This clause protects sensitive information shared during the project.
**What it does**: Both parties agree to keep project information confidential.
**Purpose**: Protects proprietary information, business strategies, trade secrets, and sensitive data.
**Terms**:
Both parties agree to:
- Keep all project-related information confidential
- Not disclose project details to third parties without written consent
- Use confidential information solely for project purposes
- Return or destroy confidential materials upon project completion or termination
- Maintain confidentiality obligations even after project completion
**Exceptions**:
- Information already publicly known
- Information independently developed
- Information required by law to be disclosed
**Duration**: Confidentiality obligations shall remain in effect for [X] years after project completion.
---
## 10. Not to Exceed Clause
### Budget Cap
**Background**: This clause sets a maximum budget limit.
**What it does**: States that total costs will not exceed a specified amount without prior written approval.
**Purpose**:
- Protects both parties from unexpected cost overruns
- Ensures budget control
- **Prevents scope creep** - Any work beyond the original scope requires approval and may affect the budget cap
**Terms**:
- Total project costs shall not exceed **{{not_to_exceed_amount}}** without prior written approval from {{client_name}}
- Any work that would exceed this amount must be approved in advance
- If additional work is needed, a change order must be signed before proceeding
- This cap includes all fees, expenses, and costs related to the project
**Change Orders and Scope Control**:
- Any changes to scope that affect cost must be documented in a written change order
- Change orders must be signed by both parties before work begins
- Change orders may adjust the not-to-exceed amount if agreed upon
- **Scope creep prevention**: Work outside the original scope (as defined in Section 2) requires a change order and approval before proceeding
- This clause helps prevent gradual expansion of project scope without proper authorization
---
## 11. Terms and Conditions
### Work Initiation
**When work begins**: {{work_initiation_date_or_condition}}
**Background**: This clause specifies exactly when the contractor is authorized to begin work.
**What it does**: Defines the start date or conditions that must be met before work begins.
**Purpose**:
- Prevents unauthorized work before contract is fully executed
- Establishes clear timeline expectations
- Protects both parties by ensuring work only begins after proper authorization
**Initiation conditions** (select applicable):
- Upon full execution of this contract (signatures from both parties)
- On a specific date: {{specific_start_date}}
- Upon receipt of initial payment/deposit
- Upon written notice from {{client_name}}
- Other: {{custom_initiation_condition}}
### Project Initiation
This project is initiated upon approval of the project pitch. Project initiation is considered complete upon stakeholder approval.
### Next Steps
After contract approval:
1. Proceed to full Project Brief development
2. Execute work plan as outlined above
3. Deliverables will be provided according to the agreed timeline
### Changes and Modifications
Any changes to scope, timeline, or investment must be agreed upon in writing by all parties.
### Intellectual Property
**Philosophy**: Clear IP ownership prevents future disputes and protects both parties' interests.
All deliverables and work products created under this contract will be owned by {{client_name}} upon full payment, unless otherwise specified in writing. This ensures clarity and prevents misunderstandings about ownership rights.
### Termination
**Philosophy**: Fair termination terms protect both parties while allowing for reasonable exit if needed.
Either party may terminate this agreement with [X] days written notice. Upon termination, payment is due for work completed to date. This ensures fair compensation for work done and reasonable notice for both parties to plan accordingly.
### Dispute Resolution
**Background**: Defines how conflicts will be resolved if they arise.
**What it does**: Establishes the process for handling disagreements.
**Purpose**: Provides a clear path for resolving disputes without costly litigation when possible.
**Method**: {{dispute_resolution_method}} (mediation/arbitration/litigation)
**Location**: {{dispute_resolution_location}}
Any disputes arising from this contract shall be resolved through {{dispute_resolution_method}} in {{dispute_resolution_location}}.
---
### Governing Law and Jurisdiction
**Background**: Determines which laws apply and where legal proceedings would take place.
**What it does**: Specifies the legal framework and court system that governs the contract.
**Purpose**: Provides legal clarity and predictability for both parties.
**Governing Law**: This contract shall be governed by and construed in accordance with the laws of {{governing_jurisdiction}}.
**Jurisdiction**: Any legal proceedings arising from this contract shall be subject to the exclusive jurisdiction of the courts of {{governing_jurisdiction}}.
**Contract Language**: This contract is executed in {{contract_language}}. In case of translation, the {{contract_language}} version shall prevail.
---
## 12. Approval
**Client Approval**:
Signature: _________________
Name: {{client_name}}
Date: _______________
**Contractor Approval**:
Signature: _________________
Name: {{contractor_name}}
Date: _______________
---
## Appendix
### Reference Documents
- Project Pitch: `docs/1-project-brief/pitch.md`
- Project Brief: (To be created after contract approval)
---
*This contract is based on the project pitch dated {{date}}.*

View File

@@ -0,0 +1,104 @@
# Inspiration Analysis: {{project_name}}
> Reference Site Analysis & Design Principles
**Created:** {{date}}
**Author:** {{user_name}}
**Related:** [Product Brief](./product-brief.md) | [Visual Direction](./visual-direction.md) | [Content & Language](./content-language.md)
---
## Sites Analyzed
{{#each sites}}
### {{this.name}}
**URL:** {{this.url}}
#### What Client Liked
{{#each this.liked}}
- **{{this.element}}** — {{this.why}}
{{/each}}
#### What Client Didn't Like
{{#each this.disliked}}
- **{{this.element}}** — {{this.why}}
{{/each}}
#### Adaptations Needed
{{#each this.adaptations}}
- **{{this.element}}** — {{this.modification}}
{{/each}}
#### Principles Extracted
{{#each this.principles}}
- {{this}}
{{/each}}
---
{{/each}}
## Design Principles (Synthesized)
### Layout
**DO:**
{{#each layout_do}}
- {{this}}
{{/each}}
**DON'T:**
{{#each layout_dont}}
- {{this}}
{{/each}}
### Content Hierarchy
**DO:**
{{#each content_do}}
- {{this}}
{{/each}}
**DON'T:**
{{#each content_dont}}
- {{this}}
{{/each}}
### Visual Style
**DO:**
{{#each visual_do}}
- {{this}}
{{/each}}
**DON'T:**
{{#each visual_dont}}
- {{this}}
{{/each}}
### User Experience
**DO:**
{{#each ux_do}}
- {{this}}
{{/each}}
**DON'T:**
{{#each ux_dont}}
- {{this}}
{{/each}}
---
## How to Use This Document
**For Scenario Outlining (Phase 4):**
Reference layout patterns when designing user flows. Use navigation principles to inform site structure.
**For Page Design (Phase 5):**
Use extracted principles as design checklist. Reference "What Client Liked" for visual direction. Avoid "What Client Didn't Like" patterns.
**For Dream Up Self-Review:**
Check generated output against documented preferences. Each design principle is a self-review checkpoint.
---
_Generated by Whiteport Design Studio_

View File

@@ -0,0 +1,93 @@
# Project Pitch: {{project_name}}
> Compelling case for why this project matters and should be built
**Created:** {{date}}
**Author:** {{user_name}}
**Status:** Ready for stakeholder approval
---
## 1. The Realization
{{realization}}
---
## 2. Why It Matters
{{why_it_matters}}
---
## 3. How We See It Working
{{how_we_see_it_working}}
---
## 4. Paths We Explored
{{paths_we_explored}}
---
## 5. Recommended Solution
{{recommended_solution}}
---
## 6. The Path Forward
{{path_forward}}
---
## 7. The Value We'll Create
{{value_we_create}}
---
## 8. Cost of Inaction
{{cost_of_inaction}}
---
## 9. Our Commitment
{{our_commitment}}
---
## 10. Summary
{{summary}}
---
## Business Context
This project serves:
- **Primary Goal:** {{business_goal}}
- **Solution:** {{solution}}
- **Target Users:** {{target_users}}
*Detailed strategic analysis (personas, driving forces, prioritization) is developed in Phase 2: Trigger Mapping.*
---
## Next Steps
**After approval**, proceed to:
- **Full Project Brief** - Detailed strategic foundation
- **Trigger Mapping** - User research and personas
- **Platform Requirements** - Technical foundation
- **UX Design** - Scenarios and prototypes
---
_Generated by Whiteport Design Studio_

View File

@@ -0,0 +1,218 @@
# Platform Requirements: {{project_name}}
> Technical Boundaries & Platform Decisions
**Created:** {{date}}
**Author:** {{user_name}}
**Related:** [Product Brief](./product-brief.md)
---
## Technology Stack
### Core Platform
**CMS/Framework:** {{cms_framework}}
**Approach:** {{tech_approach}}
{{tech_approach_details}}
### Key Technologies
| Layer | Technology | Rationale |
|-------|------------|-----------|
| **Frontend** | {{frontend_tech}} | {{frontend_rationale}} |
| **Styling** | {{styling_tech}} | {{styling_rationale}} |
| **CMS/Backend** | {{backend_tech}} | {{backend_rationale}} |
{{#if database_tech}}| **Database** | {{database_tech}} | {{database_rationale}} |{{/if}}
{{#if hosting_tech}}| **Hosting** | {{hosting_tech}} | {{hosting_rationale}} |{{/if}}
---
## Plugin/Package Stack
{{#if plugins}}
| Plugin | Purpose | Status |
|--------|---------|--------|
{{#each plugins}}
| {{this.name}} | {{this.purpose}} | {{this.status}} |
{{/each}}
{{else}}
*To be determined during development*
{{/if}}
---
## Integrations
### Required Integrations
{{#each integrations}}
- **{{this.name}}:** {{this.purpose}}
{{/each}}
### Future Integrations
{{#each future_integrations}}
- **{{this.name}}:** {{this.purpose}} *({{this.timeline}})*
{{/each}}
---
## Contact Strategy
### Primary Contact Method
{{contact_strategy}}
### Contact Channels
| Channel | Priority | Implementation |
|---------|----------|----------------|
{{#each contact_channels}}
| {{this.channel}} | {{this.priority}} | {{this.implementation}} |
{{/each}}
### Future: AI Integration
{{ai_integration_notes}}
---
## UX Constraints
*These constraints inform what's possible in Phase 4 (UX Design)*
### Platform Limitations
{{#each ux_constraints}}
- {{this}}
{{/each}}
### Performance Targets
| Metric | Target | Rationale |
|--------|--------|-----------|
| **Mobile First** | {{mobile_first}} | {{mobile_rationale}} |
| **Page Load** | {{page_load_target}} | {{load_rationale}} |
| **Offline Support** | {{offline_support}} | {{offline_rationale}} |
---
## Multilingual Requirements
{{#if multilingual}}
**Languages:** {{languages}}
**Implementation:** {{multilingual_implementation}}
**URL Structure:**
```
{{url_structure}}
```
**Translation Workflow:** {{translation_workflow}}
{{else}}
*Single language site*
{{/if}}
---
## SEO Requirements
### Technical SEO
{{#each seo_requirements}}
- {{this}}
{{/each}}
### Structured Data
| Page Type | Schema Type | Key Properties |
|-----------|-------------|----------------|
{{#each structured_data}}
| {{this.page_type}} | {{this.schema_type}} | {{this.properties}} |
{{/each}}
### Local SEO (if applicable)
{{#if is_local_business}}
- [ ] Google Business Profile claimed and verified
- [ ] NAP consistency (Name, Address, Phone) across all pages
- [ ] Business category set correctly
- [ ] Service area defined
- [ ] Photos uploaded
{{else}}
*Not a local business*
{{/if}}
### Performance & Infrastructure
| Metric | Target |
|--------|--------|
| **Largest Contentful Paint (LCP)** | < 2.5 seconds |
| **First Input Delay (FID)** | < 100ms |
| **Cumulative Layout Shift (CLS)** | < 0.1 |
| **Page Load (4G)** | < 3 seconds |
| **Total Page Weight** | < 3MB |
| **Individual Image Size** | < 200KB (hero < 400KB) |
| **Mobile-Friendly** | Yes |
| **Favicon** | All sizes (16, 32, 180, 192px) |
### Security Headers
| Header | Purpose |
|--------|---------|
| **Strict-Transport-Security (HSTS)** | Force HTTPS |
| **Content-Security-Policy (CSP)** | Prevent XSS |
| **X-Content-Type-Options** | Prevent MIME sniffing |
| **X-Frame-Options** | Prevent clickjacking |
| **Referrer-Policy** | Control referrer info |
| **Permissions-Policy** | Restrict browser features |
### SEO Plugin/Tools
{{seo_tools}}
---
## Maintenance & Ownership
| Aspect | Owner | Notes |
|--------|-------|-------|
| **Content Updates** | {{content_owner}} | {{content_notes}} |
| **Technical Maintenance** | {{tech_owner}} | {{tech_notes}} |
| **Plugin Updates** | {{plugin_owner}} | {{plugin_notes}} |
---
## Development Handoff Notes
*For Phase 6 (Deliveries)*
### Environment Setup
{{environment_setup}}
### Deployment Process
{{deployment_process}}
### Key Considerations
{{#each dev_considerations}}
- {{this}}
{{/each}}
---
## Next Steps
- [ ] **Content & Language** Define tone, languages, SEO keywords
- [ ] **Visual Direction** Establish visual style and brand
- [ ] **Phase 2: Trigger Mapping** Map user psychology
- [ ] **Phase 4: UX Design** Begin design within these constraints
---
_Generated by Whiteport Design Studio_

View File

@@ -0,0 +1,69 @@
# WDS Platform Requirements Template
# Save to: A-Project-Brief/platform-requirements.yaml
project:
name: "Project Name"
type: "mobile_app" # mobile_app | web_app | desktop_app | api
wds_version: "6.0"
created_at: "YYYY-MM-DDTHH:MM:SSZ"
platform:
frontend:
framework: "framework-name" # react_native | react | vue | angular | svelte
version: "X.X"
state_management: "library" # zustand | redux | mobx | context
navigation: "library" # react_navigation | react_router | vue_router
styling: "approach" # tailwind | styled_components | css_modules
ui_library: "library" # shadcn | mui | chakra (optional)
backend:
framework: "framework-name" # supabase | firebase | express | fastapi | django
version: "X.X"
auth: "auth-provider" # supabase_auth | firebase_auth | auth0 | custom
database: "database-type" # postgresql | mysql | mongodb | firestore
storage: "storage-provider" # supabase_storage | s3 | cloudinary
api: "api-type" # rest | graphql | grpc
database:
type: "database-type" # postgresql | mysql | mongodb
version: "XX"
orm: "orm-library" # prisma | typeorm | mongoose (optional)
deployment:
frontend: "platform" # expo_eas | vercel | netlify | aws
backend: "platform" # supabase_cloud | firebase | heroku | aws
ci_cd: "platform" # github_actions | gitlab_ci | circle_ci
hosting: "platform" # vercel | netlify | aws (if web app)
integrations:
- name: "integration-name"
provider: "provider-name"
required: true # true | false
purpose: "[Why this integration is needed]"
- name: "integration-name"
provider: "provider-name"
required: false
purpose: "[Why this integration is needed]"
constraints:
- "[Technical constraint 1]"
- "[Technical constraint 2]"
- "[Business constraint 1]"
- "[Regulatory constraint 1]"
performance_requirements:
- "[Performance requirement 1]"
- "[Performance requirement 2]"
- "[Performance requirement 3]"
security_requirements:
- "[Security requirement 1]"
- "[Security requirement 2]"
- "[Security requirement 3]"
wds_metadata:
project_brief: "A-Project-Brief/project-brief.md"
trigger_map: "B-Trigger-Map/trigger-map.md"
scenarios: "C-UX-Scenarios/"
design_system: "D-Design-System/"

View File

@@ -0,0 +1,70 @@
# Context & Working Relationship
**Step:** Phase 0 - Project Setup
**Completed:** {{date}}
**Session:** {{session_number}}
---
## Project Metadata
**Project Name:** {{project_name}}
**Project Slug:** {{project_slug}}
**Product Type:** {{website|web_app|mobile_app|landing_page}}
**Industry:** {{industry}}
---
## Working Relationship Context
### Stakes
**Level:** {{personal|business|departmental|enterprise}}
**What this means:**
{{explanation_of_stakes}}
**Stakeholders (if applicable):**
{{stakeholder_list_or_none}}
**Political Sensitivities (if applicable):**
{{sensitivities_or_none}}
---
### Collaboration Style
**Involvement Level:** {{collaborative|balanced|autonomous}}
**User Role:** {{role_description}}
**Recommendation Style:** {{options|recommend|direct}}
**What this means for our work:**
{{how_this_shapes_collaboration}}
---
### Documentation Approach
**Documentation Needs:** {{minimal|standard|comprehensive}}
**Justification Level:** {{trust_based|balanced|evidence_based}}
**Adapted approach:**
- Tone: {{tone_description}}
- Detail level: {{detail_level}}
- Evidence requirements: {{evidence_approach}}
---
## Project Configuration
**Brief Level:** {{complete|simplified}}
**Strategic Analysis:** {{full|simplified|skip}}
**Skip Design System:** {{yes|no}}
**Skip Trigger Map:** {{yes|no}}
**Product Complexity:** {{simple|standard|complex}}
**Tech Stack:** {{tech_stack_or_tbd}}
**Component Library:** {{library_or_tbd}}
---
**Documented in:** `wds-project-outline.yaml` (frontmatter)

View File

@@ -0,0 +1,85 @@
# Step 2: Vision Capture
**Completed:** {{date}}
**Session:** {{session_number}}
**Substeps:** 01-open-conversation → 02-explore-vision → 03-reflect-confirm → 04-synthesize-document
---
## Opening Question
**Agent asked:**
{{opening_question_adapted_to_context}}
**User's initial response:**
{{first_response}}
---
## Conversation Highlights
### Key Exchange 1
**Agent:** {{question_or_followup}}
**User:** {{response}}
**Signal detected:** {{signal_type}} — {{what_this_revealed}}
### Key Exchange 2
**Agent:** {{question_or_followup}}
**User:** {{response}}
**Signal detected:** {{signal_type}} — {{what_this_revealed}}
### Key Exchange 3
**Agent:** {{question_or_followup}}
**User:** {{response}}
**Signal detected:** {{signal_type}} — {{what_this_revealed}}
---
## Conversation Flow Summary
{{narrative_summary_of_conversation}}
**Total exchanges:** {{count}}
**Duration:** {{approximate_time}}
---
## Reflection Checkpoint
**Agent's synthesis (2-3 sentences):**
{{what_im_hearing_is}}
**User response:**
- [x] Confirmed
- [ ] Corrected
**Corrections (if any):**
{{what_was_misunderstood_and_corrected}}
---
## Synthesized Vision
{{vision_statement}}
---
## Key Insights Captured
1. {{insight_1}}
2. {{insight_2}}
3. {{insight_3}}
---
## Example Context (if applicable)
**Concrete example provided:**
{{example_scenario_or_none}}
This example shaped understanding of: {{what_example_clarified}}
---
**Documented in:** `wds-project-outline.yaml``vision`
**Referenced in:** Product Brief documentation

View File

@@ -0,0 +1,82 @@
# Step 3: User Definition
**Completed:** {{date}}
**Session:** {{session_number}}
---
## Opening Question
**Agent asked:**
{{opening_question_about_users}}
**User's initial response:**
{{first_response}}
---
## User Exploration
### Primary User Discovery
**Key exchanges:**
**Agent:** {{followup_question}}
**User:** {{response}}
**Agent:** {{deeper_question}}
**User:** {{response}}
**Agent:** {{clarifying_question}}
**User:** {{response}}
---
## Reflection Checkpoint
**Agent's synthesis:**
{{understanding_of_primary_user}}
**User response:**
- [ ] Confirmed
- [ ] Corrected
**Corrections (if any):**
{{corrections}}
---
## Primary User Definition
**Who they are:**
{{user_description}}
**Their context:**
{{situation_and_environment}}
**Their frustrations:**
{{pain_points}}
**What they're trying to achieve:**
{{goals_and_jobs_to_be_done}}
**How they currently solve this:**
{{current_alternatives}}
---
## Secondary Users (if applicable)
**User 2:** {{description_or_none}}
**User 3:** {{description_or_none}}
---
## User Scenarios Captured
**Scenario 1:** {{concrete_example}}
**Scenario 2:** {{concrete_example}}
---
**Documented in:** `wds-project-outline.yaml``users`

View File

@@ -0,0 +1,82 @@
# Step 4: Product Concept
**Completed:** {{date}}
**Session:** {{session_number}}
---
## Purpose
Capture the designer's STRUCTURAL vision - the founding principle or key feature that defines the product concept.
**Not just requirements - the IDEA.**
---
## Concept Exploration
**Agent asked:**
{{question_to_surface_concept}}
**User described:**
{{concept_description}}
---
## Deep Dive
### Core Structural Idea
**The founding principle:**
{{what_makes_this_product_distinct}}
**Concrete example:**
{{specific_example_of_concept_in_action}}
### Why This Matters
**User's rationale:**
{{why_this_approach}}
**Problem it solves:**
{{what_this_enables}}
---
## Reflection Checkpoint
**Agent's synthesis:**
{{understanding_of_concept}}
**User response:**
- [ ] Confirmed
- [ ] Corrected
**Corrections (if any):**
{{corrections}}
---
## Concept Documentation
**Core concept:**
{{concept_statement}}
**Implementation principle:**
{{how_this_shapes_design}}
**Example:** {{concrete_example}}
---
## Related Features
Features that stem from this concept:
1. {{feature_1}}
2. {{feature_2}}
3. {{feature_3}}
---
**Documented in:** `wds-project-outline.yaml``product_concept`
**Impacts:** Navigation structure, information architecture, feature priorities

View File

@@ -0,0 +1,72 @@
# Step 6: Inspiration & References
**Completed:** {{date}}
**Session:** {{session_number}}
---
## Visual Preference Exploration
### What User Likes
**Reference 1:** {{site_or_example}}
**What they like:** {{specific_elements}}
**Why it resonates:** {{reason}}
**Reference 2:** {{site_or_example}}
**What they like:** {{specific_elements}}
**Why it resonates:** {{reason}}
**Reference 3:** {{site_or_example}}
**What they like:** {{specific_elements}}
**Why it resonates:** {{reason}}
---
### What User Dislikes
**Reference 1:** {{site_or_example}}
**What to avoid:** {{specific_elements}}
**Why it doesn't work:** {{reason}}
**Reference 2:** {{site_or_example}}
**What to avoid:** {{specific_elements}}
**Why it doesn't work:** {{reason}}
---
## Style Preferences
**Overall aesthetic:** {{description}}
**Color preferences:** {{notes}}
**Tone/mood:** {{description}}
**Level of complexity:** {{simple|balanced|rich}}
---
## Competitor Analysis (if discussed)
**Competitor 1:** {{name}}
- What they do well: {{strengths}}
- Where they fall short: {{weaknesses}}
- How we'll differentiate: {{approach}}
**Competitor 2:** {{name}}
- What they do well: {{strengths}}
- Where they fall short: {{weaknesses}}
- How we'll differentiate: {{approach}}
---
## Reference Material Collected
- [{{name}}]({{url}}) — {{what_to_extract}}
- [{{name}}]({{url}}) — {{what_to_extract}}
- [{{name}}]({{url}}) — {{what_to_extract}}
---
**Documented in:**
- `inspiration/visual-refs.md`
- `inspiration/competitor-analysis.md`
- `wds-project-outline.yaml``inspiration`

View File

@@ -0,0 +1,86 @@
# Step 7: Positioning
**Completed:** {{date}}
**Session:** {{session_number}}
---
## Positioning Exploration
**Agent asked:**
{{opening_question_about_positioning}}
**User's initial response:**
{{first_response}}
---
## Key Exchanges
### Differentiation
**Agent:** {{question_about_difference}}
**User:** {{response}}
**What this revealed:**
{{insight_about_unique_angle}}
---
### Market Context
**Agent:** {{question_about_alternatives}}
**User:** {{response}}
**What this revealed:**
{{insight_about_competitive_landscape}}
---
### Value Proposition
**Agent:** {{question_about_value}}
**User:** {{response}}
**What this revealed:**
{{insight_about_core_value}}
---
## Reflection Checkpoint
**Agent's synthesis:**
{{positioning_understanding}}
**User response:**
- [ ] Confirmed
- [ ] Corrected
**Corrections (if any):**
{{corrections}}
---
## Positioning Statement
{{positioning_statement}}
**For:** {{target_user}}
**Who:** {{their_situation}}
**This product:** {{what_it_is}}
**That:** {{key_benefit}}
**Unlike:** {{alternatives}}
**Our approach:** {{differentiation}}
---
## Supporting Evidence
**Why this position makes sense:**
1. {{rationale_1}}
2. {{rationale_2}}
3. {{rationale_3}}
---
**Documented in:** `wds-project-outline.yaml``positioning`

View File

@@ -0,0 +1,81 @@
# Dialog Template Usage
## Quick Start
**Copy to project:**
```bash
cp -r workflows/1-project-brief/templates/project-brief-dialog projects/{{slug}}/dialog
```
**Update as you progress:**
- Complete each file when the corresponding PB step finishes
- Update README.md progress tracker
- Append to decisions.md whenever key decisions are made
---
## What to Capture
### DO:
- Key questions + user responses (not full transcript)
- Signal-based follow-ups that revealed insights
- Reflection checkpoint (synthesis + confirmation + corrections)
- Final outputs (vision, positioning, etc.)
- WHY decisions were made
### DON'T:
- Verbatim transcripts
- Procedural agent actions
- Implementation details
- Repetitive exchanges
---
## Mandatory Checkpoints
**Document EVERY reflection:**
1. Agent's synthesis (2-3 sentences)
2. User confirmed or corrected?
3. What was misunderstood? (if corrected)
---
## Integration with Steps
**Each step file should mandate:**
```markdown
## Design Log Update
Before marking complete:
1. Update `dialog/{{step}}-{{name}}.md`
2. Document reflection checkpoint
3. Record final synthesis
4. Mark complete in `dialog/README.md`
```
---
## File Sizes
All dialog files: 65-86 lines (well under 100-line target)
---
## Design Log (Meta-Level)
**For multi-session work**, agents should use the design log for state tracking and `_progress/agent-experiences/` for session insights.
**Location:** `{{root_folder}}/_progress/00-design-log.md`
**Update Protocol:**
1. Complete current task
2. Update design log with changes
3. Show git diff to user
4. Record session insights in `_progress/agent-experiences/` if needed
---
## Purpose
Create transparent record of discovery conversations so future agents (and humans) understand WHY decisions were made, not just WHAT was decided. The design log provides this continuity across sessions.

View File

@@ -0,0 +1,85 @@
# Key Decisions Log
**Project:** {{project_name}}
**Format:** Append-only decision log
---
## Decision 1: {{decision_topic}}
**Date:** {{date}}
**Step:** {{step_where_decided}}
**Session:** {{session_number}}
**Context:**
{{what_prompted_this_decision}}
**What was decided:**
{{the_decision}}
**Why:**
{{rationale}}
**Impact:**
{{how_this_shapes_project}}
**Alternatives considered:**
- {{option_1}} — {{why_not}}
- {{option_2}} — {{why_not}}
**Documented in:** {{file_path}}
---
## Decision 2: {{decision_topic}}
**Date:** {{date}}
**Step:** {{step_where_decided}}
**Session:** {{session_number}}
**Context:**
{{what_prompted_this_decision}}
**What was decided:**
{{the_decision}}
**Why:**
{{rationale}}
**Impact:**
{{how_this_shapes_project}}
**Alternatives considered:**
- {{option_1}} — {{why_not}}
- {{option_2}} — {{why_not}}
**Documented in:** {{file_path}}
---
## Decision 3: {{decision_topic}}
**Date:** {{date}}
**Step:** {{step_where_decided}}
**Session:** {{session_number}}
**Context:**
{{what_prompted_this_decision}}
**What was decided:**
{{the_decision}}
**Why:**
{{rationale}}
**Impact:**
{{how_this_shapes_project}}
**Alternatives considered:**
- {{option_1}} — {{why_not}}
**Documented in:** {{file_path}}
---
_Continue appending decisions as they're made throughout the Product Brief process._

View File

@@ -0,0 +1,76 @@
# Product Brief Dialog: {{project_name}}
**Agent:** Saga (Product Brief Analyst)
**Project:** {{project_name}}
**Started:** {{start_date}}
**Status:** {{in_progress|completed}}
**Last Updated:** {{current_date}}
---
## About This Dialog
This dialog tracks the Product Brief discovery process - the conversations, reflections, decisions, and synthesis that led to the documented brief.
---
## Project Context
**Client/Stakeholder:** {{client_name}} ({{relationship}})
**Designer:** {{designer_name}}
**Sign-off Authority:** {{who_approves}}
**Project Type:** {{internal|external|agency}}
**Working Relationship:**
{{Brief description of stakes, involvement level, how directive to be}}
---
## Progress Tracker
- [ ] [Vision Capture](02-vision.md) — What we're building and why
- [ ] [User Definition](03-users.md) — Who we're building for
- [ ] [Product Concept](04-concept.md) — The founding structural idea
- [ ] [Core Features](05-features.md) — Essential functionality
- [ ] [Inspiration & References](06-inspiration.md) — Visual preferences and references
- [ ] [Positioning](07-positioning.md) — Market position and differentiation
- [ ] [Success Metrics](08-metrics.md) — How we measure success
- [ ] [Constraints](09-constraints.md) — Limitations and boundaries
- [ ] [Launch Requirements](10-launch.md) — What's needed to ship
- [ ] [Timeline & Phases](11-timeline.md) — Roadmap and milestones
- [ ] [Review & Synthesis](12-synthesis.md) — Final review and signoff
---
## Key Decisions
See [decisions.md](decisions.md) for detailed decision log.
**Major decisions:**
1. {{decision_summary_1}}
2. {{decision_summary_2}}
3. {{decision_summary_3}}
---
## Reflection Quality
**Total Checkpoints:** {{count}}
**Confirmed First Try:** {{count}}
**Required Correction:** {{count}}
This measures how well the agent understood the user's intent.
---
## Dialog Artifacts
All dialog files are timestamped and track the natural conversation flow, not just the final outputs.
**Purpose:** Enable future agents (or humans) to understand WHY decisions were made, not just WHAT was decided.
---
**Generated Artifacts:**
- [wds-project-outline.yaml](../../projects/{{project_slug}}/wds-project-outline.yaml)
- [Product Brief documentation](../../projects/{{project_slug}}/A-Product-Brief/)

View File

@@ -0,0 +1,187 @@
# Project Brief: {{project_name}}
> Complete Strategic Foundation
**Created:** {{date}}
**Author:** {{user_name}}
**Brief Type:** Complete
---
## Vision
{{vision}}
---
## Positioning Statement
{{positioning_statement}}
**Breakdown:**
- **Target Customer:** {{target_customer}}
- **Need/Opportunity:** {{need_opportunity}}
- **Category:** {{category}}
- **Key Benefit:** {{key_benefit}}
- **Differentiator:** {{differentiator}}
---
## Business Model
**Type:** {{business_model}}
## {{#if business_model_b2b}}
## Business Customer Profile (B2B)
{{business_customer_profile}}
### Buying Roles
| Role | Description |
| ------------ | ----------------- |
| **Buyer** | {{buyer_role}} |
| **Champion** | {{champion_role}} |
| **User** | {{user_role}} |
{{/if}}
---
## {{#if business_model_b2b}}User Profile (within Business){{else}}Ideal Customer Profile (ICP){{/if}}
{{ideal_user_profile}}
### Secondary Users
{{secondary_users}}
---
## Success Criteria
{{success_criteria}}
---
## Competitive Landscape
{{competitive_landscape}}
### Our Unfair Advantage
{{unfair_advantage}}
---
## Constraints
{{constraints}}
---
## Platform & Device Strategy
**Primary Platform:** {{primary_platform}}
**Supported Devices:**
{{supported_devices}}
**Device Priority:** {{device_priority}}
**Interaction Models:**
{{interaction_models}}
**Technical Requirements:**
- **Offline Functionality:** {{offline_requirements}}
- **Native Features:** {{native_features_needed}}
**Platform Rationale:**
{{platform_rationale}}
**Future Platform Plans:**
{{future_platform_plans}}
**Design Implications:**
{{design_implications}}
**Development Implications:**
{{development_implications}}
---
## Tone of Voice
**For UI Microcopy & System Messages**
### Tone Attributes
1. **{{tone_attribute_1}}**: {{tone_description_1}}
2. **{{tone_attribute_2}}**: {{tone_description_2}}
3. **{{tone_attribute_3}}**: {{tone_description_3}}
{{#if tone_attribute_4}}4. **{{tone_attribute_4}}**: {{tone_description_4}}{{/if}}
{{#if tone_attribute_5}}5. **{{tone_attribute_5}}**: {{tone_description_5}}{{/if}}
### Examples
**Error Messages:**
- ✅ {{tone_example_error_good}}
- ❌ {{tone_example_error_bad}}
**Button Text:**
- ✅ {{tone_example_button_good}}
- ❌ {{tone_example_button_bad}}
**Empty States:**
- ✅ {{tone_example_empty_good}}
- ❌ {{tone_example_empty_bad}}
**Success Messages:**
- ✅ {{tone_example_success_good}}
- ❌ {{tone_example_success_bad}}
### Guidelines
**Do:**
{{tone_do_guidelines}}
**Don't:**
{{tone_dont_guidelines}}
---
*Note: Tone of Voice applies to UI microcopy (labels, buttons, errors, system messages). Strategic content (headlines, feature descriptions, value propositions) uses the Content Creation Workshop based on page-specific purpose and context.*
---
## Additional Context
{{additional_context}}
---
## Business Context
- **Primary Goal:** {{business_goal}}
- **Solution:** {{solution}}
- **Target Users:** {{target_users}}
*Full strategic analysis (business goals, personas, driving forces) is developed in [Phase 2: Trigger Mapping](../B-Trigger-Map/).*
---
## Next Steps
This complete brief provides strategic foundation for all design work:
- [ ] **Phase 2: Trigger Mapping** - Map user psychology to business goals
- [ ] **Phase 3: PRD Platform** - Define technical foundation
- [ ] **Phase 4: UX Design** - Begin sketching and specifications
- [ ] **Phase 5: Design System** - If enabled, build components
- [ ] **Phase 6: PRD Finalization** - Compile for development handoff
---
_Generated by Whiteport Design Studio_

View File

@@ -0,0 +1,277 @@
# Service Agreement
**Project**: {{project_name}}
**Date**: {{date}}
**Client/Owner**: {{client_name}}
**Service Provider**: {{service_provider_name}}
**Contract Language**: {{contract_language}}
**Governing Law/Jurisdiction**: {{governing_jurisdiction}}
---
> **Agreement Philosophy**: This agreement is designed to be simple, fair, and clear - providing reliable terms that support a long-lasting working relationship between both parties.
---
## 1. Project Overview
### The Realization
{{realization}}
### Recommended Solution
{{recommended_solution}}
---
## 2. Scope of Services
### The Path Forward
{{path_forward}}
### Deliverables
Based on the path forward, the following deliverables will be provided:
{{deliverables_list}}
---
## 3. Our Commitment
{{our_commitment}}
---
### Payment Terms
**Total Agreement Amount**: {{total_amount}}
**Payment Structure**: {{payment_structure}}
**Payment Schedule**:
{{payment_schedule}}
**Background**: Clear payment terms protect both parties and ensure fair compensation.
**What it does**: Defines when and how payments will be made.
**Purpose**:
- Ensures service provider receives fair compensation for work
- Provides client with clear payment expectations
- Protects both parties from payment disputes
- For fixed-price agreements, upfront payment is fair since service provider assumes cost overrun risk
**Payment Terms Details**:
- **Payment Method**: {{payment_method}} (check, wire transfer, credit card, etc.)
- **Payment Due Dates**: {{payment_due_dates}}
- **Late Payment**: {{late_payment_terms}} (e.g., interest charges, work suspension)
- **Payment Conditions**: {{payment_conditions}} (e.g., payment required before work begins, payment tied to deliverables)
**For Fixed-Price Agreements**:
This is a fixed-price agreement, meaning the service provider commits to deliver specified work for the agreed price, regardless of actual costs. Since the service provider assumes the risk of cost overruns, upfront payment (50-100%) is standard and fair. This demonstrates client commitment and enables the service provider to deliver quality work without cash flow concerns.
---
## 4. Timeline
{{timeline}}
*Note: Timeline is based on the path forward outlined above and may be adjusted based on project requirements.*
---
## 5. Why It Matters
{{why_it_matters}}
---
## 6. Expected Outcomes
### The Value We'll Create
{{value_we_create}}
---
## 7. Service Terms
### Payment Terms
{{payment_terms}}
### Deliverable Acceptance
Deliverables will be considered accepted upon:
- Completion according to specifications
- Review and approval by client
- Any requested revisions completed
### Intellectual Property
All deliverables and work products will be owned by {{client_name}} upon full payment.
---
## 8. Risks and Considerations
### Cost of Inaction
{{cost_of_inaction}}
---
## 9. Confidentiality
### Confidentiality Clause
**Background**: This clause protects sensitive information shared during the project.
**What it does**: Both parties agree to keep project information confidential.
**Purpose**: Protects proprietary information, business strategies, trade secrets, and sensitive data.
**Terms**:
Both parties agree to:
- Keep all project-related information confidential
- Not disclose project details to third parties without written consent
- Use confidential information solely for project purposes
- Return or destroy confidential materials upon project completion or termination
- Maintain confidentiality obligations even after project completion
**Exceptions**:
- Information already publicly known
- Information independently developed
- Information required by law to be disclosed
**Duration**: Confidentiality obligations shall remain in effect for [X] years after project completion.
---
## 10. Not to Exceed Clause
### Budget Cap
**Background**: This clause sets a maximum budget limit.
**What it does**: States that total costs will not exceed a specified amount without prior written approval.
**Purpose**:
- Protects both parties from unexpected cost overruns
- Ensures budget control
- **Prevents scope creep** - Any work beyond the original scope requires approval and may affect the budget cap
**Terms**:
- Total project costs shall not exceed **{{not_to_exceed_amount}}** without prior written approval from {{client_name}}
- Any work that would exceed this amount must be approved in advance
- If additional work is needed, a change order must be signed before proceeding
- This cap includes all fees, expenses, and costs related to the project
**Change Orders and Scope Control**:
- Any changes to scope that affect cost must be documented in a written change order
- Change orders must be signed by both parties before work begins
- Change orders may adjust the not-to-exceed amount if agreed upon
- **Scope creep prevention**: Work outside the original scope (as defined in Section 2) requires a change order and approval before proceeding
- This clause helps prevent gradual expansion of project scope without proper authorization
---
## 11. Terms and Conditions
### Work Initiation
**When work begins**: {{work_initiation_date_or_condition}}
**Background**: This clause specifies exactly when the service provider is authorized to begin work.
**What it does**: Defines the start date or conditions that must be met before work begins.
**Purpose**:
- Prevents unauthorized work before agreement is fully executed
- Establishes clear timeline expectations
- Protects both parties by ensuring work only begins after proper authorization
**Initiation conditions** (select applicable):
- Upon full execution of this agreement (signatures from both parties)
- On a specific date: {{specific_start_date}}
- Upon receipt of initial payment/deposit
- Upon written notice from {{client_name}}
- Other: {{custom_initiation_condition}}
### Project Initiation
This project is initiated upon approval of the project pitch. Project initiation is considered complete upon stakeholder approval.
### Changes and Modifications
Any changes to scope, timeline, or investment must be agreed upon in writing by all parties.
### Termination
Either party may terminate this agreement with [X] days written notice. Upon termination, payment is due for work completed to date.
### Dispute Resolution
**Background**: Defines how conflicts will be resolved if they arise.
**What it does**: Establishes the process for handling disagreements.
**Purpose**: Provides a clear path for resolving disputes without costly litigation when possible.
**Method**: {{dispute_resolution_method}} (mediation/arbitration/litigation)
**Location**: {{dispute_resolution_location}}
Any disputes arising from this agreement shall be resolved through {{dispute_resolution_method}} in {{dispute_resolution_location}}.
---
### Governing Law and Jurisdiction
**Background**: Determines which laws apply and where legal proceedings would take place.
**What it does**: Specifies the legal framework and court system that governs the agreement.
**Purpose**: Provides legal clarity and predictability for both parties.
**Governing Law**: This agreement shall be governed by and construed in accordance with the laws of {{governing_jurisdiction}}.
**Jurisdiction**: Any legal proceedings arising from this agreement shall be subject to the exclusive jurisdiction of the courts of {{governing_jurisdiction}}.
**Contract Language**: This agreement is executed in {{contract_language}}. In case of translation, the {{contract_language}} version shall prevail.
---
## 12. Approval
**Client/Owner Approval**:
Signature: _________________
Name: {{client_name}}
Date: _______________
**Service Provider Approval**:
Signature: _________________
Name: {{service_provider_name}}
Date: _______________
---
## Appendix
### Reference Documents
- Project Pitch: `docs/1-project-brief/pitch.md`
- Project Brief: (To be created after agreement approval)
---
*This service agreement is based on the project pitch dated {{date}}.*

View File

@@ -0,0 +1,188 @@
# Project Signoff Document
**Project**: {{project_name}}
**Date**: {{date}}
**Department/Team**: {{department_name}}
**Project Owner**: {{project_owner}}
**Document Language**: {{contract_language}}
**Governing Jurisdiction**: {{governing_jurisdiction}} (if applicable)
---
> **Document Philosophy**: This signoff document is designed to be simple, fair, and clear - providing reliable terms that support successful project execution and clear accountability.
---
## 1. Project Overview
### The Realization
{{realization}}
### Recommended Solution
{{recommended_solution}}
---
## 2. Goals and Success Metrics
### What We're Trying to Accomplish
{{goals}}
### Success Metrics
{{success_metrics}}
### How We'll Measure Success
{{measurement_approach}}
### Key Performance Indicators (KPIs)
{{kpis}}
---
## 3. Budget and Resources
### Budget Allocation
**Total Budget**: {{total_budget}}
**Budget Breakdown** (if applicable):
{{budget_breakdown}}
### Resources Needed
{{resources_needed}}
### Not-to-Exceed Budget Cap
{{not_to_exceed_budget}}
---
## 4. Ownership and Responsibility
### Project Owner
{{project_owner}}
### Process Owner
{{process_owner}}
### Key Stakeholders
{{key_stakeholders}}
### Decision-Making Authority
{{decision_making_authority}}
---
## 5. Approval and Sign-Off
### Who Needs to Approve
{{approvers_list}}
### Approval Stages
{{approval_stages}}
### Sign-Off Process
{{signoff_process}}
### Timeline for Approval
{{approval_timeline}}
---
## 6. Timeline and Milestones
### Key Milestones
{{key_milestones}}
### Delivery Dates
{{delivery_dates}}
### Critical Deadlines
{{critical_deadlines}}
---
## 7. Optional Sections
### Risks and Considerations (Optional)
{{risks_and_considerations}}
### Confidentiality (Optional)
{{confidentiality_requirements}}
### The Path Forward (Optional - High-Level Overview)
{{path_forward_high_level}}
---
## 8. Approval and Signoff
This document serves as formal approval to proceed with the project as outlined above.
**Stakeholder Signoffs**:
**Project Sponsor**:
Name: _________________
Signature: _________________
Date: _______________
**Budget Approver**:
Name: _________________
Signature: _________________
Date: _______________
**Project Owner**:
Name: {{project_owner}}
Signature: _________________
Date: _______________
---
## 9. Next Steps
Upon signoff:
1. Proceed to full Project Brief development
2. Execute work plan as outlined above
3. Deliverables will be provided according to the agreed timeline
### Changes and Modifications
Any changes to scope, timeline, or investment must be agreed upon by all signatories.
---
## Appendix
### Reference Documents
- Project Pitch: `docs/1-project-brief/pitch.md`
- Project Brief: (To be created after signoff)
---
*This signoff document is based on the project pitch dated {{date}}.*

View File

@@ -0,0 +1,44 @@
# Project Brief: {{project_name}}
> Simplified Brief - Essential context for design work
**Created:** {{date}}
**Author:** {{user_name}}
**Brief Type:** Simplified
---
## Project Scope
{{project_scope}}
---
## Challenge / Opportunity
{{challenge_opportunity}}
---
## Design Goals
{{design_goals}}
---
## Constraints
{{constraints}}
---
## Next Steps
This simplified brief provides essential context for design work. The following phases can now proceed:
- [ ] **Phase 4: UX Design** - Begin sketching and specifications
- [ ] **Phase 5: Design System** - If enabled, build components alongside design
---
_Generated by Whiteport Design Studio_

View File

@@ -0,0 +1,209 @@
# Visual Direction: {{project_name}}
> Brand Aesthetics & Design Guidelines
**Created:** {{date}}
**Author:** {{user_name}}
**Related:** [Product Brief](./product-brief.md) | [Content & Language](./content-language.md)
---
## Existing Brand Assets
### Current Assets
{{existing_assets_summary}}
| Asset | Status | Location |
|-------|--------|----------|
{{#each existing_assets}}
| {{this.asset}} | {{this.status}} | {{this.location}} |
{{/each}}
### Brand Constraints
{{#each brand_constraints}}
- {{this}}
{{/each}}
---
## Visual References
### Inspiration Sites
{{#each reference_sites}}
**[{{this.name}}]({{this.url}})**
- What we like: {{this.what_we_like}}
- Relevance: {{this.relevance}}
{{/each}}
### Visual Mood
{{mood_description}}
**Keywords:** {{mood_keywords}}
---
## Design Style
### UI Style
**Primary Style:** {{ui_style}}
{{ui_style_description}}
**Characteristics:**
{{#each ui_style_characteristics}}
- {{this}}
{{/each}}
### Design Aesthetic
**Aesthetic:** {{design_aesthetic}}
{{aesthetic_description}}
---
## Color Direction
### Color Strategy
{{color_strategy}}
### Palette Direction
| Role | Direction | Notes |
|------|-----------|-------|
| **Primary** | {{color_primary}} | {{color_primary_notes}} |
| **Secondary** | {{color_secondary}} | {{color_secondary_notes}} |
| **Accent** | {{color_accent}} | {{color_accent_notes}} |
| **Background** | {{color_background}} | {{color_background_notes}} |
| **Text** | {{color_text}} | {{color_text_notes}} |
### Color Scheme Type
**Type:** {{color_scheme_type}}
*Reference: [Color Terminology](../../../docs/models/design-nomenclature/color-terminology.md)*
---
## Typography Direction
### Type Approach
{{typography_approach}}
### Font Direction
| Role | Style | Examples | Rationale |
|------|-------|----------|-----------|
| **Headlines** | {{headline_style}} | {{headline_examples}} | {{headline_rationale}} |
| **Body** | {{body_style}} | {{body_examples}} | {{body_rationale}} |
| **UI** | {{ui_font_style}} | {{ui_font_examples}} | {{ui_font_rationale}} |
*Reference: [Typography Classification](../../../docs/models/design-nomenclature/typography-classification.md)*
---
## Layout Direction
### Layout Approach
{{layout_approach}}
### Key Layout Elements
| Element | Approach | Notes |
|---------|----------|-------|
| **Hero Section** | {{hero_approach}} | {{hero_notes}} |
| **Content Layout** | {{content_layout}} | {{content_notes}} |
| **Navigation** | {{nav_approach}} | {{nav_notes}} |
| **Cards/Modules** | {{card_approach}} | {{card_notes}} |
*Reference: [Layout Terminology](../../../docs/models/design-nomenclature/layout-terminology.md)*
---
## Visual Effects
### Effect Usage
{{effects_approach}}
### Specific Effects
| Effect | Usage | Notes |
|--------|-------|-------|
{{#each effects}}
| {{this.effect}} | {{this.usage}} | {{this.notes}} |
{{/each}}
*Reference: [Visual Effects](../../../docs/models/design-nomenclature/visual-effects.md)*
---
## Photography & Imagery
### Photography Style
{{photography_style}}
### Image Sources
| Type | Source | Notes |
|------|--------|-------|
{{#each image_sources}}
| {{this.type}} | {{this.source}} | {{this.notes}} |
{{/each}}
### Image Guidelines
{{#each image_guidelines}}
- {{this}}
{{/each}}
---
## Design Constraints
*From Platform Requirements and brand needs*
{{#each design_constraints}}
- {{this}}
{{/each}}
---
## Summary: Visual DNA
```
Style: {{summary_style}}
Colors: {{summary_colors}}
Typography: {{summary_typography}}
Mood: {{summary_mood}}
Key Element: {{summary_key_element}}
```
---
## Next Steps
- [ ] **Phase 2: Trigger Mapping** — Connect visuals to user psychology
- [ ] **Phase 4: UX Design** — Apply visual direction to designs
- [ ] **Phase 5: Design System** — Build design tokens from direction
---
## Reference Files
- [visual-references/](./visual-references/) — Collected reference images
- [Design Nomenclature](../../../docs/models/design-nomenclature/index.md) — Vocabulary reference
---
_Generated by Whiteport Design Studio_