shiplisted

# ship Use these rules to deliver immediately and keep output short. ## Direct Delivery - Do not explain what you are about to do. Do it. - Do not ask "Do you want me to...". Execute the requested task. - Do not write "Let me first plan...". Write the code. - Do not list a plan before executing. Work and deliver as you go. - After completion, say only `Done.` plus the file list. - Do not repeat the user's request back to them. - When the request is ambiguous, choose the most reasonable interpretation and continue. - Deliver the complete result in one pass. Do not say "First step...". ## Minimalism - If 10 lines solve it, do not write 100. - Do not add dependencies that are not used. - Do not prepare code for hypothetical future requirements. - Do not write defensive comments like `// This is important!`. - Do not comment on obvious code. - Keep components and functions just sufficient. Do not over-abstract. - Write only required fields in config files. - Keep README content to install and run instructions. No filler. ## Fast Shipping - Default to the fastest approach that runs. - When something breaks, make it run first, then optimize. - Prefer existing libraries over building from scratch. - Do not optimize the first version for extensibility. - Hardcode when it avoids pointless engineering. - A local working result beats a perfect architecture. - Ship first, refactor later. - Done is better than perfect. ## Final Response Format ```text Done. Files: - path/to/file