@appsforgood/next-supabase-kit 0.1.0

package/design-briefs/education-course.md

@@ -0,0 +1,25 @@
+# Education Or Course Design Brief
+
+Use when designing learning platforms, course pages, lesson players, cohort dashboards, school tools, tutorials, docs learning paths, or assessment flows.
+
+## First Screen
+
+Show the learner's current path, next lesson, progress, assessment, or decision. Do not default to a generic inspirational landing page.
+
+## Required Inputs
+
+- Learner level, goal, prior knowledge, and constraints.
+- Course structure: modules, lessons, exercises, assessments, resources, cohorts, deadlines.
+- Content types: text, video, code, quiz, project, downloadable material, instructor notes.
+- Success measures: completion, mastery, certification, practice, feedback, community support.
+
+## Avoid
+
+- Progress bars without meaningful next action.
+- Generic course cards with no prerequisites or outcomes.
+- Overly decorative dashboards that obscure learning state.
+- Accessibility gaps in video, code, quizzes, or keyboard navigation.
+
+## Required States
+
+Not started, in progress, blocked, overdue, completed, failed assessment, feedback pending, offline or slow media, mobile lesson view.

package/design-briefs/marketplace.md

@@ -0,0 +1,21 @@
+# Marketplace Design Brief
+
+Use this brief for two-sided marketplaces, listings, booking flows, buyer portals, and seller dashboards.
+
+## Product Signals
+
+- First screen should expose searchable supply, buyer intent, or seller fulfillment work.
+- Avoid fake metrics and placeholder listings.
+- Make trust, availability, pricing, location, eligibility, and next action clear.
+
+## Required States
+
+- No results, filtered results, unavailable item, pending approval, sold/booked, dispute, loading, error, and success states.
+- Buyer and seller role differences.
+- Mobile search, compare, save, and contact flows.
+
+## Design Direction
+
+- Use visual assets that reveal the actual product, place, or listing condition.
+- Prioritize comparison, sorting, saved items, trust signals, and clear transaction steps.
+- Tokens must include status colors for availability, verification, warnings, and completion.

package/design-briefs/portfolio-venue.md

@@ -0,0 +1,25 @@
+# Portfolio Or Venue Design Brief
+
+Use when designing portfolios, personal sites, studios, restaurants, hotels, venues, galleries, agencies, clinics, real-estate showcases, or object/place-focused pages.
+
+## First Screen
+
+The person, place, brand, work, or object must be immediately visible through specific imagery, identity, or proof of work. Do not make the first screen a generic slogan with abstract decoration.
+
+## Required Inputs
+
+- The thing being showcased: person, venue, product, project, place, or service.
+- Real assets: photos, case studies, menus, rooms, locations, artifacts, testimonials, availability, or press.
+- Visitor intent: book, enquire, inspect, compare, visit, hire, buy, or read.
+- Brand tone and sensory details: material, atmosphere, pace, craft, audience, locality.
+
+## Avoid
+
+- Generic agency cards.
+- Dark blurred background photos that hide the actual subject.
+- Fake logos, fake awards, or vague testimonials.
+- Hero sections that do not reveal the real work or place.
+
+## Required States
+
+Image loading, missing asset, enquiry error, booking unavailable, mobile gallery, map/location fallback, long-name wrapping, accessibility for media and carousels.

package/design-briefs/saas.md

@@ -0,0 +1,21 @@
+# SaaS Design Brief
+
+Use this brief for subscription products, team workspaces, account portals, and workflow SaaS.
+
+## Product Signals
+
+- First screen should show the core job: pipeline, inbox, workspace, editor, report, or operational queue.
+- Avoid generic hero-first pages unless the request is explicitly marketing.
+- Make plan, billing, team, permission, and usage states easy to scan.
+
+## Required States
+
+- Trial, active, past due, canceled, and upgrade-required account states.
+- Empty workspace, no data yet, loading, error, disabled, and success states.
+- Mobile layout for the primary repeated workflow, not just the settings screen.
+
+## Design Direction
+
+- Use restrained density, predictable navigation, and domain-specific labels.
+- Prefer tables, split panes, timelines, and command surfaces over decorative cards.
+- Tokens must define semantic status colors, spacing density, radius, and focus states.

package/design-briefs/tool.md

@@ -0,0 +1,21 @@
+# Tool Design Brief
+
+Use this brief for calculators, generators, editors, workflow tools, dashboards, and focused utilities.
+
+## Product Signals
+
+- First screen should be the usable tool, not a landing page explaining the tool.
+- Primary controls, current result, and next action should be visible without scrolling on common viewports.
+- Avoid decorative wrappers around the actual work surface.
+
+## Required States
+
+- Ready, dirty, validating, loading, empty, error, disabled, success, export-ready, and mobile states.
+- Keyboard access for repeated actions.
+- Clear undo, reset, save, copy, download, and share behavior where relevant.
+
+## Design Direction
+
+- Favor stable dimensions, direct manipulation, compact controls, and strong feedback.
+- Use icons for repeated tool actions when a familiar icon exists.
+- Tokens must cover control size, focus rings, surface contrast, and responsive constraints.

package/dist/index.d.ts

@@ -0,0 +1,2 @@
+
+export {  }