MyJackfruit

Help
Browse topics · Finishing the project with Kai-Zen

Finishing the project with Kai-Zen

← Finishing the project with Kai-Zen

Can I make a second app from the same plan or code?

Short answer

Yes, as a new project in its own vault: ask Kai-Zen for it, and say which parts of your first app to use again.

Before you start

Words used here (2)
project
A project is work to bring about a change you want, such as a new app or a better way of doing something.
Kai-Zen
Kai-Zen is the planning agent: it finds out what you want, chooses the way, hands the work to other agents and reports back.
Deeper

Yes. A second app is a new project. One vault holds one project, and Kai-Zen, the planning agent, never offers to put a second project in a vault that holds one. A vault is a place on GilbPlatform where records are kept. So ask Kai-Zen in the chat for a new project: it asks where to keep it and offers a new vault first, and Jackfruit, the vault agent, makes it. The answer How do I start work with Kai-Zen? shows how to ask. GilbApp has no button that copies a project or an app, and no app templates.

From the same plan. Kai-Zen sets up the new project from your own words and asks its questions again, such as who owns the project and who approves the plan; to skip them, write use your defaults in your first message. Tell it what the second app is for, and which parts of the first plan you want again; you can paste them. Kai-Zen gives your words whole to the agents that write the plan. An agent is your AI following one written procedure, its standing instructions, for one kind of work. When Kai-Zen writes a way to build something, its rules have it look first in this project, then in GilbPlatform's store of code to reuse; those rules do not name your other projects. Only when you ask Kai-Zen to keep an idea for later does it write down any project it should reuse, and then it starts no work; the answer How do I keep an idea for later? shows how. A way to build something in one plan cannot be linked into another plan, as GilbApp's plan finds links only in the same vault. So the parts you want are written again in the new plan. If you need to reuse a plan directly, write to [email protected].

From the same code. Your first app's code is files in the folder on your computer where your AI builds it, with a copy on GitHub, a website where programmers keep code, once building has started. The answer Where does all the code go, and can I get a copy of it? tells more. Tell your AI which parts of the first app you want in the second. The standards describe no way to start a new app as a copy of another: taking parts over is building work in the new project, built, checked and tested like any other step. Every project that builds software carries the rule to reuse the app's own code and never make a second way for the same thing; it speaks of one app's own code. For a new app on GilbPlatform, the builder starts from GilbPlatform's own sign-in, from its store of shared code. Agent.Coder, the agent that writes your app's code, also looks in GilbPlatform's library of ready-made code before it writes any new piece. The standard that adds code to that library, the share process, speaks of app code we wrote; it does not say how your own app's code would get in. If you need that, write to [email protected]. Tell your AI to make the GitHub copy private, unless you want everyone to see your code.

Putting the second app live. A second app gets its own name and its own address, https://<name>.pages.dev, where <name> is the name given to your site. A new name is a new site, and uses one of your 2. Each person can have 2 sites in total, apps and websites together; for more, write to [email protected]. The answer How many sites can I have, and how do I get more? tells more.

The same app, made bigger. If you want your first app to do more, rather than a second app, that is version 2 of the same project, in the same vault, at the same address; see Can I pause my project, come back later and build version 2? To try an idea without changing the main app, see Can I try an idea on the side without changing the main app?

In Claude Code in Terminal, the window where you type commands, you can ask the same way. Start Claude Code, type this line with your own short name, the one you gave your AI when you connected your computer, and press Return:
/mcp__gilb-<short name>__agent
Then say you want a new project, what it is for, and which parts of your first app to use again, and press Return.

This answer is written for a computer screen.

Source: Kai-Zen standards: Kai-Zen.ProjectRules (Vault: a vault holds one project, never a second project in a vault that holds one, a new vault offered first and made by Jackfruit; Files); Kai-Zen.Route (New); Kai-Zen.New (Setup: the question round, owner and approver; Standard: the login from the code bank for a GilbPlatform app); Kai-Zen.AskRules.One (use your defaults); Kai-Zen.NoPlacing (the requester's words whole to the level agents); Kai-Zen.ConstraintRules.Reuse ("Reuse the app's existing code ... Never a second look or a second way for the same thing."); Kai-Zen.ValueDeliveryStepRules.First; Kai-Zen.Cycle; Agent.Coder (GilbStack item 7: look up the GilbPlatformCode Library before writing any new unit; AskGoLive: 2 sites per person, [email protected] for more); Proc_v_i_c_GitHubStandardShareApp (adds app code to the library; it speaks of code we wrote). Live help pages, sentences shared: How do I reuse a Solution or a Constraint? (looks in the project, then in the Solution library; a Solution in another project cannot be linked; write to [email protected]); Do I need a new vault for each app or project?; How do I start my project over?; Can I start from a template or an example project?; Where does all the code go, and can I get a copy of it?; How many sites can I have, and how do I get more?; How do I update my app after it is live? (a new name is a new site, and uses one of your 2); Can I try an idea on the side without changing the main app?; How do I start work with Kai-Zen?

Checked against GilbApp d529620.