layout-morph
Skill0 starsChanged 7 days agoMITView on GitHub
Shared-element morphs in Vue 3 with Quasar v-morph. Use when a card, row, or chip expands into its detail view in the same screen. GSAP Flip is only the fallback when the two states are not in one view. No React, no Tailwind.
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/heyeddi-always-on.mdcCursor rule
- .cursor/rules/skill-authoring.mdcCursor rule
- aura-design-tokensSkill
- backend-type-bridgerSkill
- cli-interface-designSkill
- composable-patternsSkill
- dart-type-bridgerSkill
- design-handoff-flutterSkill
- design-system-generalizerSkill
- engineering-excellenceSkill
- fancy-ui-craftSkill
- flutter-engineeringSkill
- flutter-patternsSkill
- heyeddi-ci-configSkill
- heyeddi-ci-failsSkill
- heyeddi-ci-guideSkill
- heyeddi-ci-runnersSkill
- heyeddi-designSkill
- heyeddi-handoffSkill
- heyeddi-intakeSkill
- heyeddi-local-firstSkill
- heyeddi-orchestratorSkill
- heyeddi-productSkill
- heyeddi-pr-respondSkill
- heyeddi-pr-reviewSkill
- heyeddi-setupSkill
- heyeddiSkill
- motion-physicsSkill
- no-duplicate-uiSkill
- pre-merge-gateSkill
- primevue-auraSkill
- primevue-openprops-architectSkill
- project-engineeringSkill
- quasar-foundationSkill
- taste-penpotSkill
- ux-flow-auditorSkill
- verify-buildSkill
- visual-auditorSkill
- visual-verificationSkill
- vue-design-systemSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Do not morph every route change.
- Very specific: line 30
No extra package. Quasar already ships v-morph.
- Very specific: line 91
When prefers-reduced-motion: reduce matches, swap the group without the morph.
- Very specific: line 95
After the morph exists, @fancy-ui-craft only if this surface also needs depth.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Layout morph
A small surface grows into its detail without a hard cut. Quasar v-morph owns that move. Springs for hover, press, and dialog entry stay in @motion-physics.
When to use
- A card, list row, or chip and its expanded panel are both in the same view.
- The user asked for a shared-element or layout transition.
Do not morph every route change. Do not morph a data table into itself.
Setup
Morph is registered with Quasar in the bootstrap owned by @primevue-aura:
import { Quasar, Dialog, Notify, Morph } from 'quasar';
app.use(Quasar, { plugins: { Dialog, Notify, Morph } });No extra package. Quasar already ships v-morph.
Pattern
Both states share one group name. Colors come from @aura-design-tokens.
<script setup>
import { ref } from 'vue';
const morphGroup = ref('card');
function toggleView() {
morphGroup.value = morphGroup.value === 'card' ? 'expanded' : 'card';
}
</script>
<template>
<div>
<div
v-morph:card:step-group="morphGroup"
class="compact-card"
@click="toggleView"
>
<div class="card-title">Performance metrics</div>
</div>
<div v-morph:expanded:step-group="morphGroup" class="expanded-panel">
<h3>Performance metrics</h3>
<button type="button" @click="toggleView">Close</button>
</div>
</div>
</template>
<style scoped>
.compact-card,
.expanded-panel {
background: var(--app-surface-card);
border: 1px solid var(--app-border);
color: var(--app-text-main);
}
.compact-card {
width: 280px;
padding: 16px;
border-radius: 12px;
cursor: pointer;
}
.expanded-panel {
width: min(600px, 100%);
padding: 24px;
border-radius: 16px;
}
</style>GSAP Flip
Use gsap Flip only when the compact state and the expanded state cannot live in the same component, such as a list on one route and a detail page on another. Install gsap only in that case. Prefer a route transition or @motion-physics modalEnter when a morph would be decorative.
Reduced motion
When prefers-reduced-motion: reduce matches, swap the group without the morph. Show the expanded panel immediately.
Next
After the morph exists, @fancy-ui-craft only if this surface also needs depth. Otherwise @visual-verification.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

