All authors
Claude Skills by JuanColoradoV
github.com/JuanColoradoV16 skills1 installs5 views
- Pd Design LeadUse when a product-design request spans more than one discipline, when it's unclear which pd-* skill applies, when starting design work on a new project, or when running a design effort end-to-end (research through QA and handoff). Start here for any non-trivial design task.Votes: 0GitHub stars: 2
- Pd Design System OpsUse when the design system itself needs to grow or be reviewed: a gap was flagged during product work, a token or component is proposed or changed, no system exists yet and one should be established, or the system needs an audit or changelog entry. To apply the system in product work, use pd-design-system.Votes: 0GitHub stars: 2
- Pd Design SystemUse when translating a design into concrete design-system parts: choosing the exact type styles, color/spacing tokens, and component variants from the project's live system (Figma, Penpot, Pencil, code-based, or other) and verifying every name binds to something real. Consumes the system; to grow or change it, use pd-design-system-ops.Votes: 0GitHub stars: 2
- Pd FoundationsUse when starting or contributing to any product-design task handled by a pd-* skill (research, architecture, flows, screens, copy, visual, design system, mocks, prototypes, QA, handoff, metrics). Holds the shared contract every specialist works against. Load it before any other pd-* skill.Votes: 0GitHub stars: 2
- Pd HandoffUse when finished, QA-passed designs need to become engineering-ready: developer handoff specs, redlines and measurements, states and interaction notes, asset export, design-token-to-code mapping, and component-to-code mapping (with the design tool's code-mapping feature where available). The design-to-build bridge. Links work back to its requirement in the tracker. Part of the pd-* design team.Votes: 0GitHub stars: 2
- Pd MetricsUse when defining how to measure a design's success, or evaluating its impact after ship: success metrics, HEART / Goal-Signal-Metric, task-based metrics, analytics event and instrumentation specs, guardrail metrics, and honest result-reading from the project's analytics source. Closes the loop research opens. Part of the pd-* design team.Votes: 0GitHub stars: 2
- Pd MocksUse when building mockups or screens in the project's design tool (Figma, Penpot, Pencil, Sketch, Framer, or real code components / an HTML prototype) from finished design, content, visual, and component specs, bound to the live design system. Also use right after creating a batch of frames or screens. Part of the pd-* design team.Votes: 0GitHub stars: 2
- Pd PrototypingUse when a design needs to become an interactive or animated prototype (clickable flows, transitions, micro-interactions, motion) for usability testing or stakeholder review, in any tool: design-tool prototypes or coded prototypes. Complements pd-mocks (static screens). Part of the pd-* design team.Votes: 0GitHub stars: 2
- Pd ResponsiveUse when a design must work across screen sizes, devices, or platforms: responsive breakpoints, fluid layouts, adaptive component behavior, touch targets, density, and platform conventions (web, mobile web, iOS, Android, native apps). Consumes the design; binds to the live system. Part of the pd-* design team.Votes: 0GitHub stars: 2
- Pd Ux ArchitectureUse when a product's content, objects, or navigation need explicit structure: content modeling, taxonomy, sitemaps, navigation systems, and findability. Defines the nodes and entities of a product; sits between research and flows. Part of the pd-* design team.Votes: 0GitHub stars: 2
- Pd Ux DesignUse when screens or interactions need to be designed or redesigned: wireframes, layout, visual hierarchy, interaction design, component composition, screen specs, and the full set of states (default, loading, empty, error, success, partial, disabled). Consumes flows and binds to the live design system. Part of the pd-* design team.Votes: 0GitHub stars: 2
- Pd Ux FlowsUse when an experience spans multiple steps or screens and needs structure: mapping user flows, task flows, journey maps, and state and decision logic. Sits between research (or pd-ux-architecture) and screen design. For content structure, taxonomy, sitemaps, or navigation models, use pd-ux-architecture instead. Part of the pd-* design team.Votes: 0GitHub stars: 2
- Pd Ux QaUse before declaring any design effort done, or to audit existing work: usability heuristic evaluation, accessibility audit (WCAG level from the project profile), regulatory UI review when a compliance regime is active, design-vs-spec QA against acceptance criteria, and rendered-output audits. Produces findings rated by severity. The team's quality gate. Part of the pd-* design team.Votes: 0GitHub stars: 2
- Pd Ux ResearchUse when the problem space or users aren't well understood, when assumptions need validating, or when a design effort should start from evidence. Covers discovery, interview and survey design, usability findings, synthesis, personas, jobs-to-be-done, opportunity framing, and competitive or heuristic review. Usually the first step of a design effort. Part of the pd-* design team.Votes: 0GitHub stars: 2
- Pd Ux WritingUse when any user-facing text needs creating or improving: microcopy, labels, buttons/CTAs, headings, error messages, empty states, notifications, onboarding copy, confirmations, tooltips, voice and tone, and localization readiness. Consumes the design; runs in parallel with visual design.Votes: 0GitHub stars: 2
- Pd Visual DesignUse when a design needs visual treatment: applying typography, color, spacing, hierarchy, elevation, radius, and brand expression through the project's design-system tokens, or when a screen needs a restyle, contrast fix, or hierarchy repair. Consumes the design; runs in parallel with writing.Votes: 0GitHub stars: 2