From 36699bc7b32a9607541e1b195258a1b1d5d0d6b6 Mon Sep 17 00:00:00 2001 From: anx4758 Date: Wed, 25 Feb 2026 16:43:10 +0800 Subject: [PATCH] chore: remove unrelated prompt draft files --- prompts/expand-animation-profiles.md | 120 ------------------------- prompts/expand-interaction-patterns.md | 120 ------------------------- 2 files changed, 240 deletions(-) delete mode 100644 prompts/expand-animation-profiles.md delete mode 100644 prompts/expand-interaction-patterns.md diff --git a/prompts/expand-animation-profiles.md b/prompts/expand-animation-profiles.md deleted file mode 100644 index 71aefc0..0000000 --- a/prompts/expand-animation-profiles.md +++ /dev/null @@ -1,120 +0,0 @@ -# Expand Animation Profiles — Gemini Prompt - -## Role - -You are a senior motion design engineer specializing in web UI animation systems. Your task is to expand an existing animation profile taxonomy with new categories and variants. - -## Context - -We have a StyleKit taxonomy that maps `motion_profile` enum values to concrete animation profiles. Each profile defines intent, timing, easing, states, and anti-patterns for a specific animation behavior. - -### Current Enum Values (5) - -``` -minimal, subtle, smooth, energetic, cinematic -``` - -### Current Profiles (12) - -```json -{ - "minimal-static": { "motion_profile": "minimal", ... }, - "minimal-functional": { "motion_profile": "minimal", ... }, - "subtle-fade": { "motion_profile": "subtle", ... }, - "subtle-slide": { "motion_profile": "subtle", ... }, - "smooth-morph": { "motion_profile": "smooth", ... }, - "smooth-flow": { "motion_profile": "smooth", ... }, - "smooth-reveal": { "motion_profile": "smooth", ... }, - "energetic-bounce": { "motion_profile": "energetic", ... }, - "energetic-stagger": { "motion_profile": "energetic", ... }, - "energetic-pulse": { "motion_profile": "energetic", ... }, - "cinematic-parallax": { "motion_profile": "cinematic", ... }, - "cinematic-sequence": { "motion_profile": "cinematic", ... } -} -``` - -### One Complete Example (follow this structure exactly) - -```json -{ - "smooth-morph": { - "motion_profile": "smooth", - "intent": "Facilitates fluid transitions between geometric states to maintain visual continuity during layout changes.", - "trigger": "user-interaction", - "states": ["default", "expanded", "collapsed", "hover"], - "duration_range_ms": [250, 450], - "easing": "cubic-bezier(0.4, 0, 0.2, 1)", - "reduced_motion_fallback": "instant-state-swap", - "suitable_site_types": ["saas", "ecommerce", "landing-page"], - "anti_patterns": ["Unexpected layout shifts during morphing", "Morphing without will-change optimization"] - } -} -``` - -### Available site_types - -``` -blog, saas, dashboard, docs, ecommerce, landing-page, portfolio, general -``` - -## Your Task - -### Part 1: New Enum Values - -Propose 2-3 new `motion_profile` enum values that fill gaps in the current taxonomy. Consider: -- **playful**: bouncy, whimsical, toy-like motion for kids/casual apps -- **functional**: purely utilitarian micro-interactions (loading spinners, progress bars, skeleton screens) -- **ambient**: slow, atmospheric, background-only motion (floating particles, gradient shifts) - -For each new enum value, provide: -1. A short definition (1 sentence) -2. 2-3 concrete profiles following the exact schema below - -### Part 2: New Variants for Existing Enums - -Add 1-2 new profiles for each existing enum value that cover gaps: -- `minimal`: consider a "minimal-skeleton" for loading states -- `subtle`: consider a "subtle-scale" for hover micro-feedback -- `smooth`: consider a "smooth-spring" using spring physics -- `energetic`: consider an "energetic-flip" for card interactions -- `cinematic`: consider a "cinematic-morph" for page transitions - -## Output Format - -Return a single JSON object. **No markdown fences, no commentary — pure JSON only.** - -``` -{ - "new_enum_values": [ - { - "value": "playful", - "definition": "..." - } - ], - "new_profiles": { - "playful-wobble": { - "motion_profile": "playful", - "intent": "...", - "trigger": "user-interaction | viewport-enter | scroll-progress | page-load | attention-needed | state-change-only", - "states": ["..."], - "duration_range_ms": [min, max], - "easing": "css easing string or cubic-bezier(...)", - "reduced_motion_fallback": "none | instant-state-swap | instant-visible | fade-only | static-position | static-layers | scale-only | color-highlight-only", - "suitable_site_types": ["..."], - "anti_patterns": ["...", "..."] - } - } -} -``` - -## Quality Constraints - -1. **intent** must be a single sentence starting with a verb, describing the UX purpose (not the CSS implementation) -2. **duration_range_ms** must be realistic: [min, max] where min >= 0 and max <= 2000 -3. **easing** must be a valid CSS easing value -4. **anti_patterns** must be 2-3 specific, actionable warnings (not vague "don't overuse") -5. **reduced_motion_fallback** must be one of the allowed values listed above -6. **suitable_site_types** must only use values from the available list -7. Each profile name must follow the pattern `{enum-value}-{variant}` (kebab-case) -8. No two profiles should have identical intent — each must serve a distinct UX purpose -9. Total new profiles: aim for 10-15 across all categories diff --git a/prompts/expand-interaction-patterns.md b/prompts/expand-interaction-patterns.md deleted file mode 100644 index 9913708..0000000 --- a/prompts/expand-interaction-patterns.md +++ /dev/null @@ -1,120 +0,0 @@ -# Expand Interaction Patterns — Gemini Prompt - -## Role - -You are a senior UX engineer specializing in interaction design systems and accessibility. Your task is to expand an existing interaction pattern taxonomy with new categories and richer state coverage. - -## Context - -We have a StyleKit taxonomy that maps `interaction_pattern` enum values to structured pattern definitions. Each pattern defines a primary goal, required components, state coverage requirements, accessibility constraints, and anti-patterns. - -### Current Enum Values (6) - -``` -content-reading, conversion-focused, data-dense-feedback, showcase-narrative, docs-navigation, assistant-guided -``` - -### Current Patterns (6, 1:1 with enum) - -Each pattern key matches its enum value exactly. - -### One Complete Example (follow this structure exactly) - -```json -{ - "data-dense-feedback": { - "primary_goal": "Supports efficient data parsing and manipulation through immediate, granular interaction feedback.", - "suitable_site_types": ["dashboard", "saas"], - "required_components": ["data-table", "kpi-card", "filter-bar", "chart", "alert-strip"], - "state_coverage_requirements": { - "table-row": ["default", "hover", "selected", "loading", "error", "empty"], - "kpi-card": ["loading", "loaded", "error", "trend-up", "trend-down"], - "filter": ["default", "active", "applied-count", "clearing"] - }, - "accessibility_constraints": [ - "Tables must use semantic headers with appropriate scope attributes", - "Provide accessible data table fallbacks for complex charts", - "Announce critical status updates via aria-live regions", - "Ensure full keyboard operability for all filtering and sorting controls" - ], - "anti_patterns": [ - "Auto-refreshing data without user consent or notification", - "Hiding essential data behind tooltips without persistent alternatives", - "Relying solely on color to communicate system status" - ] - } -} -``` - -### Available site_types - -``` -blog, saas, dashboard, docs, ecommerce, landing-page, portfolio, general -``` - -## Your Task - -### Part 1: New Enum Values - -Propose 3-4 new `interaction_pattern` enum values that fill real gaps. Consider these candidates: - -- **form-wizard**: Multi-step form flows with validation, progress tracking, and error recovery -- **social-feed**: Infinite scroll, reactions, comments, real-time updates -- **media-player**: Video/audio playback controls, playlists, progress scrubbing -- **collaborative-editing**: Real-time cursors, presence indicators, conflict resolution -- **search-explore**: Faceted search, filters, sort, saved searches, result previews -- **notification-center**: Toast stacks, notification lists, read/unread, action buttons -- **onboarding-tour**: Step-by-step product tours, feature highlights, skip/resume - -Pick the 3-4 most universally useful ones. - -### Part 2: Enrich Existing Patterns - -For each of the 6 existing patterns, suggest 1-2 additional `state_coverage_requirements` entries (new component + states) that are currently missing but would improve real-world coverage. - -## Output Format - -Return a single JSON object. **No markdown fences, no commentary — pure JSON only.** - -``` -{ - "new_enum_values": [ - { - "value": "form-wizard", - "definition": "..." - } - ], - "new_patterns": { - "form-wizard": { - "primary_goal": "...", - "suitable_site_types": ["..."], - "required_components": ["..."], - "state_coverage_requirements": { - "component-name": ["state1", "state2", "..."] - }, - "accessibility_constraints": ["...", "...", "...", "..."], - "anti_patterns": ["...", "...", "..."] - } - }, - "existing_pattern_additions": { - "content-reading": { - "new_state_coverage": { - "component-name": ["state1", "state2"] - } - } - } -} -``` - -## Quality Constraints - -1. **primary_goal** must be a single sentence starting with a verb, describing the UX purpose -2. **required_components** should be 3-5 concrete UI components (kebab-case) -3. **state_coverage_requirements** must have 2-4 component entries, each with 3-6 realistic states -4. **accessibility_constraints** must be exactly 4 items, each a specific WCAG-aligned requirement (not vague) -5. **anti_patterns** must be exactly 3 items, each a specific, actionable warning -6. **suitable_site_types** must only use values from the available list -7. Pattern keys must be kebab-case and match their enum value exactly -8. No two patterns should overlap significantly in primary_goal -9. States should follow real UI lifecycle: include loading, error, empty where applicable -10. Each new `state_coverage_requirements` entry in Part 2 must target a component NOT already covered in the existing pattern