Build with an AI agent
Give your coding agent a task and the documentation index for your application’s version. Use this page to pick the right index and copy a starting prompt.
#Choose the documentation version
Pick a version with Documentation version on this page. The links and prompts below change to match it.
| Version | Content |
|---|---|
dev | Follows ongoing development |
| Released versions | Frozen; match that release exactly |
- Application documentation index links to focused Markdown guides.
- Complete application documentation bundles every guide, for when the agent needs broader context.
Tip
The root /llms.txt currently points to dev. Put the version-specific URL in
saved project instructions.
#Start an application
Use https://cicadel.fauzaanu.com/en/0.2.7/llms.txt as your Cicadel documentation index.
Create a new application in ./myapp with module example.com/myapp.
The application should: [describe the users, screens, data and permissions].
Read the relevant guides before choosing APIs. Show concrete Go and .templ code.
Configure PostgreSQL for the standard accounts and recorded-migration workflow.
Register apps explicitly, rebuild generated UI, and run checks and tests.
Verify the resulting HTTP behavior and report the local URL and any remaining setup.#Add a feature to an existing application
Read https://cicadel.fauzaanu.com/en/0.2.7/llms.txt.
First inspect this project's go.mod, registered apps, routes and existing UI.
Add [feature] using the project's conventions and matching Cicadel version.
Implement its handlers, components, validation and permissions.
If the schema changes, generate and review a recorded PostgreSQL migration.
Run the affected tests and the project's normal checks. Summarize the result.#Fix a bug
Use https://cicadel.fauzaanu.com/en/0.2.7/llms.txt and the relevant API guide.
Reproduce this problem: [steps, expected result, actual result].
Find the failing request or data flow, add a regression test, and fix it.
Preserve existing authorization, CSRF checks and migration history.
Run the test against the real affected behavior and report what passed.#Give the agent useful context
Tell the agent:
- the application module path;
- the screen or route to change;
- the expected behavior;
- who may access the data.
Warning
Supply secrets through your agent’s secure mechanism. Never paste them into a prompt.
For specialized work, point the agent at a skill. Skills are optional instructions for building applications and reusable packages.
#Framework design is separate
Application work does not need the framework roadmap or implementation history. Those documents have a separate framework index. Read the philosophy only for the reasoning behind Cicadel’s design.