Add CREATIVIA case study project (Lollypop Designathon 2025, Team 6)#27
Draft
tknatwork wants to merge 4 commits into
Draft
Add CREATIVIA case study project (Lollypop Designathon 2025, Team 6)#27tknatwork wants to merge 4 commits into
tknatwork wants to merge 4 commits into
Conversation
New `creativia/` project: an AI creative co-pilot for musicians, designed in 24 hours at the Lollypop Designathon 2025 by Team 6 around the Musician persona (Raj, a 24-year-old guitarist). This is a content-first scaffold; a working portfolio demo is planned as a later phase. Project content: - README.md — public-facing case study (brief, problem, persona, research, needs, pain points, the four-feature solution, brand system, team credits). - docs/CASE_STUDY.md — long-form write-up (Designathon context, program flow, evaluation, detailed persona use cases, pain-point -> feature mapping). - docs/BRAND.md — colour + type tokens (AI Soundwave gradient, Soundwave Blue, Accent Magenta, Almost Black, White; Outfit/Inter) with CSS variables. - docs/ROADMAP.md — phased plan from content -> static demo -> interactive demo. - assets/screens/ — 11 optimised images rendered from the team's A4 doc. - Standard scaffold: AGENTS.md, CLAUDE.md, LICENSE (MIT + design-IP note), docs/ redirects + CHANGELOG, .github copilot instructions + issue templates. Workspace registration: - README.md + AGENTS.md: two-project layout (Projects table, repo tree, project-scope rules, framing now includes design case studies). - docs/CHANGELOG.md: new-project entry. Attribution: concept is Team 6's collective work; the owner's individual contribution line is left as a TODO rather than guessed. https://claude.ai/code/session_011faX3YZF2UkdnmipG8QvnM
Replace the placeholder contribution TODO with the actual team structure: four design pods (product direction/PM, persona & research, presentation & dashboards, graphics) across eight product designers. Tushar built the presentation + dashboard screens with Drishti and shaped the niche features baked into the app. Updated README, CASE_STUDY, AGENTS content rule, and the project changelog note to match. https://claude.ai/code/session_011faX3YZF2UkdnmipG8QvnM
Read the real design file directly (design page 2:433, research board 129:5851) after the live screens were shared, and folded the verified content into the case study — plus corrected a few facts the PDF-only v0.1.0 got slightly wrong. Added: - User-interview research method (4 themes + questions) in README + CASE_STUDY. - Affinity-board synthesis (Target Audience / What Raj does / Needs / Pain points / Key Pointers) and per-use-case breakdowns. - assets/figma/ — cover, "what are we solving for", and the User Interview frame. - Note of additional artifacts (Userflow diagram, landing-page mockup). Corrected: - Brand tokens to the documented Figma values: primary gradient #FF0F7B -> #F89B29 (was #FE1E72->#F89030); Accent Magenta #E23670 (was #E32678). Updated BRAND.md, README table + badges, CSS vars. - Pain points 10 -> 11 (added "Lack of instant validation and feedback"); needs stated as the canonical 5. - Creative loop: ... -> Collaborate -> Refined Skill (was "Improvise"). - Sources now credit the Figma design file. https://claude.ai/code/session_011faX3YZF2UkdnmipG8QvnM
Pulled from a duplicate of the design file (node IDs preserved) after the live frames were shared, bypassing the original's rate limit: - Practice Session Analysis dashboard (node 77:425) — the owner's dashboard work, far crisper than the PDF render; now the Smart Practice visual. - Userflow sketches (A4-12, node 468:837). - CREATIVIA landing concept + design-process triptych (A4-8, node 468:739). Embedded in README + CASE_STUDY; CHANGELOG [0.2.0] and §9 artifacts updated. The design page is named "Documentation" in the file. https://claude.ai/code/session_011faX3YZF2UkdnmipG8QvnM
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a new project folder,
creativia/— CREATIVIA, an AI creative co‑pilot for musicians, designed in 24 hours at the Lollypop Designathon 2025 by Team 6 around the Musician persona (Raj, a 24‑year‑old guitarist).This is the content‑first phase the owner asked for — a portfolio‑ready case study. A small working demo is scoped as a later phase (see
creativia/docs/ROADMAP.md).Project content (
creativia/)README.md— public‑facing case study: brief, problem, persona, user‑interview research method, 5 needs + 11 pain points, the four‑feature solution (Instant Capture & Smart Analysis · Smart Practice Assistant · Iterate/Edit/Export · Media Library & Snippets), brand system, team & roles.docs/CASE_STUDY.md— long‑form (Designathon context, program flow, evaluation, research method + affinity‑board synthesis, detailed use cases, pain‑point → feature mapping).docs/BRAND.md— colour + type tokens (AI Soundwave gradient#FF0F7B→#F89B29, Soundwave Blue#2662D9, Accent Magenta#E23670, Almost Black#121212, White; Outfit/Inter) with CSS variables.docs/ROADMAP.md— phased plan: content → static demo → interactive demo → ship.assets/screens/— 11 optimised images from the A4 PDF;assets/figma/— frames pulled directly from the Figma design file (cover, "what are we solving for", User Interview).variables-styles-extractor/convention:AGENTS.md,CLAUDE.md,LICENSE,docs/redirects +CHANGELOG,.github/Copilot instructions + issue templates.Workspace changes
README.md+AGENTS.md— single‑project → two‑project layout (Projects table, repository tree, project‑scope rules, framing now includes design case studies).docs/CHANGELOG.md— new‑project entry.Content sourcing & accuracy
2:433, research board129:5851) once the live frames were shared. This added the user‑interview research method + affinity‑board synthesis, and corrected a few PDF‑era facts: brand tokens (#FF0F7B→#F89B29, magenta#E23670), pain‑point count (10 → 11), and the creative loop (… → Collaborate → Refined Skill, not "Improvise").Notes for review
LICENSEMIT covers the source/docs authored here; a note clarifies it does not transfer the Lollypop brand or the team's design IP.Next step
Decide whether to start Phase 1 (static demo scaffold) — proposed stack: Vite + TypeScript,
pnpm, brand tokens applied.https://claude.ai/code/session_011faX3YZF2UkdnmipG8QvnM
Generated by Claude Code