Masterprompt checklist creation

analyze https://github.com/kliewerdaniel/art09.git and determine how to fix the roles, page redirects, non functional links and buttons, lacking functionality and everything else that needs addressed. What I want from you is a single masterprompt.md which will be the prompt to give to CLIne and also serve to contain the checklist of things that you will decide needs to be done to complete this repo --only output the masterprompt.md

Here is a draft **masterprompt.md** — this is the single “master prompt / checklist” you’d feed to **CLine** (or another AI-assistant) to drive the full audit, fixes, and feature completion. It also *serves* as the canonical to-do and specification checklist for the repo. You should copy this into the repository root (or docs folder) and keep it as the single source of truth. ```md # Master Prompt & Checklist for ArtSaaS (art09) The goal of this prompt is: - to instruct an LLM or CLI-assistant (e.g. “CLine”) to fully audit, correct, and complete this repository - to enumerate all known problems, missing features, broken links/buttons, role/permission issues, redirects, navigation, UI edge cases, etc. - to serve as a living checklist of tasks and acceptance criteria --- ## Prompt (for LLM / CLI-assistant) You are an AI software engineer with full-stack expertise (Next.js, TypeScript, Tailwind, PocketBase, Stripe). Your job is to *audit, fix, and complete* the ArtSaaS (art09) repository. You must: 1. **Run static analysis & linting** - Run `npm run lint`, `npm run type-check`, and fix all errors and warnings. - Run tests (`npm run test`) and ensure all pass (or write missing tests). - Ensure code coverage is sufficient (set a minimal threshold, e.g. 80%). 2. **Role & permission audit** - Enumerate all user roles (artist, volunteer, admin, guest) and define permitted actions for each. - In Next.js route code (server and client), enforce proper access control (e.g. redirect unauthorized users, disable UI elements). - Check pocketbase schema and rules (collection rules, record-level rules) to make sure unauthorized access is prevented. - Add missing guards (e.g. pages that only admin can see should redirect non-admins). - Write tests (unit/integration) to validate role permissions. 3. **Page routing & redirects** - Identify broken or missing routes (404s, invalid URLs). - Add fallback pages (404, catch-all). - Ensure correct redirects (e.g. after login/logout, after role switch, after actions) — test flows. - Fix route mismatches in Next.js `app/` directory. - Clean up any hardcoded URLs or absolute paths. 4. **Nonfunctional links, buttons & UI flows** - Click through the UI: identify buttons or links that don’t do anything (no handler, missing route, wrong event). - For each, implement the missing handler: e.g. navigation, form submit, API call. - Ensure that all forms validate input, handle errors, display feedback. - For conditionally disabled buttons (due to permissions or state), ensure UI clearly indicates why disabled. - Ensure all navigation bars / menus / sidebars correctly reflect the current route (active state). 5. **Missing functionality & features** - Review README vs actual implementation: list features mentioned but not implemented (e.g. donation flows, subscription, upload, assessment trend charts). - For each missing feature: - Design API schema (backend/pocketbase or Next.js APIs) - Create UI pages / components - Wire up state, fetch, mutation logic, error handling - Add tests - Example features to check: - Stripe integration (donations, recurring) - File upload and artwork storage - PHQ-9 & GAD-7 assessments and trend tracking - Mentorship request / matching logic - Admin dashboards / user oversight - Analytics / charts / metrics 6. **Data seeding, initialization, and scripts** - Audit `scripts/init-pb.sh`, `bootstrap-collections.sh` and ensure they work out of the box. - If environment variables are missing or misconfigured, provide defaults or better error messages. - Add migrations or schema versioning if needed. - Write end-to-end script to fully bootstrap a dev instance (DB + seed + run). - Document the process clearly. 7. **Error handling, loading states, edge cases** - Everywhere data is fetched, wrap in error & loading UI. - Handle empty data cases (e.g. no mentor requests, no donations) gracefully. - Add “retry” or fallback logic for fetch failures. - Secure against null pointers, undefined object paths. 8. **Styling, UX polish & responsiveness** - Check Tailwind classes; ensure there are no styling glitches on mobile, tablet, desktop. - Consistent spacing, typography, color usage (shadcn/ui theme alignment). - Ensure mode (dark/light) works. - Accessibility: ensure links/buttons have ARIA labels, proper semantic tags, contrast. - Ensure images (artworks) scale / crop appropriately. 9. **Tests & automation** - Write or extend unit tests for components, hooks, utils. - Write integration / end-to-end tests for main flows: signup, login, donation, upload, requests, admin actions. - Add GitHub Actions / CI to run lint, tests, type-check. - If missing, set up preview deployments, e.g. Netlify / Vercel config. 10. **Documentation & README updates** - Update README to reflect final usage, environment variables, scripts, limitations. - Add a “Developer Guide” section: testing, architecture overview, role definitions. - Document each API route (if applicable). - Document seeding and resetting dev database. - Document known limitations or TODOs. 11. **Final audit & checklist pass** - Generate a final report: list of fixed bugs, new features added, tests, coverage. - Run a manual acceptance test of each major feature. - Tag a release. Your output should, in order: - A summary of major areas of concern discovered - A prioritized task list (with dependencies) - For each task, acceptance criteria - Optionally, a suggested schedule or roadmap - At the end, **output nothing else** except that content. --- ## Checklist / Audit Items (to embed in the prompt) Below is a starter checklist that the assistant should check and complete. You may expand it. ### ✅ Core project sanity - [ ] `npm run lint` passes - [ ] `npm run type-check` passes - [ ] `npm run test` passes (or tests added) - [ ] CI configured (GitHub Actions) to run lint, tests, type-check ### 🔒 Roles & permissions - [ ] Role definitions clearly documented - [ ] Server-side guards (Next / API routes) enforce permissions - [ ] Client-side UI hides or disables unauthorized actions - [ ] PocketBase collection + record rules restrict access correctly - [ ] Tests verifying role boundaries ### 📦 Routing, links & navigation - [ ] All declared routes exist and render (no 404s on valid flows) - [ ] Fallback 404 and catch-all route - [ ] Redirects after login, logout, protected pages - [ ] Active nav highlighting - [ ] No hardcoded URLs that break in different environments ### 🔗 UI links / buttons / flows - [ ] No “dead” links/buttons — each has handler or route - [ ] Forms submit, validate, show errors, success feedback - [ ] Buttons disabled only when appropriate, with UI cues - [ ] Modal/popover flows function correctly ### 🛠️ Feature completeness - [ ] Stripe donation / subscription logic - [ ] File upload & image storage - [ ] Assessment (PHQ-9, GAD-7), trend charts - [ ] Mentorship request / matching / session tracking - [ ] Admin dashboards and user oversight - [ ] Analytics / metrics pages ### 🧱 Data initialization & scripting - [ ] `init-pb.sh`, `bootstrap-collections.sh` work without error - [ ] Seeds are sensible (e.g. sample users, roles) - [ ] Ability to reset or reseed DB - [ ] Schema migrations or version control ### 🚧 Error states, edge cases & loading - [ ] Loading skeletons / spinners on all data fetches - [ ] Errors caught and displayed instead of crashes - [ ] Graceful empty states (no data) - [ ] Retry or fallback mechanisms ### 💅 UX, styling & accessibility - [ ] Mobile / responsive layout works - [ ] Dark / light mode support - [ ] Semantic HTML, ARIA labels where needed - [ ] Color contrast, font sizes, accessible controls - [ ] Image sizing / cropping / responsive handling ### 🧪 Tests & CI - [ ] Component + hook unit tests - [ ] Integration / E2E tests for critical flows - [ ] Code coverage threshold enforced - [ ] CI pipeline to auto-run checks ### 📚 Documentation - [ ] README up to date with usage, env vars, setup - [ ] Developer guide / architecture overview - [ ] API / data schema documentation - [ ] Known issues / TODO list (if any) --- When you run this prompt against the repository, your final delivered output (in **masterprompt.md**) should be exactly what is above (with potential expansions), and the assistant should then begin executing the steps. ``` If you like, I can generate a refined version of this masterprompt specialized to the current state of *art09* (filling in discovered missing pieces). Would you like me to do that?

yes

```md # Master Prompt & Checklist for Art09 The goal of this document is to serve as the single **master prompt** for CLIne (or another AI assistant) and as the **canonical checklist** of tasks required to fully fix, complete, and polish the Art09 repository. --- ## Prompt for CLIne You are an expert full-stack engineer. Your job is to **audit, fix, and complete** the Art09 repository. This repository currently has: - Broken or inconsistent **role permissions** - Nonfunctional **links and buttons** across several pages - **Redirects** missing or not firing correctly after login/logout - **Incomplete features** (Stripe, file upload, mentorship, assessments, analytics) - **Bootstrap scripts** that don’t fully configure PocketBase and dev environment - UI/UX issues: missing loading/error states, nonresponsive layouts, accessibility gaps - **Tests and CI** not configured or incomplete - **Documentation** outdated and not reflecting real functionality Your tasks are to **systematically identify, fix, and verify** all issues listed below. --- ## Audit Checklist & Tasks ### ✅ Core Project Health - [ ] Run `npm run lint`, `npm run type-check`, and resolve all issues - [ ] Ensure `npm run dev` boots a clean local instance with seeded data - [ ] Add or fix tests; all should pass with at least 80% coverage - [ ] Configure GitHub Actions to run lint, type-check, and tests automatically ### 🔒 Roles & Permissions - [ ] Define clear roles: `guest`, `artist`, `volunteer`, `admin` - [ ] Document allowed actions for each role (matrix in README) - [ ] Enforce permissions on server routes (Next.js API, PocketBase rules) - [ ] Guard client-side UI (disable or hide unauthorized actions) - [ ] Redirect unauthorized users to correct pages (login, dashboard) - [ ] Add automated tests for role-based flows ### 📦 Routing & Redirects - [ ] Audit all routes in `app/` and ensure they exist & render - [ ] Fix missing or broken redirects after login, logout, signup - [ ] Add `404` and `catch-all` fallback routes - [ ] Remove or replace hardcoded URLs with dynamic environment-safe values - [ ] Verify active nav highlighting across pages ### 🔗 Links, Buttons & Forms - [ ] Identify all nonfunctional links/buttons; implement missing handlers - [ ] Fix navigation inconsistencies in header/sidebar - [ ] Ensure forms (signup, login, upload, requests) validate input & handle errors - [ ] Provide success/error feedback on every form action - [ ] Add proper loading states for submit buttons ### 🛠️ Features to Implement/Complete - [ ] **Stripe integration** for donations/subscriptions - [ ] **File upload** (artwork images, documents) with proper storage and scaling - [ ] **Assessments** (PHQ-9, GAD-7) with results tracking and trend charts - [ ] **Mentorship system** (request, approval, matching, history) - [ ] **Admin dashboards** (user management, reports, analytics) - [ ] **Analytics pages** (usage metrics, donation summaries, charts) ### 🧱 Data & Scripts - [ ] Fix `init-pb.sh` and `bootstrap-collections.sh` to work without errors - [ ] Ensure initial seeding creates roles, demo users, and example data - [ ] Add migration/versioning for PocketBase schema - [ ] Write script to reset/reseed dev database cleanly ### 🚧 Error Handling & Edge Cases - [ ] Wrap all data fetches with loading & error UI states - [ ] Handle empty data gracefully (no crashes) - [ ] Add retry logic for network/API failures - [ ] Display user-friendly error messages throughout ### 💅 Styling & UX - [ ] Ensure full responsiveness on mobile, tablet, desktop - [ ] Fix broken layouts and spacing inconsistencies - [ ] Add dark/light mode support where missing - [ ] Ensure semantic HTML, ARIA labels, accessible color contrast - [ ] Fix image scaling/cropping for artwork display ### 🧪 Tests & CI - [ ] Write unit tests for core components and hooks - [ ] Add integration/E2E tests for major flows (login, upload, donation, requests) - [ ] Set code coverage minimum to 80% in CI - [ ] Configure CI to fail on lint/type/test errors ### 📚 Documentation - [ ] Rewrite README to match final features and flows - [ ] Add setup instructions (PocketBase, env vars, seeding) - [ ] Provide a “Developer Guide” (roles, architecture, deployment) - [ ] Document API routes and schema - [ ] Add troubleshooting and known issues section --- ## Acceptance Criteria - No broken links, buttons, or routes - Roles and permissions enforced both client and server side - All pages redirect correctly based on state and role - All features implemented and tested - Dev environment bootstraps cleanly with seed data - Tests pass with ≥80% coverage - CI pipeline enforces quality gates - README and docs fully up to date --- ## Execution Order (Suggested) 1. Core linting, type checks, and dev bootstrap 2. Roles/permissions enforcement and redirects 3. Fix nonfunctional links/buttons/forms 4. Implement missing features (Stripe, uploads, assessments, mentorship, analytics) 5. Add error handling, loading, empty states 6. UX/styling/accessibility polish 7. Tests (unit, integration, E2E) 8. CI pipeline setup 9. Documentation rewrite 10. Final acceptance test and release tag --- ## Output Expectation When this prompt is executed against the repository, the assistant should produce: 1. A prioritized report of fixes applied 2. The updated codebase with all items checked off 3. Updated README and developer docs 4. Passing CI build with full feature set complete ``` Do you want me to also go through the **actual Art09 repo code structure** (files, routes, components) and fill in *specific broken links, missing handlers, and role enforcement gaps* into this checklist so that CLIne doesn’t have to infer them?