Filesystem MCP Server

# Agent Configuration ## CORE_DIRECTIVES ### Language and Communication - Code/API/Technical Terms: English only - Tone: Professional, direct, solution-focused - Style: Concise, technically clear explanations - Error Handling: Always provide clear errors with actionable solutions ## STRICT_PROHIBITIONS ### NO_EMOJI EMOJI STRICTLY PROHIBITED in: - Code (variables, functions, classes, interfaces, types) - Comments - Commit messages - Documentation (README, CHANGELOG, API docs) - Log messages (console.log, logger) EXCEPTION: User-facing UI text only ### NO_MOCK_DATA - Never use mock/fake data - Tests: Use real scenarios, integration tests - Database: Real test instances, not mocks ### STRICT_TYPE_SAFETY **100% Type Safety REQUIRED across ALL languages.** - **Prohibited Loose Types**: - **TS/JS**: `any`, `unknown` (use Zod/Valibot). - **Java/C#**: `Object`, raw types. - **Go**: `interface{}`, `any`. - **C/C++**: `void*` (use smart pointers/templates). - **Swift**: `Any`, `AnyObject`. - **Rust**: `unsafe` (unless strictly justified). - **Validation**: Validate ALL external data (API, DB, Input) at runtime. - **Strictness**: No implicit types. Explicit return types required. ### LOGGING_POLICY - `console.log`, `console.warn`, `console.error` are STRICTLY FORBIDDEN. - All logging must use **Winston** (or the project's logger utility) only. - Production code may only use: `logger.info`, `logger.warn`, `logger.error`. - `logger.debug` is allowed only locally and must NOT be committed. - Emojis are forbidden in all logs. ### NO_LOCAL_DEV_SERVER - Never run: bun run dev, yarn dev, npm start - Agent scope: Write code, analyze, prepare deployment - Build/Start: GitHub Actions or production pipeline only ### NO_UNAUTHORIZED_GIT_OPERATIONS - Never commit or push without explicit user permission ## GIT_WORKFLOW ### Strategy (GitHub Flow) - Branches: `feature/xyz`, `fix/xyz`, `refactor/xyz`. - Flow: Main → Feature → PR (AI Review) → Main. ### Standard Process 1. `git checkout -b feature/xyz` 2. Develop & Commit: `git commit -m "feat: ..."` (Turkish required) 3. `gh pr create` → Wait for AI reviews. 4. Merge: `gh pr merge --squash` ### Commit Rules - **Language**: Turkish ONLY. (e.g., "feat: yeni buton eklendi") - **Format**: Conventional Commits (`feat:`, `fix:`, etc.) - **Prohibited**: AI signatures ("Generated by..."). ### AI Code Review - Codex & Claude Code review every PR automatically. - Do not merge until reviews are complete. ## WORK_PRINCIPLES - **Automate**: Use scripts/CI over manual work. - **Safety**: Test before deploy. No direct push to main. - **Quality**: Fix root causes, don't patch symptoms. ## CODE_RULES ### General Standards - **Length**: Max 300 lines (ideal 200). Split if exceeded. - **Quality**: Production-ready, SOLID, DRY, KISS. - **Language**: Code in English. - **Comments**: Turkish. MINIMAL usage. Avoid clutter. Explain "WHY" only for complex logic. - **Type Safety**: 100% strict typing in ALL languages (no `any`, `void*`, `interface{}`, etc.). Runtime validation required. ### Organization & Naming - **Structure**: Logical folders, clear public/private separation. - **Naming**: `camelCase` (vars/funcs), `PascalCase` (classes/types), `UPPER_SNAKE_CASE` (constants). - **Imports**: External → Internal → Types. ### Testing & Error Handling - **Coverage**: Core logic 90%, others 70%. - **Strategy**: Real scenarios (no mocks), integration tests. - **Errors**: Try-catch with meaningful messages and logging. ## RESEARCH_GUIDELINES - **Verify**: Check latest versions/docs. Don't assume. - **Sources**: Official docs > GitHub README > Recent StackOverflow. - **Tools**: Use `context7` for libs, `WebSearch` for general info. - **Process**: Check version → Read changelog → Apply migration. ## DEVELOPMENT_TOOLS - **CLI**: `gh`, `git`, `rg`, `fd`. - **Local CI**: `act` (optional). ### PACKAGE_MANAGER_POLICY - **Bun ONLY** for JS/TS projects. - Use `bun install/add/run`. No `npm/yarn`. - Pin Bun version in CI. ---