stuck
SolidDiagnoses a broken course setup by reading the folder, so the student never has to describe the problem in English. Takes no argument. Reports which class they are on and which files are filled, then names one blocker and one fix: Claude Code opened at the wrong level, .claude/skills/ missing, skills not loading because the trust question was never answered, a file whose scaffolding was deleted before it was filled, work going into an answer-key .example.md, an unfilled YOUR TURN, a skill run before the files it reads were filled, or a hunt for a file no skill creates. When it cannot tell, it writes the group-chat message for the student. Use whenever a student says they are stuck, confused, blocked, or that something is not working.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- mshadmanrahman
- Repository
- mshadmanrahman/claude-for-designers
- Created
- 2 months ago
- Last Updated
- today
- Language
- HTML
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
get-unstuck
Pause, surface the current plan + open questions, and suggest the next concrete step so the agent (or operator) can recover from a deadlock or analysis paralysis.
stud
{{ ƔƔƔ }} Plan a non-trivial feature by interviewing to resolve unknowns, then studding every function as a runnable walking-skeleton (fake data, real wiring) so names, placement, and contracts can be reviewed before any real logic is written. Stops for review; fill is a separate pass.
pairing
Build work collaboratively in reviewable pieces, handing each piece back for review before starting the next, so the person stays in the lead and steers while the work happens instead of reviewing a finished result. Use when someone says to pair with them on something, asks to collaborate rather than direct, wants to review as it goes, or wants to guide the work piece by piece — on code, on a design decision, or on writing. For a test-first build it runs tdd, for restructuring it runs refactor, for an interface contract it runs design-an-api, and for plan work it runs iterative-plan-review or plan-implementation, each collaboratively; invoke any of those directly instead to run it straight through without pausing. Does not pace someone through code that already exists and builds nothing — use code-walkthrough. Does not explain, summarize, or research something instead of producing it — use code-overview or research.