amazonq: add initial set of agent rules

cbgbt · cbgbt · commit fe4928f0d7a6 · 2025-07-30T00:51:08.000Z
diff --git a/.amazonq/rules/01-implementing-features.md b/.amazonq/rules/01-implementing-features.md
@@ -0,0 +1,19 @@
+## Implementing Features
+
+- Whenever you implement a feature or create a code change you MUST follow this process
+
+## Implementation Process
+
+1. You MUST implement the code required changes without waiting for human input.
+2. You MUST run the build to ensure tests pass.
+3. You MUST debug and fix any failures.
+4. You MUST thoroughly and pedantically follow any provided style guides, paying special attention to MUST, SHOULD, and MAY statements.
+5. When the code is finished, you MUST ensure that the following checks have been completed:
+   - You MUST perform a build, based on the programming language (e.g. cargo build)
+   - You MUST run tests based on language (e.g. cargo test or pytest)
+   - You MUST check lints using the programming language preferences (e.g. cargo clippy, mypy + ruff)
+   - You MUST format the changes (e.g. cargo fmt or black)
+6. You MUST print a status update summarizing the work done (you MUST NOT show any code, just do a verbal summary)
+7. You MUST perform a code-review using the style guide as a reference, paying special attention to SHOULD, MUST, and MAY statements. You MUST print a summary of the review (for code samples, you MUST NOT print large sections of code. You MAY only show handfuls of lines when it makes sense)
+8. You MUST implement the changes suggested by the code review by going back to step 1.
+9. You MUST iterate on the code until all elements of point 5. are complete.
diff --git a/.amazonq/rules/02-using-git.md b/.amazonq/rules/02-using-git.md
@@ -0,0 +1,10 @@
+## Using Git
+
+- You MUST never use `git push` or any command that would send code off the host.
+- You MUST never perform deletions.
+- You MUST never commit any `.gitignore`d content to git.
+- You MUST create local commits with `git add` and `git commit`.
+- If anything goes wrong with Git, you MUST NOT delete data or attempt destructive operations.
+- You MUST NOT rebase changes or modify Git history in any way.
+- You MUST NOT use `git filter-branch`, `git reset --hard`, or similar commands.
+- If you encounter Git issues, you MUST immediately report them and exit gracefully.
diff --git a/.amazonq/rules/03-bottlerocket-git-format.md b/.amazonq/rules/03-bottlerocket-git-format.md
@@ -0,0 +1,24 @@
+## Bottlerocket Git Commit Convention
+
+* Commits MUST NOT follow the conventional commit format
+* Commits MUST follow this format:
+```
+<component>: <description>
+
+<body>
+```
+
+Where:
+* <component> MUST be the subsystem you modified (e.g., "prompt-plan", "implement", "code-review")
+* <description> MUST use present imperative tense (e.g., "add", "fix", "update", not "adds", "fixed", "updated")
+* <description> MUST be lowercase and MUST NOT end with a period
+* The commit message SHOULD complete the sentence: "If applied, this commit will ________"
+* If needed, you MAY add a body separated by a blank line, with lines no longer than 72 characters
+
+Example:
+```
+prompt-plan: implement structured format parser
+
+This change adds a parser for the structured prompt plan format that
+extracts prompt information and status.
+`
