with one click
studio
studio contains 33 collected skills from Dragoon0x, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Audit a brand's full identity (logo, typography, color, voice, visual language) for consistency, distinctiveness, and gap. Use when the user asks for a brand audit, identity review, brand health check, or wants to evaluate how a brand shows up across surfaces.
Plan a content calendar tied to product, brand, or marketing goals. Use when the user asks for a content plan, editorial calendar, content strategy, posting schedule, or wants to map content to themes and audiences over a period of time.
Write a sequence of emails for onboarding, nurture, sales, lifecycle, or launch. Use when the user asks for a drip campaign, email sequence, welcome series, onboarding emails, sales cadence, or any multi-email flow tied to a goal.
Design an a/b test or experiment including hypothesis, metrics, sample size, and analysis plan. Use whenever the user mentions a/b test, experiment, split test, multivariate test, or needs to design a test that produces a decision-quality result.
Audit a design or component for WCAG accessibility compliance. Use whenever the user mentions a11y, accessibility audit, WCAG check, contrast issues, keyboard navigation, screen reader support, focus order, or asks if a design is accessible.
Extract a brand voice guide from existing copy samples. Use whenever the user shares past copy and asks to define a voice, document a voice, create voice guidelines, or wants to make their existing voice teachable and repeatable.
Write a customer case study or success story that proves a claim with specific evidence. Use whenever the user mentions case study, customer story, success story, customer outcome, or wants to turn a customer's experience into proof for marketing or sales.
Analyze competitors including direct and adjacent products, positioning, pricing, and feature gaps. Use whenever the user mentions competitive analysis, competitor research, market positioning, competitive landscape, or needs to understand who else is in their space.
Write a complete component specification including api, states, variants, accessibility, and usage. Use whenever the user needs a component spec, component documentation, component api design, or is designing a new component for a design system.
Design a dark mode that pairs with an existing light mode, including color mapping, contrast adjustments, and surface elevation. Use whenever the user mentions dark mode, dark theme, theme switching, or wants to add dark mode to an existing design.
Design data visualizations including charts, graphs, and dashboards with attention to clarity, color use, and chart selection. Use whenever the user mentions data viz, charts, graphs, dashboards, analytics design, or needs to communicate numbers visually.
Run a structured design critique on a screen, mockup, component, or Figma file. Use whenever the user asks for design review, design feedback, design critique, design check, or wants someone to look at a screen and say what's working and what isn't.
Audit a codebase or design files for design system health, token drift, and inconsistency. Use whenever the user mentions design system audit, design token drift, design consistency, color drift, spacing drift, or wants to find and consolidate inconsistencies across components.
Scope a feature to its smallest valuable shape. Use whenever the user mentions scoping, MVP, smallest version, cutting scope, or needs to figure out what to keep, what to cut, and what to defer.
Generate a developer handoff spec from a Figma file or design. Use whenever the user mentions handoff, dev handoff, figma handoff, design to code, or needs a structured spec for engineers to implement a design.
Design an icon system including stroke, fill, sizes, grid, and consistency rules. Use whenever the user mentions icon system, iconography, icon set, icon library, icon design, or needs icons that feel like they belong together.
Frame a product, feature, or user need using Jobs-to-be-Done methodology. Use whenever the user mentions JTBD, jobs to be done, user job, job statement, or wants to understand what users are really hiring a product to do.
Write landing page copy including hero, sections, social proof, and ctas. Use whenever the user mentions landing page, landing copy, homepage copy, marketing site, hero section, or needs copy for a page designed to convert.
Plan a product or feature launch including audience, narrative, channels, and timing. Use whenever the user mentions launch, launch plan, product launch, feature launch, announcement, rollout plan, or needs to coordinate going public with a product or feature.
Build a messaging architecture including hero message, pillars, proof points, and audience variants. Use whenever the user mentions messaging architecture, messaging hierarchy, messaging framework, or needs to organize what to say across pages, audiences, and channels.
Design product metrics including north-star, primary, secondary, and guardrail metrics. Use whenever the user mentions metrics, north star metric, kpi, success metric, key results, or needs to figure out what to measure to know if something is working.
Write ui microcopy including button labels, empty states, error messages, tooltips, form labels, and onboarding strings. Use whenever the user mentions microcopy, ui strings, button text, error messages, empty states, tooltips, form labels, or any short interface text.
Define motion principles, easing curves, durations, and interaction behaviors for a design system or product. Use whenever the user mentions motion design, animation principles, easing, transition timing, micro-interactions, or wants to make a product feel intentional in how it moves.
Generate names for products, features, companies, or brands with rationale and availability checks. Use whenever the user needs a name, wants naming options, asks for product naming, company naming, feature naming, or wants help finding a name with the right meaning and that's actually available.
Write a positioning statement that defines who a product is for, what it does, and against what alternatives. Use whenever the user mentions positioning, positioning statement, market positioning, product positioning, or needs to articulate what their product is and who it's for.
Write a product requirements document (PRD) that captures problem, goal, scope, approach, and risk. Use whenever the user mentions PRD, product requirements, product doc, product brief, requirements doc, or needs to write a structured document about what to build and why.
Write release notes, what's new posts, and ship announcements that tell users what shipped in their terms. Use whenever the user mentions release notes, changelog, what's new, ship announcement, version notes, or needs to communicate what changed in a release.
Synthesize user interviews, surveys, support tickets, or other research into themes and recommendations. Use whenever the user shares interview transcripts, survey responses, support data, customer research, or asks for synthesis of qualitative input.
Define responsive design rules including breakpoints, fluid scales, and what changes per viewport. Use whenever the user mentions responsive design, breakpoints, mobile design, fluid typography, viewport sizing, or wants to design for multiple screen sizes.
Plan a product roadmap including themes, bets, and sequencing. Use whenever the user mentions roadmap, planning, quarterly planning, what to build next, sequencing features, or needs to organize work over a meaningful time horizon.
Write a technical or feature specification covering behavior, states, edge cases, and acceptance criteria. Use whenever the user mentions spec, feature spec, technical spec, behavior spec, or needs a document that an engineer can implement against.
Write taglines, slogans, and headlines that capture a product or brand. Use whenever the user needs a tagline, slogan, headline, hero line, one-liner, or any short piece of copy that has to do a lot of work.
Write a value proposition that connects what a product does to what a user gets. Use whenever the user mentions value prop, value proposition, customer value, benefit statement, or needs to articulate the value of their product in customer terms.