dragoon0x
- 690 skills
- 0 followers
- 12 hours ago last updated
- ▌ Feedback Synthesis 2 · dragoon0xTurn raw customer feedback from multiple sources into clear product insights and priorities. Covers feedback collection, pattern recognition, and separating signal from noise. Use when feedback feels overwhelming, contradictory, or when the team can't agree on what users actually want.
- ▌ Roadmap Planning 2 · dragoon0xBuild a product roadmap that balances customer needs, business goals, and technical reality. A roadmap is a strategy communicated through planned work, not a feature list with dates. Use when building quarterly or annual plans, when stakeholders pull in different directions, or when the current roadmap feels reactive.
- ▌ Prioritization Frameworks 2 · dragoon0xApply structured prioritization methods to decide what to build and what to cut. Covers RICE, ICE, MoSCoW, and knowing when each framework fits. Use when the backlog is overwhelming, stakeholders disagree on priorities, or when everything feels like P0.
- ▌ Frontcraft · dragoon0x bundleThe definitive frontend craft specification. 324 rules across 20 categories with measurable thresholds, covering motion, typography, accessibility, color, performance, layout, forms, and interaction design. Every rule has a name, priority level, and production code. Install with: npx skills add Dragoon0x/frontcraft
- ▌ Useslidekit · dragoon0x bundleComprehensive presentation design skill for Claude Code. Projection-aware design, audience-adaptive layouts, narrative architecture, perceptual data visualization, anti-AI-slop detection, rehearsal intelligence, and multi-format export. Complements Anthropic's built-in PPTX skill.
- ▌ Useforgekit · dragoon0x bundleGenerate optimal Claude Code configuration for any project. Creates CLAUDE.md, settings.json, skills, hooks, agents, and commands tailored to your stack. Run /forge to start.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Interface Ship · dragoon0x bundleRun the final evidence-based release gate and issue a SHIP, SHIP WITH KNOWN LIMITATIONS, or DO NOT SHIP verdict. Use before releasing interface work, when deciding whether quality and coverage are sufficient, or when remaining risk must be made explicit.
- ▌ Interface Craft · dragoon0x bundleRefine visual hierarchy, typography, spacing, density, color, material, and optical alignment. Use when an interface looks unresolved, cramped, flat, or busy, or when tightening visual quality before release.
- ▌ Interface Critic · dragoon0x bundleAdversarially review a complete interface across product, architecture, craft, interaction, adaptation, state, accessibility, and engineering, and diagnose root causes. Use when requesting a hard critique, a pre-release quality pass, or an explanation for why an interface feels wrong.
- ▌ Interface Review · dragoon0xRun a unified evidence-driven review of an interface, change, flow, or product surface by coordinating the 10X Interface disciplines and producing one consolidated decision.
- ▌ Adaptive Interface · dragoon0x bundleAdapt one interface across space, input, content pressure, text scaling, orientation, localization, and reduced motion. Use when designing or reviewing responsive behavior, touch and keyboard support, or layouts that break under real content.
- ▌ Interaction Engine · dragoon0x bundleDesign interaction contracts, feedback, motion, timing, direct manipulation, interruption, cancellation, and recovery. Use when specifying or reviewing how an interface responds to input, choosing whether and how to animate, or fixing behavior that feels unresponsive or theatrical.
- ▌ Interface Forensics · dragoon0x bundleReconstruct the design logic and grammar behind an existing interface from live UI, screenshots, source, or DOM. Use when analyzing why an interface works, rebuilding a reference, or extracting a system from an existing product.
- ▌ Interface Architecture · dragoon0x bundleModel an interface's task hierarchy, surfaces, navigation, flows, component boundaries, and state ownership. Use when structuring a new surface, reorganizing navigation, deciding where a task belongs, or diagnosing whether a problem is structural rather than visual.
- ▌ Interface Intelligence · dragoon0x bundleUnderstand the real interface problem before deciding on a solution, separating request from intent and evidence from assumption. Use for ambiguous interface requests, major redesigns, unfamiliar products, consequential interaction decisions, or when the proposed UI may not be the real solution.
- ▌
- ▌ Interface Lab · dragoon0x bundleTurn a design uncertainty into a controlled comparison of materially different directions that produces a decision. Use when a consequential interface choice is genuinely unresolved and prototyping would reduce the risk of committing.
- ▌
- ▌ Second Opinion · dragoon0x bundleBuild a structured packet to paste into another model or share with a colleague. Includes branch, head, recent commits, and optional file contents (max 5 files, 200 lines each). dragoon does NOT call other models for you - this is the prompt you copy. Use when stuck on an approach, considering tradeoffs, or wanting external review. Run as `node ~/.claude/skills/dragoon/skills/second-opinion/scripts/second-opinion.js "<topic>" [--file path]`.
- ▌ QA · dragoon0x bundleScaffold a playwright e2e test suite with 4 smoke tests (page loads, h1 visible, no console errors, no broken images). Detects the project's stack to set the right baseURL. Writes a runner script that installs browsers on first run. Dragoon does NOT install browsers itself - the runner script does. Defaults to dry-run; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/qa/scripts/qa.js`.
- ▌ Map · dragoon0x bundleArchitecture overview of the codebase. Reports total file/line/byte counts, top hot files (most imported), largest files by line count, orphan files (imported by nobody), and most-used external dependencies. Pure regex on import statements, no AST. Use to understand a new codebase, find dead code, or audit dependency surface. Run as `node ~/.claude/skills/dragoon/skills/map/scripts/map.js [root]`.
- ▌ Diff · dragoon0x bundleScaffold a playwright visual regression test suite that takes per-route full-page screenshots and compares against committed baselines. Pixel diffing is done by playwright's toHaveScreenshot, not by dragoon. Use when the user wants visual regression coverage. Pass --routes to set the routes to capture. Defaults to dry-run; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/diff/scripts/diff.js`.
- ▌ Docs · dragoon0x bundleDetect drift between markdown docs (README, docs/) and the actual codebase. Catches references to npm scripts that don't exist, scoped dependencies not in package.json, file paths in backticks that don't resolve on disk, and undocumented npm scripts. Use to audit documentation hygiene before a release or after a major refactor. Exits non-zero on findings. Run as `node ~/.claude/skills/dragoon/skills/docs/scripts/docs.js`.
- ▌ Land · dragoon0x bundlePost-merge sanity check. Verifies branch, HEAD sha, that local matches remote, and that the working tree is clean. dragoon does NOT trigger deploys (platform-specific creds out of scope). Use right before a deploy step in CI or before manual prod pushes. Exits non-zero if any check fails. Run as `node ~/.claude/skills/dragoon/skills/land/scripts/land.js`.
- ▌ Perf · dragoon0x bundleStatic performance hints (large images, missing img dimensions, no loading=lazy, sync script tags) plus optional Lighthouse JSON report ingestion that surfaces failing audits ranked by potential ms savings. Use when the user wants to audit web performance or process a Lighthouse report. Dragoon does NOT run Lighthouse itself - generate the report with `npx lighthouse <url> --output json --output-path lh.json` and pass --lighthouse. Run as `node ~/.claude/skills/dragoon/skills/perf/scripts/perf.js [--lighthouse path]`.
- ▌ Scan · dragoon0x bundleFingerprint a codebase's design DNA and write dragoon.json. Use when the user wants to set up dragoon in a project, or asks to "scan", "fingerprint", or "analyze" the design system. Always run this first before /critique, /slop, or /review on a project that hasn't been scanned yet. Outputs detected stack, palette, type scale, spacing grid, motion curves, and accessibility metrics. Run as `node ~/.claude/skills/dragoon/skills/scan/scripts/scan.js [root]`.
- ▌ Ship · dragoon0x bundlePre-PR check orchestrator. Runs /critique with a threshold (default 80), /slop --severity high, gathers git context (branch, changed files), and optionally opens a PR via the gh CLI. Use before opening any PR. Exits non-zero if any check fails. Run as `node ~/.claude/skills/dragoon/skills/ship/scripts/ship.js`.
- ▌ Sync · dragoon0x bundleExport design tokens to figma.tokens.json (tokens-studio-compatible format) so they can be imported into the Figma "tokens studio" plugin. dragoon does NOT live-sync with Figma - that requires OAuth and the Figma REST API. Use for one-way export from code to Figma, manually re-run after major token changes. Run as `node ~/.claude/skills/dragoon/skills/sync/scripts/sync.js`.
- ▌ Brief · dragoon0x bundleGenerate a structured product brief markdown from a one-line idea, pre-filled with codebase facts (stack, type system, palette, components count) from dragoon.json. Use when the user is starting a new feature, project, or initiative and wants to think through it before coding. Output goes to .dragoon/plans/brief-{slug}-{date}.md. Defaults to dry-run preview; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/brief/scripts/brief.js "<idea>"`.
- ▌ Color · dragoon0x bundleGenerate a color palette token file (CSS variables, tailwind config, or JS module) from the palette detected by /scan. Uses inferred role names (foreground, background, accent, danger, etc.) where possible, numeric fallback otherwise. Use when the user wants to formalize color tokens, extract a palette from existing code, or scaffold a color system. Defaults to dry-run preview; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/color/scripts/color.js`.
- ▌ Forge · dragoon0x bundleGenerate a new dragoon skill scaffold (SKILL.md, scripts/<name>.js, test/<name>.test.js, README.md) into .dragoon/forge/<name>/ for review. dragoon does NOT auto-install forged skills. After review, copy into ~/.dragoon/skills/ and add an entry to bin/dragoon's COMMANDS map. Use to extend the pack with custom skills. Run as `node ~/.claude/skills/dragoon/skills/forge/scripts/forge.js <name>`.
- ▌ Retro · dragoon0x bundleWeekly retro markdown template with git stats pre-loaded (commit count, files changed, +/- lines, contributors). Forces a what-shipped, what-slipped, what-we-learned, what-to-do-less-of, what-to-do-more-of, and quality-trends section. Use end-of-week or end-of-sprint. Output goes to .dragoon/retros/retro-{date}.md. Run as `node ~/.claude/skills/dragoon/skills/retro/scripts/retro.js`.
- ▌ Canary · dragoon0x bundleGenerate a curl-based canary watcher script for a deployed URL. Validates URL is http/https, status code is 100-599, interval is 5-86400 seconds. The generated script supports one-shot (default) and --watch (continuous loop) modes. Wire into cron or a CI scheduled job. Run as `node ~/.claude/skills/dragoon/skills/canary/scripts/canary.js <url>`.
- ▌ Freeze · dragoon0x bundleDeclare directories that are off-limits to edits. Stores the list in .dragoon/freeze.json. Optionally installs a git pre-commit hook that fails the commit if any frozen path is touched. Subcommands list/add/remove/hook/check. Use when isolating a refactor, locking legacy directories, or onboarding a contributor with limited scope. Run as `node ~/.claude/skills/dragoon/skills/freeze/scripts/freeze.js <subcommand>`.
- ▌ Memory · dragoon0x bundleSmall persistent key-value store at .dragoon/memory.json for project-specific facts dragoon (and the user) want to remember across sessions. Subcommands list/get/set/remove/clear. Keys are lowercase ascii (./_/-, max 64). Values are plain text (max 8KB, max 256 keys). Use to remember conventions, decisions, gotchas. Run as `node ~/.claude/skills/dragoon/skills/memory/scripts/memory.js <subcommand>`.
- ▌ Motion · dragoon0x bundleGenerate motion tokens (durations + easings) using values detected by /scan, falling back to material-quality defaults when nothing was detected. Produces fast/normal/slow durations and standard/enter/exit easings. Use when the user wants to formalize motion tokens or scaffold a motion system. Defaults to dry-run; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/motion/scripts/motion.js`.
- ▌ Review · dragoon0x bundleUnified code + design review in a single pass. Runs slop detection, design critique, and engineering signals (TODO/FIXME, any types, large files) at once. On any UI files in scope (jsx/tsx/vue/svelte/css/scss/html), /critique and /slop run automatically - engineering review and design review in one read. Use when the user wants to review a PR, diff, file, or folder. Supports `--diff` to review only files changed in git working tree. Run as `node ~/.claude/skills/dragoon/skills/review/scripts/review.js [path]`.
- ▌ Careful · dragoon0x bundleWrite a checklist of destructive commands the user wants to think twice about (rm -rf, force push, hard reset, db drop, etc.) to .dragoon/CAREFUL.md. dragoon does NOT block commands at runtime - this is a discipline tool, a list the agent reads before risky operations. Use to set explicit guardrails for an AI agent or new contributor. Run as `node ~/.claude/skills/dragoon/skills/careful/scripts/careful.js`.
- ▌ Handoff · dragoon0x bundleGenerate a markdown dev handoff doc with everything the next engineer needs - stack, design tokens, palette, type scale, spacing grid, motion, existing components, and conventions - all pulled from dragoon.json. Use when handing off work to another engineer or documenting the codebase for new contributors. Output goes to .dragoon/handoff/handoff-{slug}.md. Defaults to dry-run; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/handoff/scripts/handoff.js [feature]`.
- ▌ Install · dragoon0xOne-line install for dragoon. Detects supported coding agents (claude-code, codex, cursor, opencode, factory, kiro) and installs the skill pack into each. Multi-host on day one. Use when the user wants to install dragoon, mentions setup, or asks how to add dragoon to their environment. The install script is `./setup` at the repo root.
- ▌ Autoplan · dragoon0x bundleRun /brief, /plan-eng, and /plan-design in one shot to bootstrap a complete sprint plan. All three documents land in .dragoon/plans/ pre-filled with codebase facts. Use when the user wants to spin up a full plan quickly. Defaults to dry-run; pass --apply to write all three files. Run as `node ~/.claude/skills/dragoon/skills/autoplan/scripts/autoplan.js "<idea>"`.
- ▌ Plan Eng · dragoon0x bundleGenerate a structured engineering plan markdown for an idea, pre-filled with codebase facts (stack, dependencies, current critique score) from dragoon.json. Forces a test matrix, edge cases, migration plan, and review checklist. Use after /brief or before any non-trivial feature implementation. Output goes to .dragoon/plans/plan-eng-{slug}-{date}.md. Defaults to dry-run; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/plan-eng/scripts/plan-eng.js "<idea>"`.
- ▌ Research · dragoon0x bundleGenerate a structured research template for a topic. Use before deciding to build something - forces specific decision-driven research with sources, expert disagreement, and a steelman. dragoon does NOT fetch the web. Output goes to .dragoon/research/research-{slug}-{date}.md. Run as `node ~/.claude/skills/dragoon/skills/research/scripts/research.js "<topic>"`.
- ▌ Tailwind · dragoon0x bundleGenerate one consolidated tailwind.config.js combining colors, spacing, fontFamily, fontSize, borderRadius, transitionDuration, and transitionTimingFunction from the manifest. Single file instead of four separate token cjs files. Use when setting up tailwind for the first time or refreshing the config after major token changes. Run as `node ~/.claude/skills/dragoon/skills/tailwind/scripts/tailwind.js`.
- ▌ Component · dragoon0x bundleGenerate a UI component scaffold in the codebase's actual style. Reads dragoon.json to match framework (react/vue/svelte), styling layer (tailwind/css-modules/plain), language (typescript/javascript), and design tokens (radius, spacing, palette). Defaults to dry-run preview; pass --apply to write files. Use when the user wants to create a new component, scaffold UI primitives, or add a component to their codebase. Run as `node ~/.claude/skills/dragoon/skills/component/scripts/component.js <Name>`.
- ▌ Inventory · dragoon0x bundleCatalog of components (PascalCase files), hooks (useFoo), pages/routes, story files, and token files in the codebase. Use to understand what already exists before adding more, or to audit a design system. Heuristic-based, no AST. Run as `node ~/.claude/skills/dragoon/skills/inventory/scripts/inventory.js [root]`.
- ▌ Storybook · dragoon0x bundleScaffold storybook config (.storybook/main.ts, preview.ts) plus auto-generated *.stories.tsx files for every PascalCase component in the codebase that has a matching named export. Caps at 50 components per run. dragoon does NOT install storybook - run `npx storybook init` after. Use to bootstrap stories quickly across an existing component library. Run as `node ~/.claude/skills/dragoon/skills/storybook/scripts/storybook.js`.
- ▌
- ▌ Investigate · dragoon0x bundleStructured root-cause investigation template. Encodes the rule "no patches until you can reproduce, predict, and explain the bug." Forces hypothesis-test pairs, evidence collection, and a prevention plan. Use when the user reports a bug or asks to fix something they don't fully understand yet. Run as `node ~/.claude/skills/dragoon/skills/investigate/scripts/investigate.js "<symptom>"`.
- ▌ Plan Design · dragoon0x bundleGenerate a structured design plan markdown that respects the constraints in dragoon.json (spacing grid, type ratio, palette, font families). Forces a screens-and-flows breakdown, accessibility plan, responsive plan, and design review checklist gated on /critique and /slop. Use after /brief or before any UI work. Output goes to .dragoon/plans/plan-design-{slug}-{date}.md. Defaults to dry-run; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/plan-design/scripts/plan-design.js "<idea>"`.
- ▌ Jtbd Framing · dragoon0xFrame 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.
- ▌ Landing Copy · dragoon0xWrite 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.
- ▌ Spec Writing · dragoon0xWrite 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.
- ▌ Design Review · dragoon0xRun 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.
- ▌ Metric Design · dragoon0xDesign 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.
- ▌ Ab Test Design · dragoon0xDesign 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.
- ▌ Component Spec · dragoon0xWrite 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.
- ▌ Email Sequence · dragoon0xWrite 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.
- ▌ Data Viz Design · dragoon0xDesign 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.
- ▌ Feature Scoping · dragoon0xScope 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.
- ▌ Tagline Writing · dragoon0xWrite 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.
- ▌ Content Calendar · dragoon0xPlan 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.
- ▌ Motion Direction · dragoon0xDefine 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.
- ▌ Responsive Rules · dragoon0xDefine 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.
- ▌ Dark Mode Pairing · dragoon0xDesign 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.
- ▌ Microcopy Writing · dragoon0xWrite 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.
- ▌ Naming Generation · dragoon0xGenerate 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.
- ▌ Release Narrative · dragoon0xWrite 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.
- ▌ Figma Handoff Spec · dragoon0xGenerate 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.
- ▌ Iconography System · dragoon0xDesign 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.
- ▌ Research Synthesis · dragoon0xSynthesize 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.
- ▌ Value Prop Writing · dragoon0xWrite 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.
- ▌ Accessibility Audit · dragoon0xAudit 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.
- ▌ Design System Audit · dragoon0xAudit 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.
- ▌ Brand Identity Audit · dragoon0xAudit 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.
- ▌ Competitive Analysis · dragoon0xAnalyze 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.
- ▌ Positioning Statement · dragoon0xWrite 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.
- ▌ Brand Voice Extraction · dragoon0xExtract 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.
- ▌ Messaging Architecture · dragoon0xBuild 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.
- ▌ Taste Gap · dragoon0xNavigate the gap between what you can see and what you can make. The Ira Glass gap. Use when a designer is frustrated by the distance between their taste and their output, when mentoring someone through a creative plateau, or when someone is considering quitting because their work doesn't match their vision.
- ▌ Absence Audit · dragoon0xNotice what's deliberately missing from a design. Restraint is a taste signal. Use when studying minimalist products, evaluating design maturity, or understanding the power of removal.
- ▌ Field Notes · dragoon0xStructured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.
- ▌ Design Ranking · dragoon0xRank multiple design solutions and explain why. Separate personal preference from quality judgment. Use when comparing design options, evaluating competing approaches, or making design decisions with clear reasoning.
- ▌ Visual Audit · dragoon0xThe 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.
- ▌ Type Systems · dragoon0xScale, weight, line height, and tracking as a coherent system. Use when building type scales, auditing typography consistency, or diagnosing why text feels off.
- ▌ Taste Vs Trends · dragoon0xTell the difference between design decisions that age well and decisions that follow the crowd. Use when evaluating whether a design choice is principled or fashionable, or when a client asks to 'make it look modern.'
- ▌ Decision Tracing · dragoon0xReverse-engineer why a design decision was made. Move from observation to inference. Use when studying products you admire, learning from competitors, or building analytical design thinking.
- ▌ Flow Patterns · dragoon0xTask sequences, progressive disclosure, and the pacing of an experience over time. Use when designing multi-step flows, evaluating onboarding, or diagnosing why users get lost.
- ▌ Motion Design · dragoon0xAnimation as communication. Feedback, orientation, emphasis, delight. If motion doesn't serve one of these four purposes, it shouldn't exist. Use when evaluating animation quality, designing transitions, or deciding whether motion adds or subtracts.
- ▌ Type As Signal · dragoon0xRead a designer's taste through their typography decisions alone. Type is the fastest taste signal in any design. Use when evaluating design maturity, assessing portfolio quality, or understanding what typography reveals about design thinking.
- ▌ Type Selection · dragoon0xChoose typefaces based on voice and context, not trends. Use when selecting fonts for a project, evaluating type choices, or understanding what a typeface communicates before anyone reads a word.
- ▌ Self Assessment · dragoon0xDiagnose your taste gaps across six skill areas. Know what to practice. Use when starting a taste development program, checking progress, or identifying specific areas to improve.
- ▌ Taste As Strategy · dragoon0xUse taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.
- ▌ Timing Feedback · dragoon0xResponse timing, acknowledgment, and making the interface feel alive. Every action deserves a response at the right speed. Use when designing interactions, evaluating responsiveness, or diagnosing why a product feels sluggish or dead.
- ▌ Version Archaeology · dragoon0xStudy how products evolve over time using archived versions. The decisions that survive redesigns are the taste decisions. Use when understanding what's essential vs. cosmetic in a design, or learning from product evolution.