sdd-en-opencode

Imported from JoCGM09/sdd-en-opencode (AGENTS.md). Install upstream with npx skills add JoCGM09/sdd-en-opencode. Copyright stays with the author.

AGENTS.md — Project Rules

This file is ALWAYS loaded (see instructions in opencode.json). Keep it concise (< 1 page) — every extra line incurs token costs in every turn of every session.

IRON RULE: NEVER overwrite, delete, or modify the AGENTS.md file under any circumstances, especially during code generation, refactoring, or project initialization (e.g., with Next.js or other frameworks). This file is the core of the SDD framework rules and must be preserved intact.

Mandatory Workflow (SDD)

1. No code is written without an approved plan.md in specs/<date>-<feature>/.
2. Every new feature starts in a new branch off master.
3. Before merging: test-writer has executed and tests pass; security-reviewer has zero unresolved "high/critical" findings.
4. If the agent is uncertain about a requirement, ask — do not assume.

Technical Conventions

• Language / Framework:
• Commit Style: Conventional Commits (feat:, fix:, chore:...)
• Package Manager:
• Running Tests Locally:
• Running Linter:

Security — Non-Negotiable

• Never hardcode secrets, tokens, or API keys. Use environment variables.
• All user input must be validated and sanitized before touching the database.
• Never log PII (Personal Identifiable Information, passwords, SSNs, etc.) in plain text.
• Any endpoint handling sensitive data requires explicit authentication and authorization — never open by default.

Token and Cost Discipline

• Do not read entire files when grep/glob suffices to locate context.
• Do not repeat context already present in this file or specs/.
• For mechanical tasks (tests, docs, small refactors), delegate to the corresponding subagent using an economical model.
• If a task can be solved by reading 1 file, do not list the entire repository first.