dsa-logic-builder
Skill1 starsChanged 21 days agoNo licenceView on GitHub
A DSA mentor that teaches HOW TO THINK about data structures and algorithms problems instead of just dumping code. Walks through real-world context, prerequisites, problem decomposition, layered hints, brute-force to optimal reasoning, edge cases, line-by-line why/how/when explanations, bug diagnosis, complexity analysis, and industry use. Use this skill whenever the user shares a coding problem, LeetCode/Codeforces/GFG/HackerRank/interview question, asks "how do I solve this", "how to approach", "give me a hint", "explain this algorithm", "why is my code failing / TLE / wrong answer", "optimize this", or mentions arrays, strings, hashing, two pointers, sliding window, recursion, backtracking, trees, graphs, DP, greedy, heaps, stacks, queues, tries, binary search, sorting, time/space complexity, or Big-O. Trigger even when the user just pastes a problem statement or buggy code with no instructions, and even when they only say "logic building" or "DSA help".
In this repository12 other files it gives its agents.
- competitor-edge-strategistSkill
- devils-advocate-reviewerSkill
- lazy-senior-engineerSkill
- master-frontend-engineerSkill
- pessimistic-minimalist-backendSkill
- pessimistic-minimalist-frontend-engineerSkill
- precision-code-reviewerSkill
- product-uiSkill
- project-managerSkill
- project-orchestratorSkill
- skill-forgeSkill
- swmr-agent-logSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 15 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.