English
Your project, in your hands.
Kottoko is designed as a downloadable foundation. Keep a clear project brief with the source while you customize the result and check each change.
Downloads are not open yet. The linked guidance helps you prepare your project now.
A brief for your project
A shared reference for you and anyone helping you build.
- Purpose
- What you are building
- Audience
- Who it is for
- Main action
- What people should do
- Constraints
- What to preserve or avoid
Know what your agent can change.
Choose a sample request. Review the scope before anyone changes your project.
A bounded request
Planning example
New customer page
- Existing navigation stays unchanged
- Sign-in stays unchanged
Where this change belongs
Authored example
- Customer extension areaProposed new file
resources/js/pages/custom/service.tsxProposed new file; it has not been created
Review the proposal
Authored example
Within the requested scope
One new customer page; existing navigation and sign-in stay unchanged.
- Proposed new fileCustomer extension area
What to check
Does it stay within the requested scope?
Ask for the affected files and the reason each change is needed. Return unrelated or unexplained changes for revision.
How will the result be tested?
Review the page at narrow and desktop sizes and with a keyboard. Ask which checks ran and what remains unverified.
Ask for relevant checks and a preview of the user journey. A proposed test is not a passing result; ask which checks ran and what remains unverified.
Publication requires separate approval.
No agent runs here. No files change.
Understand the source boundary
- Your own pages and logic
- Use the declared extension areas.
- Starter pages
- Your adopted changes are preserved for review.
- Generated theme output
- Change the supported inputs, then regenerate.
- Kottoko core
- Use a supported extension or review an explicit fork.
Source files and project guidance
Project instructions point to the installed manifest and source ownership. Use the relevant public contracts and checks for the chosen task.
Review an agent proposal
Start with one requested outcome, list the affected files, and check the proposal against the source boundary before implementation.
- State the outcome and what to preserve
- Check each proposed change
- Review the verification evidence
- Revise the scope or authorize only the agreed work
AGENTS.mdkottoko.manifest.jsonapp/Kottoko/AGENTS.mdkottoko.ownership.json
- Customer extension area
app/Domain/** - Customer extension area
resources/js/pages/custom/** - Customer extension area
routes/custom.php - Adopted starter page
resources/js/pages/dashboard.tsx - Generated output
resources/css/kottoko/theme.generated.css - Managed core
app/Actions/Fortify/CreateNewUser.php
Generated output is derived from supported inputs.
An explicit managed-source fork reduces automatic update safety. Review the consequences before a separately authorized operation.
Project guidance does not grant remote access, provider credentials or permission to publish.
Public guides contain selected customer information. Internal work orders, private research and credentials stay outside them.
Read the setup guidanceDownloads are not open yet. These examples help you prepare.
A clear path from start to update.
Once downloads open, each step stays in your project and can be reviewed before you move on.
Start locally
Download the released source, follow its setup instructions on your computer, and keep the brief with the project.
Make a change
Use Kitchen for supported choices or ask an agent to propose a source change. Review what changed before accepting it.
Verify and update
Preview and test the result. Back up your work and review conflicts before applying a supported update.
A useful starting point for an agent.
Your brief explains the goal. Project files describe supported ways to change the foundation and how to check the result.
Readable project guidance
An agent can read the project brief, configuration, extension points, and verification instructions. You decide the task and review its proposed work.
Safe customization
Use Kitchen for supported content and design choices. Keep source changes within documented ownership boundaries and test them before a release.
A foundation you can adapt.
Kottoko provides the starting source. Your project and its production content remain under your control, subject to the download and license terms.
- Adapt the licensed source for your project within its terms.
- Production content and submissions stay with your project and chosen providers; they are not synced to your Kottoko account.
- Back up, review, and verify updates rather than silently replacing your changes.
Build a website or app.With the core features included.
Kottoko is a starter project for websites and apps. It includes pages, user accounts, forms, and online store features you can customize instead of building from scratch.
The features you need, already built in.
See your changes as you make them.
Edit content, tune the design and choose features against the same website your visitors see.
Make Kottoko your own.
Change the heading and accent in this miniature page. It uses the same heading, field, and color controls as the website.
Make Kottoko your own.
Change the heading and accent in this miniature page. It uses the same heading, field, and color controls as the website.
What you can build
Explore starting points for websites, shops and member experiences.
Websites
Publish your ideas, work and resources.
Commerce
Sell products, downloads and subscriptions.
Members & apps
Create spaces for members and customers.
Growth
Connect with your audience and understand what works.
Design
Shape the look and feel of your project.
Operations
Keep your project connected and running.
Questions before you start.
Is Kottoko for websites or apps?
Both. Start with public pages, then use accounts, dashboards, forms, commerce, and other included features as your idea needs them.
Do I need to write code?
The editor lets you try supported content, design, and feature choices visually. Building custom behavior, connecting services, and deploying the project can require a developer or coding agent.
Are payments and email ready to use?
The payment integrations currently support test mode. These browser examples do not charge money or send transactional email. Live payment support still needs implementation and review; email delivery needs its own provider setup.
How do updates work?
Review how a change affects your project, prepare a backup, and check the result before release. Your hosting and setup determine the recovery steps.
Can I download Kottoko now?
Public downloads are not open yet. Explore the examples and documentation, or join the list below for launch updates.
Build your next project with a head start.
Get launch news, new examples, and product updates.
Confirm by email. Leave anytime. Read our privacy notice.