1
free
Activation Engine
What should I do this week with one creator signal?
Seven-day plan, product route, MCP plan, assistant prompt, and community handoff.
Brand and product foundation
GenCreator should be a self-serve creator intelligence OS.
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.
Brand specimen
Vector-first, product-ready
GenCreator
Creator intelligence OS
Create
Signal to packet
Activate
Packet to week
Practice
Proof to community
01
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?
02
Make MCP the software spine
MCP gives GenCreator a portable language for tools, resources, prompts, and approvals across assistants and workbenches.
03
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.
04
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
The identity starts with real vector primitives.
The mark is a generator loop with a center rail and approval arrow. It has to hold at favicon size, app icon size, product-card size, and partner-doc size.
16px proof
32px proof
64px proof
128px proof
svg
Primary vector mark
Navigation, app surfaces, product cards, export covers, and small-size proof.
Open assetsvg
One-color vector mark
High-contrast surfaces, favicons, partner decks, invoices, and print-safe exports.
Open assetsvg
Horizontal wordmark
Partner docs, media kits, delivery rooms, product receipts, and community onboarding.
Open assetsvg
Icon primitive sheet
Inspectable vector sheet for the creation, activation, MCP, community, approval, and Studio primitives.
Open assetsvg
Social template sheet
Inspectable vector layout reference for carousel, vertical video, OG, newsletter, and wide product-proof frames.
Open assetroute
Brand social system
Production route for logo rules, type decisions, social formats, carousel systems, motion frames, GTM plays, and assistant prompts.
Open assetapi
Brand social API
Assistant-readable JSON and markdown contract for social media, video, motion, and brand production.
Open assetcomponent
React brand component
Live UI mark and lockup shared by navigation, hero badges, and product pages.
Open assetroute
Brand foundation page
Human-readable brand, product, software, community, and service-boundary system.
Open assetapi
Brand foundation API
Assistant-readable JSON contract for brand assets, tokens, icon primitives, product ladder, and MCP software layer.
Open assetmarkdown
Brand foundation markdown
Portable strategy and brand contract for collaborators, agents, and future product packaging.
Open assetIcon language
Symbols should explain the operating model.
These primitives are simple line icons derived from the same logic as the mark: input, rail, loop, route, and approval. They work in UI, docs, delivery rooms, and community rituals.
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.
Color and material
Premium, cool, precise, and built for product work.
Blue is architecture, cyan is signal, green is approval. The palette avoids warm courseware and generic purple SaaS haze.
Ink
#05060A
Primary background and premium command surface.
Surface
#0A0C14
Stable panels, app shells, and product proof sections.
Raised
#101522
Interactive glass cards and docked tool areas.
Border
#1A1F2E
Subtle separation without decorative outlines.
Ink light
#F1F7FF
Primary text, mark contrast, and document exports.
Architecture blue
#275EFE
Systems thinking, structure, and MCP routes.
Trust blue
#6EA8FE
Navigation states, secondary highlights, and proof chips.
Signal cyan
#38BDF8
Outlier radar, creation flow, and active intelligence.
Approval green
#34D399
Human approval, community proof, and safe completion.
Ice highlight
#8BE9FD
Premium edges, specular glass, and hero highlights.
Generator flow
Primary mark strokes, CTA glow, and product flow state.
Command glass
Premium liquid-glass cards, delivery rooms, and app controls.
Proof field
Hero atmospheres that show system depth without becoming decorative haze.
Approval edge
Approval bars, timeline connectors, and checkout success states.
Business architecture
The scalable product ladder comes before the personal help.
The business works when every buyer knows the next artifact, the delivery format, the support boundary, and the route into community or Studio.
Open
2
free
Learning Path Engine
What should I learn, install, practice, buy, or escalate next?
Learning modules, skill packs, MCP resources, product handoff, community bridge, and Studio boundary.
3
self serve
Self-Serve Kit Composer
Can this idea become an installable digital product?
Modules, prompts, MCP resources, checkout handoff, and activation rhythm.
4
paid
Paid digital products
Which artifact solves my current bottleneck fastest?
Vault Kit, Campaign Pack System, and Agent and MCP Pack with clear support boundaries.
5
community
GenCreator.community
Where does the work get practiced and sharpened?
Weekly proof loop, source pulse, review request format, and member artifact library.
6
studio
Studio
When do I need direct judgment instead of more material?
Private review, offer critique, campaign judgment, and agent workflow design.
Software spine
MCP, skills, agents, and Eve make GenCreator more than content packaging.
The strongest version is a general-intelligence workbench for creator businesses: portable workflows, governed tools, memory, approvals, and a community practice loop.
MCP Gateway
GenCreator should be usable inside the assistants creators already trust, with tools, resources, prompts, and modes.
Read-only, draft-only, and approval-required modes; no external posting in v1.
Inspect layerSkill Pack Library
The product becomes useful when a creator can install a workflow into their own assistant and produce one artifact.
Skills teach behavior and draft artifacts; they do not claim private implementation support.
Inspect layerLearning Path Engine
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.
The path recommends product and practice routes; it does not replace proof, member entitlement checks, or direct review.
Inspect layerCreator Vault
Self-serve product becomes more valuable when voice, offer, proof, source credit, approval, MCP resources, and community review live in one operating state.
Browser-local and deterministic until authenticated member vault persistence and entitlement checks are wired.
Inspect layerAgent and MCP Pack
Roles, prompts, MCP config, and approval policy make the system more valuable than a static prompt file.
Agents draft, inspect, and prepare review records; humans approve public actions.
Inspect layerEve Workbench
Eve is the future operator, but starts as a deterministic brief generator until memory and entitlements are stable.
No autonomous publishing, charging, deleting, messaging, or external writes.
Inspect layerCreation Workspace
Creators need one place where signal, plan, assistant prompt, checkout handoff, and community review stay connected.
Browser-local today; member vault persistence belongs behind auth and entitlement checks.
Inspect layerCheckout and fulfillment contracts
The sales system must state what is bought, what is delivered, what is blocked, and what support is not included.
Provider products and gated paid bundles remain explicit blockers until wired.
Inspect layerGenCreator.community
The community is the transformation layer.
Community turns the product into a weekly practice: source pulse, build block, review thread, Friday proof, and digest. The point is not passive access. The point is a repeated culture of building with taste, evidence, gratitude, and approval.
No passive entry: bring one artifact, one question, and one proof metric.
01
Source pulse: name the source material and the proof that would change the plan.
02
Build block: create one artifact from the vault, campaign, skill, agent, or approval layer.
03
Review thread: ask for one decision, not broad feedback.
04
Friday proof: share what changed, what shipped, and what remains constrained.
05
Digest: return the best example to the member artifact library.
Service boundaries
1:1 belongs where it creates judgment, not where product should do the work.
Scalable digital product
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
Does not include
- Unlimited custom implementation
- Private review by default
- External account access
Community practice
The community turns artifacts into rhythm, taste, accountability, and better examples.
Includes
- Weekly proof loop
- Review prompts
- Source pulse
- Member examples
- Upgrade path
Does not include
- Passive course access
- Broad feedback without an artifact
- Guaranteed private attention
Direct judgment
1:1 help stays premium and scarce, reserved for creators with proof and pressure.
Includes
- Offer review
- Campaign critique
- Agent workflow design
- Manual judgment
Does not include
- Always-on consulting
- Unbounded done-for-you delivery
- Publishing without approval
Assistant prompts
The strategy should be usable inside the assistant.
These prompts turn the brand into product decisions, MCP design, community handoff, and Studio gating.
Open JSON contractFind the self-serve product
Use when deciding what GenCreator should build or sell next.
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 before adding tools or agent features.
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 when moving a creator from product output into community.
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 before routing a creator into Studio.
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.