mshadmanrahman/claude-for-designers
Skill Claude Code
Break a design brief into executable time-boxed tasks, each with a done-when line. Use immediately before a build session.
A working repository for designers who use Claude as a collaborator. Skills, principles, project templates, and a career vault.
This repository also configures its own agents. See what claude-for-designers tells them →
mshadmanrahman/claude-for-designers
Skill Claude Code
Break a design brief into executable time-boxed tasks, each with a done-when line. Use immediately before a build session.
mshadmanrahman/claude-for-designers
Skill Claude Code
Turn an interrogated brief into the single source of truth for a design project. Use after /grill-me, before any IA or UI work.
mshadmanrahman/claude-for-designers
Skill Claude Code
Critique a design on layout, accessibility, responsiveness, dark mode and edge cases, with Pass, Needs work or Fail verdicts. Use on a built screen.
mshadmanrahman/claude-for-designers
Skill Claude Code
Establish color, typography, spacing, radius and motion as named role-based tokens. Use before building any interface.
mshadmanrahman/claude-for-designers
Skill Claude Code
Build an interface from the brief and the tokens rather than from a guess. Use only after grill-me, design-brief, information-architecture and design-tokens have run.
mshadmanrahman/claude-for-designers
Skill Claude Code
One move you can run on anything: point grill-me at a target and it makes you defend your thinking from first principles until the true matter is clear. Point it at your working contract and it rewrites the weak lines in place. Point it at a brief and it produces a Requirements Handshake. Point it at research, an…
mshadmanrahman/claude-for-designers
Skill Claude Code
Audit a design against Nielsen's ten usability heuristics, tying every finding to a specific element with a specific fix. Use on a built screen or a detailed mockup.
mshadmanrahman/claude-for-designers
Skill Claude Code
Map the user journey first, then derive the screen inventory, navigation and hierarchy from it, flagging any screen that serves no journey step. Writes the four-part markdown plus an HTML diagram of the step-to-screen mapping. Use after the brief is settled and before tokens or UI.
mshadmanrahman/claude-for-designers
Skill Claude Code
Stress-test a design through three lenses, confused user, skeptical engineer and impatient PM, before it goes to a stakeholder. Requires an actual design, an HTML file, Figma link or screenshot.
mshadmanrahman/claude-for-designers
Skill Claude Code
Diagnoses 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…
mshadmanrahman/claude-for-designers
Skill Claude Code
Turns one pasted job post into an application folder built only from the student's own career vault: a tailored resume, a cover letter under 250 words, and an HR call sheet with the answers already drafted. Reads career-vault/01 to 06 first and refuses to run while the positioning, portfolio story or resume are still…
mshadmanrahman/claude-for-designers
Skill Claude Code
Reads the newest entry of a project's log.md and tells the student where they left off: what they did and decided, what is open, and the next step. Takes an optional project name. With several projects and no name, shows a menu of each project's last entry. Read only. Use when the student says pick up, where did I…
mshadmanrahman/claude-for-designers
Skill Claude Code
Saves today's work session as a four-line entry (did, decided, open, next) at the top of the project's log.md, after the student confirms it, so a fresh chat can continue tomorrow with /pick-up. Writes to projects/ /log.md or career-vault/log.md, one entry per project touched, never to new-client. Use when the student…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: