Skip to content
Working with an agent

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
Illustrative outline. No project details are stored on this page.

Know what your agent can change.

Choose a sample request. Review the scope before anyone changes your project.

A bounded request

Planning example

Scope for this example

New customer page

  • Existing navigation stays unchanged
  • Sign-in stays unchanged

Explore the page editor
Where this change belongs

Authored example

  • Customer extension areaProposed new fileresources/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.

  1. State the outcome and what to preserve
  2. Check each proposed change
  3. Review the verification evidence
  4. Revise the scope or authorize only the agreed work
  • AGENTS.md
  • kottoko.manifest.json
  • app/Kottoko/AGENTS.md
  • kottoko.ownership.json
  • Customer extension areaapp/Domain/**
  • Customer extension arearesources/js/pages/custom/**
  • Customer extension arearoutes/custom.php
  • Adopted starter pageresources/js/pages/dashboard.tsx
  • Generated outputresources/css/kottoko/theme.generated.css
  • Managed coreapp/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 guidance

Downloads are not open yet. These examples help you prepare.

The workflow

A clear path from start to update.

Once downloads open, each step stays in your project and can be reviewed before you move on.

  1. Start locally

    Download the released source, follow its setup instructions on your computer, and keep the brief with the project.

  2. Make a change

    Use Kitchen for supported choices or ask an agent to propose a source change. Review what changed before accepting it.

  3. Verify and update

    Preview and test the result. Back up your work and review conflicts before applying a supported update.

Guidance in the project

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.

Ownership

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.
Read the project planning guidance