swift-cyclelisted

# Swift Cycle ## Goal Maintain design consistency, execution continuity, and traceability with the smallest useful documentation set. Adjust the framework incrementally from repository evidence. Never describe a candidate, test, tool, or decision as verified when evidence is missing. ## Use the project's language 1. Respond and create documents in the user's requested language. 2. Preserve terminology and filename conventions already established in the repository. 3. Keep standard filenames such as `README.md`, `DESIGN.md`, `AGENTS.md`, `TODO.md`, and `DEVLOG.md` unchanged unless the project already uses an equivalent. 4. For Simplified Chinese terminology and document wording, read `references/zh-CN.md`. ## Inspect the real state first 1. Read repository instructions, `README.md`, `DESIGN.md`, relevant `docs/`, `.gitignore`, and existing maintenance records. 2. Inspect the Git branch, status, and relevant diff. Separate pre-existing user changes from the current task. 3. Distinguish confirmed facts, assumptions, and inferences. Do not invent repository structure, tests, tools, decisions, or validation results. 4. Preserve existing user work. Do not remove data, discard changes, or perform unrelated cleanup. ## Reuse before building Before implementation: 1. Check the current repository for reusable code, scripts, dependencies, tools, documentation, and implementation patterns. 2. Then evaluate official solutions and already installed Skills, plugins, MCP integration