chore: add planning artifacts, UX screen prototypes, and Claude config

[don-petry]

Summary

• Add BMAD planning output: architecture decisions, epics breakdown, UX design specification, and implementation readiness report
• Add interactive UX screen prototypes (HTML) for all major app flows: onboarding, customer discovery, vendor home, manager dashboard, notifications, and design system documentation
• Add Claude Code memory bank and settings configuration for the project

These are planning artifacts generated during the BMAD methodology workflow and Claude Code project configuration. No application code changes.

Test plan

• Verify planning artifacts render correctly in GitHub markdown viewer
• Verify UX screen HTML files open correctly in a browser

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores

  • Updated version control to exclude machine-specific project memory files.

• Documentation

  • Added comprehensive documentation establishing workflow rules, design-to-implementation conventions, asset handling, approved tech stack, component and styling guidelines, accessibility and mobile UX requirements, testing expectations, and event/audit patterns.

[Copilot]

Pull request overview

Adds BMAD planning artifacts and UX prototype screens to support implementation planning for the “markets” app, along with Claude project configuration/memory files.

Changes:

• Added UX screen prototypes (HTML) and a versions.json index for screen/version tracking.
• Added UX design specification and an implementation readiness assessment report.
• Added Claude project guidance/config (CLAUDE.md, .claude/settings.json, and .claude/projects/.../memory/*).

Reviewed changes

Copilot reviewed 25 out of 26 changed files in this pull request and generated 20 comments.

Show a summary per file

File	Description
_bmad-output/planning-artifacts/ux-screens/versions.json	Index of UX screen files and version metadata.
_bmad-output/planning-artifacts/ux-screens/vendor-home.html	Vendor “My Markets” prototype screen.
_bmad-output/planning-artifacts/ux-screens/onboarding-vendor.html	Vendor onboarding flow prototypes (profile/products/markets).
_bmad-output/planning-artifacts/ux-screens/onboarding-manager.html	Manager onboarding + post-onboarding management prototypes.
_bmad-output/planning-artifacts/ux-screens/onboarding-customer.html	Customer onboarding flow prototypes (location/preferences/follow).
_bmad-output/planning-artifacts/ux-screens/onboarding-auth.html	Auth + role selection prototype.
_bmad-output/planning-artifacts/ux-screens/notification-preferences.html	Notification preferences prototype screens across roles.
_bmad-output/planning-artifacts/ux-screens/manager-dashboard.html	Manager dashboard prototype screen.
_bmad-output/planning-artifacts/ux-screens/design-system-components.html	Design system component catalog prototype.
_bmad-output/planning-artifacts/ux-screens/design-system-colors-typography.html	Design system tokens (colors/typography/spacing) reference.
_bmad-output/planning-artifacts/ux-screens/customer-following.html	Customer “Following” prototype screen.
_bmad-output/planning-artifacts/ux-screens/customer-discover.html	Customer “Discover” prototype screen.
_bmad-output/planning-artifacts/ux-screens/activity-log.html	Activity log prototype screens across roles.
_bmad-output/planning-artifacts/ux-design-specification.md	Comprehensive UX specification aligned to PRD/architecture.
_bmad-output/planning-artifacts/implementation-readiness-report-2026-03-21.md	Planning assessment of readiness, epic coverage, and gaps.
CLAUDE.md	Project conventions for design system, styling, Figma integration, and architecture rules.
.claude/settings.json	Claude plugin enablement configuration.
.claude/projects/-home-donpetry-markets/memory/user_role.md	Claude memory content describing user background/context.
.claude/projects/-home-donpetry-markets/memory/reference_winston.md	Claude memory reference note.
.claude/projects/-home-donpetry-markets/memory/project_stack_decisions.md	Claude memory stack decisions note.
.claude/projects/-home-donpetry-markets/memory/project_monetization.md	Claude memory monetization note.
.claude/projects/-home-donpetry-markets/memory/project_agentic_showcase.md	Claude memory methodology/showcase note.
.claude/projects/-home-donpetry-markets/memory/MEMORY.md	Index for the Claude memory folder.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates repository configuration and adds project-wide documentation: .gitignore now excludes Claude Code machine-specific project memory files, and two new docs (CLAUDE.md, Agents.md) define Figma-to-code rules, stack conventions, styling/component standards, accessibility, testing, and backend event-driven contracts.

Changes

Cohort / File(s)	Summary
Configuration .gitignore	Added entries to exclude Claude Code machine-specific project memory files (.claude/projects/-home-*).
Design & Figma workflow CLAUDE.md	New document prescribing Figma MCP workflow (get_design_context → get_metadata fallback, require get_screenshot), asset handling (use Figma MCP assets, store under assets/, use expo-image), mapping rules to Gluestack UI v3 and NativeWind, token usage, navigation conventions, and allowed icon sources.
Project standards & architecture Agents.md	New comprehensive project standards covering frontend/backend tech stack (React Native/Expo, TypeScript, Expo Router, Gluestack UI v3, NativeWind, Apollo/GraphQL, Go/gqlgen on Cloud Run, Firebase), component/layout organization, styling/naming/accessibility rules, mobile UX expectations, testing requirements, event-driven backend contract (audit logging, domain events, session variables), and forbidden patterns.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The PR title partially aligns with the changeset, referring to Claude config and planning artifacts, but misrepresents the actual contents: the commit summary shows CLAUDE.md and Agents.md (documentation standards), not UX screen prototypes or planning outputs in the current changes.	Clarify the scope: confirm whether the title should reflect only the current changeset (CLAUDE.md + Agents.md + .gitignore) or if planning artifacts and prototypes are in separate files not shown in the raw summary.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/planning-artifacts-and-config

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CLAUDE.md`:
- Around line 35-66: The fenced code block in CLAUDE.md containing the project
directory tree lacks a language specifier; update the opening fence from ``` to
```text (i.e., replace the triple backticks that start the block with ```text)
so the block is explicitly marked as plain text for proper syntax highlighting
and readability.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 07c66f58-0ffa-4662-89ea-98f3c0c026cd

📥 Commits

Reviewing files that changed from the base of the PR and between 72d45b3 and eae9c18.

⛔ Files ignored due to path filters (24)

• .claude/settings.json is excluded by !.claude/**
• _bmad-output/planning-artifacts/architecture.md is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/epics.md is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/implementation-readiness-report-2026-03-21.md is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-design-specification.md is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/activity-log.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/customer-discover.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/customer-following.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/design-system-colors-typography.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/design-system-components.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/manager-dashboard.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/notification-preferences.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/notifications.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/onboarding-auth.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/onboarding-customer.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/onboarding-manager.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/onboarding-vendor.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/prototype.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/vendor-home.html is excluded by !_bmad-output/**
• _bmad-output/planning-artifacts/ux-screens/versions.json is excluded by !_bmad-output/**
• _bmad-output/test-artifacts/test-design-architecture.md is excluded by !_bmad-output/**
• _bmad-output/test-artifacts/test-design-progress.md is excluded by !_bmad-output/**
• _bmad-output/test-artifacts/test-design-qa.md is excluded by !_bmad-output/**
• _bmad-output/test-artifacts/test-design/markets-handoff.md is excluded by !_bmad-output/**

📒 Files selected for processing (2)

• .gitignore
• CLAUDE.md

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CLAUDE.md`:
- Line 34: The documentation line referencing a non-existent config.ts should be
fixed: either create a new config.ts that exports the design token structure
used elsewhere (matching the shape documented in Agents.md, e.g., token keys and
types) or update CLAUDE.md to point to the actual file that contains design
tokens (reference Agents.md or the real token file name) so the instruction is
accurate; modify the sentence that currently names config.ts to instead
reference the chosen resolution and ensure it mentions mapping Figma colors to
the design token keys used by the project.
- Around line 11-12: Update CLAUDE.md to clarify that the Figma file identified
by file key `LMawgHcglco0TG32UAQUhE` (URL
`https://www.figma.com/design/LMawgHcglco0TG32UAQUhE/Markets`) requires explicit
"Anyone with the link" sharing for unauthenticated access; verify the current
sharing setting and state whether authentication/invitation is required, and if
so add instructions for requesting access or provide a public/exported link.
Include a one-line note next to the File key/URL entry indicating the verified
access level and a contact or steps to obtain access if it is not public.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: adc84516-bb75-45c6-9e48-3697a6958508

📥 Commits

Reviewing files that changed from the base of the PR and between 94549ae and a809d78.

📒 Files selected for processing (2)

• Agents.md
• CLAUDE.md

✅ Files skipped from review due to trivial changes (1)

• Agents.md

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify that config.ts does not exist in the repository.

# Search for config.ts in the repository
echo "Searching for config.ts..."
fd -t f '^config\.ts$'

if [ $? -ne 0 ] || [ -z "$(fd -t f '^config\.ts$')" ]; then
  echo "✗ config.ts not found in repository"
  echo "This confirms the documentation references a non-existent file."
else
  echo "✓ config.ts exists at the following location(s):"
  fd -t f '^config\.ts$'
fi

# Also check for similar config files that might be the intended reference
echo -e "\nChecking for similar config files..."
fd -t f 'config\.(ts|js|json)$' | head -10

Repository: petry-projects/markets

Length of output: 230

---

Fix documentation reference to non-existent config.ts file.

Line 34 instructs mapping Figma colors to design tokens in config.ts, but this file does not exist in the repository. This makes the documentation inaccurate and creates an impossible constraint for anyone attempting to follow these instructions.

Either create the config.ts file with the design token structure as specified in Agents.md, or update this line to reference the correct file where design tokens are actually stored.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CLAUDE.md` at line 34, The documentation line referencing a non-existent
config.ts should be fixed: either create a new config.ts that exports the design
token structure used elsewhere (matching the shape documented in Agents.md,
e.g., token keys and types) or update CLAUDE.md to point to the actual file that
contains design tokens (reference Agents.md or the real token file name) so the
instruction is accurate; modify the sentence that currently names config.ts to
instead reference the chosen resolution and ensure it mentions mapping Figma
colors to the design token keys used by the project.