Skip to content
GenCreatorFree planning kit

Turn one artifact into a working packet.

Export prompts, module checklists, and a review plan for free. CreatorPack is not for sale yet. Community membership and Studio are parked; this kit does not unlock them.

Self-Serve Kit Composer

Agent-first GenCreator kit for Founder-led AI creation system

Turn one artifact into memory notes, campaign prompts, assistant setup instructions, an approval record, and a review plan.

Kit

kit_1b857382

First module

Agent install task

Artifact

Product focus

Delivery style

Export

Buyer outcome

Install one assistant role, read one MCP resource, and create eve_e2181b65 before any public output.

Best for creators who already work with Claude, Codex, Cursor, or another assistant and want safer operating instructions.

Modules

6

First use

12 min

Format

json + markdown

Generated modules

Current availability

Free planning kit

Export prompts, module checklists, and a review plan for free. CreatorPack is not for sale yet. Community membership and Studio are parked; this kit does not unlock them.

Agent and MCP Pack: Not for sale yet. Pricing is published only when checkout is live; join the founding list to hear first.

Activation rhythm

Day 1Name the artifact and proof metricFounder-led AI creation system plus how many assistant actions create review records before external work
Day 2Create the memory rowVoice, offer, audience, proof, and approval policy fields.
Day 3Install one assistant role and run a dry approval taskInstall one assistant role, read one MCP resource, and create eve_e2181b65 before any public output.
Day 4Run approvaleve_e2181b65

Assistant prompt

You are helping a creator use a GenCreator Self-Serve Kit.

Current availability: Export prompts, module checklists, and a review plan for free. CreatorPack is not for sale yet. Community membership and Studio are parked; this kit does not unlock them.
Verify availability at https://gencreator.ai/pricing. Legacy module names are not purchasable offers.

Kit focus: agent_first
Delivery style: assistant_guided
Artifact: Founder-led AI creation system
Summary: Turn one idea into a reusable vault, campaign packet, assistant role, approval task, and community review request.
Proof metric: how many assistant actions create review records before external work
First approval task: eve_e2181b65

Work through these modules in order:
1. Agent install task: Install one assistant role and one MCP read path before expanding the workflow.
2. Approval record: Convert the riskiest next action into a human decision record.
3. Creator vault row: Create the first memory row before any assistant writes.
4. Campaign packet: Turn the artifact into one approval-safe campaign packet.
5. Community review request: Bring one artifact and one decision into the proof loop.
6. Seven-day activation plan: Give the buyer a seven-day rhythm after the first artifact exists.

Rules:
- Ask for missing proof before drafting.
- Use read_only for inspection, draft_only for local drafts, and approval_required for public, paid, customer-facing, destructive, or reputation-sensitive actions.
- Do not claim paid access, checkout, entitlement, or community posting is available based on a module name or legacy provider configuration. Check current public availability first.
- Return the smallest useful artifact, one risk note, and the next product or community handoff.

Operating decision

Start with a working packet

Name one artifact, choose the first module, and export instructions you can use yourself or with an assistant.

Operating decision

Assistant-ready by default

Every artifact has prompts, MCP resources, approval rules, and support boundaries that an assistant can read.

Operating decision

Prepare a useful review

Bring an artifact, a proof metric, and one precise question to a reviewer you choose. Community membership is parked.

MCP and software layer

The kit is also an agent-readable resource contract.

The right software posture is simple: expose resources for context, prompts for repeatable work, tools for controlled actions, and keep external writes approval-required until entitlement and audit paths are wired.

1Generate kitName the artifact, choose the focus, and export the working packet.
2Choose a moduleStart with memory, campaign prompts, assistant setup, or a review request.
3Review one artifactUse the seven-day plan to make, check, and revise your work. No membership is required to prepare the packet.
4Package what workedTurn the finished artifact into examples, updates, and a sharper public offer.