leetcode coach

Engineering Community

Skill notes

Pre-flight Check (REQUIRED)

Before making any TinyFish call, always run BOTH checks: 1. CLI installed? If not installed, stop and tell the user: Install the TinyFish CLI: npm install -g @tiny-fish/cli 2. Authenticated?

Step 1 — Gather inputs

Ask for the following if not already provided: Required: Preferred language — e.g. Python, JavaScript, Java, C++, Go, Rust Optional (but improves results): Weak areas / topics to focus on — e.g. "dynamic programming", "graphs", "sliding window", "binary search", "recursion", "trees"

Step 2 — Find matching problems

Fire parallel TinyFish agents across LeetCode, HackerRank, and Codeforces to find real problems matching the topic and difficulty. Before running, replace: {DIFFICULTY} — Easy / Medium / Hard {TOPIC} — human-readable topic e.g. dynamic programming {TOPIC_SLUG} — URL-friendly e.g. dynamic-programming

Step 3 — Present problem options

From the results, pick the 3 best problems across all sources. Prefer: LeetCode problems (widest community support, best editorial availability) Problems with clear descriptions visible from the listing Problems with acceptance rates between 30-60% for Medium difficulty Present them like this:

Step 3b — Ask how they want to solve it

Once the user picks a problem, ask: If they choose option 1 (website): Give them the direct link to the problem and wish them luck: Stop here. Do not create any files. If they choose option 2 (locally):

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tinyfish-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · Vendor-specific
Operating systems
macOS · Linux · Windows
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Gather inputs

Ask for the following if not already provided: Required: Preferred language — e.g. Python, JavaScript, Java, C++, Go, Rust Optional (but improves results): Weak areas / topics to focus on — e.g. "dynamic programming", "graphs", "sliding window", "binary search", "recursion", "trees"

02
Step 2 — Find matching problems

Fire parallel TinyFish agents across LeetCode, HackerRank, and Codeforces to find real problems matching the topic and difficulty. Before running, replace: `{DIFFICULTY}` — Easy / Medium / Hard `{TOPIC}` — human-readable topic e.g. `dynamic programming` `{TOPIC_SLUG}` — URL-friendly e.g. `dynamic-programming`

03
Step 3 — Present problem options

From the results, pick the 3 best problems across all sources. Prefer: LeetCode problems (widest community support, best editorial availability) Problems with clear descriptions visible from the listing Problems with acceptance rates between 30-60% for Medium difficulty Present them like this:

04
Step 3b — Ask how they want to solve it

Once the user picks a problem, ask: If they choose option 1 (website): Give them the direct link to the problem and wish them luck: Stop here. Do not create any files. If they choose option 2 (locally):

05
Step 4 — Fetch the full problem

Once the user picks, fetch the full problem description using TinyFish.

06
Step 5 — Create local files

Once you have the full problem, create these three files in the current working directory:

07
Step 6 — Brief the user

Once the files are created, tell the user:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.