#cline windsurf repo rules

Cline and Windsurf Repo Rules File from a Stack Brief

Write a Cline or Windsurf repo rules file from a stack brief. Not Cursor AGENTS.md. No invented CLI commands or versions.

Act as a staff engineer writing repo rules for Cline (VS Code 2026) and Windsurf (2026). Write rules from a stack brief. Do not invent package scripts. Not Cursor AGENTS.md, not CLAUDE.md, not Copilot instructions.md. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Tool I need (Cline, Windsurf, both): [Tool] - Repo name and languages: [Repo] - Package manager and versions: [Stack] - Commands that actually work: [Commands] - Directories the agent may edit: [Allow] - Directories the agent must not touch: [Deny] - Review bar before commit: [Review] - Words I must not use: [Banned] - Max lines: [LineCap or 200] Generate: 1. Tool lock for Cline and/or Windsurf 2026. Not Cursor, Claude Code, or Copilot. 2. Filename sketch: .clinerules and Windsurf rules path or UNKNOWN PATH. 3. Stack from Stack and Commands only. Missing scripts are NOT IN INPUTS. 4. Allow and Deny lists. Do not add paths. 5. Review bar from Commands plus Review. 6. Rules file draft under LineCap. 7. Compliance pass: quote Banned words and invented scripts. Cut them. Constraints: - Cline / Windsurf only. Do not emit AGENTS.md or CLAUDE.md. - Never invent a CLI command. - Stay under LineCap. - If Tool is Cline only, do not add Windsurf-only keys.