AI Prompt for Rules & Instructions Files
Port an existing Cody (Sourcegraph) rules file into the Augment format, preserving intent and adapting to Augment's capabilities.
You are an expert developer experience engineer with deep expertise in tooling migration. Port a project's AI-assistant rules from **Cody (Sourcegraph)** to **Augment** for a Expo + EAS app. **Source tool:** Cody (Sourcegraph) **Target tool:** Augment **Repo:** Expo + EAS app **Team:** 100+ engineer enterprise **Key convention to preserve:** never use default exports -- named only ## Context Each AI coding tool reads rules from a different file with different capabilities: - `.cursorrules` -> single flat markdown, no frontmatter, always applied - `.cursor/rules/*.mdc` -> scoped by globs, YAML frontmatter with `description`, `globs`, `alwaysApply` - `.github/copilot-instructions.md` -> single markdown, Copilot prepends it to every chat - `CLAUDE.md` -> Claude Code project memory, supports imports via `@path/to/file.md`, lives at repo root (project) or `~/.claude/CLAUDE.md` (user) - `.windsurfrules` -> markdown, per-project - `CONVENTIONS.md` -> Aider reads via `--read` - `.continue/config.yaml` -> `systemMessage` string field, YAML-escaped ## Your task ### Step 1: Parse the source Ask the user to paste the existing Cody (Sourcegraph) file. Extract: - Project overview section - Hard rules (imperatives) - Soft preferences - Test / CI conventions - Forbidden patterns - Any tool-specific directives that do NOT translate (flag these explicitly) ### Step 2: Produce the target file Write the equivalent Augment file with: - Correct filename and path as a header comment - Correct frontmatter / schema for Augment - Reorganized sections to match Augment idioms - A "Preserved from Cody (Sourcegraph)" section at the bottom listing every rule kept verbatim ### Step 3: Capability delta report Produce a short table: | Capability | Cody (Sourcegraph) | Augment | Action taken | |---|---|---|---| | Scoped rules by path | ... | ... | ... | | File imports | ... | ... | ... | | Always-apply toggle | ... | ... | ... | | Per-language overrides | ... | ... | ... | ### Step 4: Gaps & manual steps List anything that cannot be migrated automatically and needs a human decision. ## Output format 1. The full target file, fenced 2. The capability delta table 3. Gaps list Do not drop any rule without explicitly calling it out. Preserve never use default exports -- named only as a hard rule in the output. Structure as a professional report with: Executive Summary, Key Findings, Detailed Analysis, Recommendations, and Next Steps.
More prompts for Rules & Instructions Files.
Port an existing Continue.dev rules file into the Windsurf format, preserving intent and adapting to Windsurf's capabilities.
Port an existing Codeium rules file into the Windsurf format, preserving intent and adapting to Windsurf's capabilities.
Ready-to-paste Windsurf rules/instructions file tuned for Spring Boot service codebases owned by solo founder. Enforces SQL migrations must be reversible.
Generate a narrow, path-scoped rule file that fires only on Swift files in a Go microservice.
Ready-to-paste Zed Assistant rules/instructions file tuned for VS Code extension codebases owned by 100+ engineer enterprise. Enforces never use default exports -- named only.
Ready-to-paste Windsurf rules/instructions file tuned for Kubernetes operator codebases owned by YC-batch pre-seed team. Enforces use composition over inheritance.