Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Give Kilo Code concrete, repository-specific instructions in AGENTS.md, then add Laravel-aware guidance where it helps. This can make the expectations for an AI coding change clearer; it cannot guarantee clean code. Laravel Boost is a separate option for supplying Laravel- and version-specific context, not a requirement for Kilo’s AGENTS.md support.
Start with decisions your Laravel project has already made
Write down the conventions a contributor would otherwise have to discover or ask about. Useful guidance is specific enough to shape a change, but not so broad that it becomes a second copy of the codebase.
- Architecture: where business logic belongs, how controllers and services are used, and whether existing module boundaries should be preserved.
- Validation and authorization: which patterns the project uses, and where checks belong. Point to established examples rather than inventing new conventions.
- Naming and style: local choices that are not obvious from the framework defaults or automated formatting.
- Testing: which test types to add for a change, how tests are organized, and the relevant command to run if your project has a settled command.
- Known traps: package-specific constraints, compatibility requirements, or design decisions that are easy to miss and costly to undo.
Prefer instructions such as “follow the existing Form Request pattern for request validation; inspect a neighboring endpoint before adding another” over “write clean, maintainable code.” Kilo’s guidance recommends concrete, specific rules, examples, concise organization, and regular review: Kilo Code’s AGENTS.md documentation.
Put shared project rules in a root AGENTS.md
Kilo Code documents AGENTS.md as a project instruction file for coding standards and agent guidance. Its documentation identifies the project-root file as the recommended primary location and describes support for additional files in subdirectories. Kilo characterizes the format as a standardized way to configure agent behavior across coding tools.
#1 Best Overall
- HIGH QUALITY - CODE - EXPLORE - SETTLE at Planet Mars. The future is here and it's ready to play! CoderMarz is the only board game and STEM toy, that teaches about Mars facts, Coding and Artificial Intelligence concepts using a fun gameplay.
- EASY PLAY - Use it at home, in school, coding clubs, Montessori, STEM clubs, boys girls scout, summer clubs, tutoring, after school, day care, maker space, hackathons and for Girls who code!
- YOUNG INVENTOR - Created by Samaira, a 11 year old girl and covered by over 100 Media and News, including TIME, NBC TODAY Show, Business Insider, Yahoo Finance, NBC Bay Area, Sony, Mercury News and many more. Her first two games are now used in over 750 schools worldwide.
- FIRST EVER AI+MARS GAME - The only game that introduces kids to Mars Plains, Mountains, Rovers and Facts and AI Concepts. Teaches Coding, Facts about Mars, Training, Prediction, Adaptive Learning and Back Propagation. Also teaches Coding concepts like Loops, Functions, Conditionals and Algorithm writing and more. (PC: beautyinordinarythings)
- THINK MARS THINK AI - Artificial Intelligence is a big and emerging branch. The “Intelligence” in machines is programmed by “Training”. Training involves Back-propagation which is Retraining or Fine Tuning. Using astro and code card this game sneakily introduces AI concepts which form foundation of today’s AI world. Learn more now and amaze everyone with how much you know before everyone gets on the Mars bandwagon with all the new science exploration and talk that will be occurring shortly!
A useful root file might look like this:
# Project guidance
## Laravel conventions
- Follow established patterns in the code you are changing; inspect a nearby example first.
- Keep request validation and authorization consistent with the existing application.
- Add or update tests for behavior changes, using the project's existing test conventions.
## Change boundaries
- Avoid unrelated refactors.
- Preserve compatibility with the Laravel and package versions installed in this repository.
- If a requirement conflicts with existing patterns, explain the conflict before choosing a new pattern.Treat those bullets as examples to adapt, not a universal Laravel standard. Replace them with the decisions your team actually follows; otherwise the file can prompt the agent to apply patterns your application does not use.
Scope instructions without mixing formats
One root file is a good starting point, but a repository may contain areas with distinct requirements. Kilo documents per-directory AGENTS.md files, which let guidance live closer to the code it governs. Use them for genuinely local conventions—for example, a package or subsystem with its own test expectations—rather than repeating root rules in every folder.
Laravel Boost documents another, distinct mechanism: Markdown rule files under .ai/rules, optionally scoped to file paths, with an index to help agents discover applicable rules. These Boost rule files are not interchangeable with Kilo’s directory-level AGENTS.md files. Choose and maintain each format according to the tool and workflow that will consume it. See Laravel Boost documentation.
Rank #2
- CHALLENGING FUN : Inspire the next NASA engineer with this toy that teaches coding through 20 free online projects. Perfect for curious and smart kids aged 8 - 12
- EASY TO USE : 8 built-in LED lights, two buttons, and a speaker on Code Rocket mean you can start playing and coding immediately. No electronics experience required
- REAL LEARNING : 20 free online projects teach typed C++ coding just like what is used at NASA. The perfect next step from block-coding or Scratch-coding
- PERFECT GIFT : Provides hours of fun for kids and huge learning opportunities that might inspire their career. Highly awarded by parent review organizations
- Free software requires a Mac, Windows, or Chromebook computer or laptop and an internet connection. Not compatible with smartphones or tablets
Use Laravel Boost for Laravel-specific context when appropriate
Laravel describes Boost as a way to provide Laravel-specific, version-aware guidelines and agent-facing documentation tools. That context can complement repository instructions: project rules explain your application’s decisions, while framework- and ecosystem-oriented guidance can help an agent account for the Laravel versions and packages in use.
Laravel’s AI-assisted development documentation describes Boost’s role and setup: Laravel AI Assisted Development (12.x). Check the documentation for the Laravel version installed in your application, as well as the relevant package versions, before adopting a particular setup. The cited Laravel pages cover different documentation versions (12.x and 13.x); neither establishes that one configuration applies to every app.
Make Kilo’s instruction sources part of your mental model
AGENTS.md is not Kilo’s only possible source of instructions. Kilo’s documentation describes a precedence model involving agent prompts, project kilo.jsonc instructions, AGENTS.md, global instructions, and skills. Its custom-instructions documentation also covers recognized project files such as AGENTS.md, CLAUDE.md, and CONTEXT.md, along with global, per-directory, and configured instruction sources. Details can vary across clients and releases, so verify the behavior for the Kilo interface and version your team uses rather than assuming every instruction source has equal priority. See Kilo Code’s Custom Instructions documentation.
When guidance seems to be ignored or conflicts with a prompt, check which files and instruction sources are active and how Kilo prioritizes them. Avoid putting conflicting versions of the same rule in multiple places.
Ask the agent to inspect relevant guidance before editing
A prompt can direct the agent to identify and follow applicable project rules before it changes files. For example:
Before editing, inspect the applicable AGENTS.md files and any Laravel Boost rules relevant to the files in this change. Summarize the conventions that apply, then make the smallest change that follows them. Add or update tests for the behavior you change, and report which tests you ran and their results.This prompt is a request, not proof that the agent found every rule or produced correct code. Review the proposed diff yourself, check that the change fits the surrounding architecture, and run the project’s relevant tests. If the agent reports a test result, verify that the command actually ran and that the result covers the changed behavior.
Keep the guidance current and useful
Instructions lose value when they describe an old architecture, duplicate framework defaults, or contradict the code. Keep them focused on decisions that matter during changes; include short examples or links to in-repository examples where a rule needs explanation. Review a rule when the relevant code or team convention changes, and remove it when it no longer applies.
Official Kilo and Laravel documentation describes these instruction features and their intended uses; it does not establish a measured reduction in sloppy code or prove that this workflow improves results by a particular amount. The practical aim is narrower: make project expectations visible to the agent and easier for a developer to check.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
