cadwaladyr revised this gist 3 weeks ago. Go to revision
1 file changed, 48 insertions
WorkSpace.setup(file created)
| @@ -0,0 +1,48 @@ | |||
| 1 | + | You are preparing this workspace for a future implementation in LANGUAGE. | |
| 2 | + | ||
| 3 | + | The target machine is a MacBook Pro running macOS. Your only job in this run is to make sure this workspace is ready to build a real application in LANGUAGE with these capabilities: | |
| 4 | + | ||
| 5 | + | - CLI argument parsing | |
| 6 | + | - HTTP client and, if practical, a small local HTTP server | |
| 7 | + | - SQLite persistence | |
| 8 | + | - config-file parsing, preferably TOML; JSON, INI, or another idiomatic config format is acceptable if TOML support is weak | |
| 9 | + | - tests | |
| 10 | + | - formatter or style checker, if one exists for this language | |
| 11 | + | - a repeatable build command | |
| 12 | + | - a repeatable test command | |
| 13 | + | ||
| 14 | + | Do not implement the final application yet. The application spec will be provided in a later run. | |
| 15 | + | ||
| 16 | + | Work to perform: | |
| 17 | + | ||
| 18 | + | 1. Inspect the current system and workspace. | |
| 19 | + | 2. Determine the idiomatic compiler/interpreter, build tool, package manager, and test tool for LANGUAGE on macOS. | |
| 20 | + | 3. Install or configure the missing language tooling only as needed. | |
| 21 | + | 4. Prefer Homebrew or the language’s official installer/package manager. | |
| 22 | + | 5. Avoid global changes unless they are normal and necessary for the LANGUAGE toolchain. | |
| 23 | + | 6. If an action modifies anything outside the workspace, explain why it is necessary before doing it. | |
| 24 | + | 7. Create a minimal smoke-test project in this workspace. | |
| 25 | + | 8. Add the smallest possible example that proves the workspace can: | |
| 26 | + | - parse CLI arguments, | |
| 27 | + | - make or expose an HTTP request/endpoint, | |
| 28 | + | - open SQLite and run a simple query, | |
| 29 | + | - read a config file, | |
| 30 | + | - run a test. | |
| 31 | + | 9. Add a README.md documenting: | |
| 32 | + | - installed tools, | |
| 33 | + | - project layout, | |
| 34 | + | - build command, | |
| 35 | + | - test command, | |
| 36 | + | - run command, | |
| 37 | + | - any limitations or missing pieces. | |
| 38 | + | 10. Run the build and tests. | |
| 39 | + | 11. Leave the workspace clean and ready for the later application implementation prompt. | |
| 40 | + | ||
| 41 | + | Important constraints: | |
| 42 | + | ||
| 43 | + | - Keep this setup idiomatic for LANGUAGE. | |
| 44 | + | - Do not quietly substitute another implementation language. | |
| 45 | + | - Shell scripts are acceptable only for setup convenience. | |
| 46 | + | - If a dependency is unavailable or broken on macOS, choose the closest practical idiomatic alternative and document the tradeoff. | |
| 47 | + | - Prefer simple, boring dependencies over clever or obscure ones. | |
| 48 | + | - The final result of this run should be a verified LANGUAGE project skeleton, not the finished application. | |
Newer
Older