AI SummaryA system prompt for autonomous coding workflows that integrates GitHub and project management MCPs, enforcing structured task completion with explicit exit criteria and secret management practices. Developers building lightweight autonomous coding engines in Claude, Cursor, Windsurf, or ChatGPT environments benefit from pre-defined operational rules and completion protocols.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "appforge-poc — System Prompt" prompt rules to my project. Repository: https://github.com/Day-in-the-Country-LLC/appforge-poc Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
poc for lightweight autonomous coding engine
GitHub MCP + Issue Protocol
Use GitHub MCP for all GitHub Issue operations (comments, labels, metadata, PRs). Use Appforge MCP for all Github Project operations (project status updates, issue assignments). Do not use shell commands to edit issues or PRs. If you are blocked and require action from the developer: • You MUST follow the blocked-task-handling skill and stop. No alternatives. Ensure all instructions are completed. If you complete all work for an issue: • You MUST follow the code-complete-issue-pr-handling skill and stop. No alternatives. Ensure all instructions are completed. Always ensure that creating ACE_TASK_DONE.json is the final step of the workflow before you exit. Write it in the current task workspace (the same repo/worktree that contains ACE_TASK.md). Never exit without completing the appropriate skill (blocked or code-complete) and writing ACE_TASK_DONE.json. Always follow ACE_TASK.md exactly and in order.
Secret Management
All secrets are tracked in Terraform in /path/to/your/terraform-repo. All secrets are pulled from GCP Secret Manager. Secrets never come from environment variables. If your work requires access to a secret, first check whether it exists in the Terraform repo. If it does not exist, add it in the Terraform repo and then pull it from GCP Secret Manager. When adding a secret to Terraform, use the ditc-terraform-secret-add skill (which includes creating a GitHub issue for repo-owner to add the secret value in GCP Secret Manager).
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts