Qredence
- 73 skills
- 0 followers
- 6 hours ago last updated
- ▌ Recall · qredenceSemantic search for memory. Use to find solutions, patterns, or context from Chroma Cloud.
- ▌
- ▌ Changelog Generator · qredenceAutomatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
- ▌
- ▌
- ▌ Dspy Rlm · qredence bundleUse when analyzing, explaining, or implementing dspy.RLM (Recursive Language Model / REPL code agent). Not for RAG or dspy.Retrieve.
- ▌ Analyzing Rlm Performance · qredenceAnalyzes and tunes Fleet's DSPy RLM loop, provider budgets, and Daytona broker latency. Use when reviewing RLM efficiency, reducing prompt or retry cost, instrumenting interpreter cells, or deciding whether Daytona snapshots/prewarming are justified.
- ▌ Long Context · qredence bundleUse bounded retrieval to analyze large documents, transcripts, code, or datasets.
- ▌ Data Analysis · qredenceCompute and verify descriptive statistics, trends, and qualified anomalies.
- ▌
- ▌ Workspace Files · qredence bundleUse durable Session Workspace, Project, Attachment, and Artifact tools correctly.
- ▌ Layout · qredenceDiagnose or improve layout in selected Figma frames, screens, components, or Figma Make prototypes by clarifying reading order, grouping, hierarchy, spacing rhythm, density, adaptation, and content extremes. Use when UI feels crowded, flat, misaligned, hard to scan, structurally unclear, or unstable across sizes.
- ▌ Polish · qredenceRun a final Figma Design or Figma Make quality pass that refines spacing, alignment, typography, color consistency, component state coverage, copy consistency, accessibility basics, and visual coherence without changing the underlying concept. Use when a UI is close and needs launch-ready finish rather than redesign. Not for Figma Sites publish readiness (site-launch-checklist) or Dev Mode handoff preparation (dev-handoff-prep).
- ▌ Improve UI · qredenceAudit one selected Figma Design surface or Figma Make prototype against visible design evidence, connected libraries, local styles, variables, components, sibling screens, and user task goals, then return up to three supported UI improvement findings with clear evidence and proposed changes. Do not use for design-system conformance audits (follow-ds-guidelines), Nielsen-heuristic evaluations (heuristic-evaluation), or cross-screen consistency checks (visual-consistency-check).
- ▌ Design Crit · qredenceCritique selected Figma frames, components, flows, or Figma Make prototype output with structured design feedback, severity, visible evidence, user impact, and actionable next changes. Use when the user asks for UX critique, design review, conversion review, accessibility feedback, or quality assessment before making changes.
- ▌ File Cleanup · qredenceReorganizes a messy, sprawling file into clearly named, logically ordered pages and sections, archiving or clearly marking stale exploration work, without altering any final designs. Use when a working file has become hard to navigate after a lot of exploration.
- ▌ Prototype QA · qredenceReviews a prototype plan or visible/provided prototype details for missing links, ambiguous destinations, dead ends, overlay risks, orphaned frames, and state-logic gaps. Use before sharing a prototype for testing, review, or demo. Treat results as evidence-based QA findings and a manual test plan, not as guaranteed automated traversal unless the current Figma Agent session explicitly supports prototype inspection.
- ▌ Build From Prd · qredenceReads a product requirements document (PRD) and produces the corresponding Figma design -- screens, states, and flow -- reusing existing design system components wherever possible and flagging any requirement that has no corresponding pattern yet. Use when a PRD or spec exists and needs to become an actual design, especially when paired with a connector to the requirements source.
- ▌ Comment Triage · qredenceReads all open comments on a file and triages them into categories (needs a design change, needs a decision/answer, already resolved but not marked, out of scope) so a designer can work through feedback efficiently. Use when a file has accumulated many comments and it's unclear what still needs action.
- ▌ Build Primitive · qredenceDesign, revise, or specify a reusable Figma component primitive for Figma Design or Figma Make, including anatomy, variants, states, accessibility expectations, content rules, and behavior when relevant. Use for buttons, inputs, dialogs, menus, tabs, cards, tables, pickers, uploaders, steppers, and other foundational UI primitives.
- ▌ Component Audit · qredenceReviews a component set (all variants of one component) for structural consistency: naming, variant properties, layer structure, auto layout settings, and exposed component properties. Use when publishing or updating a component to a shared library, or when a component has grown organically and needs a health check before others build on it.
- ▌ Handoff Summary · qredenceWrites a concise handoff summary of a file's current state -- what's finished, what's in progress, key decisions made and why, and open questions -- for a teammate picking up the work, a new team member, or a stakeholder update. Use whenever context needs to transfer cleanly to someone else.
- ▌ Persona Builder · qredenceBuilds a lightweight, evidence-grounded persona (or refreshes an existing one) from available research notes, interview data, or survey results for a specific project -- avoiding invented demographic detail not supported by the source data. Use when a project needs a shared reference point for who it's designing for.
- ▌ Affinity Mapping · qredenceGroups raw qualitative data (research notes, survey verbatims, support tickets, interview quotes) into a bottom-up affinity map -- clustering related observations before naming themes, rather than sorting into pre-defined buckets. Use for open-ended research synthesis where categories aren't known in advance.
- ▌ Dev Handoff Prep · qredencePrepares a finished design for developer handoff in Dev Mode: verifies naming, checks for stray unstyled elements, adds redline/behavior annotations for anything code can't infer from static layers, and confirms components are ready to inspect. Use as the last step before marking a design 'ready for development'.
- ▌ Sticky Synthesis · qredenceSynthesizes provided sticky-note content into evidence-based themes, counts, takeaways, and outliers. Use after a brainstorm, retro, or research session when sticky content is visible in the current Figma Design file or supplied as text.
- ▌ Content Inventory · qredenceExtracts every piece of user-facing text in a file or flow into a structured, exportable table (screen, element, current text, character count) for copy review, translation hand-off, or content audits. Use when copy needs to be reviewed, translated, or tracked outside of Figma.
- ▌ Deck From Outline · qredenceConverts an outline or document into a slide-by-slide presentation plan and, when supported, a consistent deck in the active Figma surface.
- ▌ Design Change Diff · qredenceExplains verified changes between two supplied or accessible design states in language useful to product and engineering teams. Use when before-and-after frames, versions, screenshots, or a documented change list are available.
- ▌ Design Tokens Sync · qredenceCompares Figma variables (colors, spacing, typography, radii) against a codebase's design tokens (CSS custom properties, JSON, or a tokens package) and reports mismatches, missing tokens, and naming drift in both directions. Use when design and engineering tokens need to be reconciled, e.g. before a release or after either side changes independently.
- ▌ Figma Skill Router · qredenceUse when a Figma Design agent must choose one installed Figma skill for a request or design-file context.
- ▌ Accessibility Audit · qredenceAudits a design against WCAG 2.2 AA basics that are checkable in Figma: color contrast, text sizing, tap/click target size, focus order implied by layer order, and presence of alt-text-equivalent labels for meaningful images/icons. Use before a design is considered done, or when accessibility compliance is a requirement.
- ▌ Code Connect Mapper · qredencePlans and drafts the mapping between Figma components/variants and their corresponding code components and props for Code Connect, so Dev Mode can show real production code snippets instead of generic markup. Use when setting up or expanding Code Connect coverage for a design system library.
- ▌ Content Tone Review · qredenceReviews existing copy in a design against a stated voice-and-tone guideline (or against the file's own established voice if no separate guideline exists) and flags lines that are inconsistent, too formal/casual, jargon-heavy, or unclear. Use as a copy QA pass distinct from drafting new copy.
- ▌ Journey Map Builder · qredenceBuilds an evidence-grounded journey-map structure from research notes, transcripts, or a described experience. Use when stages, actions, thoughts, pain points, and opportunities need to become a shareable Figma Design artifact or structured specification.
- ▌ Microcopy Generator · qredenceDrafts microcopy -- button labels, empty states, error messages, tooltips, confirmation dialogs, form hints -- for a specific screen or component, matching a stated (or inferred from existing content) voice and tone. Use when placeholder text needs to become real, ship-ready copy.
- ▌ Prototype From Flow · qredenceProduces a prototype connection plan from a described user flow, flow diagram, PRD, or set of designed screens. Use when screens exist or a flow is described and the team needs a clear map of frames, triggers, actions, branches, overlays, and missing screens before manual prototype wiring. This is a planning/specification skill, not an interaction-editing skill.
- ▌ Rename Layers Batch · qredenceBatch-renames a large set of layers according to a rule (pattern, content-based inference, or find/replace) in one pass, reporting every change made. Use for quick, mechanical bulk renaming, as a lighter-weight companion to the more comprehensive naming-convention-enforcer.
- ▌ Competitive Teardown · qredenceTears down a competitor's product, flow, or specific feature -- analyzing structure, patterns, strengths, and weaknesses -- and extracts concrete, actionable insights for the current project. Use when researching competitors before or during a design phase.
- ▌ Follow Ds Guidelines · qredenceAudits a selected frame, screen, or file against the team's published design system (components, styles, and variables) and flags every deviation with a suggested fix. Use when a design needs to conform to existing design system rules before review or handoff. Does not create new components -- use component-audit or legacy-styles-to-variables for that.
- ▌ Heuristic Evaluation · qredenceEvaluates a flow or screen against Jakob Nielsen's 10 usability heuristics (visibility of system status, match with the real world, user control, consistency, error prevention, recognition over recall, flexibility, minimalist design, error recovery, help and documentation) and reports concrete violations. Use for a fast, structured usability pass independent of visual polish.
- ▌ Semantic Color Audit · qredenceAudits code for raw Tailwind palette color classes or hardcoded colors used where a semantic design-system token should be used instead, catching drift between the token system and actual usage. Use periodically or before a release to catch semantic color drift.
- ▌ Wire Up Interactions · qredenceProduces precise interaction specs for specific prototype behaviors, including source element, trigger, action, destination, overlay behavior, animation, and verification steps. Use when a prototype interaction is missing, wrong, or needs refinement, but treat the result as a manual wiring plan unless the current Figma Agent session explicitly supports interaction editing.
- ▌ Workshop Facilitator · qredenceDesigns a workshop structure with sections, prompts, timing, and facilitator guidance. Use for brainstorms, retrospectives, kickoffs, or design studios when the result should be created in Figma Design or delivered as a board specification.
- ▌ Apply Color Variables · qredenceApply existing Figma Color variables from a specified Variables collection to hard-coded colors in the current selection, page, or file. Use when colors are not bound to collection variables and should be standardized to the design system.
- ▌ Branch Review Summary · qredenceSummarizes provided or accessible design-branch changes for reviewers, highlighting scope, rationale, risk, and review focus. Use when branch or before/after evidence is available in the current session.
- ▌ Component Naming Sync · qredenceKeeps naming consistent across Figma component names, variant/prop names, and their code equivalents -- PascalCase components, camelCase props, kebab-case files and CSS classes -- so design and code stay traceable to each other. Use when component or variant names drift between Figma and code.
- ▌ Cva Variant Generator · qredenceGenerates a class-variance-authority (cva) variant configuration from a Figma component's variant properties, mapping each Figma variant option to its corresponding Tailwind class set. Use when turning a Figma component with multiple variants into styled, type-safe code variants.
- ▌ Library Health Report · qredenceAudits accessible components, styles, and variables for naming, duplication, documentation, and structural health. Use for a scoped library review; include usage or publication findings only when the required library or analytics context is explicitly available.
- ▌ Motion Spec Generator · qredenceDefines and documents a precise motion spec (duration, easing curve, delay, properties animated) for key transitions in a flow, so the intended motion feel is captured explicitly rather than left to be reverse-engineered from a prototype. Use when documenting motion decisions for engineering handoff or design system consistency.
- ▌ Site Launch Checklist · qredenceReviews a Figma Sites project against a pre-launch checklist: responsive behavior across breakpoints, working links/navigation, page titles and meta content, image alt text, and load-affecting asset sizes. Use before publishing a Figma Sites project.
- ▌ Design Brief Generator · qredencePlan a Figma Design screen, component, flow, or Figma Make prototype through a short discovery interview, then produce a confirmed design brief without generating UI. Use when the user has a vague request, early product idea, unclear scope, competing constraints, or needs alignment before design generation.
- ▌ Localization Readiness · qredenceChecks a design for issues that will surface once text is translated: fixed-width containers that will clip longer languages, RTL layout assumptions, concatenated/hardcoded sentence fragments, and untranslatable content baked into images. Use before sending a design or file for localization.
- ▌ Shadcn Theme Variables · qredenceAdd, repair, or normalize Figma Variables so a Figma design file matches the shadcn/ui semantic theming model. Use when the user asks to create shadcn theme variables, fix light/dark theme variables, map Figma Variables to shadcn CSS tokens, align variables with app/globals.css, or update variable-bound properties for shadcn-style components.
- ▌ Spacing Scale Enforcer · qredenceMaps arbitrary spacing values to the nearest step on the project's spacing scale (typically Tailwind's 4px-based scale) and flags off-scale spacing in designs or code. Use when spacing looks inconsistent or when translating Figma spacing values into Tailwind utility classes.
- ▌ Figma To Code Component · qredenceTranslates a selected Figma frame or component into idiomatic code for a specified target (e.g. React + Tailwind, React + CSS Modules, SwiftUI, Jetpack Compose), mapping Figma variables to design tokens and Figma auto layout to the target's layout system. Use for a first-pass implementation of a specific design element, not a full application build.
- ▌ Screenshot To Component · qredenceUse when the user provides a screenshot or crop of a UI component, panel, sidebar, modal, menu, card, toolbar, form, or dense app surface and wants it recreated as a structured Figma Design component. Focuses on editable hierarchy, auto layout, semantic nesting, reusable subcomponents, component properties, variants, and maintainable layer naming instead of flat screenshot tracing.
- ▌ Visual Consistency Check · qredenceScans a flow for inconsistent spacing, alignment, corner radii, icon styles, and grid usage across screens that should feel like one cohesive product. Use when multiple screens were designed at different times or by different people and need to feel unified.
- ▌ Brand Kit Asset Generator · qredenceCreates or specifies on-brand marketing asset variants from an existing brand kit. Use when colors, typography, logos, templates, and required output sizes are available in the current Figma Design context or supplied by the user.
- ▌ Design First UI Prompting · qredenceTurn a vague product, page, screen, component, or prototype request into a Figma-ready prompt with clear goal, audience, layout, typography, color, content, states, constraints, and non-goals. Use before asking Figma Agent or Figma Make to generate, revise, or refine UI when the user needs a stronger prompt rather than direct design execution.
- ▌ Plugin Widget Recommender · qredenceRecommends plugin or widget categories for a concrete Figma workflow and audits supplied plugin usage against a supplied approval policy. Use when the user needs tool-selection guidance or a policy comparison; verify current marketplace availability and do not assume access to file-level plugin history or organization admin data.
- ▌ States Completeness Check · qredenceChecks that every screen and key component in a flow has the full set of states it needs -- empty, loading, populated, error, partial/edge-case data, and (for components) hover/focus/pressed/disabled -- and lists which are missing. Use before a flow is considered complete for handoff.
- ▌ Token Tailwind Theme Sync · qredenceSyncs Figma variables (color, spacing, radius, typography) into a tailwind.config theme extension and CSS custom properties, following shadcn's theming file structure. Use when Figma variables have changed and the Tailwind/CSS theme needs to catch up, specifically for shadcn-based projects.
- ▌ Variable Driven Prototype · qredenceDesigns a state model for a variable-driven Figma prototype, including variables, initial values, set-variable moments, conditional branches, reflected UI states, and manual verification steps. Use when a prototype needs remembered state or branching logic, but treat the result as a specification unless the current Figma Agent session explicitly supports prototype interaction editing.
- ▌ Legacy Styles To Variables · qredenceFinds hardcoded fill, stroke, and effect colors, hardcoded spacing values, or old-style color/text styles in a file and migrates them to the equivalent shared variables or styles from an enabled library. Use when adopting variables in a file that predates them, or migrating a file onto a newer design system version.
- ▌ Naming Convention Enforcer · qredenceRenames layers, frames, components, and pages to follow a specified naming convention (e.g. PascalCase components, sentence-case screens, prefix-based icon names). Use for cleaning up messy layer names before handoff, publishing, or Dev Mode inspection.
- ▌ Shadcn Component Structure · qredenceEnsures generated React components follow shadcn/ui structural conventions -- forwardRef/ref handling, cn() className merging, cva-based variants, proper prop interfaces extending native element types, and correct file placement. Use when generating or reviewing component code meant to fit into a shadcn/ui-based codebase.
- ▌ Tailwind Class Order Check · qredenceAudits className strings for consistent ordering, duplicate or conflicting utility classes, and alignment with the project's class-sorting convention. Use when reviewing generated or hand-written component code for Tailwind class hygiene.
- ▌ Animation Consistency Check · qredenceAudits animated components and prototype transitions across a file for consistent easing, duration, and motion character, flagging transitions that feel out of step with the rest of the product's motion language. Use when multiple people or sessions have added animation and it needs to feel cohesive.
- ▌ Container Layout Normalizer · qredenceSets consistent container widths, max-width, centering, and responsive padding across breakpoints, matching standard Tailwind/shadcn container conventions instead of ad hoc per-page values. Use when a layout's outer container sizing looks inconsistent or arbitrary.
- ▌ Responsive Breakpoint Check · qredenceReviews a layout's auto layout, constraints, and resizing settings to verify it will adapt correctly across specified breakpoints (e.g. mobile, tablet, desktop) rather than just checking how it looks at one frame size. Use when a design needs to work responsively, especially for Figma Sites or handoff to a responsive web build.
- ▌ Base UI Primitive Composition · qredenceComposes interactive components (dialogs, popovers, tooltips, menus, tabs, accordions) from Base UI's unstyled primitive parts (Root/Trigger/Portal/Content/etc.) instead of hand-rolled behavior, preserving built-in accessibility and state management. Use when building any interactive/overlay component that has a Base UI or Radix equivalent primitive.
- ▌ Color Token Format Normalizer · qredenceConverts colors to the CSS-variable/HSL token format used by shadcn's theming convention (--background, --primary, etc.), flags hardcoded hex/rgb values that should reference a token, and keeps light/dark pairs aligned. Use when generating or auditing color usage in a shadcn-based codebase.