{productName}
+{tagline}
+{price}
+ Shop Now
+ {tagline}
+Failed to load data. {error.message}
+ +
+```
+
+**Reduce JavaScript Bundle**:
+- Code splitting (route-based, component-based)
+- Tree shaking (remove unused code)
+- Remove unused dependencies
+- Lazy load non-critical code
+- Use dynamic imports for large components
+
+```javascript
+// Lazy load heavy component
+const HeavyChart = lazy(() => import('./HeavyChart'));
+```
+
+**Optimize CSS**:
+- Remove unused CSS
+- Critical CSS inline, rest async
+- Minimize CSS files
+- Use CSS containment for independent regions
+
+**Optimize Fonts**:
+- Use `font-display: swap` or `optional`
+- Subset fonts (only characters you need)
+- Preload critical fonts
+- Use system fonts when appropriate
+- Limit font weights loaded
+
+```css
+@font-face {
+ font-family: 'CustomFont';
+ src: url('/fonts/custom.woff2') format('woff2');
+ font-display: swap; /* Show fallback immediately */
+ unicode-range: U+0020-007F; /* Basic Latin only */
+}
+```
+
+**Optimize Loading Strategy**:
+- Critical resources first (async/defer non-critical)
+- Preload critical assets
+- Prefetch likely next pages
+- Service worker for offline/caching
+- HTTP/2 or HTTP/3 for multiplexing
+
+### Rendering Performance
+
+**Avoid Layout Thrashing**:
+```javascript
+// ❌ Bad: Alternating reads and writes (causes reflows)
+elements.forEach(el => {
+ const height = el.offsetHeight; // Read (forces layout)
+ el.style.height = height * 2; // Write
+});
+
+// ✅ Good: Batch reads, then batch writes
+const heights = elements.map(el => el.offsetHeight); // All reads
+elements.forEach((el, i) => {
+ el.style.height = heights[i] * 2; // All writes
+});
+```
+
+**Optimize Rendering**:
+- Use CSS `contain` property for independent regions
+- Minimize DOM depth (flatter is faster)
+- Reduce DOM size (fewer elements)
+- Use `content-visibility: auto` for long lists
+- Virtual scrolling for very long lists (react-window, react-virtualized)
+
+**Reduce Paint & Composite**:
+- Use `transform` and `opacity` for animations (GPU-accelerated)
+- Avoid animating layout properties (width, height, top, left)
+- Use `will-change` sparingly for known expensive operations
+- Minimize paint areas (smaller is faster)
+
+### Animation Performance
+
+**GPU Acceleration**:
+```css
+/* ✅ GPU-accelerated (fast) */
+.animated {
+ transform: translateX(100px);
+ opacity: 0.5;
+}
+
+/* ❌ CPU-bound (slow) */
+.animated {
+ left: 100px;
+ width: 300px;
+}
+```
+
+**Smooth 60fps**:
+- Target 16ms per frame (60fps)
+- Use `requestAnimationFrame` for JS animations
+- Debounce/throttle scroll handlers
+- Use CSS animations when possible
+- Avoid long-running JavaScript during animations
+
+**Intersection Observer**:
+```javascript
+// Efficiently detect when elements enter viewport
+const observer = new IntersectionObserver((entries) => {
+ entries.forEach(entry => {
+ if (entry.isIntersecting) {
+ // Element is visible, lazy load or animate
+ }
+ });
+});
+```
+
+### React/Framework Optimization
+
+**React-specific**:
+- Use `memo()` for expensive components
+- `useMemo()` and `useCallback()` for expensive computations
+- Virtualize long lists
+- Code split routes
+- Avoid inline function creation in render
+- Use React DevTools Profiler
+
+**Framework-agnostic**:
+- Minimize re-renders
+- Debounce expensive operations
+- Memoize computed values
+- Lazy load routes and components
+
+### Network Optimization
+
+**Reduce Requests**:
+- Combine small files
+- Use SVG sprites for icons
+- Inline small critical assets
+- Remove unused third-party scripts
+
+**Optimize APIs**:
+- Use pagination (don't load everything)
+- GraphQL to request only needed fields
+- Response compression (gzip, brotli)
+- HTTP caching headers
+- CDN for static assets
+
+**Optimize for Slow Connections**:
+- Adaptive loading based on connection (navigator.connection)
+- Optimistic UI updates
+- Request prioritization
+- Progressive enhancement
+
+## Core Web Vitals Optimization
+
+### Largest Contentful Paint (LCP < 2.5s)
+- Optimize hero images
+- Inline critical CSS
+- Preload key resources
+- Use CDN
+- Server-side rendering
+
+### First Input Delay (FID < 100ms) / INP (< 200ms)
+- Break up long tasks
+- Defer non-critical JavaScript
+- Use web workers for heavy computation
+- Reduce JavaScript execution time
+
+### Cumulative Layout Shift (CLS < 0.1)
+- Set dimensions on images and videos
+- Don't inject content above existing content
+- Use `aspect-ratio` CSS property
+- Reserve space for ads/embeds
+- Avoid animations that cause layout shifts
+
+```css
+/* Reserve space for image */
+.image-container {
+ aspect-ratio: 16 / 9;
+}
+```
+
+## Performance Monitoring
+
+**Tools to use**:
+- Chrome DevTools (Lighthouse, Performance panel)
+- WebPageTest
+- Core Web Vitals (Chrome UX Report)
+- Bundle analyzers (webpack-bundle-analyzer)
+- Performance monitoring (Sentry, DataDog, New Relic)
+
+**Key metrics**:
+- LCP, FID/INP, CLS (Core Web Vitals)
+- Time to Interactive (TTI)
+- First Contentful Paint (FCP)
+- Total Blocking Time (TBT)
+- Bundle size
+- Request count
+
+**IMPORTANT**: Measure on real devices with real network conditions. Desktop Chrome with fast connection isn't representative.
+
+**NEVER**:
+- Optimize without measuring (premature optimization)
+- Sacrifice accessibility for performance
+- Break functionality while optimizing
+- Use `will-change` everywhere (creates new layers, uses memory)
+- Lazy load above-fold content
+- Optimize micro-optimizations while ignoring major issues (optimize the biggest bottleneck first)
+- Forget about mobile performance (often slower devices, slower connections)
+
+## Verify Improvements
+
+Test that optimizations worked:
+
+- **Before/after metrics**: Compare Lighthouse scores
+- **Real user monitoring**: Track improvements for real users
+- **Different devices**: Test on low-end Android, not just flagship iPhone
+- **Slow connections**: Throttle to 3G, test experience
+- **No regressions**: Ensure functionality still works
+- **User perception**: Does it *feel* faster?
+
+Remember: Performance is a feature. Fast experiences feel more responsive, more polished, more professional. Optimize systematically, measure ruthlessly, and prioritize user-perceived performance.
+
diff --git a/personas/_shared/community-skills/impeccable-overdrive/SKILL.md b/personas/_shared/community-skills/impeccable-overdrive/SKILL.md
new file mode 100644
index 0000000..b67bbed
--- /dev/null
+++ b/personas/_shared/community-skills/impeccable-overdrive/SKILL.md
@@ -0,0 +1,141 @@
+---
+name: overdrive
+description: "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary."
+argument-hint: "[target]"
+user-invocable: true
+---
+
+Start your response with:
+
+```
+──────────── ⚡ OVERDRIVE ─────────────
+》》》 Entering overdrive mode...
+```
+
+Push an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic.
+
+## MANDATORY PREPARATION
+
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first.
+
+**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate.
+
+### Propose Before Building
+
+This skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST:
+
+1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like.
+2. **{{ask_instruction}}** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity).
+3. Only proceed with the direction the user confirms.
+
+Skipping this step risks building something embarrassing that needs to be thrown away.
+
+### Iterate with Browser Automation
+
+Technically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between "technically works" and "looks extraordinary" is closed through visual iteration, not code alone.
+
+---
+
+## Assess What "Extraordinary" Means Here
+
+The right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say "wow, that's nice"?**
+
+### For visual/marketing surfaces
+Pages, hero sections, landing pages, portfolios — the "wow" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor.
+
+### For functional UI
+Tables, forms, dialogs, navigation — the "wow" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics.
+
+### For performance-critical UI
+The "wow" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates.
+
+### For data-heavy interfaces
+Charts and dashboards — the "wow" is in fluidity: GPU-accelerated rendering via Canvas/WebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally.
+
+**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around.
+
+## The Toolkit
+
+Organized by what you're trying to achieve, not by technology name.
+
+### Make transitions feel cinematic
+- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations.
+- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes
+- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver.
+
+### Tie animation to scroll position
+- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome/Edge/Safari; Firefox: flag only — always provide a static fallback)
+
+### Render beyond CSS
+- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express.
+- **WebGPU** (Chrome/Edge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2.
+- **Canvas 2D / OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas.
+- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable.
+
+### Make data feel alive
+- **Virtual scrolling** — render only visible rows for tables/lists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones.
+- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG/DOM. Libraries: deck.gl, regl-based custom renderers.
+- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts.
+
+### Animate complex properties
+- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate.
+- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography.
+
+### Push performance boundaries
+- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank.
+- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background.
+- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs.
+
+### Interact with the device
+- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start.
+- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission.
+
+**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary.
+
+## Implement with Discipline
+
+### Progressive enhancement is non-negotiable
+
+Every technique must degrade gracefully. The experience without the enhancement must still be good.
+
+```css
+@supports (animation-timeline: scroll()) {
+ .hero { animation-timeline: scroll(); }
+}
+```
+
+```javascript
+if ('gpu' in navigator) { /* WebGPU */ }
+else if (canvas.getContext('webgl2')) { /* WebGL2 fallback */ }
+/* CSS-only fallback must still look good */
+```
+
+### Performance rules
+
+- Target 60fps. If dropping below 50, simplify.
+- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative.
+- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport.
+- Pause off-screen rendering. Kill what you can't see.
+- Test on real mid-range devices, not just your development machine.
+
+### Polish is the difference
+
+The gap between "cool" and "extraordinary" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable.
+
+**NEVER**:
+- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion
+- Ship effects that cause jank on mid-range devices
+- Use bleeding-edge APIs without a functional fallback
+- Add sound without explicit user opt-in
+- Use technical ambition to mask weak design fundamentals — fix those first with other skills
+- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise
+
+## Verify the Result
+
+- **The wow test**: Show it to someone who hasn't seen it. Do they react?
+- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice?
+- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth?
+- **The accessibility test**: Enable reduced motion. Still beautiful?
+- **The context test**: Does this make sense for THIS brand and audience?
+
+Remember: "Technically extraordinary" isn't about using the newest API. It's about making an interface do something users didn't think a website could do.
diff --git a/personas/_shared/community-skills/impeccable-polish/SKILL.md b/personas/_shared/community-skills/impeccable-polish/SKILL.md
new file mode 100644
index 0000000..a7070ef
--- /dev/null
+++ b/personas/_shared/community-skills/impeccable-polish/SKILL.md
@@ -0,0 +1,203 @@
+---
+name: polish
+description: "Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great."
+argument-hint: "[target]"
+user-invocable: true
+---
+
+## MANDATORY PREPARATION
+
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first. Additionally gather: quality bar (MVP vs flagship).
+
+---
+
+Perform a meticulous final pass to catch all the small details that separate good work from great work. The difference between shipped and polished.
+
+## Pre-Polish Assessment
+
+Understand the current state and goals:
+
+1. **Review completeness**:
+ - Is it functionally complete?
+ - Are there known issues to preserve (mark with TODOs)?
+ - What's the quality bar? (MVP vs flagship feature?)
+ - When does it ship? (How much time for polish?)
+
+2. **Identify polish areas**:
+ - Visual inconsistencies
+ - Spacing and alignment issues
+ - Interaction state gaps
+ - Copy inconsistencies
+ - Edge cases and error states
+ - Loading and transition smoothness
+
+**CRITICAL**: Polish is the last step, not the first. Don't polish work that's not functionally complete.
+
+## Polish Systematically
+
+Work through these dimensions methodically:
+
+### Visual Alignment & Spacing
+
+- **Pixel-perfect alignment**: Everything lines up to grid
+- **Consistent spacing**: All gaps use spacing scale (no random 13px gaps)
+- **Optical alignment**: Adjust for visual weight (icons may need offset for optical centering)
+- **Responsive consistency**: Spacing and alignment work at all breakpoints
+- **Grid adherence**: Elements snap to baseline grid
+
+**Check**:
+- Enable grid overlay and verify alignment
+- Check spacing with browser inspector
+- Test at multiple viewport sizes
+- Look for elements that "feel" off
+
+### Typography Refinement
+
+- **Hierarchy consistency**: Same elements use same sizes/weights throughout
+- **Line length**: 45-75 characters for body text
+- **Line height**: Appropriate for font size and context
+- **Widows & orphans**: No single words on last line
+- **Hyphenation**: Appropriate for language and column width
+- **Kerning**: Adjust letter spacing where needed (especially headlines)
+- **Font loading**: No FOUT/FOIT flashes
+
+### Color & Contrast
+
+- **Contrast ratios**: All text meets WCAG standards
+- **Consistent token usage**: No hard-coded colors, all use design tokens
+- **Theme consistency**: Works in all theme variants
+- **Color meaning**: Same colors mean same things throughout
+- **Accessible focus**: Focus indicators visible with sufficient contrast
+- **Tinted neutrals**: No pure gray or pure black—add subtle color tint (0.01 chroma)
+- **Gray on color**: Never put gray text on colored backgrounds—use a shade of that color or transparency
+
+### Interaction States
+
+Every interactive element needs all states:
+
+- **Default**: Resting state
+- **Hover**: Subtle feedback (color, scale, shadow)
+- **Focus**: Keyboard focus indicator (never remove without replacement)
+- **Active**: Click/tap feedback
+- **Disabled**: Clearly non-interactive
+- **Loading**: Async action feedback
+- **Error**: Validation or error state
+- **Success**: Successful completion
+
+**Missing states create confusion and broken experiences**.
+
+### Micro-interactions & Transitions
+
+- **Smooth transitions**: All state changes animated appropriately (150-300ms)
+- **Consistent easing**: Use ease-out-quart/quint/expo for natural deceleration. Never bounce or elastic—they feel dated.
+- **No jank**: 60fps animations, only animate transform and opacity
+- **Appropriate motion**: Motion serves purpose, not decoration
+- **Reduced motion**: Respects `prefers-reduced-motion`
+
+### Content & Copy
+
+- **Consistent terminology**: Same things called same names throughout
+- **Consistent capitalization**: Title Case vs Sentence case applied consistently
+- **Grammar & spelling**: No typos
+- **Appropriate length**: Not too wordy, not too terse
+- **Punctuation consistency**: Periods on sentences, not on labels (unless all labels have them)
+
+### Icons & Images
+
+- **Consistent style**: All icons from same family or matching style
+- **Appropriate sizing**: Icons sized consistently for context
+- **Proper alignment**: Icons align with adjacent text optically
+- **Alt text**: All images have descriptive alt text
+- **Loading states**: Images don't cause layout shift, proper aspect ratios
+- **Retina support**: 2x assets for high-DPI screens
+
+### Forms & Inputs
+
+- **Label consistency**: All inputs properly labeled
+- **Required indicators**: Clear and consistent
+- **Error messages**: Helpful and consistent
+- **Tab order**: Logical keyboard navigation
+- **Auto-focus**: Appropriate (don't overuse)
+- **Validation timing**: Consistent (on blur vs on submit)
+
+### Edge Cases & Error States
+
+- **Loading states**: All async actions have loading feedback
+- **Empty states**: Helpful empty states, not just blank space
+- **Error states**: Clear error messages with recovery paths
+- **Success states**: Confirmation of successful actions
+- **Long content**: Handles very long names, descriptions, etc.
+- **No content**: Handles missing data gracefully
+- **Offline**: Appropriate offline handling (if applicable)
+
+### Responsiveness
+
+- **All breakpoints**: Test mobile, tablet, desktop
+- **Touch targets**: 44x44px minimum on touch devices
+- **Readable text**: No text smaller than 14px on mobile
+- **No horizontal scroll**: Content fits viewport
+- **Appropriate reflow**: Content adapts logically
+
+### Performance
+
+- **Fast initial load**: Optimize critical path
+- **No layout shift**: Elements don't jump after load (CLS)
+- **Smooth interactions**: No lag or jank
+- **Optimized images**: Appropriate formats and sizes
+- **Lazy loading**: Off-screen content loads lazily
+
+### Code Quality
+
+- **Remove console logs**: No debug logging in production
+- **Remove commented code**: Clean up dead code
+- **Remove unused imports**: Clean up unused dependencies
+- **Consistent naming**: Variables and functions follow conventions
+- **Type safety**: No TypeScript `any` or ignored errors
+- **Accessibility**: Proper ARIA labels and semantic HTML
+
+## Polish Checklist
+
+Go through systematically:
+
+- [ ] Visual alignment perfect at all breakpoints
+- [ ] Spacing uses design tokens consistently
+- [ ] Typography hierarchy consistent
+- [ ] All interactive states implemented
+- [ ] All transitions smooth (60fps)
+- [ ] Copy is consistent and polished
+- [ ] Icons are consistent and properly sized
+- [ ] All forms properly labeled and validated
+- [ ] Error states are helpful
+- [ ] Loading states are clear
+- [ ] Empty states are welcoming
+- [ ] Touch targets are 44x44px minimum
+- [ ] Contrast ratios meet WCAG AA
+- [ ] Keyboard navigation works
+- [ ] Focus indicators visible
+- [ ] No console errors or warnings
+- [ ] No layout shift on load
+- [ ] Works in all supported browsers
+- [ ] Respects reduced motion preference
+- [ ] Code is clean (no TODOs, console.logs, commented code)
+
+**IMPORTANT**: Polish is about details. Zoom in. Squint at it. Use it yourself. The little things add up.
+
+**NEVER**:
+- Polish before it's functionally complete
+- Spend hours on polish if it ships in 30 minutes (triage)
+- Introduce bugs while polishing (test thoroughly)
+- Ignore systematic issues (if spacing is off everywhere, fix the system)
+- Perfect one thing while leaving others rough (consistent quality level)
+
+## Final Verification
+
+Before marking as done:
+
+- **Use it yourself**: Actually interact with the feature
+- **Test on real devices**: Not just browser DevTools
+- **Ask someone else to review**: Fresh eyes catch things
+- **Compare to design**: Match intended design
+- **Check all states**: Don't just test happy path
+
+Remember: You have impeccable attention to detail and exquisite taste. Polish until it feels effortless, looks intentional, and works flawlessly. Sweat the details - they matter.
+
diff --git a/personas/_shared/community-skills/impeccable-quieter/SKILL.md b/personas/_shared/community-skills/impeccable-quieter/SKILL.md
new file mode 100644
index 0000000..ccf7d62
--- /dev/null
+++ b/personas/_shared/community-skills/impeccable-quieter/SKILL.md
@@ -0,0 +1,102 @@
+---
+name: quieter
+description: "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic."
+argument-hint: "[target]"
+user-invocable: true
+---
+
+Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness.
+
+## MANDATORY PREPARATION
+
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first.
+
+---
+
+## Assess Current State
+
+Analyze what makes the design feel too intense:
+
+1. **Identify intensity sources**:
+ - **Color saturation**: Overly bright or saturated colors
+ - **Contrast extremes**: Too much high-contrast juxtaposition
+ - **Visual weight**: Too many bold, heavy elements competing
+ - **Animation excess**: Too much motion or overly dramatic effects
+ - **Complexity**: Too many visual elements, patterns, or decorations
+ - **Scale**: Everything is large and loud with no hierarchy
+
+2. **Understand the context**:
+ - What's the purpose? (Marketing vs tool vs reading experience)
+ - Who's the audience? (Some contexts need energy)
+ - What's working? (Don't throw away good ideas)
+ - What's the core message? (Preserve what matters)
+
+If any of these are unclear from the codebase, {{ask_instruction}}
+
+**CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness.
+
+## Plan Refinement
+
+Create a strategy to reduce intensity while maintaining impact:
+
+- **Color approach**: Desaturate or shift to more sophisticated tones?
+- **Hierarchy approach**: Which elements should stay bold (very few), which should recede?
+- **Simplification approach**: What can be removed entirely?
+- **Sophistication approach**: How can we signal quality through restraint?
+
+**IMPORTANT**: Great quiet design is harder than great bold design. Subtlety requires precision.
+
+## Refine the Design
+
+Systematically reduce intensity across these dimensions:
+
+### Color Refinement
+- **Reduce saturation**: Shift from fully saturated to 70-85% saturation
+- **Soften palette**: Replace bright colors with muted, sophisticated tones
+- **Reduce color variety**: Use fewer colors more thoughtfully
+- **Neutral dominance**: Let neutrals do more work, use color as accent (10% rule)
+- **Gentler contrasts**: High contrast only where it matters most
+- **Tinted grays**: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness
+- **Never gray on color**: If you have gray text on a colored background, use a darker shade of that color or transparency instead
+
+### Visual Weight Reduction
+- **Typography**: Reduce font weights (900 → 600, 700 → 500), decrease sizes where appropriate
+- **Hierarchy through subtlety**: Use weight, size, and space instead of color and boldness
+- **White space**: Increase breathing room, reduce density
+- **Borders & lines**: Reduce thickness, decrease opacity, or remove entirely
+
+### Simplification
+- **Remove decorative elements**: Gradients, shadows, patterns, textures that don't serve purpose
+- **Simplify shapes**: Reduce border radius extremes, simplify custom shapes
+- **Reduce layering**: Flatten visual hierarchy where possible
+- **Clean up effects**: Reduce or remove blur effects, glows, multiple shadows
+
+### Motion Reduction
+- **Reduce animation intensity**: Shorter distances (10-20px instead of 40px), gentler easing
+- **Remove decorative animations**: Keep functional motion, remove flourishes
+- **Subtle micro-interactions**: Replace dramatic effects with gentle feedback
+- **Refined easing**: Use ease-out-quart for smooth, understated motion—never bounce or elastic
+- **Remove animations entirely** if they're not serving a clear purpose
+
+### Composition Refinement
+- **Reduce scale jumps**: Smaller contrast between sizes creates calmer feeling
+- **Align to grid**: Bring rogue elements back into systematic alignment
+- **Even out spacing**: Replace extreme spacing variations with consistent rhythm
+
+**NEVER**:
+- Make everything the same size/weight (hierarchy still matters)
+- Remove all color (quiet ≠ grayscale)
+- Eliminate all personality (maintain character through refinement)
+- Sacrifice usability for aesthetics (functional elements still need clear affordances)
+- Make everything small and light (some anchors needed)
+
+## Verify Quality
+
+Ensure refinement maintains quality:
+
+- **Still functional**: Can users still accomplish tasks easily?
+- **Still distinctive**: Does it have character, or is it generic now?
+- **Better reading**: Is text easier to read for extended periods?
+- **Sophistication**: Does it feel more refined and premium?
+
+Remember: Quiet design is confident design. It doesn't need to shout. Less is more, but less is also harder. Refine with precision and maintain intentionality.
diff --git a/personas/_shared/community-skills/impeccable-teach-impeccable/SKILL.md b/personas/_shared/community-skills/impeccable-teach-impeccable/SKILL.md
new file mode 100644
index 0000000..0fc4860
--- /dev/null
+++ b/personas/_shared/community-skills/impeccable-teach-impeccable/SKILL.md
@@ -0,0 +1,71 @@
+---
+name: teach-impeccable
+description: One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
+user-invocable: true
+---
+
+Gather design context for this project, then persist it for all future sessions.
+
+## Step 1: Explore the Codebase
+
+Before asking questions, thoroughly scan the project to discover what you can:
+
+- **README and docs**: Project purpose, target audience, any stated goals
+- **Package.json / config files**: Tech stack, dependencies, existing design libraries
+- **Existing components**: Current design patterns, spacing, typography in use
+- **Brand assets**: Logos, favicons, color values already defined
+- **Design tokens / CSS variables**: Existing color palettes, font stacks, spacing scales
+- **Any style guides or brand documentation**
+
+Note what you've learned and what remains unclear.
+
+## Step 2: Ask UX-Focused Questions
+
+{{ask_instruction}} Focus only on what you couldn't infer from the codebase:
+
+### Users & Purpose
+- Who uses this? What's their context when using it?
+- What job are they trying to get done?
+- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)
+
+### Brand & Personality
+- How would you describe the brand personality in 3 words?
+- Any reference sites or apps that capture the right feel? What specifically about them?
+- What should this explicitly NOT look like? Any anti-references?
+
+### Aesthetic Preferences
+- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.)
+- Light mode, dark mode, or both?
+- Any colors that must be used or avoided?
+
+### Accessibility & Inclusion
+- Specific accessibility requirements? (WCAG level, known user needs)
+- Considerations for reduced motion, color blindness, or other accommodations?
+
+Skip questions where the answer is already clear from the codebase exploration.
+
+## Step 3: Write Design Context
+
+Synthesize your findings and the user's answers into a `## Design Context` section:
+
+```markdown
+## Design Context
+
+### Users
+[Who they are, their context, the job to be done]
+
+### Brand Personality
+[Voice, tone, 3-word personality, emotional goals]
+
+### Aesthetic Direction
+[Visual tone, references, anti-references, theme]
+
+### Design Principles
+[3-5 principles derived from the conversation that should guide all design decisions]
+```
+
+Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place.
+
+Then {{ask_instruction}} whether they'd also like the Design Context appended to {{config_file}}. If yes, append or update the section there as well.
+
+Confirm completion and summarize the key design principles that will now guide all future work.
diff --git a/personas/_shared/community-skills/impeccable-typeset/SKILL.md b/personas/_shared/community-skills/impeccable-typeset/SKILL.md
new file mode 100644
index 0000000..47db02c
--- /dev/null
+++ b/personas/_shared/community-skills/impeccable-typeset/SKILL.md
@@ -0,0 +1,115 @@
+---
+name: typeset
+description: "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography."
+argument-hint: "[target]"
+user-invocable: true
+---
+
+Assess and improve typography that feels generic, inconsistent, or poorly structured — turning default-looking text into intentional, well-crafted type.
+
+## MANDATORY PREPARATION
+
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first.
+
+---
+
+## Assess Current Typography
+
+Analyze what's weak or generic about the current type:
+
+1. **Font choices**:
+ - Are we using invisible defaults? (Inter, Roboto, Arial, Open Sans, system defaults)
+ - Does the font match the brand personality? (A playful brand shouldn't use a corporate typeface)
+ - Are there too many font families? (More than 2-3 is almost always a mess)
+
+2. **Hierarchy**:
+ - Can you tell headings from body from captions at a glance?
+ - Are font sizes too close together? (14px, 15px, 16px = muddy hierarchy)
+ - Are weight contrasts strong enough? (Medium vs Regular is barely visible)
+
+3. **Sizing & scale**:
+ - Is there a consistent type scale, or are sizes arbitrary?
+ - Does body text meet minimum readability? (16px+)
+ - Is the sizing strategy appropriate for the context? (Fixed `rem` scales for app UIs; fluid `clamp()` for marketing/content page headings)
+
+4. **Readability**:
+ - Are line lengths comfortable? (45-75 characters ideal)
+ - Is line-height appropriate for the font and context?
+ - Is there enough contrast between text and background?
+
+5. **Consistency**:
+ - Are the same elements styled the same way throughout?
+ - Are font weights used consistently? (Not bold in one section, semibold in another for the same role)
+ - Is letter-spacing intentional or default everywhere?
+
+**CRITICAL**: The goal isn't to make text "fancier" — it's to make it clearer, more readable, and more intentional. Good typography is invisible; bad typography is distracting.
+
+## Plan Typography Improvements
+
+Consult the [typography reference](reference/typography.md) from the frontend-design skill for detailed guidance on scales, pairing, and loading strategies.
+
+Create a systematic plan:
+
+- **Font selection**: Do fonts need replacing? What fits the brand/context?
+- **Type scale**: Establish a modular scale (e.g., 1.25 ratio) with clear hierarchy
+- **Weight strategy**: Which weights serve which roles? (Regular for body, Semibold for labels, Bold for headings — or whatever fits)
+- **Spacing**: Line-heights, letter-spacing, and margins between typographic elements
+
+## Improve Typography Systematically
+
+### Font Selection
+
+If fonts need replacing:
+- Choose fonts that reflect the brand personality
+- Pair with genuine contrast (serif + sans, geometric + humanist) — or use a single family in multiple weights
+- Ensure web font loading doesn't cause layout shift (`font-display: swap`, metric-matched fallbacks)
+
+### Establish Hierarchy
+
+Build a clear type scale:
+- **5 sizes cover most needs**: caption, secondary, body, subheading, heading
+- **Use a consistent ratio** between levels (1.25, 1.333, or 1.5)
+- **Combine dimensions**: Size + weight + color + space for strong hierarchy — don't rely on size alone
+- **App UIs**: Use a fixed `rem`-based type scale, optionally adjusted at 1-2 breakpoints. Fluid sizing undermines the spatial predictability that dense, container-based layouts need
+- **Marketing / content pages**: Use fluid sizing via `clamp(min, preferred, max)` for headings and display text. Keep body text fixed
+
+### Fix Readability
+
+- Set `max-width` on text containers using `ch` units (`max-width: 65ch`)
+- Adjust line-height per context: tighter for headings (1.1-1.2), looser for body (1.5-1.7)
+- Increase line-height slightly for light-on-dark text
+- Ensure body text is at least 16px / 1rem
+
+### Refine Details
+
+- Use `tabular-nums` for data tables and numbers that should align
+- Apply proper `letter-spacing`: slightly open for small caps and uppercase, default or tight for large display text
+- Use semantic token names (`--text-body`, `--text-heading`), not value names (`--font-16`)
+- Set `font-kerning: normal` and consider OpenType features where appropriate
+
+### Weight Consistency
+
+- Define clear roles for each weight and stick to them
+- Don't use more than 3-4 weights (Regular, Medium, Semibold, Bold is plenty)
+- Load only the weights you actually use (each weight adds to page load)
+
+**NEVER**:
+- Use more than 2-3 font families
+- Pick sizes arbitrarily — commit to a scale
+- Set body text below 16px
+- Use decorative/display fonts for body text
+- Disable browser zoom (`user-scalable=no`)
+- Use `px` for font sizes — use `rem` to respect user settings
+- Default to Inter/Roboto/Open Sans when personality matters
+- Pair fonts that are similar but not identical (two geometric sans-serifs)
+
+## Verify Typography Improvements
+
+- **Hierarchy**: Can you identify heading vs body vs caption instantly?
+- **Readability**: Is body text comfortable to read in long passages?
+- **Consistency**: Are same-role elements styled identically throughout?
+- **Personality**: Does the typography reflect the brand?
+- **Performance**: Are web fonts loading efficiently without layout shift?
+- **Accessibility**: Does text meet WCAG contrast ratios? Is it zoomable to 200%?
+
+Remember: Typography is the foundation of interface design — it carries the majority of information. Getting it right is the highest-leverage improvement you can make.
diff --git a/personas/_shared/community-skills/json-canvas/SKILL.md b/personas/_shared/community-skills/json-canvas/SKILL.md
new file mode 100644
index 0000000..8fb2c9d
--- /dev/null
+++ b/personas/_shared/community-skills/json-canvas/SKILL.md
@@ -0,0 +1,244 @@
+---
+name: json-canvas
+description: Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.
+---
+
+# JSON Canvas Skill
+
+## File Structure
+
+A canvas file (`.canvas`) contains two top-level arrays following the [JSON Canvas Spec 1.0](https://jsoncanvas.org/spec/1.0/):
+
+```json
+{
+ "nodes": [],
+ "edges": []
+}
+```
+
+- `nodes` (optional): Array of node objects
+- `edges` (optional): Array of edge objects connecting nodes
+
+## Common Workflows
+
+### 1. Create a New Canvas
+
+1. Create a `.canvas` file with the base structure `{"nodes": [], "edges": []}`
+2. Generate unique 16-character hex IDs for each node (e.g., `"6f0ad84f44ce9c17"`)
+3. Add nodes with required fields: `id`, `type`, `x`, `y`, `width`, `height`
+4. Add edges referencing valid node IDs via `fromNode` and `toNode`
+5. **Validate**: Parse the JSON to confirm it is valid. Verify all `fromNode`/`toNode` values exist in the nodes array
+
+### 2. Add a Node to an Existing Canvas
+
+1. Read and parse the existing `.canvas` file
+2. Generate a unique ID that does not collide with existing node or edge IDs
+3. Choose position (`x`, `y`) that avoids overlapping existing nodes (leave 50-100px spacing)
+4. Append the new node object to the `nodes` array
+5. Optionally add edges connecting the new node to existing nodes
+6. **Validate**: Confirm all IDs are unique and all edge references resolve to existing nodes
+
+### 3. Connect Two Nodes
+
+1. Identify the source and target node IDs
+2. Generate a unique edge ID
+3. Set `fromNode` and `toNode` to the source and target IDs
+4. Optionally set `fromSide`/`toSide` (top, right, bottom, left) for anchor points
+5. Optionally set `label` for descriptive text on the edge
+6. Append the edge to the `edges` array
+7. **Validate**: Confirm both `fromNode` and `toNode` reference existing node IDs
+
+### 4. Edit an Existing Canvas
+
+1. Read and parse the `.canvas` file as JSON
+2. Locate the target node or edge by `id`
+3. Modify the desired attributes (text, position, color, etc.)
+4. Write the updated JSON back to the file
+5. **Validate**: Re-check all ID uniqueness and edge reference integrity after editing
+
+## Nodes
+
+Nodes are objects placed on the canvas. Array order determines z-index: first node = bottom layer, last node = top layer.
+
+### Generic Node Attributes
+
+| Attribute | Required | Type | Description |
+|-----------|----------|------|-------------|
+| `id` | Yes | string | Unique 16-char hex identifier |
+| `type` | Yes | string | `text`, `file`, `link`, or `group` |
+| `x` | Yes | integer | X position in pixels |
+| `y` | Yes | integer | Y position in pixels |
+| `width` | Yes | integer | Width in pixels |
+| `height` | Yes | integer | Height in pixels |
+| `color` | No | canvasColor | Preset `"1"`-`"6"` or hex (e.g., `"#FF0000"`) |
+
+### Text Nodes
+
+| Attribute | Required | Type | Description |
+|-----------|----------|------|-------------|
+| `text` | Yes | string | Plain text with Markdown syntax |
+
+```json
+{
+ "id": "6f0ad84f44ce9c17",
+ "type": "text",
+ "x": 0,
+ "y": 0,
+ "width": 400,
+ "height": 200,
+ "text": "# Hello World\n\nThis is **Markdown** content."
+}
+```
+
+**Newline pitfall**: Use `\n` for line breaks in JSON strings. Do **not** use the literal `\\n` -- Obsidian renders that as the characters `\` and `n`.
+
+### File Nodes
+
+| Attribute | Required | Type | Description |
+|-----------|----------|------|-------------|
+| `file` | Yes | string | Path to file within the system |
+| `subpath` | No | string | Link to heading or block (starts with `#`) |
+
+```json
+{
+ "id": "a1b2c3d4e5f67890",
+ "type": "file",
+ "x": 500,
+ "y": 0,
+ "width": 400,
+ "height": 300,
+ "file": "Attachments/diagram.png"
+}
+```
+
+### Link Nodes
+
+| Attribute | Required | Type | Description |
+|-----------|----------|------|-------------|
+| `url` | Yes | string | External URL |
+
+```json
+{
+ "id": "c3d4e5f678901234",
+ "type": "link",
+ "x": 1000,
+ "y": 0,
+ "width": 400,
+ "height": 200,
+ "url": "https://obsidian.md"
+}
+```
+
+### Group Nodes
+
+Groups are visual containers for organizing other nodes. Position child nodes inside the group's bounds.
+
+| Attribute | Required | Type | Description |
+|-----------|----------|------|-------------|
+| `label` | No | string | Text label for the group |
+| `background` | No | string | Path to background image |
+| `backgroundStyle` | No | string | `cover`, `ratio`, or `repeat` |
+
+```json
+{
+ "id": "d4e5f6789012345a",
+ "type": "group",
+ "x": -50,
+ "y": -50,
+ "width": 1000,
+ "height": 600,
+ "label": "Project Overview",
+ "color": "4"
+}
+```
+
+## Edges
+
+Edges connect nodes via `fromNode` and `toNode` IDs.
+
+| Attribute | Required | Type | Default | Description |
+|-----------|----------|------|---------|-------------|
+| `id` | Yes | string | - | Unique identifier |
+| `fromNode` | Yes | string | - | Source node ID |
+| `fromSide` | No | string | - | `top`, `right`, `bottom`, or `left` |
+| `fromEnd` | No | string | `none` | `none` or `arrow` |
+| `toNode` | Yes | string | - | Target node ID |
+| `toSide` | No | string | - | `top`, `right`, `bottom`, or `left` |
+| `toEnd` | No | string | `arrow` | `none` or `arrow` |
+| `color` | No | canvasColor | - | Line color |
+| `label` | No | string | - | Text label |
+
+```json
+{
+ "id": "0123456789abcdef",
+ "fromNode": "6f0ad84f44ce9c17",
+ "fromSide": "right",
+ "toNode": "a1b2c3d4e5f67890",
+ "toSide": "left",
+ "toEnd": "arrow",
+ "label": "leads to"
+}
+```
+
+## Colors
+
+The `canvasColor` type accepts either a hex string or a preset number:
+
+| Preset | Color |
+|--------|-------|
+| `"1"` | Red |
+| `"2"` | Orange |
+| `"3"` | Yellow |
+| `"4"` | Green |
+| `"5"` | Cyan |
+| `"6"` | Purple |
+
+Preset color values are intentionally undefined -- applications use their own brand colors.
+
+## ID Generation
+
+Generate 16-character lowercase hexadecimal strings (64-bit random value):
+
+```
+"6f0ad84f44ce9c17"
+"a3b2c1d0e9f8a7b6"
+```
+
+## Layout Guidelines
+
+- Coordinates can be negative (canvas extends infinitely)
+- `x` increases right, `y` increases down; position is the top-left corner
+- Space nodes 50-100px apart; leave 20-50px padding inside groups
+- Align to grid (multiples of 10 or 20) for cleaner layouts
+
+| Node Type | Suggested Width | Suggested Height |
+|-----------|-----------------|------------------|
+| Small text | 200-300 | 80-150 |
+| Medium text | 300-450 | 150-300 |
+| Large text | 400-600 | 300-500 |
+| File preview | 300-500 | 200-400 |
+| Link preview | 250-400 | 100-200 |
+
+## Validation Checklist
+
+After creating or editing a canvas file, verify:
+
+1. All `id` values are unique across both nodes and edges
+2. Every `fromNode` and `toNode` references an existing node ID
+3. Required fields are present for each node type (`text` for text nodes, `file` for file nodes, `url` for link nodes)
+4. `type` is one of: `text`, `file`, `link`, `group`
+5. `fromSide`/`toSide` values are one of: `top`, `right`, `bottom`, `left`
+6. `fromEnd`/`toEnd` values are one of: `none`, `arrow`
+7. Color presets are `"1"` through `"6"` or valid hex (e.g., `"#FF0000"`)
+8. JSON is valid and parseable
+
+If validation fails, check for duplicate IDs, dangling edge references, or malformed JSON strings (especially unescaped newlines in text content).
+
+## Complete Examples
+
+See [references/EXAMPLES.md](references/EXAMPLES.md) for full canvas examples including mind maps, project boards, research canvases, and flowcharts.
+
+## References
+
+- [JSON Canvas Spec 1.0](https://jsoncanvas.org/spec/1.0/)
+- [JSON Canvas GitHub](https://github.com/obsidianmd/jsoncanvas)
diff --git a/personas/_shared/community-skills/json-canvas/references/EXAMPLES.md b/personas/_shared/community-skills/json-canvas/references/EXAMPLES.md
new file mode 100644
index 0000000..c94f996
--- /dev/null
+++ b/personas/_shared/community-skills/json-canvas/references/EXAMPLES.md
@@ -0,0 +1,329 @@
+# JSON Canvas Complete Examples
+
+## Simple Canvas with Text and Connections
+
+```json
+{
+ "nodes": [
+ {
+ "id": "8a9b0c1d2e3f4a5b",
+ "type": "text",
+ "x": 0,
+ "y": 0,
+ "width": 300,
+ "height": 150,
+ "text": "# Main Idea\n\nThis is the central concept."
+ },
+ {
+ "id": "1a2b3c4d5e6f7a8b",
+ "type": "text",
+ "x": 400,
+ "y": -100,
+ "width": 250,
+ "height": 100,
+ "text": "## Supporting Point A\n\nDetails here."
+ },
+ {
+ "id": "2b3c4d5e6f7a8b9c",
+ "type": "text",
+ "x": 400,
+ "y": 100,
+ "width": 250,
+ "height": 100,
+ "text": "## Supporting Point B\n\nMore details."
+ }
+ ],
+ "edges": [
+ {
+ "id": "3c4d5e6f7a8b9c0d",
+ "fromNode": "8a9b0c1d2e3f4a5b",
+ "fromSide": "right",
+ "toNode": "1a2b3c4d5e6f7a8b",
+ "toSide": "left"
+ },
+ {
+ "id": "4d5e6f7a8b9c0d1e",
+ "fromNode": "8a9b0c1d2e3f4a5b",
+ "fromSide": "right",
+ "toNode": "2b3c4d5e6f7a8b9c",
+ "toSide": "left"
+ }
+ ]
+}
+```
+
+## Project Board with Groups
+
+```json
+{
+ "nodes": [
+ {
+ "id": "5e6f7a8b9c0d1e2f",
+ "type": "group",
+ "x": 0,
+ "y": 0,
+ "width": 300,
+ "height": 500,
+ "label": "To Do",
+ "color": "1"
+ },
+ {
+ "id": "6f7a8b9c0d1e2f3a",
+ "type": "group",
+ "x": 350,
+ "y": 0,
+ "width": 300,
+ "height": 500,
+ "label": "In Progress",
+ "color": "3"
+ },
+ {
+ "id": "7a8b9c0d1e2f3a4b",
+ "type": "group",
+ "x": 700,
+ "y": 0,
+ "width": 300,
+ "height": 500,
+ "label": "Done",
+ "color": "4"
+ },
+ {
+ "id": "8b9c0d1e2f3a4b5c",
+ "type": "text",
+ "x": 20,
+ "y": 50,
+ "width": 260,
+ "height": 80,
+ "text": "## Task 1\n\nImplement feature X"
+ },
+ {
+ "id": "9c0d1e2f3a4b5c6d",
+ "type": "text",
+ "x": 370,
+ "y": 50,
+ "width": 260,
+ "height": 80,
+ "text": "## Task 2\n\nReview PR #123",
+ "color": "2"
+ },
+ {
+ "id": "0d1e2f3a4b5c6d7e",
+ "type": "text",
+ "x": 720,
+ "y": 50,
+ "width": 260,
+ "height": 80,
+ "text": "## Task 3\n\n~~Setup CI/CD~~"
+ }
+ ],
+ "edges": []
+}
+```
+
+## Research Canvas with Files and Links
+
+```json
+{
+ "nodes": [
+ {
+ "id": "1e2f3a4b5c6d7e8f",
+ "type": "text",
+ "x": 300,
+ "y": 200,
+ "width": 400,
+ "height": 200,
+ "text": "# Research Topic\n\n## Key Questions\n\n- How does X affect Y?\n- What are the implications?",
+ "color": "5"
+ },
+ {
+ "id": "2f3a4b5c6d7e8f9a",
+ "type": "file",
+ "x": 0,
+ "y": 0,
+ "width": 250,
+ "height": 150,
+ "file": "Literature/Paper A.pdf"
+ },
+ {
+ "id": "3a4b5c6d7e8f9a0b",
+ "type": "file",
+ "x": 0,
+ "y": 200,
+ "width": 250,
+ "height": 150,
+ "file": "Notes/Meeting Notes.md",
+ "subpath": "#Key Insights"
+ },
+ {
+ "id": "4b5c6d7e8f9a0b1c",
+ "type": "link",
+ "x": 0,
+ "y": 400,
+ "width": 250,
+ "height": 100,
+ "url": "https://example.com/research"
+ },
+ {
+ "id": "5c6d7e8f9a0b1c2d",
+ "type": "file",
+ "x": 750,
+ "y": 150,
+ "width": 300,
+ "height": 250,
+ "file": "Attachments/diagram.png"
+ }
+ ],
+ "edges": [
+ {
+ "id": "6d7e8f9a0b1c2d3e",
+ "fromNode": "2f3a4b5c6d7e8f9a",
+ "fromSide": "right",
+ "toNode": "1e2f3a4b5c6d7e8f",
+ "toSide": "left",
+ "label": "supports"
+ },
+ {
+ "id": "7e8f9a0b1c2d3e4f",
+ "fromNode": "3a4b5c6d7e8f9a0b",
+ "fromSide": "right",
+ "toNode": "1e2f3a4b5c6d7e8f",
+ "toSide": "left",
+ "label": "informs"
+ },
+ {
+ "id": "8f9a0b1c2d3e4f5a",
+ "fromNode": "4b5c6d7e8f9a0b1c",
+ "fromSide": "right",
+ "toNode": "1e2f3a4b5c6d7e8f",
+ "toSide": "left",
+ "toEnd": "arrow",
+ "color": "6"
+ },
+ {
+ "id": "9a0b1c2d3e4f5a6b",
+ "fromNode": "1e2f3a4b5c6d7e8f",
+ "fromSide": "right",
+ "toNode": "5c6d7e8f9a0b1c2d",
+ "toSide": "left",
+ "label": "visualized by"
+ }
+ ]
+}
+```
+
+## Flowchart
+
+```json
+{
+ "nodes": [
+ {
+ "id": "a0b1c2d3e4f5a6b7",
+ "type": "text",
+ "x": 200,
+ "y": 0,
+ "width": 150,
+ "height": 60,
+ "text": "**Start**",
+ "color": "4"
+ },
+ {
+ "id": "b1c2d3e4f5a6b7c8",
+ "type": "text",
+ "x": 200,
+ "y": 100,
+ "width": 150,
+ "height": 60,
+ "text": "Step 1:\nGather data"
+ },
+ {
+ "id": "c2d3e4f5a6b7c8d9",
+ "type": "text",
+ "x": 200,
+ "y": 200,
+ "width": 150,
+ "height": 80,
+ "text": "**Decision**\n\nIs data valid?",
+ "color": "3"
+ },
+ {
+ "id": "d3e4f5a6b7c8d9e0",
+ "type": "text",
+ "x": 400,
+ "y": 200,
+ "width": 150,
+ "height": 60,
+ "text": "Process data"
+ },
+ {
+ "id": "e4f5a6b7c8d9e0f1",
+ "type": "text",
+ "x": 0,
+ "y": 200,
+ "width": 150,
+ "height": 60,
+ "text": "Request new data",
+ "color": "1"
+ },
+ {
+ "id": "f5a6b7c8d9e0f1a2",
+ "type": "text",
+ "x": 400,
+ "y": 320,
+ "width": 150,
+ "height": 60,
+ "text": "**End**",
+ "color": "4"
+ }
+ ],
+ "edges": [
+ {
+ "id": "a6b7c8d9e0f1a2b3",
+ "fromNode": "a0b1c2d3e4f5a6b7",
+ "fromSide": "bottom",
+ "toNode": "b1c2d3e4f5a6b7c8",
+ "toSide": "top"
+ },
+ {
+ "id": "b7c8d9e0f1a2b3c4",
+ "fromNode": "b1c2d3e4f5a6b7c8",
+ "fromSide": "bottom",
+ "toNode": "c2d3e4f5a6b7c8d9",
+ "toSide": "top"
+ },
+ {
+ "id": "c8d9e0f1a2b3c4d5",
+ "fromNode": "c2d3e4f5a6b7c8d9",
+ "fromSide": "right",
+ "toNode": "d3e4f5a6b7c8d9e0",
+ "toSide": "left",
+ "label": "Yes",
+ "color": "4"
+ },
+ {
+ "id": "d9e0f1a2b3c4d5e6",
+ "fromNode": "c2d3e4f5a6b7c8d9",
+ "fromSide": "left",
+ "toNode": "e4f5a6b7c8d9e0f1",
+ "toSide": "right",
+ "label": "No",
+ "color": "1"
+ },
+ {
+ "id": "e0f1a2b3c4d5e6f7",
+ "fromNode": "e4f5a6b7c8d9e0f1",
+ "fromSide": "top",
+ "fromEnd": "none",
+ "toNode": "b1c2d3e4f5a6b7c8",
+ "toSide": "left",
+ "toEnd": "arrow"
+ },
+ {
+ "id": "f1a2b3c4d5e6f7a8",
+ "fromNode": "d3e4f5a6b7c8d9e0",
+ "fromSide": "bottom",
+ "toNode": "f5a6b7c8d9e0f1a2",
+ "toSide": "top"
+ }
+ ]
+}
+```
diff --git a/personas/_shared/community-skills/launch-strategy/SKILL.md b/personas/_shared/community-skills/launch-strategy/SKILL.md
new file mode 100644
index 0000000..cdcc22d
--- /dev/null
+++ b/personas/_shared/community-skills/launch-strategy/SKILL.md
@@ -0,0 +1,353 @@
+---
+name: launch-strategy
+description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas."
+metadata:
+ version: 1.1.0
+---
+
+# Launch Strategy
+
+You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.
+
+## Before Starting
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+---
+
+## Core Philosophy
+
+The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.
+
+A strong launch isn't about a single moment. It's about:
+- Getting your product into users' hands early
+- Learning from real feedback
+- Making a splash at every stage
+- Building momentum that compounds over time
+
+---
+
+## The ORB Framework
+
+Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.
+
+### Owned Channels
+You own the channel (though not the audience). Direct access without algorithms or platform rules.
+
+**Examples:**
+- Email list
+- Blog
+- Podcast
+- Branded community (Slack, Discord)
+- Website/product
+
+**Why they matter:**
+- Get more effective over time
+- No algorithm changes or pay-to-play
+- Direct relationship with audience
+- Compound value from content
+
+**Start with 1-2 based on audience:**
+- Industry lacks quality content → Start a blog
+- People want direct updates → Focus on email
+- Engagement matters → Build a community
+
+**Example - Superhuman:**
+Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.
+
+### Rented Channels
+Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.
+
+**Examples:**
+- Social media (Twitter/X, LinkedIn, Instagram)
+- App stores and marketplaces
+- YouTube
+- Reddit
+
+**How to use correctly:**
+- Pick 1-2 platforms where your audience is active
+- Use them to drive traffic to owned channels
+- Don't rely on them as your only strategy
+
+**Example - Notion:**
+Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding.
+
+**Platform-specific tactics:**
+- Twitter/X: Threads that spark conversation → link to newsletter
+- LinkedIn: High-value posts → lead to gated content or email signup
+- Marketplaces (Shopify, Slack): Optimize listing → drive to site for more
+
+Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.
+
+### Borrowed Channels
+Tap into someone else's audience to shortcut the hardest part—getting noticed.
+
+**Examples:**
+- Guest content (blog posts, podcast interviews, newsletter features)
+- Collaborations (webinars, co-marketing, social takeovers)
+- Speaking engagements (conferences, panels, virtual summits)
+- Influencer partnerships
+
+**Be proactive, not passive:**
+1. List industry leaders your audience follows
+2. Pitch win-win collaborations
+3. Use tools like SparkToro or Listen Notes to find audience overlap
+4. Set up affiliate/referral incentives (for channel partner launches, use [Introw](../../tools/integrations/introw.md) to manage deal registration and commissions)
+
+**Example - TRMNL:**
+Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.
+
+Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.
+
+---
+
+## Five-Phase Launch Approach
+
+Launching isn't a one-day event. It's a phased process that builds momentum.
+
+### Phase 1: Internal Launch
+Gather initial feedback and iron out major issues before going public.
+
+**Actions:**
+- Recruit early users one-on-one to test for free
+- Collect feedback on usability gaps and missing features
+- Ensure prototype is functional enough to demo (doesn't need to be production-ready)
+
+**Goal:** Validate core functionality with friendly users.
+
+### Phase 2: Alpha Launch
+Put the product in front of external users in a controlled way.
+
+**Actions:**
+- Create landing page with early access signup form
+- Announce the product exists
+- Invite users individually to start testing
+- MVP should be working in production (even if still evolving)
+
+**Goal:** First external validation and initial waitlist building.
+
+### Phase 3: Beta Launch
+Scale up early access while generating external buzz.
+
+**Actions:**
+- Work through early access list (some free, some paid)
+- Start marketing with teasers about problems you solve
+- Recruit friends, investors, and influencers to test and share
+
+**Consider adding:**
+- Coming soon landing page or waitlist
+- "Beta" sticker in dashboard navigation
+- Email invites to early access list
+- Early access toggle in settings for experimental features
+
+**Goal:** Build buzz and refine product with broader feedback.
+
+### Phase 4: Early Access Launch
+Shift from small-scale testing to controlled expansion.
+
+**Actions:**
+- Leak product details: screenshots, feature GIFs, demos
+- Gather quantitative usage data and qualitative feedback
+- Run user research with engaged users (incentivize with credits)
+- Optionally run product/market fit survey to refine messaging
+
+**Expansion options:**
+- Option A: Throttle invites in batches (5-10% at a time)
+- Option B: Invite all users at once under "early access" framing
+
+**Goal:** Validate at scale and prepare for full launch.
+
+### Phase 5: Full Launch
+Open the floodgates.
+
+**Actions:**
+- Open self-serve signups
+- Start charging (if not already)
+- Announce general availability across all channels
+
+**Launch touchpoints:**
+- Customer emails
+- In-app popups and product tours
+- Website banner linking to launch assets
+- "New" sticker in dashboard navigation
+- Blog post announcement
+- Social posts across platforms
+- Product Hunt, BetaList, Hacker News, etc.
+
+**Goal:** Maximum visibility and conversion to paying users.
+
+---
+
+## Product Hunt Launch Strategy
+
+Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.
+
+### Pros
+- Exposure to tech-savvy early adopter audience
+- Credibility bump (especially if Product of the Day)
+- Potential PR coverage and backlinks
+
+### Cons
+- Very competitive to rank well
+- Short-lived traffic spikes
+- Requires significant pre-launch planning
+
+### How to Launch Successfully
+
+**Before launch day:**
+1. Build relationships with influential supporters, content hubs, and communities
+2. Optimize your listing: compelling tagline, polished visuals, short demo video
+3. Study successful launches to identify what worked
+4. Engage in relevant communities—provide value before pitching
+5. Prepare your team for all-day engagement
+
+**On launch day:**
+1. Treat it as an all-day event
+2. Respond to every comment in real-time
+3. Answer questions and spark discussions
+4. Encourage your existing audience to engage
+5. Direct traffic back to your site to capture signups
+
+**After launch day:**
+1. Follow up with everyone who engaged
+2. Convert Product Hunt traffic into owned relationships (email signups)
+3. Continue momentum with post-launch content
+
+### Case Studies
+
+**SavvyCal** (Scheduling tool):
+- Optimized landing page and onboarding before launch
+- Built relationships with productivity/SaaS influencers in advance
+- Responded to every comment on launch day
+- Result: #2 Product of the Month
+
+**Reform** (Form builder):
+- Studied successful launches and applied insights
+- Crafted clear tagline, polished visuals, demo video
+- Engaged in communities before launch (provided value first)
+- Treated launch as all-day engagement event
+- Directed traffic to capture signups
+- Result: #1 Product of the Day
+
+---
+
+## Post-Launch Product Marketing
+
+Your launch isn't over when the announcement goes live. Now comes adoption and retention work.
+
+### Immediate Post-Launch Actions
+
+**Educate new users:**
+Set up automated onboarding email sequence introducing key features and use cases.
+
+**Reinforce the launch:**
+Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.
+
+**Differentiate against competitors:**
+Publish comparison pages highlighting why you're the obvious choice.
+
+**Update web pages:**
+Add dedicated sections about the new feature/product across your site.
+
+**Offer hands-on preview:**
+Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.
+
+### Keep Momentum Going
+It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.
+
+---
+
+## Ongoing Launch Strategy
+
+Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement.
+
+### How to Prioritize What to Announce
+
+Use this matrix to decide how much marketing each update deserves:
+
+**Major updates** (new features, product overhauls):
+- Full campaign across multiple channels
+- Blog post, email campaign, in-app messages, social media
+- Maximize exposure
+
+**Medium updates** (new integrations, UI enhancements):
+- Targeted announcement
+- Email to relevant segments, in-app banner
+- Don't need full fanfare
+
+**Minor updates** (bug fixes, small tweaks):
+- Changelog and release notes
+- Signal that product is improving
+- Don't dominate marketing
+
+### Announcement Tactics
+
+**Space out releases:**
+Instead of shipping everything at once, stagger announcements to maintain momentum.
+
+**Reuse high-performing tactics:**
+If a previous announcement resonated, apply those insights to future updates.
+
+**Keep engaging:**
+Continue using email, social, and in-app messaging to highlight improvements.
+
+**Signal active development:**
+Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.
+
+---
+
+## Launch Checklist
+
+### Pre-Launch
+- [ ] Landing page with clear value proposition
+- [ ] Email capture / waitlist signup
+- [ ] Early access list built
+- [ ] Owned channels established (email, blog, community)
+- [ ] Rented channel presence (social profiles optimized)
+- [ ] Borrowed channel opportunities identified (podcasts, influencers)
+- [ ] Product Hunt listing prepared (if using)
+- [ ] Launch assets created (screenshots, demo video, GIFs)
+- [ ] Onboarding flow ready
+- [ ] Analytics/tracking in place
+
+### Launch Day
+- [ ] Announcement email to list
+- [ ] Blog post published
+- [ ] Social posts scheduled and posted
+- [ ] Product Hunt listing live (if using)
+- [ ] In-app announcement for existing users
+- [ ] Website banner/notification active
+- [ ] Team ready to engage and respond
+- [ ] Monitor for issues and feedback
+
+### Post-Launch
+- [ ] Onboarding email sequence active
+- [ ] Follow-up with engaged prospects
+- [ ] Roundup email includes announcement
+- [ ] Comparison pages published
+- [ ] Interactive demo created
+- [ ] Gather and act on feedback
+- [ ] Plan next launch moment
+
+---
+
+## Task-Specific Questions
+
+1. What are you launching? (New product, major feature, minor update)
+2. What's your current audience size and engagement?
+3. What owned channels do you have? (Email list size, blog traffic, community)
+4. What's your timeline for launch?
+5. Have you launched before? What worked/didn't work?
+6. Are you considering Product Hunt? What's your preparation status?
+
+---
+
+## Related Skills
+
+- **marketing-ideas**: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals)
+- **email-sequence**: For launch and onboarding email sequences
+- **page-cro**: For optimizing launch landing pages
+- **marketing-psychology**: For psychology behind waitlists and exclusivity
+- **programmatic-seo**: For comparison pages mentioned in post-launch
+- **sales-enablement**: For launch sales collateral and enablement materials
diff --git a/personas/_shared/community-skills/lead-magnets/SKILL.md b/personas/_shared/community-skills/lead-magnets/SKILL.md
new file mode 100644
index 0000000..bb6bf6d
--- /dev/null
+++ b/personas/_shared/community-skills/lead-magnets/SKILL.md
@@ -0,0 +1,310 @@
+---
+name: lead-magnets
+description: When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tool-strategy. For writing the actual content, see copywriting. For the email sequence after capture, see email-sequence.
+metadata:
+ version: 1.0.0
+---
+
+# Lead Magnets
+
+You are an expert in lead magnet strategy. Your goal is to help plan lead magnets that capture emails, generate qualified leads, and naturally lead to product adoption.
+
+## Before Planning
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Gather this context (ask if not provided):
+
+### 1. Business Context
+- What does the company do?
+- Who is the ideal customer?
+- What problems does your product solve?
+
+### 2. Current Lead Generation
+- How do you currently capture leads?
+- What lead magnets or offers do you have?
+- What's your current conversion rate on email capture?
+
+### 3. Content Assets
+- What existing content could be repurposed? (blog posts, guides, data)
+- What expertise can you package?
+- What templates or tools do you use internally?
+
+### 4. Goals
+- Primary goal: email list growth, lead quality, product education?
+- Target audience stage: awareness, consideration, or decision?
+- Timeline and resource constraints?
+
+---
+
+## Lead Magnet Principles
+
+### 1. Solve a Specific Problem
+- Address one clear pain point, not a broad topic
+- "How to write cold emails that get replies" > "Marketing guide"
+
+### 2. Match the Buyer Stage
+- Awareness leads need education
+- Consideration leads need comparison and evaluation
+- Decision leads need implementation help
+
+### 3. High Perceived Value, Low Time Investment
+- Should look like it's worth paying for
+- Consumable in under 30 minutes (ideally under 10)
+- Immediate, actionable takeaway
+
+### 4. Natural Path to Product
+- Solves a problem your product also solves
+- Creates awareness of a gap your product fills
+- Demonstrates your expertise in the space
+
+### 5. Easy to Consume
+- One clear format (don't mix ebook + video + spreadsheet)
+- Works on mobile
+- No special software required
+
+---
+
+## Lead Magnet Types
+
+| Type | Best For | Effort | Time to Create |
+|------|----------|--------|----------------|
+| Checklist | Quick wins, process steps | Low | 1-2 hours |
+| Cheat sheet | Reference material, shortcuts | Low | 2-4 hours |
+| Template (doc/spreadsheet/Notion) | Repeatable processes, workflows | Low-Med | 2-8 hours |
+| Swipe file | Inspiration, examples | Medium | 4-8 hours |
+| Ebook/guide | Deep education, authority | High | 1-3 weeks |
+| Mini-course (email) | Education + nurture | Medium | 1-2 weeks |
+| Mini-course (video) | Education + personality | High | 2-4 weeks |
+| Quiz/assessment | Segmentation, engagement | Medium | 1-2 weeks |
+| Webinar | Authority, live engagement | Medium | 1 week prep |
+| Resource library | Ongoing value, return visits | High | Ongoing |
+| Free trial/community access | Product experience | Varies | Varies |
+
+**For detailed creation guidance per format**: See [references/format-guide.md](references/format-guide.md)
+
+---
+
+## Matching Lead Magnets to Buyer Stage
+
+### Awareness Stage
+Goal: Educate on the problem. Attract people who don't know you yet.
+
+| Format | Example |
+|--------|---------|
+| Checklist | "10-Point Website Audit Checklist" |
+| Cheat sheet | "SEO Cheat Sheet for Beginners" |
+| Ebook/guide | "The Complete Guide to Email Marketing" |
+| Quiz | "What Type of Marketer Are You?" |
+
+### Consideration Stage
+Goal: Help evaluate solutions. Build trust and demonstrate expertise.
+
+| Format | Example |
+|--------|---------|
+| Comparison template | "CRM Comparison Spreadsheet" |
+| Assessment | "Marketing Maturity Assessment" |
+| Case study collection | "5 Companies That 3x'd Their Pipeline" |
+| Webinar | "How to Choose the Right Analytics Tool" |
+
+### Decision Stage
+Goal: Help implement. Remove friction to purchase.
+
+| Format | Example |
+|--------|---------|
+| Template | "Ready-to-Use Sales Email Templates" |
+| Free trial | "14-Day Free Trial" |
+| Implementation guide | "Migration Checklist: Switch in 30 Minutes" |
+| ROI calculator | "Calculate Your Savings" (→ see **free-tool-strategy**) |
+
+---
+
+## Gating Strategy
+
+### Gating Options
+
+| Approach | When to Use | Trade-off |
+|----------|-------------|-----------|
+| **Full gate** | High-value content, bottom-funnel | Max capture, lower reach |
+| **Partial gate** | Preview + full version | Balance of reach and capture |
+| **Ungated + optional** | Top-funnel education | Max reach, lower capture |
+| **Content upgrade** | Blog post + bonus | Contextual, high-intent |
+
+### What to Ask For
+
+- **Email only** — highest conversion, lowest friction
+- **Email + name** — enables personalization, slight friction increase
+- **Email + company/role** — better lead qualification, more friction
+- **Multi-field** — only for high-value offers (webinars, demos)
+
+Rule of thumb: Ask for the minimum needed. Every extra field reduces conversion by 5-10%.
+
+### How to Frame the Exchange
+
+- Make the value obvious: "Get the full 25-page guide free"
+- Show a preview: table of contents, first page, sample results
+- Add social proof: "Downloaded by 5,000+ marketers"
+- Reduce risk: "No spam. Unsubscribe anytime."
+
+**For form optimization**: See **form-cro** skill
+**For popup implementation**: See **popup-cro** skill
+
+---
+
+## Landing Page & Delivery
+
+### Landing Page Structure
+
+1. **Headline** — Clear benefit: what they'll get and why it matters
+2. **Preview/mockup** — Visual of the lead magnet (cover, screenshot, sample page)
+3. **What's inside** — 3-5 bullet points of key takeaways
+4. **Social proof** — Download count, testimonials, logos
+5. **Form** — Minimal fields, clear CTA button
+6. **FAQ** — Address hesitations (Is it really free? What format?)
+
+**For landing page optimization**: See **page-cro** skill
+
+### Delivery Methods
+
+| Method | Pros | Cons |
+|--------|------|------|
+| **Instant download** | Immediate gratification | No email verification |
+| **Email delivery** | Verifies email, starts relationship | Slight delay |
+| **Thank you page + email** | Best of both—instant access + email copy | Slightly more complex |
+| **Drip delivery** | Builds habit, multiple touchpoints | Only for courses/series |
+
+### Thank You Page Optimization
+
+Don't waste the thank you page. After they've converted:
+- Confirm delivery ("Check your inbox")
+- Offer a next step (book a demo, start trial, join community)
+- Share on social (pre-written tweet/post)
+- Recommend related content
+
+---
+
+## Promotion & Distribution
+
+### Blog CTAs & Content Upgrades
+
+- Add relevant CTAs within blog posts (inline, end-of-post)
+- Create post-specific content upgrades (bonus checklist for a how-to post)
+- Content upgrades convert 2-5x better than generic sidebar CTAs
+
+### Exit-Intent & Popups
+
+- Trigger on exit intent or scroll depth
+- Match the popup offer to the page content
+- **See popup-cro** for implementation
+
+### Social Media
+
+- Share snippets and teasers from the lead magnet
+- Create carousel posts from key points
+- Use the lead magnet as the CTA in your bio/profile
+- **See social-content** for social strategy
+
+### Paid Promotion
+
+- Facebook/Instagram lead ads for top-funnel lead magnets
+- Google Ads for high-intent lead magnets (templates, tools)
+- LinkedIn for B2B lead magnets
+- Retarget blog visitors with lead magnet ads
+- **See paid-ads** for campaign strategy
+
+### Partner Co-Promotion
+
+- Cross-promote with complementary brands
+- Guest webinars with partner audiences
+- Include in partner newsletters
+- Bundle in resource collections
+
+---
+
+## Measuring Success
+
+### Key Metrics
+
+| Metric | What It Tells You | Benchmark |
+|--------|-------------------|-----------|
+| **Landing page conversion rate** | Offer attractiveness | 20-40% (warm traffic), 5-15% (cold) |
+| **Cost per lead** | Acquisition efficiency | Varies by channel and industry |
+| **Lead-to-customer rate** | Lead quality | 1-5% (B2B), varies widely |
+| **Email engagement** | Content relevance | 30-50% open, 2-5% click |
+| **Time to conversion** | Nurture effectiveness | Track by lead magnet source |
+
+**For detailed benchmarks by format and industry**: See [references/benchmarks.md](references/benchmarks.md)
+
+### A/B Testing Ideas
+
+- **Headline**: Benefit-focused vs. curiosity-driven
+- **Format**: Checklist vs. guide on same topic
+- **Gate level**: Full gate vs. partial preview
+- **Form fields**: Email-only vs. email + name
+- **CTA copy**: "Download Free Guide" vs. "Get Your Copy"
+- **Delivery**: Instant download vs. email delivery
+
+### Lead Quality Signals
+
+Good lead magnet attracted quality leads if:
+- Higher-than-average email engagement
+- Leads progress to trial/demo at expected rates
+- Low unsubscribe rate after delivery
+- Leads match ICP demographics
+
+---
+
+## Output Format
+
+When creating a lead magnet strategy, provide:
+
+### 1. Lead Magnet Recommendation
+- Format and topic
+- Target buyer stage
+- Why this format for this audience
+- Estimated creation effort
+
+### 2. Content Outline
+- Key sections/components
+- Length and scope
+- What makes it unique or valuable
+
+### 3. Gating & Capture Plan
+- What to gate and how
+- Form fields
+- Landing page structure
+
+### 4. Distribution Plan
+- Promotion channels
+- Content upgrade opportunities
+- Paid amplification (if applicable)
+
+### 5. Measurement Plan
+- KPIs and targets
+- What to A/B test first
+
+---
+
+## Task-Specific Questions
+
+1. What existing content or expertise could you turn into a lead magnet?
+2. Where does your audience spend time online?
+3. What's the most common question prospects ask before buying?
+4. Do you have an email nurture sequence set up for new leads?
+5. What's your budget for design and promotion?
+
+---
+
+## Related Skills
+
+- **free-tool-strategy**: For interactive tools as lead magnets (calculators, graders, quizzes)
+- **copywriting**: For writing the lead magnet content itself
+- **email-sequence**: For nurture sequences after lead capture
+- **page-cro**: For optimizing lead magnet landing pages
+- **popup-cro**: For popup-based lead capture
+- **form-cro**: For optimizing capture forms
+- **content-strategy**: For content planning and topic selection
+- **analytics-tracking**: For measuring lead magnet performance
+- **paid-ads**: For paid promotion of lead magnets
+- **social-content**: For social media promotion
diff --git a/personas/_shared/community-skills/lead-magnets/references/benchmarks.md b/personas/_shared/community-skills/lead-magnets/references/benchmarks.md
new file mode 100644
index 0000000..e54e948
--- /dev/null
+++ b/personas/_shared/community-skills/lead-magnets/references/benchmarks.md
@@ -0,0 +1,129 @@
+# Lead Magnet Benchmarks
+
+Reference data for planning and evaluating lead magnet performance.
+
+---
+
+## Conversion Rate Benchmarks
+
+### By Format Type
+
+| Format | Landing Page Conversion | Notes |
+|--------|------------------------|-------|
+| Checklist | 30-50% | High because low commitment |
+| Cheat sheet | 25-40% | Quick reference appeal |
+| Template | 25-45% | Immediate utility drives conversion |
+| Ebook/guide | 20-35% | Higher commitment, lower rate |
+| Quiz | 30-50% | Engagement drives completion |
+| Webinar | 20-40% (registration) | 30-50% attendance rate of registrants |
+| Mini-course | 15-30% | Higher commitment, higher quality leads |
+| Free trial | 5-15% | High intent but high friction |
+
+### By Traffic Source
+
+| Source | Expected Conversion | Why |
+|--------|-------------------|-----|
+| Blog content upgrade | 3-8% of post readers | Contextually relevant |
+| Dedicated landing page (organic) | 20-40% | High intent |
+| Dedicated landing page (paid) | 10-25% | Cold traffic |
+| Exit-intent popup | 2-5% of visitors | Interruption-based |
+| Sidebar/banner CTA | 0.5-2% | Low engagement |
+| Social media link | 10-20% | Warm but browsing |
+
+### By Industry (Landing Page)
+
+| Industry | Average Conversion |
+|----------|-------------------|
+| SaaS/Tech | 15-25% |
+| Marketing/Agency | 20-35% |
+| Finance | 10-20% |
+| E-commerce | 10-20% |
+| Education | 20-35% |
+| Health/Wellness | 15-25% |
+
+---
+
+## Lead Quality Indicators
+
+### Signals of High-Quality Leads
+- Open first 3 emails at 40%+ rate
+- Click through to content or product pages
+- Return to site within 30 days
+- Match ICP demographics (role, company size, industry)
+- Progress to trial, demo, or purchase within 90 days
+
+### Signals of Low-Quality Leads
+- Unsubscribe within first 3 emails
+- Never open beyond delivery email
+- Use disposable email addresses
+- Don't match target customer profile
+- Downloaded for the content, no product interest
+
+### Quality vs. Quantity by Format
+
+| Format | Lead Volume | Lead Quality | Net Value |
+|--------|-------------|-------------|-----------|
+| Generic ebook | High | Low-Medium | Medium |
+| Specific template | Medium | High | High |
+| Industry report | Medium | Medium-High | High |
+| Quiz/assessment | High | Medium (segmentable) | High |
+| Webinar | Low-Medium | High | High |
+| Checklist | High | Low-Medium | Medium |
+| Free trial | Low | Very High | Very High |
+
+---
+
+## Cost Benchmarks
+
+### Cost Per Lead by Channel
+
+| Channel | Typical CPL | Notes |
+|---------|-------------|-------|
+| Organic search | $0-5 | Lowest, but slow to build |
+| Blog content upgrade | $0-2 | Nearly free if you have traffic |
+| Facebook/Instagram Ads | $3-15 | B2C lower, B2B higher |
+| Google Ads | $10-50 | High intent, higher cost |
+| LinkedIn Ads | $25-75 | B2B, expensive but qualified |
+| Partner co-promotion | $0-5 | Depends on relationship |
+
+### Creation Cost by Format
+
+| Format | DIY Cost | With Designer/Freelancer |
+|--------|----------|-------------------------|
+| Checklist | Free | $100-300 |
+| Cheat sheet | Free | $200-500 |
+| Template | Free | $100-500 |
+| Ebook (10-25 pages) | Free | $500-2,000 |
+| Quiz | $0-100/mo (tool) | $500-2,000 |
+| Webinar | Free (Zoom) | $500-1,500 (production) |
+| Mini-course (email) | Free | $500-1,500 (copywriting) |
+| Video course | $0-200 (gear) | $2,000-5,000 |
+
+---
+
+## Timeline Expectations
+
+### Time to Create
+
+| Format | Solo Creator | With Team |
+|--------|-------------|-----------|
+| Checklist | 1-2 hours | Same day |
+| Cheat sheet | 2-4 hours | Same day |
+| Template | 2-8 hours | 1-2 days |
+| Swipe file | 4-8 hours | 1-2 days |
+| Ebook | 1-3 weeks | 1-2 weeks |
+| Quiz | 1-2 weeks | 1 week |
+| Webinar prep | 1 week | 3-5 days |
+| Mini-course | 1-2 weeks | 1 week |
+
+### Time to See Results
+
+| Phase | Timeline |
+|-------|----------|
+| First leads | Immediately with existing traffic or paid |
+| Organic traffic growth | 2-6 months (SEO) |
+| Meaningful lead volume | 1-3 months |
+| Measurable impact on pipeline | 3-6 months |
+| Full ROI assessment | 6-12 months |
+
+**Note**: These benchmarks are general guidelines. Your actual results depend on audience, niche, traffic volume, and offer quality. Start measuring from day one and build your own benchmarks.
diff --git a/personas/_shared/community-skills/lead-magnets/references/format-guide.md b/personas/_shared/community-skills/lead-magnets/references/format-guide.md
new file mode 100644
index 0000000..b4f7f79
--- /dev/null
+++ b/personas/_shared/community-skills/lead-magnets/references/format-guide.md
@@ -0,0 +1,196 @@
+# Lead Magnet Format Guide
+
+Detailed creation guidance for each lead magnet format.
+
+## Contents
+- Ebooks & Guides
+- Checklists
+- Cheat Sheets
+- Templates & Spreadsheets
+- Swipe Files
+- Mini-Courses
+- Quizzes & Assessments
+- Webinars & Workshops
+
+---
+
+## Ebooks & Guides
+
+**Best for**: Building authority, deep education, awareness-stage leads
+
+**Structure**:
+1. Title page with professional design
+2. Table of contents
+3. Introduction — frame the problem, set expectations
+4. 3-7 chapters — one key concept per chapter
+5. Summary — recap key takeaways
+6. CTA — next step toward your product
+
+**Guidelines**:
+- Ideal length: 10-25 pages (shorter is fine if valuable)
+- Include visuals: charts, diagrams, screenshots
+- Use callout boxes for key stats or quotes
+- End each chapter with a quick takeaway
+- Don't pad — density beats length
+
+**Tools**: Canva, Google Docs → PDF, Notion export, Designrr, Beacon.by
+
+---
+
+## Checklists
+
+**Best for**: Process-oriented tasks, quick wins, implementation help
+
+**Structure**:
+- Title: "[Number]-Point [Topic] Checklist"
+- Numbered or checkbox items
+- Group into logical sections if 10+ items
+- Brief explanation per item (1-2 sentences)
+
+**Guidelines**:
+- Keep to 1-2 pages
+- Use actionable language ("Verify X", "Set up Y", "Remove Z")
+- Order by workflow sequence or priority
+- Make it printable — clean layout, generous spacing
+- Include a "done" checkbox for each item
+
+**What works**: Step-by-step processes, audit criteria, launch checklists, setup guides
+
+---
+
+## Cheat Sheets
+
+**Best for**: Reference material, shortcuts, quick-lookup information
+
+**Structure**:
+- One page (two pages max)
+- Organized by category or workflow
+- Dense but scannable
+- Visual hierarchy with headers and grouping
+
+**Guidelines**:
+- Optimize for quick reference, not reading
+- Use tables, grids, or columns
+- Include formulas, shortcuts, or code snippets
+- Design for printing or saving as desktop reference
+- Bold the most important items
+
+**What works**: Keyboard shortcuts, formula references, terminology glossaries, decision matrices
+
+---
+
+## Templates & Spreadsheets
+
+**Best for**: Repeatable processes, planning, tracking
+
+### Spreadsheet Templates (Google Sheets / Excel)
+- Include a "How to Use" tab with instructions
+- Pre-fill with example data
+- Use data validation for dropdown fields
+- Add conditional formatting for visual cues
+- Lock formula cells, leave input cells editable
+- Include a "Make a Copy" link (Google Sheets)
+
+### Notion Templates
+- Provide a duplicate link
+- Include a getting-started guide
+- Pre-populate with example content
+- Use Notion's database features (views, filters, relations)
+- Keep it simple — don't over-engineer
+
+### Document Templates
+- Provide in multiple formats (Google Doc, Word, PDF)
+- Include placeholder text with [BRACKETS] for customization
+- Add inline instructions in a different color
+- Make it immediately usable with minimal editing
+
+**Key principle**: Templates should be usable within 5 minutes of downloading.
+
+---
+
+## Swipe Files
+
+**Best for**: Inspiration, examples, learning from others
+
+**Structure**:
+- Curated collection of 15-50 examples
+- Organized by category, type, or use case
+- Each example includes:
+ - The example itself (screenshot, text, link)
+ - Why it works (2-3 bullet annotations)
+ - How to adapt it (1-2 sentences)
+
+**Guidelines**:
+- Quality over quantity — curate ruthlessly
+- Add your analysis, don't just collect
+- Organize for browsing (categories, tags)
+- Update periodically with fresh examples
+- Credit original sources
+
+**What works**: Email subject lines, landing pages, ad copy, CTAs, onboarding flows, pricing pages
+
+---
+
+## Mini-Courses
+
+### Email-Based Mini-Courses
+- 3-5 emails delivered over 5-7 days
+- One lesson per email, one concept per lesson
+- Each email: teach → example → exercise
+- Progressive difficulty (build on previous lessons)
+- Final email: summary + CTA for product or next step
+
+### Video-Based Mini-Courses
+- 3-5 videos, 5-15 minutes each
+- Host on unlisted YouTube, Loom, or course platform
+- Deliver links via email drip
+- Include worksheets or exercises per lesson
+- More personal — builds stronger connection
+
+**Cadence**: Every 1-2 days. Don't stretch too thin or compress too tight.
+
+**Key principle**: Each lesson should deliver standalone value. If someone only watches lesson 2, they should still learn something useful.
+
+---
+
+## Quizzes & Assessments
+
+**Best for**: Engagement, segmentation, personalized results
+
+**Question Design**:
+- 5-10 questions (sweet spot: 7)
+- Multiple choice only — no open-ended
+- Questions should feel insightful, not obvious
+- Progress indicator ("Question 3 of 7")
+
+**Result Segmentation**:
+- 3-5 result categories
+- Each result: name, description, personalized recommendations
+- Tailor follow-up emails by result type
+- Share-worthy result format ("I got: Growth Stage Marketer!")
+
+**Implementation**: Gate results behind email capture. The quiz itself is ungated — the personalized results require an email.
+
+**For building interactive quizzes**: See **free-tool-strategy** skill for technical implementation guidance.
+
+---
+
+## Webinars & Workshops
+
+### Live Webinars
+- 30-45 minutes teaching + 15 minutes Q&A
+- Structure: Hook → Teach (3 key points) → Demo/example → CTA
+- Promote 1-2 weeks in advance
+- Send 3 reminder emails (confirmation, day before, 1 hour before)
+- Record for replay (extends value)
+
+### Evergreen Webinars
+- Pre-recorded, available on demand
+- Same structure as live but tighter editing
+- Always-on lead generation
+- Gate with email registration
+- Automated follow-up sequence
+
+**Follow-up**: Send replay link + summary + CTA within 24 hours. Continue with nurture sequence.
+
+**Key principle**: Teach something genuinely useful. A webinar that's just a sales pitch will damage trust.
diff --git a/personas/_shared/community-skills/marketing-ideas/SKILL.md b/personas/_shared/community-skills/marketing-ideas/SKILL.md
new file mode 100644
index 0000000..85ada27
--- /dev/null
+++ b/personas/_shared/community-skills/marketing-ideas/SKILL.md
@@ -0,0 +1,167 @@
+---
+name: marketing-ideas
+description: "When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (paid-ads, social-content, email-sequence, etc.)."
+metadata:
+ version: 1.1.0
+---
+
+# Marketing Ideas for SaaS
+
+You are a marketing strategist with a library of 139 proven marketing ideas. Your goal is to help users find the right marketing strategies for their specific situation, stage, and resources.
+
+## How to Use This Skill
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+When asked for marketing ideas:
+1. Ask about their product, audience, and current stage if not clear
+2. Suggest 3-5 most relevant ideas based on their context
+3. Provide details on implementation for chosen ideas
+4. Consider their resources (time, budget, team size)
+
+---
+
+## Ideas by Category (Quick Reference)
+
+| Category | Ideas | Examples |
+|----------|-------|----------|
+| Content & SEO | 1-10 | Programmatic SEO, Glossary marketing, Content repurposing |
+| Competitor | 11-13 | Comparison pages, Marketing jiu-jitsu |
+| Free Tools | 14-22 | Calculators, Generators, Chrome extensions |
+| Paid Ads | 23-34 | LinkedIn, Google, Retargeting, Podcast ads |
+| Social & Community | 35-44 | LinkedIn audience, Reddit marketing, Short-form video |
+| Email | 45-53 | Founder emails, Onboarding sequences, Win-back |
+| Partnerships | 54-64 | Affiliate programs, Integration marketing, Newsletter swaps |
+| Events | 65-72 | Webinars, Conference speaking, Virtual summits |
+| PR & Media | 73-76 | Press coverage, Documentaries |
+| Launches | 77-86 | Product Hunt, Lifetime deals, Giveaways |
+| Product-Led | 87-96 | Viral loops, Powered-by marketing, Free migrations |
+| Content Formats | 97-109 | Podcasts, Courses, Annual reports, Year wraps |
+| Unconventional | 110-122 | Awards, Challenges, Guerrilla marketing |
+| Platforms | 123-130 | App marketplaces, Review sites, YouTube |
+| International | 131-132 | Expansion, Price localization |
+| Developer | 133-136 | DevRel, Certifications |
+| Audience-Specific | 137-139 | Referrals, Podcast tours, Customer language |
+
+**For the complete list with descriptions**: See [references/ideas-by-category.md](references/ideas-by-category.md)
+
+---
+
+## Implementation Tips
+
+### By Stage
+
+**Pre-launch:**
+- Waitlist referrals (#79)
+- Early access pricing (#81)
+- Product Hunt prep (#78)
+
+**Early stage:**
+- Content & SEO (#1-10)
+- Community (#35)
+- Founder-led sales (#47)
+
+**Growth stage:**
+- Paid acquisition (#23-34)
+- Partnerships (#54-64)
+- Events (#65-72)
+
+**Scale:**
+- Brand campaigns
+- International (#131-132)
+- Media acquisitions (#73)
+
+### By Budget
+
+**Free:**
+- Content & SEO
+- Community building
+- Social media
+- Comment marketing
+
+**Low budget:**
+- Targeted ads
+- Sponsorships
+- Free tools
+
+**Medium budget:**
+- Events
+- Partnerships
+- PR
+
+**High budget:**
+- Acquisitions
+- Conferences
+- Brand campaigns
+
+### By Timeline
+
+**Quick wins:**
+- Ads, email, social posts
+
+**Medium-term:**
+- Content, SEO, community
+
+**Long-term:**
+- Brand, thought leadership, platform effects
+
+---
+
+## Top Ideas by Use Case
+
+### Need Leads Fast
+- Google Ads (#31) - High-intent search
+- LinkedIn Ads (#28) - B2B targeting
+- Engineering as Marketing (#15) - Free tool lead gen
+
+### Building Authority
+- Conference Speaking (#70)
+- Book Marketing (#104)
+- Podcasts (#107)
+
+### Low Budget Growth
+- Easy Keyword Ranking (#1)
+- Reddit Marketing (#38)
+- Comment Marketing (#44)
+
+### Product-Led Growth
+- Viral Loops (#93)
+- Powered By Marketing (#87)
+- In-App Upsells (#91)
+
+### Enterprise Sales
+- Investor Marketing (#133)
+- Expert Networks (#57)
+- Conference Sponsorship (#72)
+
+---
+
+## Output Format
+
+When recommending ideas, provide for each:
+
+- **Idea name**: One-line description
+- **Why it fits**: Connection to their situation
+- **How to start**: First 2-3 implementation steps
+- **Expected outcome**: What success looks like
+- **Resources needed**: Time, budget, skills required
+
+---
+
+## Task-Specific Questions
+
+1. What's your current stage and main growth goal?
+2. What's your marketing budget and team size?
+3. What have you already tried that worked or didn't?
+4. What competitor tactics do you admire?
+
+---
+
+## Related Skills
+
+- **programmatic-seo**: For scaling SEO content (#4)
+- **competitor-alternatives**: For comparison pages (#11)
+- **email-sequence**: For email marketing tactics
+- **free-tool-strategy**: For engineering as marketing (#15)
+- **referral-program**: For viral growth (#93)
diff --git a/personas/_shared/community-skills/marketing-ideas/references/ideas-by-category.md b/personas/_shared/community-skills/marketing-ideas/references/ideas-by-category.md
new file mode 100644
index 0000000..3819a9c
--- /dev/null
+++ b/personas/_shared/community-skills/marketing-ideas/references/ideas-by-category.md
@@ -0,0 +1,366 @@
+# The 139 Marketing Ideas
+
+Complete list of proven marketing approaches organized by category.
+
+## Contents
+- Content & SEO (1-10)
+- Competitor & Comparison (11-13)
+- Free Tools & Engineering (14-22)
+- Paid Advertising (23-34)
+- Social Media & Community (35-44)
+- Email Marketing (45-53)
+- Partnerships & Programs (54-64)
+- Events & Speaking (65-72)
+- PR & Media (73-76)
+- Launches & Promotions (77-86)
+- Product-Led Growth (87-96)
+- Content Formats (97-109)
+- Unconventional & Creative (110-122)
+- Platforms & Marketplaces (123-130)
+- International & Localization (131-132)
+- Developer & Technical (133-136)
+- Audience-Specific (137-139)
+
+## Content & SEO (1-10)
+
+1. **Easy Keyword Ranking** - Target low-competition keywords where you can rank quickly. Find terms competitors overlook—niche variations, long-tail queries, emerging topics.
+
+2. **SEO Audit** - Conduct comprehensive technical SEO audits of your own site and share findings publicly. Document fixes and improvements to build authority.
+
+3. **Glossary Marketing** - Create comprehensive glossaries defining industry terms. Each term becomes an SEO-optimized page targeting "what is X" searches.
+
+4. **Programmatic SEO** - Build template-driven pages at scale targeting keyword patterns. Location pages, comparison pages, integration pages—any pattern with search volume.
+
+5. **Content Repurposing** - Transform one piece of content into multiple formats. Blog post becomes Twitter thread, YouTube video, podcast episode, infographic.
+
+6. **Proprietary Data Content** - Leverage unique data from your product to create original research and reports. Data competitors can't replicate creates linkable assets.
+
+7. **Internal Linking** - Strategic internal linking distributes authority and improves crawlability. Build topical clusters connecting related content.
+
+8. **Content Refreshing** - Regularly update existing content with fresh data, examples, and insights. Refreshed content often outperforms new content.
+
+9. **Knowledge Base SEO** - Optimize help documentation for search. Support articles targeting problem-solution queries capture users actively seeking solutions.
+
+10. **Parasite SEO** - Publish content on high-authority platforms (Medium, LinkedIn, Substack) that rank faster than your own domain.
+
+---
+
+## Competitor & Comparison (11-13)
+
+11. **Competitor Comparison Pages** - Create detailed comparison pages positioning your product against competitors. "[Your Product] vs [Competitor]" pages capture high-intent searchers.
+
+12. **Marketing Jiu-Jitsu** - Turn competitor weaknesses into your strengths. When competitors raise prices, launch affordability campaigns.
+
+13. **Competitive Ad Research** - Study competitor advertising through tools like SpyFu or Facebook Ad Library. Learn what messaging resonates.
+
+---
+
+## Free Tools & Engineering (14-22)
+
+14. **Side Projects as Marketing** - Build small, useful tools related to your main product. Side projects attract users who may later convert.
+
+15. **Engineering as Marketing** - Build free tools that solve real problems. Calculators, analyzers, generators—useful utilities that naturally lead to your paid product.
+
+16. **Importers as Marketing** - Build import tools for competitor data. "Import from [Competitor]" reduces switching friction.
+
+17. **Quiz Marketing** - Create interactive quizzes that engage users while qualifying leads. Personality quizzes, assessments, and diagnostic tools generate shares.
+
+18. **Calculator Marketing** - Build calculators solving real problems—ROI calculators, pricing estimators, savings tools. Calculators attract links and rank well.
+
+19. **Chrome Extensions** - Create browser extensions providing standalone value. Chrome Web Store becomes another distribution channel.
+
+20. **Microsites** - Build focused microsites for specific campaigns, products, or audiences. Dedicated domains can rank faster.
+
+21. **Scanners** - Build free scanning tools that audit or analyze something. Website scanners, security checkers, performance analyzers.
+
+22. **Public APIs** - Open APIs enable developers to build on your platform, creating an ecosystem.
+
+---
+
+## Paid Advertising (23-34)
+
+23. **Podcast Advertising** - Sponsor relevant podcasts to reach engaged audiences. Host-read ads perform especially well.
+
+24. **Pre-targeting Ads** - Show awareness ads before launching direct response campaigns. Warm audiences convert better.
+
+25. **Facebook Ads** - Meta's detailed targeting reaches specific audiences. Test creative variations and leverage retargeting.
+
+26. **Instagram Ads** - Visual-first advertising for products with strong imagery. Stories and Reels ads capture attention.
+
+27. **Twitter Ads** - Reach engaged professionals discussing industry topics. Promoted tweets and follower campaigns.
+
+28. **LinkedIn Ads** - Target by job title, company size, and industry. Premium CPMs justified by B2B purchase intent.
+
+29. **Reddit Ads** - Reach passionate communities with authentic messaging. Transparency wins on Reddit.
+
+30. **Quora Ads** - Target users actively asking questions your product answers. Intent-rich environment.
+
+31. **Google Ads** - Capture high-intent search queries. Brand terms, competitor terms, and category terms.
+
+32. **YouTube Ads** - Video ads with detailed targeting. Pre-roll and discovery ads reach users consuming related content.
+
+33. **Cross-Platform Retargeting** - Follow users across platforms with consistent messaging.
+
+34. **Click-to-Messenger Ads** - Ads that open direct conversations rather than landing pages.
+
+---
+
+## Social Media & Community (35-44)
+
+35. **Community Marketing** - Build and nurture communities around your product. Slack groups, Discord servers, Facebook groups.
+
+36. **Quora Marketing** - Answer relevant questions with genuine expertise. Include product mentions where naturally appropriate.
+
+37. **Reddit Keyword Research** - Mine Reddit for real language your audience uses. Discover pain points and desires.
+
+38. **Reddit Marketing** - Participate authentically in relevant subreddits. Provide value first.
+
+39. **LinkedIn Audience** - Build personal brands on LinkedIn for B2B reach. Thought leadership builds authority.
+
+40. **Instagram Audience** - Visual storytelling for products with strong aesthetics. Behind-the-scenes and user stories.
+
+41. **X Audience** - Build presence on X/Twitter through consistent value. Threads and insights grow followings.
+
+42. **Short Form Video** - TikTok, Reels, and Shorts reach new audiences with snackable content.
+
+43. **Engagement Pods** - Coordinate with peers to boost each other's content engagement.
+
+44. **Comment Marketing** - Thoughtful comments on relevant content build visibility.
+
+---
+
+## Email Marketing (45-53)
+
+45. **Mistake Email Marketing** - Send "oops" emails when something genuinely goes wrong. Authenticity generates engagement.
+
+46. **Reactivation Emails** - Win back churned or inactive users with targeted campaigns.
+
+47. **Founder Welcome Email** - Personal welcome emails from founders create connection.
+
+48. **Dynamic Email Capture** - Smart email capture that adapts to user behavior. Exit intent, scroll depth triggers.
+
+49. **Monthly Newsletters** - Consistent newsletters keep your brand top-of-mind.
+
+50. **Inbox Placement** - Technical email optimization for deliverability. Authentication and list hygiene.
+
+51. **Onboarding Emails** - Guide new users to activation with targeted sequences.
+
+52. **Win-back Emails** - Re-engage churned users with compelling reasons to return.
+
+53. **Trial Reactivation** - Expired trials aren't lost causes. Targeted campaigns can recover them.
+
+---
+
+## Partnerships & Programs (54-64)
+
+54. **Affiliate Discovery Through Backlinks** - Find potential affiliates by analyzing who links to competitors.
+
+55. **Influencer Whitelisting** - Run ads through influencer accounts for authentic reach.
+
+56. **Reseller Programs** - Enable agencies to resell your product. White-label options create distribution partners.
+
+57. **Expert Networks** - Build networks of certified experts who implement your product.
+
+58. **Newsletter Swaps** - Exchange promotional mentions with complementary newsletters.
+
+59. **Article Quotes** - Contribute expert quotes to journalists. HARO connects experts with writers.
+
+60. **Pixel Sharing** - Partner with complementary companies to share remarketing audiences.
+
+61. **Shared Slack Channels** - Create shared channels with partners and customers.
+
+62. **Affiliate Program** - Structured commission programs for referrers.
+
+63. **Integration Marketing** - Joint marketing with integration partners.
+
+64. **Community Sponsorship** - Sponsor relevant communities, newsletters, or publications.
+
+---
+
+## Events & Speaking (65-72)
+
+65. **Live Webinars** - Educational webinars demonstrate expertise while generating leads.
+
+66. **Virtual Summits** - Multi-speaker online events attract audiences through varied perspectives.
+
+67. **Roadshows** - Take your product on the road to meet customers directly.
+
+68. **Local Meetups** - Host or attend local meetups in key markets.
+
+69. **Meetup Sponsorship** - Sponsor relevant meetups to reach engaged local audiences.
+
+70. **Conference Speaking** - Speak at industry conferences to reach engaged audiences.
+
+71. **Conferences** - Host your own conference to become the center of your industry.
+
+72. **Conference Sponsorship** - Sponsor relevant conferences for brand visibility.
+
+---
+
+## PR & Media (73-76)
+
+73. **Media Acquisitions as Marketing** - Acquire newsletters, podcasts, or publications in your space.
+
+74. **Press Coverage** - Pitch newsworthy stories to relevant publications.
+
+75. **Fundraising PR** - Leverage funding announcements for press coverage.
+
+76. **Documentaries** - Create documentary content exploring your industry or customers.
+
+---
+
+## Launches & Promotions (77-86)
+
+77. **Black Friday Promotions** - Annual deals create urgency and acquisition spikes.
+
+78. **Product Hunt Launch** - Structured Product Hunt launches reach early adopters.
+
+79. **Early-Access Referrals** - Reward referrals with earlier access during launches.
+
+80. **New Year Promotions** - New Year brings fresh budgets and goal-setting energy.
+
+81. **Early Access Pricing** - Launch with discounted early access tiers.
+
+82. **Product Hunt Alternatives** - Launch on BetaList, Launching Next, AlternativeTo.
+
+83. **Twitter Giveaways** - Engagement-boosting giveaways that require follows or retweets.
+
+84. **Giveaways** - Strategic giveaways attract attention and capture leads.
+
+85. **Vacation Giveaways** - Grand prize giveaways generate massive engagement.
+
+86. **Lifetime Deals** - One-time payment deals generate cash and users.
+
+---
+
+## Product-Led Growth (87-96)
+
+87. **Powered By Marketing** - "Powered by [Your Product]" badges create free impressions.
+
+88. **Free Migrations** - Offer free migration services from competitors.
+
+89. **Contract Buyouts** - Pay to exit competitor contracts.
+
+90. **One-Click Registration** - Minimize signup friction with OAuth options.
+
+91. **In-App Upsells** - Strategic upgrade prompts within the product experience.
+
+92. **Newsletter Referrals** - Built-in referral programs for newsletters.
+
+93. **Viral Loops** - Product mechanics that naturally encourage sharing.
+
+94. **Offboarding Flows** - Optimize cancellation flows to retain or learn.
+
+95. **Concierge Setup** - White-glove onboarding for high-value accounts.
+
+96. **Onboarding Optimization** - Continuous improvement of new user experience.
+
+---
+
+## Content Formats (97-109)
+
+97. **Playlists as Marketing** - Create Spotify playlists for your audience.
+
+98. **Template Marketing** - Offer free templates users can immediately use.
+
+99. **Graphic Novel Marketing** - Transform complex stories into visual narratives.
+
+100. **Promo Videos** - High-quality promotional videos showcase your product.
+
+101. **Industry Interviews** - Interview customers, experts, and thought leaders.
+
+102. **Social Screenshots** - Design shareable screenshot templates for social proof.
+
+103. **Online Courses** - Educational courses establish authority while generating leads.
+
+104. **Book Marketing** - Author a book establishing expertise in your domain.
+
+105. **Annual Reports** - Publish annual reports showcasing industry data and trends.
+
+106. **End of Year Wraps** - Personalized year-end summaries users want to share.
+
+107. **Podcasts** - Launch a podcast reaching audiences during commutes.
+
+108. **Changelogs** - Public changelogs showcase product momentum.
+
+109. **Public Demos** - Live product demonstrations showing real usage.
+
+---
+
+## Unconventional & Creative (110-122)
+
+110. **Awards as Marketing** - Create industry awards positioning your brand as tastemaker.
+
+111. **Challenges as Marketing** - Launch viral challenges that spread organically.
+
+112. **Reality TV Marketing** - Create reality-show style content following real customers.
+
+113. **Controversy as Marketing** - Strategic positioning against industry norms.
+
+114. **Moneyball Marketing** - Data-driven marketing finding undervalued channels.
+
+115. **Curation as Marketing** - Curate valuable resources for your audience.
+
+116. **Grants as Marketing** - Offer grants to customers or community members.
+
+117. **Product Competitions** - Sponsor competitions using your product.
+
+118. **Cameo Marketing** - Use Cameo celebrities for personalized messages.
+
+119. **OOH Advertising** - Out-of-home advertising—billboards, transit ads.
+
+120. **Marketing Stunts** - Bold, attention-grabbing marketing moments.
+
+121. **Guerrilla Marketing** - Unconventional, low-cost marketing in unexpected places.
+
+122. **Humor Marketing** - Use humor to stand out and create memorability.
+
+---
+
+## Platforms & Marketplaces (123-130)
+
+123. **Open Source as Marketing** - Open-source components or tools build developer goodwill.
+
+124. **App Store Optimization** - Optimize app store listings for discoverability.
+
+125. **App Marketplaces** - List in Salesforce AppExchange, Shopify App Store, etc.
+
+126. **YouTube Reviews** - Get YouTubers to review your product.
+
+127. **YouTube Channel** - Build a YouTube presence with tutorials and thought leadership.
+
+128. **Source Platforms** - Submit to G2, Capterra, GetApp, and similar directories.
+
+129. **Review Sites** - Actively manage presence on review platforms.
+
+130. **Live Audio** - Host Twitter Spaces, Clubhouse, or LinkedIn Audio discussions.
+
+---
+
+## International & Localization (131-132)
+
+131. **International Expansion** - Expand to new geographic markets with localization.
+
+132. **Price Localization** - Adjust pricing for local purchasing power.
+
+---
+
+## Developer & Technical (133-136)
+
+133. **Investor Marketing** - Market to investors for portfolio introductions.
+
+134. **Certifications** - Create certification programs validating expertise.
+
+135. **Support as Marketing** - Exceptional support creates stories customers share.
+
+136. **Developer Relations** - Build relationships with developer communities.
+
+---
+
+## Audience-Specific (137-139)
+
+137. **Two-Sided Referrals** - Reward both referrer and referred.
+
+138. **Podcast Tours** - Guest on multiple podcasts reaching your target audience.
+
+139. **Customer Language** - Use the exact words your customers use in marketing.
diff --git a/personas/_shared/community-skills/marketing-psychology/SKILL.md b/personas/_shared/community-skills/marketing-psychology/SKILL.md
new file mode 100644
index 0000000..5b23873
--- /dev/null
+++ b/personas/_shared/community-skills/marketing-psychology/SKILL.md
@@ -0,0 +1,455 @@
+---
+name: marketing-psychology
+description: "When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context."
+metadata:
+ version: 1.1.0
+---
+
+# Marketing Psychology & Mental Models
+
+You are an expert in applying psychological principles and mental models to marketing. Your goal is to help users understand why people buy, how to influence behavior ethically, and how to make better marketing decisions.
+
+## How to Use This Skill
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before applying mental models. Use that context to tailor recommendations to the specific product and audience.
+
+Mental models are thinking tools that help you make better decisions, understand customer behavior, and create more effective marketing. When helping users:
+
+1. Identify which mental models apply to their situation
+2. Explain the psychology behind the model
+3. Provide specific marketing applications
+4. Suggest how to implement ethically
+
+---
+
+## Foundational Thinking Models
+
+These models sharpen your strategy and help you solve the right problems.
+
+### First Principles
+Break problems down to basic truths and build solutions from there. Instead of copying competitors, ask "why" repeatedly to find root causes. Use the 5 Whys technique to tunnel down to what really matters.
+
+**Marketing application**: Don't assume you need content marketing because competitors do. Ask why you need it, what problem it solves, and whether there's a better solution.
+
+### Jobs to Be Done
+People don't buy products—they "hire" them to get a job done. Focus on the outcome customers want, not features.
+
+**Marketing application**: A drill buyer doesn't want a drill—they want a hole. Frame your product around the job it accomplishes, not its specifications.
+
+### Circle of Competence
+Know what you're good at and stay within it. Venture outside only with proper learning or expert help.
+
+**Marketing application**: Don't chase every channel. Double down where you have genuine expertise and competitive advantage.
+
+### Inversion
+Instead of asking "How do I succeed?", ask "What would guarantee failure?" Then avoid those things.
+
+**Marketing application**: List everything that would make your campaign fail—confusing messaging, wrong audience, slow landing page—then systematically prevent each.
+
+### Occam's Razor
+The simplest explanation is usually correct. Avoid overcomplicating strategies or attributing results to complex causes when simple ones suffice.
+
+**Marketing application**: If conversions dropped, check the obvious first (broken form, page speed) before assuming complex attribution issues.
+
+### Pareto Principle (80/20 Rule)
+Roughly 80% of results come from 20% of efforts. Identify and focus on the vital few.
+
+**Marketing application**: Find the 20% of channels, customers, or content driving 80% of results. Cut or reduce the rest.
+
+### Local vs. Global Optima
+A local optimum is the best solution nearby, but a global optimum is the best overall. Don't get stuck optimizing the wrong thing.
+
+**Marketing application**: Optimizing email subject lines (local) won't help if email isn't the right channel (global). Zoom out before zooming in.
+
+### Theory of Constraints
+Every system has one bottleneck limiting throughput. Find and fix that constraint before optimizing elsewhere.
+
+**Marketing application**: If your funnel converts well but traffic is low, more conversion optimization won't help. Fix the traffic bottleneck first.
+
+### Opportunity Cost
+Every choice has a cost—what you give up by not choosing alternatives. Consider what you're saying no to.
+
+**Marketing application**: Time spent on a low-ROI channel is time not spent on high-ROI activities. Always compare against alternatives.
+
+### Law of Diminishing Returns
+After a point, additional investment yields progressively smaller gains.
+
+**Marketing application**: The 10th blog post won't have the same impact as the first. Know when to diversify rather than double down.
+
+### Second-Order Thinking
+Consider not just immediate effects, but the effects of those effects.
+
+**Marketing application**: A flash sale boosts revenue (first order) but may train customers to wait for discounts (second order).
+
+### Map ≠ Territory
+Models and data represent reality but aren't reality itself. Don't confuse your analytics dashboard with actual customer experience.
+
+**Marketing application**: Your customer persona is a useful model, but real customers are more complex. Stay in touch with actual users.
+
+### Probabilistic Thinking
+Think in probabilities, not certainties. Estimate likelihoods and plan for multiple outcomes.
+
+**Marketing application**: Don't bet everything on one campaign. Spread risk and plan for scenarios where your primary strategy underperforms.
+
+### Barbell Strategy
+Combine extreme safety with small high-risk/high-reward bets. Avoid the mediocre middle.
+
+**Marketing application**: Put 80% of budget into proven channels, 20% into experimental bets. Avoid moderate-risk, moderate-reward middle.
+
+---
+
+## Understanding Buyers & Human Psychology
+
+These models explain how customers think, decide, and behave.
+
+### Fundamental Attribution Error
+People attribute others' behavior to character, not circumstances. "They didn't buy because they're not serious" vs. "The checkout was confusing."
+
+**Marketing application**: When customers don't convert, examine your process before blaming them. The problem is usually situational, not personal.
+
+### Mere Exposure Effect
+People prefer things they've seen before. Familiarity breeds liking.
+
+**Marketing application**: Consistent brand presence builds preference over time. Repetition across channels creates comfort and trust.
+
+### Availability Heuristic
+People judge likelihood by how easily examples come to mind. Recent or vivid events seem more common.
+
+**Marketing application**: Case studies and testimonials make success feel more achievable. Make positive outcomes easy to imagine.
+
+### Confirmation Bias
+People seek information confirming existing beliefs and ignore contradictory evidence.
+
+**Marketing application**: Understand what your audience already believes and align messaging accordingly. Fighting beliefs head-on rarely works.
+
+### The Lindy Effect
+The longer something has survived, the longer it's likely to continue. Old ideas often outlast new ones.
+
+**Marketing application**: Proven marketing principles (clear value props, social proof) outlast trendy tactics. Don't abandon fundamentals for fads.
+
+### Mimetic Desire
+People want things because others want them. Desire is socially contagious.
+
+**Marketing application**: Show that desirable people want your product. Waitlists, exclusivity, and social proof trigger mimetic desire.
+
+### Sunk Cost Fallacy
+People continue investing in something because of past investment, even when it's no longer rational.
+
+**Marketing application**: Know when to kill underperforming campaigns. Past spend shouldn't justify future spend if results aren't there.
+
+### Endowment Effect
+People value things more once they own them.
+
+**Marketing application**: Free trials, samples, and freemium models let customers "own" the product, making them reluctant to give it up.
+
+### IKEA Effect
+People value things more when they've put effort into creating them.
+
+**Marketing application**: Let customers customize, configure, or build something. Their investment increases perceived value and commitment.
+
+### Zero-Price Effect
+Free isn't just a low price—it's psychologically different. "Free" triggers irrational preference.
+
+**Marketing application**: Free tiers, free trials, and free shipping have disproportionate appeal. The jump from $1 to $0 is bigger than $2 to $1.
+
+### Hyperbolic Discounting / Present Bias
+People strongly prefer immediate rewards over future ones, even when waiting is more rational.
+
+**Marketing application**: Emphasize immediate benefits ("Start saving time today") over future ones ("You'll see ROI in 6 months").
+
+### Status-Quo Bias
+People prefer the current state of affairs. Change requires effort and feels risky.
+
+**Marketing application**: Reduce friction to switch. Make the transition feel safe and easy. "Import your data in one click."
+
+### Default Effect
+People tend to accept pre-selected options. Defaults are powerful.
+
+**Marketing application**: Pre-select the plan you want customers to choose. Opt-out beats opt-in for subscriptions (ethically applied).
+
+### Paradox of Choice
+Too many options overwhelm and paralyze. Fewer choices often lead to more decisions.
+
+**Marketing application**: Limit options. Three pricing tiers beat seven. Recommend a single "best for most" option.
+
+### Goal-Gradient Effect
+People accelerate effort as they approach a goal. Progress visualization motivates action.
+
+**Marketing application**: Show progress bars, completion percentages, and "almost there" messaging to drive completion.
+
+### Peak-End Rule
+People judge experiences by the peak (best or worst moment) and the end, not the average.
+
+**Marketing application**: Design memorable peaks (surprise upgrades, delightful moments) and strong endings (thank you pages, follow-up emails).
+
+### Zeigarnik Effect
+Unfinished tasks occupy the mind more than completed ones. Open loops create tension.
+
+**Marketing application**: "You're 80% done" creates pull to finish. Incomplete profiles, abandoned carts, and cliffhangers leverage this.
+
+### Pratfall Effect
+Competent people become more likable when they show a small flaw. Perfection is less relatable.
+
+**Marketing application**: Admitting a weakness ("We're not the cheapest, but...") can increase trust and differentiation.
+
+### Curse of Knowledge
+Once you know something, you can't imagine not knowing it. Experts struggle to explain simply.
+
+**Marketing application**: Your product seems obvious to you but confusing to newcomers. Test copy with people unfamiliar with your space.
+
+### Mental Accounting
+People treat money differently based on its source or intended use, even though money is fungible.
+
+**Marketing application**: Frame costs in favorable mental accounts. "$3/day" feels different than "$90/month" even though it's the same.
+
+### Regret Aversion
+People avoid actions that might cause regret, even if the expected outcome is positive.
+
+**Marketing application**: Address regret directly. Money-back guarantees, free trials, and "no commitment" messaging reduce regret fear.
+
+### Bandwagon Effect / Social Proof
+People follow what others are doing. Popularity signals quality and safety.
+
+**Marketing application**: Show customer counts, testimonials, logos, reviews, and "trending" indicators. Numbers create confidence.
+
+---
+
+## Influencing Behavior & Persuasion
+
+These models help you ethically influence customer decisions.
+
+### Reciprocity Principle
+People feel obligated to return favors. Give first, and people want to give back.
+
+**Marketing application**: Free content, free tools, and generous free tiers create reciprocal obligation. Give value before asking for anything.
+
+### Commitment & Consistency
+Once people commit to something, they want to stay consistent with that commitment.
+
+**Marketing application**: Get small commitments first (email signup, free trial). People who've taken one step are more likely to take the next.
+
+### Authority Bias
+People defer to experts and authority figures. Credentials and expertise create trust.
+
+**Marketing application**: Feature expert endorsements, certifications, "featured in" logos, and thought leadership content.
+
+### Liking / Similarity Bias
+People say yes to those they like and those similar to themselves.
+
+**Marketing application**: Use relatable spokespeople, founder stories, and community language. "Built by marketers for marketers" signals similarity.
+
+### Unity Principle
+Shared identity drives influence. "One of us" is powerful.
+
+**Marketing application**: Position your brand as part of the customer's tribe. Use insider language and shared values.
+
+### Scarcity / Urgency Heuristic
+Limited availability increases perceived value. Scarcity signals desirability.
+
+**Marketing application**: Limited-time offers, low-stock warnings, and exclusive access create urgency. Only use when genuine.
+
+### Foot-in-the-Door Technique
+Start with a small request, then escalate. Compliance with small requests leads to compliance with larger ones.
+
+**Marketing application**: Free trial → paid plan → annual plan → enterprise. Each step builds on the last.
+
+### Door-in-the-Face Technique
+Start with an unreasonably large request, then retreat to what you actually want. The contrast makes the second request seem reasonable.
+
+**Marketing application**: Show enterprise pricing first, then reveal the affordable starter plan. The contrast makes it feel like a deal.
+
+### Loss Aversion / Prospect Theory
+Losses feel roughly twice as painful as equivalent gains feel good. People will work harder to avoid losing than to gain.
+
+**Marketing application**: Frame in terms of what they'll lose by not acting. "Don't miss out" beats "You could gain."
+
+### Anchoring Effect
+The first number people see heavily influences subsequent judgments.
+
+**Marketing application**: Show the higher price first (original price, competitor price, enterprise tier) to anchor expectations.
+
+### Decoy Effect
+Adding a third, inferior option makes one of the original two look better.
+
+**Marketing application**: A "decoy" pricing tier that's clearly worse value makes your preferred tier look like the obvious choice.
+
+### Framing Effect
+How something is presented changes how it's perceived. Same facts, different frames.
+
+**Marketing application**: "90% success rate" vs. "10% failure rate" are identical but feel different. Frame positively.
+
+### Contrast Effect
+Things seem different depending on what they're compared to.
+
+**Marketing application**: Show the "before" state clearly. The contrast with your "after" makes improvements vivid.
+
+---
+
+## Pricing Psychology
+
+These models specifically address how people perceive and respond to prices.
+
+### Charm Pricing / Left-Digit Effect
+Prices ending in 9 seem significantly lower than the next round number. $99 feels much cheaper than $100.
+
+**Marketing application**: Use .99 or .95 endings for value-focused products. The left digit dominates perception.
+
+### Rounded-Price (Fluency) Effect
+Round numbers feel premium and are easier to process. $100 signals quality; $99 signals value.
+
+**Marketing application**: Use round prices for premium products ($500/month), charm prices for value products ($497/month).
+
+### Rule of 100
+For prices under $100, percentage discounts seem larger ("20% off"). For prices over $100, absolute discounts seem larger ("$50 off").
+
+**Marketing application**: $80 product: "20% off" beats "$16 off." $500 product: "$100 off" beats "20% off."
+
+### Price Relativity / Good-Better-Best
+People judge prices relative to options presented. A middle tier seems reasonable between cheap and expensive.
+
+**Marketing application**: Three tiers where the middle is your target. The expensive tier makes it look reasonable; the cheap tier provides an anchor.
+
+### Mental Accounting (Pricing)
+Framing the same price differently changes perception.
+
+**Marketing application**: "$1/day" feels cheaper than "$30/month." "Less than your morning coffee" reframes the expense.
+
+---
+
+## Design & Delivery Models
+
+These models help you design effective marketing systems.
+
+### Hick's Law
+Decision time increases with the number and complexity of choices. More options = slower decisions = more abandonment.
+
+**Marketing application**: Simplify choices. One clear CTA beats three. Fewer form fields beat more.
+
+### AIDA Funnel
+Attention → Interest → Desire → Action. The classic customer journey model.
+
+**Marketing application**: Structure pages and campaigns to move through each stage. Capture attention before building desire.
+
+### Rule of 7
+Prospects need roughly 7 touchpoints before converting. One ad rarely converts; sustained presence does.
+
+**Marketing application**: Build multi-touch campaigns across channels. Retargeting, email sequences, and consistent presence compound.
+
+### Nudge Theory / Choice Architecture
+Small changes in how choices are presented significantly influence decisions.
+
+**Marketing application**: Default selections, strategic ordering, and friction reduction guide behavior without restricting choice.
+
+### BJ Fogg Behavior Model
+Behavior = Motivation × Ability × Prompt. All three must be present for action.
+
+**Marketing application**: High motivation but hard to do = won't happen. Easy to do but no prompt = won't happen. Design for all three.
+
+### EAST Framework
+Make desired behaviors: Easy, Attractive, Social, Timely.
+
+**Marketing application**: Reduce friction (easy), make it appealing (attractive), show others doing it (social), ask at the right moment (timely).
+
+### COM-B Model
+Behavior requires: Capability, Opportunity, Motivation.
+
+**Marketing application**: Can they do it (capability)? Is the path clear (opportunity)? Do they want to (motivation)? Address all three.
+
+### Activation Energy
+The initial energy required to start something. High activation energy prevents action even if the task is easy overall.
+
+**Marketing application**: Reduce starting friction. Pre-fill forms, offer templates, show quick wins. Make the first step trivially easy.
+
+### North Star Metric
+One metric that best captures the value you deliver to customers. Focus creates alignment.
+
+**Marketing application**: Identify your North Star (active users, completed projects, revenue per customer) and align all efforts toward it.
+
+### The Cobra Effect
+When incentives backfire and produce the opposite of intended results.
+
+**Marketing application**: Test incentive structures. A referral bonus might attract low-quality referrals gaming the system.
+
+---
+
+## Growth & Scaling Models
+
+These models explain how marketing compounds and scales.
+
+### Feedback Loops
+Output becomes input, creating cycles. Positive loops accelerate growth; negative loops create decline.
+
+**Marketing application**: Build virtuous cycles: more users → more content → better SEO → more users. Identify and strengthen positive loops.
+
+### Compounding
+Small, consistent gains accumulate into large results over time. Early gains matter most.
+
+**Marketing application**: Consistent content, SEO, and brand building compound. Start early; benefits accumulate exponentially.
+
+### Network Effects
+A product becomes more valuable as more people use it.
+
+**Marketing application**: Design features that improve with more users: shared workspaces, integrations, marketplaces, communities.
+
+### Flywheel Effect
+Sustained effort creates momentum that eventually maintains itself. Hard to start, easy to maintain.
+
+**Marketing application**: Content → traffic → leads → customers → case studies → more content. Each element powers the next.
+
+### Switching Costs
+The price (time, money, effort, data) of changing to a competitor. High switching costs create retention.
+
+**Marketing application**: Increase switching costs ethically: integrations, data accumulation, workflow customization, team adoption.
+
+### Exploration vs. Exploitation
+Balance trying new things (exploration) with optimizing what works (exploitation).
+
+**Marketing application**: Don't abandon working channels for shiny new ones, but allocate some budget to experiments.
+
+### Critical Mass / Tipping Point
+The threshold after which growth becomes self-sustaining.
+
+**Marketing application**: Focus resources on reaching critical mass in one segment before expanding. Depth before breadth.
+
+### Survivorship Bias
+Focusing on successes while ignoring failures that aren't visible.
+
+**Marketing application**: Study failed campaigns, not just successful ones. The viral hit you're copying had 99 failures you didn't see.
+
+---
+
+## Quick Reference
+
+When facing a marketing challenge, consider:
+
+| Challenge | Relevant Models |
+|-----------|-----------------|
+| Low conversions | Hick's Law, Activation Energy, BJ Fogg, Friction |
+| Price objections | Anchoring, Framing, Mental Accounting, Loss Aversion |
+| Building trust | Authority, Social Proof, Reciprocity, Pratfall Effect |
+| Increasing urgency | Scarcity, Loss Aversion, Zeigarnik Effect |
+| Retention/churn | Endowment Effect, Switching Costs, Status-Quo Bias |
+| Growth stalling | Theory of Constraints, Local vs Global Optima, Compounding |
+| Decision paralysis | Paradox of Choice, Default Effect, Nudge Theory |
+| Onboarding | Goal-Gradient, IKEA Effect, Commitment & Consistency |
+
+---
+
+## Task-Specific Questions
+
+1. What specific behavior are you trying to influence?
+2. What does your customer believe before encountering your marketing?
+3. Where in the journey (awareness → consideration → decision) is this?
+4. What's currently preventing the desired action?
+5. Have you tested this with real customers?
+
+---
+
+## Related Skills
+
+- **page-cro**: Apply psychology to page optimization
+- **copywriting**: Write copy using psychological principles
+- **popup-cro**: Use triggers and psychology in popups
+- **pricing-page optimization**: See page-cro for pricing psychology
+- **ab-test-setup**: Test psychological hypotheses
diff --git a/personas/_shared/community-skills/next-best-practices/SKILL.md b/personas/_shared/community-skills/next-best-practices/SKILL.md
new file mode 100644
index 0000000..437896b
--- /dev/null
+++ b/personas/_shared/community-skills/next-best-practices/SKILL.md
@@ -0,0 +1,153 @@
+---
+name: next-best-practices
+description: Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
+user-invocable: false
+---
+
+# Next.js Best Practices
+
+Apply these rules when writing or reviewing Next.js code.
+
+## File Conventions
+
+See [file-conventions.md](./file-conventions.md) for:
+- Project structure and special files
+- Route segments (dynamic, catch-all, groups)
+- Parallel and intercepting routes
+- Middleware rename in v16 (middleware → proxy)
+
+## RSC Boundaries
+
+Detect invalid React Server Component patterns.
+
+See [rsc-boundaries.md](./rsc-boundaries.md) for:
+- Async client component detection (invalid)
+- Non-serializable props detection
+- Server Action exceptions
+
+## Async Patterns
+
+Next.js 15+ async API changes.
+
+See [async-patterns.md](./async-patterns.md) for:
+- Async `params` and `searchParams`
+- Async `cookies()` and `headers()`
+- Migration codemod
+
+## Runtime Selection
+
+See [runtime-selection.md](./runtime-selection.md) for:
+- Default to Node.js runtime
+- When Edge runtime is appropriate
+
+## Directives
+
+See [directives.md](./directives.md) for:
+- `'use client'`, `'use server'` (React)
+- `'use cache'` (Next.js)
+
+## Functions
+
+See [functions.md](./functions.md) for:
+- Navigation hooks: `useRouter`, `usePathname`, `useSearchParams`, `useParams`
+- Server functions: `cookies`, `headers`, `draftMode`, `after`
+- Generate functions: `generateStaticParams`, `generateMetadata`
+
+## Error Handling
+
+See [error-handling.md](./error-handling.md) for:
+- `error.tsx`, `global-error.tsx`, `not-found.tsx`
+- `redirect`, `permanentRedirect`, `notFound`
+- `forbidden`, `unauthorized` (auth errors)
+- `unstable_rethrow` for catch blocks
+
+## Data Patterns
+
+See [data-patterns.md](./data-patterns.md) for:
+- Server Components vs Server Actions vs Route Handlers
+- Avoiding data waterfalls (`Promise.all`, Suspense, preload)
+- Client component data fetching
+
+## Route Handlers
+
+See [route-handlers.md](./route-handlers.md) for:
+- `route.ts` basics
+- GET handler conflicts with `page.tsx`
+- Environment behavior (no React DOM)
+- When to use vs Server Actions
+
+## Metadata & OG Images
+
+See [metadata.md](./metadata.md) for:
+- Static and dynamic metadata
+- `generateMetadata` function
+- OG image generation with `next/og`
+- File-based metadata conventions
+
+## Image Optimization
+
+See [image.md](./image.md) for:
+- Always use `next/image` over `Theme: {theme}
+} +``` + +--- + +## `use cache` Directive + +### File Level + +```tsx +'use cache' + +export default async function Page() { + // Entire page is cached + const data = await fetchData() + return! | logical not |
+
+## Properties
+
+### Three Types of Properties
+
+1. **Note properties** - From frontmatter: `note.author` or just `author`
+2. **File properties** - File metadata: `file.name`, `file.mtime`, etc.
+3. **Formula properties** - Computed values: `formula.my_formula`
+
+### File Properties Reference
+
+| Property | Type | Description |
+|----------|------|-------------|
+| `file.name` | String | File name |
+| `file.basename` | String | File name without extension |
+| `file.path` | String | Full path to file |
+| `file.folder` | String | Parent folder path |
+| `file.ext` | String | File extension |
+| `file.size` | Number | File size in bytes |
+| `file.ctime` | Date | Created time |
+| `file.mtime` | Date | Modified time |
+| `file.tags` | List | All tags in file |
+| `file.links` | List | Internal links in file |
+| `file.backlinks` | List | Files linking to this file |
+| `file.embeds` | List | Embeds in the note |
+| `file.properties` | Object | All frontmatter properties |
+
+### The `this` Keyword
+
+- In main content area: refers to the base file itself
+- When embedded: refers to the embedding file
+- In sidebar: refers to the active file in main content
+
+## Formula Syntax
+
+Formulas compute values from properties. Defined in the `formulas` section.
+
+```yaml
+formulas:
+ # Simple arithmetic
+ total: "price * quantity"
+
+ # Conditional logic
+ status_icon: 'if(done, "✅", "⏳")'
+
+ # String formatting
+ formatted_price: 'if(price, price.toFixed(2) + " dollars")'
+
+ # Date formatting
+ created: 'file.ctime.format("YYYY-MM-DD")'
+
+ # Calculate days since created (use .days for Duration)
+ days_old: '(now() - file.ctime).days'
+
+ # Calculate days until due date
+ days_until_due: 'if(due_date, (date(due_date) - today()).days, "")'
+```
+
+## Key Functions
+
+Most commonly used functions. For the complete reference of all types (Date, String, Number, List, File, Link, Object, RegExp), see [FUNCTIONS_REFERENCE.md](references/FUNCTIONS_REFERENCE.md).
+
+| Function | Signature | Description |
+|----------|-----------|-------------|
+| `date()` | `date(string): date` | Parse string to date (`YYYY-MM-DD HH:mm:ss`) |
+| `now()` | `now(): date` | Current date and time |
+| `today()` | `today(): date` | Current date (time = 00:00:00) |
+| `if()` | `if(condition, trueResult, falseResult?)` | Conditional |
+| `duration()` | `duration(string): duration` | Parse duration string |
+| `file()` | `file(path): file` | Get file object |
+| `link()` | `link(path, display?): Link` | Create a link |
+
+### Duration Type
+
+When subtracting two dates, the result is a **Duration** type (not a number).
+
+**Duration Fields:** `duration.days`, `duration.hours`, `duration.minutes`, `duration.seconds`, `duration.milliseconds`
+
+**IMPORTANT:** Duration does NOT support `.round()`, `.floor()`, `.ceil()` directly. Access a numeric field first (like `.days`), then apply number functions.
+
+```yaml
+# CORRECT: Calculate days between dates
+"(date(due_date) - today()).days" # Returns number of days
+"(now() - file.ctime).days" # Days since created
+"(date(due_date) - today()).days.round(0)" # Rounded days
+
+# WRONG - will cause error:
+# "((date(due) - today()) / 86400000).round(0)" # Duration doesn't support division then round
+```
+
+### Date Arithmetic
+
+```yaml
+# Duration units: y/year/years, M/month/months, d/day/days,
+# w/week/weeks, h/hour/hours, m/minute/minutes, s/second/seconds
+"now() + \"1 day\"" # Tomorrow
+"today() + \"7d\"" # A week from today
+"now() - file.ctime" # Returns Duration
+"(now() - file.ctime).days" # Get days as number
+```
+
+## View Types
+
+### Table View
+
+```yaml
+views:
+ - type: table
+ name: "My Table"
+ order:
+ - file.name
+ - status
+ - due_date
+ summaries:
+ price: Sum
+ count: Average
+```
+
+### Cards View
+
+```yaml
+views:
+ - type: cards
+ name: "Gallery"
+ order:
+ - file.name
+ - cover_image
+ - description
+```
+
+### List View
+
+```yaml
+views:
+ - type: list
+ name: "Simple List"
+ order:
+ - file.name
+ - status
+```
+
+### Map View
+
+Requires latitude/longitude properties and the Maps community plugin.
+
+```yaml
+views:
+ - type: map
+ name: "Locations"
+ # Map-specific settings for lat/lng properties
+```
+
+## Default Summary Formulas
+
+| Name | Input Type | Description |
+|------|------------|-------------|
+| `Average` | Number | Mathematical mean |
+| `Min` | Number | Smallest number |
+| `Max` | Number | Largest number |
+| `Sum` | Number | Sum of all numbers |
+| `Range` | Number | Max - Min |
+| `Median` | Number | Mathematical median |
+| `Stddev` | Number | Standard deviation |
+| `Earliest` | Date | Earliest date |
+| `Latest` | Date | Latest date |
+| `Range` | Date | Latest - Earliest |
+| `Checked` | Boolean | Count of true values |
+| `Unchecked` | Boolean | Count of false values |
+| `Empty` | Any | Count of empty values |
+| `Filled` | Any | Count of non-empty values |
+| `Unique` | Any | Count of unique values |
+
+## Complete Examples
+
+### Task Tracker Base
+
+```yaml
+filters:
+ and:
+ - file.hasTag("task")
+ - 'file.ext == "md"'
+
+formulas:
+ days_until_due: 'if(due, (date(due) - today()).days, "")'
+ is_overdue: 'if(due, date(due) < today() && status != "done", false)'
+ priority_label: 'if(priority == 1, "🔴 High", if(priority == 2, "🟡 Medium", "🟢 Low"))'
+
+properties:
+ status:
+ displayName: Status
+ formula.days_until_due:
+ displayName: "Days Until Due"
+ formula.priority_label:
+ displayName: Priority
+
+views:
+ - type: table
+ name: "Active Tasks"
+ filters:
+ and:
+ - 'status != "done"'
+ order:
+ - file.name
+ - status
+ - formula.priority_label
+ - due
+ - formula.days_until_due
+ groupBy:
+ property: status
+ direction: ASC
+ summaries:
+ formula.days_until_due: Average
+
+ - type: table
+ name: "Completed"
+ filters:
+ and:
+ - 'status == "done"'
+ order:
+ - file.name
+ - completed_date
+```
+
+### Reading List Base
+
+```yaml
+filters:
+ or:
+ - file.hasTag("book")
+ - file.hasTag("article")
+
+formulas:
+ reading_time: 'if(pages, (pages * 2).toString() + " min", "")'
+ status_icon: 'if(status == "reading", "📖", if(status == "done", "✅", "📚"))'
+ year_read: 'if(finished_date, date(finished_date).year, "")'
+
+properties:
+ author:
+ displayName: Author
+ formula.status_icon:
+ displayName: ""
+ formula.reading_time:
+ displayName: "Est. Time"
+
+views:
+ - type: cards
+ name: "Library"
+ order:
+ - cover
+ - file.name
+ - author
+ - formula.status_icon
+ filters:
+ not:
+ - 'status == "dropped"'
+
+ - type: table
+ name: "Reading List"
+ filters:
+ and:
+ - 'status == "to-read"'
+ order:
+ - file.name
+ - author
+ - pages
+ - formula.reading_time
+```
+
+### Daily Notes Index
+
+```yaml
+filters:
+ and:
+ - file.inFolder("Daily Notes")
+ - '/^\d{4}-\d{2}-\d{2}$/.matches(file.basename)'
+
+formulas:
+ word_estimate: '(file.size / 5).round(0)'
+ day_of_week: 'date(file.basename).format("dddd")'
+
+properties:
+ formula.day_of_week:
+ displayName: "Day"
+ formula.word_estimate:
+ displayName: "~Words"
+
+views:
+ - type: table
+ name: "Recent Notes"
+ limit: 30
+ order:
+ - file.name
+ - formula.day_of_week
+ - formula.word_estimate
+ - file.mtime
+```
+
+## Embedding Bases
+
+Embed in Markdown files:
+
+```markdown
+![[MyBase.base]]
+
+
+![[MyBase.base#View Name]]
+```
+
+## YAML Quoting Rules
+
+- Use single quotes for formulas containing double quotes: `'if(done, "Yes", "No")'`
+- Use double quotes for simple strings: `"My View Name"`
+- Escape nested quotes properly in complex expressions
+
+## Troubleshooting
+
+### YAML Syntax Errors
+
+**Unquoted special characters**: Strings containing `:`, `{`, `}`, `[`, `]`, `,`, `&`, `*`, `#`, `?`, `|`, `-`, `<`, `>`, `=`, `!`, `%`, `@`, `` ` `` must be quoted.
+
+```yaml
+# WRONG - colon in unquoted string
+displayName: Status: Active
+
+# CORRECT
+displayName: "Status: Active"
+```
+
+**Mismatched quotes in formulas**: When a formula contains double quotes, wrap the entire formula in single quotes.
+
+```yaml
+# WRONG - double quotes inside double quotes
+formulas:
+ label: "if(done, "Yes", "No")"
+
+# CORRECT - single quotes wrapping double quotes
+formulas:
+ label: 'if(done, "Yes", "No")'
+```
+
+### Common Formula Errors
+
+**Duration math without field access**: Subtracting dates returns a Duration, not a number. Always access `.days`, `.hours`, etc.
+
+```yaml
+# WRONG - Duration is not a number
+"(now() - file.ctime).round(0)"
+
+# CORRECT - access .days first, then round
+"(now() - file.ctime).days.round(0)"
+```
+
+**Missing null checks**: Properties may not exist on all notes. Use `if()` to guard.
+
+```yaml
+# WRONG - crashes if due_date is empty
+"(date(due_date) - today()).days"
+
+# CORRECT - guard with if()
+'if(due_date, (date(due_date) - today()).days, "")'
+```
+
+**Referencing undefined formulas**: Ensure every `formula.X` in `order` or `properties` has a matching entry in `formulas`.
+
+```yaml
+# This will fail silently if 'total' is not defined in formulas
+order:
+ - formula.total
+
+# Fix: define it
+formulas:
+ total: "price * quantity"
+```
+
+## References
+
+- [Bases Syntax](https://help.obsidian.md/bases/syntax)
+- [Functions](https://help.obsidian.md/bases/functions)
+- [Views](https://help.obsidian.md/bases/views)
+- [Formulas](https://help.obsidian.md/formulas)
+- [Complete Functions Reference](references/FUNCTIONS_REFERENCE.md)
diff --git a/personas/_shared/community-skills/obsidian-bases/references/FUNCTIONS_REFERENCE.md b/personas/_shared/community-skills/obsidian-bases/references/FUNCTIONS_REFERENCE.md
new file mode 100644
index 0000000..047888d
--- /dev/null
+++ b/personas/_shared/community-skills/obsidian-bases/references/FUNCTIONS_REFERENCE.md
@@ -0,0 +1,173 @@
+# Functions Reference
+
+## Global Functions
+
+| Function | Signature | Description |
+|----------|-----------|-------------|
+| `date()` | `date(string): date` | Parse string to date. Format: `YYYY-MM-DD HH:mm:ss` |
+| `duration()` | `duration(string): duration` | Parse duration string |
+| `now()` | `now(): date` | Current date and time |
+| `today()` | `today(): date` | Current date (time = 00:00:00) |
+| `if()` | `if(condition, trueResult, falseResult?)` | Conditional |
+| `min()` | `min(n1, n2, ...): number` | Smallest number |
+| `max()` | `max(n1, n2, ...): number` | Largest number |
+| `number()` | `number(any): number` | Convert to number |
+| `link()` | `link(path, display?): Link` | Create a link |
+| `list()` | `list(element): List` | Wrap in list if not already |
+| `file()` | `file(path): file` | Get file object |
+| `image()` | `image(path): image` | Create image for rendering |
+| `icon()` | `icon(name): icon` | Lucide icon by name |
+| `html()` | `html(string): html` | Render as HTML |
+| `escapeHTML()` | `escapeHTML(string): string` | Escape HTML characters |
+
+## Any Type Functions
+
+| Function | Signature | Description |
+|----------|-----------|-------------|
+| `isTruthy()` | `any.isTruthy(): boolean` | Coerce to boolean |
+| `isType()` | `any.isType(type): boolean` | Check type |
+| `toString()` | `any.toString(): string` | Convert to string |
+
+## Date Functions & Fields
+
+**Fields:** `date.year`, `date.month`, `date.day`, `date.hour`, `date.minute`, `date.second`, `date.millisecond`
+
+| Function | Signature | Description |
+|----------|-----------|-------------|
+| `date()` | `date.date(): date` | Remove time portion |
+| `format()` | `date.format(string): string` | Format with Moment.js pattern |
+| `time()` | `date.time(): string` | Get time as string |
+| `relative()` | `date.relative(): string` | Human-readable relative time |
+| `isEmpty()` | `date.isEmpty(): boolean` | Always false for dates |
+
+## Duration Type
+
+When subtracting two dates, the result is a **Duration** type (not a number). Duration has its own properties and methods.
+
+**Duration Fields:**
+| Field | Type | Description |
+|-------|------|-------------|
+| `duration.days` | Number | Total days in duration |
+| `duration.hours` | Number | Total hours in duration |
+| `duration.minutes` | Number | Total minutes in duration |
+| `duration.seconds` | Number | Total seconds in duration |
+| `duration.milliseconds` | Number | Total milliseconds in duration |
+
+**IMPORTANT:** Duration does NOT support `.round()`, `.floor()`, `.ceil()` directly. You must access a numeric field first (like `.days`), then apply number functions.
+
+```yaml
+# CORRECT: Calculate days between dates
+"(date(due_date) - today()).days" # Returns number of days
+"(now() - file.ctime).days" # Days since created
+
+# CORRECT: Round the numeric result if needed
+"(date(due_date) - today()).days.round(0)" # Rounded days
+"(now() - file.ctime).hours.round(0)" # Rounded hours
+
+# WRONG - will cause error:
+# "((date(due) - today()) / 86400000).round(0)" # Duration doesn't support division then round
+```
+
+## Date Arithmetic
+
+```yaml
+# Duration units: y/year/years, M/month/months, d/day/days,
+# w/week/weeks, h/hour/hours, m/minute/minutes, s/second/seconds
+
+# Add/subtract durations
+"date + \"1M\"" # Add 1 month
+"date - \"2h\"" # Subtract 2 hours
+"now() + \"1 day\"" # Tomorrow
+"today() + \"7d\"" # A week from today
+
+# Subtract dates returns Duration type
+"now() - file.ctime" # Returns Duration
+"(now() - file.ctime).days" # Get days as number
+"(now() - file.ctime).hours" # Get hours as number
+
+# Complex duration arithmetic
+"now() + (duration('1d') * 2)"
+```
+
+## String Functions
+
+**Field:** `string.length`
+
+| Function | Signature | Description |
+|----------|-----------|-------------|
+| `contains()` | `string.contains(value): boolean` | Check substring |
+| `containsAll()` | `string.containsAll(...values): boolean` | All substrings present |
+| `containsAny()` | `string.containsAny(...values): boolean` | Any substring present |
+| `startsWith()` | `string.startsWith(query): boolean` | Starts with query |
+| `endsWith()` | `string.endsWith(query): boolean` | Ends with query |
+| `isEmpty()` | `string.isEmpty(): boolean` | Empty or not present |
+| `lower()` | `string.lower(): string` | To lowercase |
+| `title()` | `string.title(): string` | To Title Case |
+| `trim()` | `string.trim(): string` | Remove whitespace |
+| `replace()` | `string.replace(pattern, replacement): string` | Replace pattern |
+| `repeat()` | `string.repeat(count): string` | Repeat string |
+| `reverse()` | `string.reverse(): string` | Reverse string |
+| `slice()` | `string.slice(start, end?): string` | Substring |
+| `split()` | `string.split(separator, n?): list` | Split to list |
+
+## Number Functions
+
+| Function | Signature | Description |
+|----------|-----------|-------------|
+| `abs()` | `number.abs(): number` | Absolute value |
+| `ceil()` | `number.ceil(): number` | Round up |
+| `floor()` | `number.floor(): number` | Round down |
+| `round()` | `number.round(digits?): number` | Round to digits |
+| `toFixed()` | `number.toFixed(precision): string` | Fixed-point notation |
+| `isEmpty()` | `number.isEmpty(): boolean` | Not present |
+
+## List Functions
+
+**Field:** `list.length`
+
+| Function | Signature | Description |
+|----------|-----------|-------------|
+| `contains()` | `list.contains(value): boolean` | Element exists |
+| `containsAll()` | `list.containsAll(...values): boolean` | All elements exist |
+| `containsAny()` | `list.containsAny(...values): boolean` | Any element exists |
+| `filter()` | `list.filter(expression): list` | Filter by condition (uses `value`, `index`) |
+| `map()` | `list.map(expression): list` | Transform elements (uses `value`, `index`) |
+| `reduce()` | `list.reduce(expression, initial): any` | Reduce to single value (uses `value`, `index`, `acc`) |
+| `flat()` | `list.flat(): list` | Flatten nested lists |
+| `join()` | `list.join(separator): string` | Join to string |
+| `reverse()` | `list.reverse(): list` | Reverse order |
+| `slice()` | `list.slice(start, end?): list` | Sublist |
+| `sort()` | `list.sort(): list` | Sort ascending |
+| `unique()` | `list.unique(): list` | Remove duplicates |
+| `isEmpty()` | `list.isEmpty(): boolean` | No elements |
+
+## File Functions
+
+| Function | Signature | Description |
+|----------|-----------|-------------|
+| `asLink()` | `file.asLink(display?): Link` | Convert to link |
+| `hasLink()` | `file.hasLink(otherFile): boolean` | Has link to file |
+| `hasTag()` | `file.hasTag(...tags): boolean` | Has any of the tags |
+| `hasProperty()` | `file.hasProperty(name): boolean` | Has property |
+| `inFolder()` | `file.inFolder(folder): boolean` | In folder or subfolder |
+
+## Link Functions
+
+| Function | Signature | Description |
+|----------|-----------|-------------|
+| `asFile()` | `link.asFile(): file` | Get file object |
+| `linksTo()` | `link.linksTo(file): boolean` | Links to file |
+
+## Object Functions
+
+| Function | Signature | Description |
+|----------|-----------|-------------|
+| `isEmpty()` | `object.isEmpty(): boolean` | No properties |
+| `keys()` | `object.keys(): list` | List of keys |
+| `values()` | `object.values(): list` | List of values |
+
+## Regular Expression Functions
+
+| Function | Signature | Description |
+|----------|-----------|-------------|
+| `matches()` | `regexp.matches(string): boolean` | Test if matches |
diff --git a/personas/_shared/community-skills/obsidian-cli/SKILL.md b/personas/_shared/community-skills/obsidian-cli/SKILL.md
new file mode 100644
index 0000000..0046c45
--- /dev/null
+++ b/personas/_shared/community-skills/obsidian-cli/SKILL.md
@@ -0,0 +1,106 @@
+---
+name: obsidian-cli
+description: Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
+---
+
+# Obsidian CLI
+
+Use the `obsidian` CLI to interact with a running Obsidian instance. Requires Obsidian to be open.
+
+## Command reference
+
+Run `obsidian help` to see all available commands. This is always up to date. Full docs: https://help.obsidian.md/cli
+
+## Syntax
+
+**Parameters** take a value with `=`. Quote values with spaces:
+
+```bash
+obsidian create name="My Note" content="Hello world"
+```
+
+**Flags** are boolean switches with no value:
+
+```bash
+obsidian create name="My Note" silent overwrite
+```
+
+For multiline content use `\n` for newline and `\t` for tab.
+
+## File targeting
+
+Many commands accept `file` or `path` to target a file. Without either, the active file is used.
+
+- `file=
startTransition(() => onSelect())} />
+
+{item.name}
+ +