Loading prompt…
Turns a project idea into a complete scaffold: a summary, build steps, directory structure, the purpose of each file, commented source for every file, a setup script and a README.
Version 1 · 3 variables · 2 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
What the project should do. Narrow and concrete beats broad and ambitious.
Language, runtime and any framework you want used. Say 'your choice, explain why' to leave it open.
Hard limits and things to deliberately leave out: no database, standard library only, must run offline, target version.
Fill in Project idea, Stack or language to copy the customized prompt.
PROJECT:
A command-line tool that watches a directory and mirrors changed files into an S3 bucket continuously.
SUMMARY:
A watcher process observes filesystem events under a root directory. Each create or modify event is debounced, then handed to a worker that uploads the file to S3 under a key mirroring its relative path. A small JSON state file records the last-uploaded hash per path so a restart does not re-upload unchanged files.
STEPS:
1. Install dependencies and configure AWS credentials in the environment.
2. Create a config file naming the watch root and bucket.Showing all 1 public result from Claude Opus 5 on version 1.
PROJECT:
A command-line tool that watches a directory and mirrors changed files into an S3 bucket continuously.
SUMMARY:
A watcher process observes filesystem events under a root directory. Each create or modify event is debounced, then handed to a worker that uploads the file to S3 under a key mirroring its relative path. A small JSON state file records the last-uploaded hash per path so a restart does not re-upload unchanged files.
STEPS:
1. Install dependencies and configure AWS credentials in the environment.
2. Create a config file naming the watch root and bucket.
3. Run the watcher; it performs one reconciling pass, then streams changes.
4. Stop with Ctrl-C; in-flight uploads finish before exit.
STRUCTURE:
```
filesync/
README.md
pyproject.toml
src/filesync/
__init__.py
cli.py
watcher.py
uploader.py
state.py
tests/
test_state.py
```
DETAILED EXPLANATION:
- `cli.py`: parses arguments, loads config, wires the watcher to the uploader.
- `watcher.py`: wraps watchdog, debounces rapid events into a single upload.
- `uploader.py`: computes the S3 key, uploads, retries with backoff.
- `state.py`: reads and atomically writes the hash-per-path JSON file.
CODE:
Contributor notes: Illustrative example — not an actual model run. Written to show the shape of a good answer so the prompt can be judged before you spend a call on it. Attribution: adapted from https://github.com/danielmiessler/fabric by danielmiessler, licensed MIT. Source file: https://github.com/danielmiessler/fabric/blob/main/data/patterns/create_coding_project/system.md
1 public result from 1 model
Reports go to moderators and are never shown publicly.
No public results yet
Break a dependency replacement into reviewable stages with compatibility checks, exit criteria and realistic rollback limits.
No public results yet
Define realistic traffic, workload data, measurements and stopping rules for an authorized performance test.
No public results yet
Find source-visible labeling, semantics and keyboard risks, while separating code findings from checks that require a browser.
No public results yet
Map feature assets, trust boundaries and data flows to concrete threats, existing controls and targeted verification tasks.
No public results yet
Turn an API contract into a small client design that handles retryable failures, deadlines and idempotency deliberately.
No public results yet
Interpret supplied plan evidence and prioritize query or index experiments without inventing costs or speedups.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.