# GenCreator Brand Foundation Canonical: https://gencreator.ai/brand Version: 1.0.0 ## Strategic Answer Yes. GenCreator has major potential, but the center of gravity should be scalable digital product first, community second, and 1:1 Studio judgment only after proof exists. ## Thesis GenCreator is a creator intelligence OS for generative culture: a premium self-serve product system, not a generic course funnel. ## Mission Help AI-native creators build systems that raise the quality of what they make. ## Vision A generative culture where creators use agents with taste, evidence, memory, attribution, and human approval. ## Positioning The self-serve creator intelligence OS: creation packets, activation plans, skill packs, agent packs, MCP resources, community practice, and Studio review. ## Promise One creator can operate with the discipline of an AI Center of Excellence while keeping their own voice, taste, and judgment. ## Strategic Choices - Build the scalable product before the services: The product must answer the first buyer question without a call: what do I make, install, practice, or buy this week? - Make MCP the software spine: MCP gives GenCreator a portable language for tools, resources, prompts, and approvals across assistants and workbenches. - Turn community into the compounding layer: GenCreator.community should start from artifacts, proof loops, and source pulse rituals so the system gets better through practice. - Keep 1:1 rare and high-trust: Personal help becomes more valuable when it reviews real work from the self-serve system, not vague ambition. ## Brand Assets - Primary vector mark: https://gencreator.ai/brand/gencreator-mark.svg Use: Navigation, app surfaces, product cards, export covers, and small-size proof. - One-color vector mark: https://gencreator.ai/brand/gencreator-mark-mono.svg Use: High-contrast surfaces, favicons, partner decks, invoices, and print-safe exports. - Horizontal wordmark: https://gencreator.ai/brand/gencreator-wordmark.svg Use: Partner docs, media kits, delivery rooms, product receipts, and community onboarding. - Icon primitive sheet: https://gencreator.ai/brand/gencreator-icon-sheet.svg Use: Inspectable vector sheet for the creation, activation, MCP, community, approval, and Studio primitives. - Social template sheet: https://gencreator.ai/brand/gencreator-social-template-sheet.svg Use: Inspectable vector layout reference for carousel, vertical video, OG, newsletter, and wide product-proof frames. - Brand social system: https://gencreator.ai/brand/social Use: Production route for logo rules, type decisions, social formats, carousel systems, motion frames, GTM plays, and assistant prompts. - Brand social API: https://gencreator.ai/api/brand/social Use: Assistant-readable JSON and markdown contract for social media, video, motion, and brand production. - React brand component: https://gencreator.ai/app/components/BrandMark.tsx Use: Live UI mark and lockup shared by navigation, hero badges, and product pages. - Brand foundation page: https://gencreator.ai/brand Use: Human-readable brand, product, software, community, and service-boundary system. - Brand foundation API: https://gencreator.ai/api/brand Use: Assistant-readable JSON contract for brand assets, tokens, icon primitives, product ladder, and MCP software layer. - Brand foundation markdown: https://gencreator.ai/api/brand?format=markdown Use: Portable strategy and brand contract for collaborators, agents, and future product packaging. ## Color Tokens - Ink: #05060A Role: Primary background and premium command surface. - Surface: #0A0C14 Role: Stable panels, app shells, and product proof sections. - Raised: #101522 Role: Interactive glass cards and docked tool areas. - Border: #1A1F2E Role: Subtle separation without decorative outlines. - Ink light: #F1F7FF Role: Primary text, mark contrast, and document exports. - Architecture blue: #275EFE Role: Systems thinking, structure, and MCP routes. - Trust blue: #6EA8FE Role: Navigation states, secondary highlights, and proof chips. - Signal cyan: #38BDF8 Role: Outlier radar, creation flow, and active intelligence. - Approval green: #34D399 Role: Human approval, community proof, and safe completion. - Ice highlight: #8BE9FD Role: Premium edges, specular glass, and hero highlights. ## Gradients - Generator flow: linear-gradient(135deg, #6EA8FE 0%, #38BDF8 52%, #34D399 100%) Use: Primary mark strokes, CTA glow, and product flow state. - Command glass: linear-gradient(180deg, rgba(241,247,255,0.09) 0%, rgba(241,247,255,0.026) 48%, rgba(56,189,248,0.045) 100%) Use: Premium liquid-glass cards, delivery rooms, and app controls. - Proof field: radial-gradient(circle at 12% 14%, rgba(39,94,254,0.28), transparent 32%), radial-gradient(circle at 84% 18%, rgba(56,189,248,0.18), transparent 34%), radial-gradient(circle at 50% 94%, rgba(52,211,153,0.16), transparent 36%) Use: Hero atmospheres that show system depth without becoming decorative haze. - Approval edge: linear-gradient(90deg, rgba(56,189,248,0.1) 0%, rgba(139,233,253,0.72) 52%, rgba(52,211,153,0.28) 100%) Use: Approval bars, timeline connectors, and checkout success states. ## Icon Primitives - Creation packet: One signal becomes a usable artifact with proof, draft, and route. - Activation path: The artifact becomes seven days of operating behavior. - Intelligence vault: Voice, audience, proof, offers, and policy become reusable memory. - MCP gateway: Tools, resources, prompts, and permissions make the OS portable. - Community proof loop: Finished artifacts enter review, ritual, example, and memory. - Human approval: Drafts stay drafts until a person approves the public action. - Gratitude layer: Sources, collaborators, customers, and teachers stay visible. - Studio judgment: Direct review enters after the self-serve system creates proof. ## Product Ladder - Activation Engine: https://gencreator.ai/activate Mode: free Buyer question: What should I do this week with one creator signal? Deliverable: Seven-day plan, product route, MCP plan, assistant prompt, and community handoff. Proof: Live route, JSON API, markdown export, and smoke coverage. - Learning Path Engine: https://gencreator.ai/learn Mode: free Buyer question: What should I learn, install, practice, buy, or escalate next? Deliverable: Learning modules, skill packs, MCP resources, product handoff, community bridge, and Studio boundary. Proof: Live route, JSON API, markdown export, product manifest entry, and MCP resource contract. - Self-Serve Kit Composer: https://gencreator.ai/products/kit Mode: self_serve Buyer question: Can this idea become an installable digital product? Deliverable: Modules, prompts, MCP resources, checkout handoff, and activation rhythm. Proof: Live composer, API, markdown export, and product manifest entry. - Paid digital products: https://gencreator.ai/products/delivery Mode: paid Buyer question: Which artifact solves my current bottleneck fastest? Deliverable: Vault Kit, Campaign Pack System, and Agent and MCP Pack with clear support boundaries. Proof: Starter artifacts, buy resolver, fulfillment preview, and checkout readiness map. - GenCreator.community: https://gencreator.ai/community/onboarding Mode: community Buyer question: Where does the work get practiced and sharpened? Deliverable: Weekly proof loop, source pulse, review request format, and member artifact library. Proof: Artifact-first onboarding, cohort structure, and community handoff from activation. - Studio: https://gencreator.ai/studio/apply Mode: studio Buyer question: When do I need direct judgment instead of more material? Deliverable: Private review, offer critique, campaign judgment, and agent workflow design. Proof: Application route, manual review scope, and capped service boundary. ## Software Layers - MCP Gateway: https://gencreator.ai/mcp Role: Agent interoperability Why it matters: GenCreator should be usable inside the assistants creators already trust, with tools, resources, prompts, and modes. Boundary: Read-only, draft-only, and approval-required modes; no external posting in v1. - Skill Pack Library: https://gencreator.ai/products/skill-packs Role: Portable workflows Why it matters: The product becomes useful when a creator can install a workflow into their own assistant and produce one artifact. Boundary: Skills teach behavior and draft artifacts; they do not claim private implementation support. - Learning Path Engine: https://gencreator.ai/learn Role: Self-serve education routing Why it matters: GenCreator becomes easier to buy when a creator can see the right module, skill pack, MCP resource, community bridge, and Studio boundary from one state. Boundary: The path recommends product and practice routes; it does not replace proof, member entitlement checks, or direct review. - Creator Vault: https://gencreator.ai/vault Role: Reusable creator memory Why it matters: Self-serve product becomes more valuable when voice, offer, proof, source credit, approval, MCP resources, and community review live in one operating state. Boundary: Browser-local and deterministic until authenticated member vault persistence and entitlement checks are wired. - Agent and MCP Pack: https://gencreator.ai/products/agent-pack Role: Governed assistant stack Why it matters: Roles, prompts, MCP config, and approval policy make the system more valuable than a static prompt file. Boundary: Agents draft, inspect, and prepare review records; humans approve public actions. - Eve Workbench: https://gencreator.ai/eve Role: Operating role Why it matters: Eve is the future operator, but starts as a deterministic brief generator until memory and entitlements are stable. Boundary: No autonomous publishing, charging, deleting, messaging, or external writes. - Creation Workspace: https://gencreator.ai/workspace Role: Continuity layer Why it matters: Creators need one place where signal, plan, assistant prompt, checkout handoff, and community review stay connected. Boundary: Browser-local today; member vault persistence belongs behind auth and entitlement checks. - Checkout and fulfillment contracts: https://gencreator.ai/products/checkout Role: Commercial reliability Why it matters: The sales system must state what is bought, what is delivered, what is blocked, and what support is not included. Boundary: Provider products and gated paid bundles remain explicit blockers until wired. ## Community System Community turns the product into a weekly practice: source pulse, build block, review thread, Friday proof, and digest. Proof rule: No passive entry: bring one artifact, one question, and one proof metric. - Source pulse: name the source material and the proof that would change the plan. - Build block: create one artifact from the vault, campaign, skill, agent, or approval layer. - Review thread: ask for one decision, not broad feedback. - Friday proof: share what changed, what shipped, and what remains constrained. - Digest: return the best example to the member artifact library. ## Service Boundaries - Scalable digital product: https://gencreator.ai/products Promise: The first business priority is a product that creates value without a call. Includes: Diagnostics, Activation plans, Kits, Skill packs, Agent pack contracts, Markdown and JSON exports Excludes: Unlimited custom implementation, Private review by default, External account access - Community practice: https://gencreator.ai/community/onboarding Promise: The community turns artifacts into rhythm, taste, accountability, and better examples. Includes: Weekly proof loop, Review prompts, Source pulse, Member examples, Upgrade path Excludes: Passive course access, Broad feedback without an artifact, Guaranteed private attention - Direct judgment: https://gencreator.ai/studio/apply Promise: 1:1 help stays premium and scarce, reserved for creators with proof and pressure. Includes: Offer review, Campaign critique, Agent workflow design, Manual judgment Excludes: Always-on consulting, Unbounded done-for-you delivery, Publishing without approval ## Voice Rules - Use sentence case and calm, precise product language. - Lead with the artifact, proof, and next action. - Say what the system will not do before trust is at risk. - Never imply autonomous publishing or unlimited private support. - Use gratitude, source credit, and human approval as product features. - Avoid generic course language, hype phrasing, and decorative design claims. ## Assistant Prompts ### Find the self-serve product Use: Use when deciding what GenCreator should build or sell next. ```text Turn this creator problem into a scalable GenCreator product. Name the buyer, first artifact, delivery format, support boundary, activation plan, MCP resource, community proof loop, and paid upgrade. ``` ### Check MCP product fit Use: Use before adding tools or agent features. ```text Audit this workflow for MCP fit. List which parts should be resources, tools, prompts, approval-required actions, and local-only instructions. State what must not be automated. ``` ### Shape the community handoff Use: Use when moving a creator from product output into community. ```text Turn this finished artifact into a GenCreator.community review request. Include the artifact, one decision question, proof metric, source credit, and next seven-day action. ``` ### Decide if 1:1 is earned Use: Use before routing a creator into Studio. ```text Decide whether this creator needs Studio or another self-serve loop. Check proof, revenue or audience pressure, campaign clarity, agent readiness, and what direct judgment would change. ``` ## References - Model Context Protocol specification: https://modelcontextprotocol.io/specification/2025-11-25 Use: MCP uses JSON-RPC and standard primitives for hosts, clients, servers, tools, resources, and prompts. - MCP security best practices: https://modelcontextprotocol.io/docs/tutorials/security/security_best_practices Use: GenCreator should keep authorization, approval, and tool modes explicit before adding external writes. - MCP Inspector: https://modelcontextprotocol.io/docs/tools/inspector Use: Future GenCreator MCP work should be testable through inspector-style tool, resource, and prompt checks.