This repository was archived by the owner on Jan 23, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Refactor templates from legacy Cursor rules to agents.md format #51
Merged
jhaynie
merged 2 commits into
main
from
devin/1755667839-refactor-cursor-rules-to-agents-md
Aug 21, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| # Agentuity Configuration Guidelines | ||
|
|
||
| This guide provides instructions for working with Agentuity configuration files and project setup. | ||
|
|
||
| ## 1. Agentuity Configuration File | ||
|
|
||
| The `agentuity.yaml` file is used by Agentuity to configure the AI Agent project. You should NOT suggest edits to this file unless specifically requested, as it contains critical project configuration managed by the Agentuity platform. | ||
|
|
||
| ## 2. Project Structure | ||
|
|
||
| Follow the established project structure for your chosen runtime: | ||
|
|
||
| - **Python projects**: Use the `agentuity_agents/` directory for agent implementations | ||
| - **JavaScript/TypeScript projects**: Use the `src/agents/` directory for agent implementations | ||
| - **Configuration files**: Keep `agentuity.yaml`, `.env` files, and other configuration in the project root | ||
|
|
||
| ## 3. Development Workflow | ||
|
|
||
| - Use `agentuity dev` to start the development server | ||
| - Use `agentuity agent create` to scaffold new agents | ||
| - Use `agentuity deploy` to deploy your agents to production | ||
| - Follow the runtime-specific guidelines in your project's AGENTS.md file | ||
|
|
||
| ## 4. Environment Management | ||
|
|
||
| - Use `.env.development` for development-specific environment variables | ||
| - Use `.env.production` for production environment variables | ||
| - Never commit sensitive credentials to version control | ||
| - Use the Agentuity Console for managing secrets in production |
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
LGTM: AGENTS.md creation is correctly added at project root using the JS-specific source.
Placement after README.md and before editorconfig is good. The key names match existing create_file usage (“from”), and the path aligns with common/js assets used elsewhere in this template.
Run this script to verify end-to-end consistency across templates and ensure no legacy Cursor artifacts remain:
🏁 Script executed:
Length of output: 2501
Missing AGENTS.md in bunjs & python-uv templates
All AGENTS.md sources (
common/js/AGENTS.md,common/py/AGENTS.md,common/AGENTS.md) exist and no legacy.cursor/.mdcartifacts remain, but thecreate_fileblock is only innodejs/rules.yaml. The other two language templates need the same addition:• bunjs/rules.yaml
• python-uv/rules.yaml
Please add, immediately after the README.md step (and before the editorconfig step), in each file:
For example, in
bunjs/rules.yaml:And in
python-uv/rules.yamlswap infrom: "common/py/AGENTS.md".🤖 Prompt for AI Agents