`, `

`-`

`, `

`, `
` for all text content\n - Use `class=\"placeholder\"` for areas where charts/tables will be added (render with gray background for visibility)\n - **CRITICAL**: Rasterize gradients and icons as PNG images FIRST using Sharp, then reference in HTML\n - **LAYOUT**: For slides with charts/tables/images, use either full-slide layout or two-column layout for better readability\n3. Create and run a JavaScript file using the [`html2pptx.js`](scripts/html2pptx.js) library to convert HTML slides to PowerPoint and save the presentation\n - Use the `html2pptx()` function to process each HTML file\n - Add charts and tables to placeholder areas using PptxGenJS API\n - Save the presentation using `pptx.writeFile()`\n4. **Visual validation**: Generate thumbnails and inspect for layout issues\n - Create thumbnail grid: `python scripts/thumbnail.py output.pptx workspace/thumbnails --cols 4`\n - Read and carefully examine the thumbnail image for:\n - **Text cutoff**: Text being cut off by header bars, shapes, or slide edges\n - **Text overlap**: Text overlapping with other text or shapes\n - **Positioning issues**: Content too close to slide boundaries or other elements\n - **Contrast issues**: Insufficient contrast between text and backgrounds\n - If issues found, adjust HTML margins/spacing/colors and regenerate the presentation\n - Repeat until all slides are visually correct\n\n## Editing an existing PowerPoint presentation\n\nWhen edit slides in an existing PowerPoint presentation, you need to work with the raw Office Open XML (OOXML) format. This involves unpacking the .pptx file, editing the XML content, and repacking it.\n\n### Workflow\n1. **MANDATORY - READ ENTIRE FILE**: Read [`ooxml.md`](ooxml.md) (~500 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for detailed guidance on OOXML structure and editing workflows before any presentation editing.\n2. Unpack the presentation: `python ooxml/scripts/unpack.py `\n3. Edit the XML files (primarily `ppt/slides/slide{N}.xml` and related files)\n4. **CRITICAL**: Validate immediately after each edit and fix any validation errors before proceeding: `python ooxml/scripts/validate.py --original `\n5. Pack the final presentation: `python ooxml/scripts/pack.py `\n\n## Creating a new PowerPoint presentation **using a template**\n\nWhen you need to create a presentation that follows an existing template's design, you'll need to duplicate and re-arrange template slides before then replacing placeholder context.\n\n### Workflow\n1. **Extract template text AND create visual thumbnail grid**:\n * Extract text: `python -m markitdown template.pptx > template-content.md`\n * Read `template-content.md`: Read the entire file to understand the contents of the template presentation. **NEVER set any range limits when reading this file.**\n * Create thumbnail grids: `python scripts/thumbnail.py template.pptx`\n * See [Creating Thumbnail Grids](#creating-thumbnail-grids) section for more details\n\n2. **Analyze template and save inventory to a file**:\n * **Visual Analysis**: Review thumbnail grid(s) to understand slide layouts, design patterns, and visual structure\n * Create and save a template inventory file at `template-inventory.md` containing:\n ```markdown\n # Template Inventory Analysis\n **Total Slides: [count]**\n **IMPORTANT: Slides are 0-indexed (first slide = 0, last slide = count-1)**\n\n ## [Category Name]\n - Slide 0: [Layout code if available] - Description/purpose\n - Slide 1: [Layout code] - Description/purpose\n - Slide 2: [Layout code] - Description/purpose\n [... EVERY slide must be listed individually with its index ...]\n ```\n * **Using the thumbnail grid**: Reference the visual thumbnails to identify:\n - Layout patterns (title slides, content layouts, section dividers)\n - Image placeholder locations and counts\n - Design consistency across slide groups\n - Visual hierarchy and structure\n * This inventory file is REQUIRED for selecting appropriate templates in the next step\n\n3. **Create presentation outline based on template inventory**:\n * Review available templates from step 2.\n * Choose an intro or title template for the first slide. This should be one of the first templates.\n * Choose safe, text-based layouts for the other slides.\n * **CRITICAL: Match layout structure to actual content**:\n - Single-column layouts: Use for unified narrative or single topic\n - Two-column layouts: Use ONLY when you have exactly 2 distinct items/concepts\n - Three-column layouts: Use ONLY when you have exactly 3 distinct items/concepts\n - Image + text layouts: Use ONLY when you have actual images to insert\n - Quote layouts: Use ONLY for actual quotes from people (with attribution), never for emphasis\n - Never use layouts with more placeholders than you have content\n - If you have 2 items, don't force them into a 3-column layout\n - If you have 4+ items, consider breaking into multiple slides or using a list format\n * Count your actual content pieces BEFORE selecting the layout\n * Verify each placeholder in the chosen layout will be filled with meaningful content\n * Select one option representing the **best** layout for each content section.\n * Save `outline.md` with content AND template mapping that leverages available designs\n * Example template mapping:\n ```\n # Template slides to use (0-based indexing)\n # WARNING: Verify indices are within range! Template with 73 slides has indices 0-72\n # Mapping: slide numbers from outline -> template slide indices\n template_mapping = [\n 0, # Use slide 0 (Title/Cover)\n 34, # Use slide 34 (B1: Title and body)\n 34, # Use slide 34 again (duplicate for second B1)\n 50, # Use slide 50 (E1: Quote)\n 54, # Use slide 54 (F2: Closing + Text)\n ]\n ```\n\n4. **Duplicate, reorder, and delete slides using `rearrange.py`**:\n * Use the `scripts/rearrange.py` script to create a new presentation with slides in the desired order:\n ```bash\n python scripts/rearrange.py template.pptx working.pptx 0,34,34,50,52\n ```\n * The script handles duplicating repeated slides, deleting unused slides, and reordering automatically\n * Slide indices are 0-based (first slide is 0, second is 1, etc.)\n * The same slide index can appear multiple times to duplicate that slide\n\n5. **Extract ALL text using the `inventory.py` script**:\n * **Run inventory extraction**:\n ```bash\n python scripts/inventory.py working.pptx text-inventory.json\n ```\n * **Read text-inventory.json**: Read the entire text-inventory.json file to understand all shapes and their properties. **NEVER set any range limits when reading this file.**\n\n * The inventory JSON structure:\n ```json\n {\n \"slide-0\": {\n \"shape-0\": {\n \"placeholder_type\": \"TITLE\", // or null for non-placeholders\n \"left\": 1.5, // position in inches\n \"top\": 2.0,\n \"width\": 7.5,\n \"height\": 1.2,\n \"paragraphs\": [\n {\n \"text\": \"Paragraph text\",\n // Optional properties (only included when non-default):\n \"bullet\": true, // explicit bullet detected\n \"level\": 0, // only included when bullet is true\n \"alignment\": \"CENTER\", // CENTER, RIGHT (not LEFT)\n \"space_before\": 10.0, // space before paragraph in points\n \"space_after\": 6.0, // space after paragraph in points\n \"line_spacing\": 22.4, // line spacing in points\n \"font_name\": \"Arial\", // from first run\n \"font_size\": 14.0, // in points\n \"bold\": true,\n \"italic\": false,\n \"underline\": false,\n \"color\": \"FF0000\" // RGB color\n }\n ]\n }\n }\n }\n ```\n\n * Key features:\n - **Slides**: Named as \"slide-0\", \"slide-1\", etc.\n - **Shapes**: Ordered by visual position (top-to-bottom, left-to-right) as \"shape-0\", \"shape-1\", etc.\n - **Placeholder types**: TITLE, CENTER_TITLE, SUBTITLE, BODY, OBJECT, or null\n - **Default font size**: `default_font_size` in points extracted from layout placeholders (when available)\n - **Slide numbers are filtered**: Shapes with SLIDE_NUMBER placeholder type are automatically excluded from inventory\n - **Bullets**: When `bullet: true`, `level` is always included (even if 0)\n - **Spacing**: `space_before`, `space_after`, and `line_spacing` in points (only included when set)\n - **Colors**: `color` for RGB (e.g., \"FF0000\"), `theme_color` for theme colors (e.g., \"DARK_1\")\n - **Properties**: Only non-default values are included in the output\n\n6. **Generate replacement text and save the data to a JSON file**\n Based on the text inventory from the previous step:\n - **CRITICAL**: First verify which shapes exist in the inventory - only reference shapes that are actually present\n - **VALIDATION**: The replace.py script will validate that all shapes in your replacement JSON exist in the inventory\n - If you reference a non-existent shape, you'll get an error showing available shapes\n - If you reference a non-existent slide, you'll get an error indicating the slide doesn't exist\n - All validation errors are shown at once before the script exits\n - **IMPORTANT**: The replace.py script uses inventory.py internally to identify ALL text shapes\n - **AUTOMATIC CLEARING**: ALL text shapes from the inventory will be cleared unless you provide \"paragraphs\" for them\n - Add a \"paragraphs\" field to shapes that need content (not \"replacement_paragraphs\")\n - Shapes without \"paragraphs\" in the replacement JSON will have their text cleared automatically\n - Paragraphs with bullets will be automatically left aligned. Don't set the `alignment` property on when `\"bullet\": true`\n - Generate appropriate replacement content for placeholder text\n - Use shape size to determine appropriate content length\n - **CRITICAL**: Include paragraph properties from the original inventory - don't just provide text\n - **IMPORTANT**: When bullet: true, do NOT include bullet symbols (•, -, *) in text - they're added automatically\n - **ESSENTIAL FORMATTING RULES**:\n - Headers/titles should typically have `\"bold\": true`\n - List items should have `\"bullet\": true, \"level\": 0` (level is required when bullet is true)\n - Preserve any alignment properties (e.g., `\"alignment\": \"CENTER\"` for centered text)\n - Include font properties when different from default (e.g., `\"font_size\": 14.0`, `\"font_name\": \"Lora\"`)\n - Colors: Use `\"color\": \"FF0000\"` for RGB or `\"theme_color\": \"DARK_1\"` for theme colors\n - The replacement script expects **properly formatted paragraphs**, not just text strings\n - **Overlapping shapes**: Prefer shapes with larger default_font_size or more appropriate placeholder_type\n - Save the updated inventory with replacements to `replacement-text.json`\n - **WARNING**: Different template layouts have different shape counts - always check the actual inventory before creating replacements\n\n Example paragraphs field showing proper formatting:\n ```json\n \"paragraphs\": [\n {\n \"text\": \"New presentation title text\",\n \"alignment\": \"CENTER\",\n \"bold\": true\n },\n {\n \"text\": \"Section Header\",\n \"bold\": true\n },\n {\n \"text\": \"First bullet point without bullet symbol\",\n \"bullet\": true,\n \"level\": 0\n },\n {\n \"text\": \"Red colored text\",\n \"color\": \"FF0000\"\n },\n {\n \"text\": \"Theme colored text\",\n \"theme_color\": \"DARK_1\"\n },\n {\n \"text\": \"Regular paragraph text without special formatting\"\n }\n ]\n ```\n\n **Shapes not listed in the replacement JSON are automatically cleared**:\n ```json\n {\n \"slide-0\": {\n \"shape-0\": {\n \"paragraphs\": [...] // This shape gets new text\n }\n // shape-1 and shape-2 from inventory will be cleared automatically\n }\n }\n ```\n\n **Common formatting patterns for presentations**:\n - Title slides: Bold text, sometimes centered\n - Section headers within slides: Bold text\n - Bullet lists: Each item needs `\"bullet\": true, \"level\": 0`\n - Body text: Usually no special properties needed\n - Quotes: May have special alignment or font properties\n\n7. **Apply replacements using the `replace.py` script**\n ```bash\n python scripts/replace.py working.pptx replacement-text.json output.pptx\n ```\n\n The script will:\n - First extract the inventory of ALL text shapes using functions from inventory.py\n - Validate that all shapes in the replacement JSON exist in the inventory\n - Clear text from ALL shapes identified in the inventory\n - Apply new text only to shapes with \"paragraphs\" defined in the replacement JSON\n - Preserve formatting by applying paragraph properties from the JSON\n - Handle bullets, alignment, font properties, and colors automatically\n - Save the updated presentation\n\n Example validation errors:\n ```\n ERROR: Invalid shapes in replacement JSON:\n - Shape 'shape-99' not found on 'slide-0'. Available shapes: shape-0, shape-1, shape-4\n - Slide 'slide-999' not found in inventory\n ```\n\n ```\n ERROR: Replacement text made overflow worse in these shapes:\n - slide-0/shape-2: overflow worsened by 1.25\" (was 0.00\", now 1.25\")\n ```\n\n## Creating Thumbnail Grids\n\nTo create visual thumbnail grids of PowerPoint slides for quick analysis and reference:\n\n```bash\npython scripts/thumbnail.py template.pptx [output_prefix]\n```\n\n**Features**:\n- Creates: `thumbnails.jpg` (or `thumbnails-1.jpg`, `thumbnails-2.jpg`, etc. for large decks)\n- Default: 5 columns, max 30 slides per grid (5×6)\n- Custom prefix: `python scripts/thumbnail.py template.pptx my-grid`\n - Note: The output prefix should include the path if you want output in a specific directory (e.g., `workspace/my-grid`)\n- Adjust columns: `--cols 4` (range: 3-6, affects slides per grid)\n- Grid limits: 3 cols = 12 slides/grid, 4 cols = 20, 5 cols = 30, 6 cols = 42\n- Slides are zero-indexed (Slide 0, Slide 1, etc.)\n\n**Use cases**:\n- Template analysis: Quickly understand slide layouts and design patterns\n- Content review: Visual overview of entire presentation\n- Navigation reference: Find specific slides by their visual appearance\n- Quality check: Verify all slides are properly formatted\n\n**Examples**:\n```bash\n# Basic usage\npython scripts/thumbnail.py presentation.pptx\n\n# Combine options: custom name, columns\npython scripts/thumbnail.py template.pptx analysis --cols 4\n```\n\n## Converting Slides to Images\n\nTo visually analyze PowerPoint slides, convert them to images using a two-step process:\n\n1. **Convert PPTX to PDF**:\n ```bash\n soffice --headless --convert-to pdf template.pptx\n ```\n\n2. **Convert PDF pages to JPEG images**:\n ```bash\n pdftoppm -jpeg -r 150 template.pdf slide\n ```\n This creates files like `slide-1.jpg`, `slide-2.jpg`, etc.\n\nOptions:\n- `-r 150`: Sets resolution to 150 DPI (adjust for quality/size balance)\n- `-jpeg`: Output JPEG format (use `-png` for PNG if preferred)\n- `-f N`: First page to convert (e.g., `-f 2` starts from page 2)\n- `-l N`: Last page to convert (e.g., `-l 5` stops at page 5)\n- `slide`: Prefix for output files\n\nExample for specific range:\n```bash\npdftoppm -jpeg -r 150 -f 2 -l 5 template.pdf slide # Converts only pages 2-5\n```\n\n## Code Style Guidelines\n**IMPORTANT**: When generating code for PPTX operations:\n- Write concise code\n- Avoid verbose variable names and redundant operations\n- Avoid unnecessary print statements\n\n## Dependencies\n\nRequired dependencies (should already be installed):\n\n- **markitdown**: `pip install \"markitdown[pptx]\"` (for text extraction from presentations)\n- **pptxgenjs**: `npm install -g pptxgenjs` (for creating presentations via html2pptx)\n- **playwright**: `npm install -g playwright` (for HTML rendering in html2pptx)\n- **react-icons**: `npm install -g react-icons react react-dom` (for icons)\n- **sharp**: `npm install -g sharp` (for SVG rasterization and image processing)\n- **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)\n- **Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)\n- **defusedxml**: `pip install defusedxml` (for secure XML parsing)","format":"legacy","source":"claude-code","last_sync":"2025-12-08T12:31:36.814Z","content_hash":"b6f25545bfb358739f1532f793458b5dbc87ee009933cb7c306b2d951ab6617f"},{"uid":"content.slack-gif-creator","name":"slack-gif-creator","category":"content","description":"Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","content":"---\nname: slack-gif-creator\ndescription: Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"\nlicense: Complete terms in LICENSE.txt\n---\n\n# Slack GIF Creator\n\nA toolkit providing utilities and knowledge for creating animated GIFs optimized for Slack.\n\n## Slack Requirements\n\n**Dimensions:**\n- Emoji GIFs: 128x128 (recommended)\n- Message GIFs: 480x480\n\n**Parameters:**\n- FPS: 10-30 (lower is smaller file size)\n- Colors: 48-128 (fewer = smaller file size)\n- Duration: Keep under 3 seconds for emoji GIFs\n\n## Core Workflow\n\n```python\nfrom core.gif_builder import GIFBuilder\nfrom PIL import Image, ImageDraw\n\n# 1. Create builder\nbuilder = GIFBuilder(width=128, height=128, fps=10)\n\n# 2. Generate frames\nfor i in range(12):\n frame = Image.new('RGB', (128, 128), (240, 248, 255))\n draw = ImageDraw.Draw(frame)\n\n # Draw your animation using PIL primitives\n # (circles, polygons, lines, etc.)\n\n builder.add_frame(frame)\n\n# 3. Save with optimization\nbuilder.save('output.gif', num_colors=48, optimize_for_emoji=True)\n```\n\n## Drawing Graphics\n\n### Working with User-Uploaded Images\nIf a user uploads an image, consider whether they want to:\n- **Use it directly** (e.g., \"animate this\", \"split this into frames\")\n- **Use it as inspiration** (e.g., \"make something like this\")\n\nLoad and work with images using PIL:\n```python\nfrom PIL import Image\n\nuploaded = Image.open('file.png')\n# Use directly, or just as reference for colors/style\n```\n\n### Drawing from Scratch\nWhen drawing graphics from scratch, use PIL ImageDraw primitives:\n\n```python\nfrom PIL import ImageDraw\n\ndraw = ImageDraw.Draw(frame)\n\n# Circles/ovals\ndraw.ellipse([x1, y1, x2, y2], fill=(r, g, b), outline=(r, g, b), width=3)\n\n# Stars, triangles, any polygon\npoints = [(x1, y1), (x2, y2), (x3, y3), ...]\ndraw.polygon(points, fill=(r, g, b), outline=(r, g, b), width=3)\n\n# Lines\ndraw.line([(x1, y1), (x2, y2)], fill=(r, g, b), width=5)\n\n# Rectangles\ndraw.rectangle([x1, y1, x2, y2], fill=(r, g, b), outline=(r, g, b), width=3)\n```\n\n**Don't use:** Emoji fonts (unreliable across platforms) or assume pre-packaged graphics exist in this skill.\n\n### Making Graphics Look Good\n\nGraphics should look polished and creative, not basic. Here's how:\n\n**Use thicker lines** - Always set `width=2` or higher for outlines and lines. Thin lines (width=1) look choppy and amateurish.\n\n**Add visual depth**:\n- Use gradients for backgrounds (`create_gradient_background`)\n- Layer multiple shapes for complexity (e.g., a star with a smaller star inside)\n\n**Make shapes more interesting**:\n- Don't just draw a plain circle - add highlights, rings, or patterns\n- Stars can have glows (draw larger, semi-transparent versions behind)\n- Combine multiple shapes (stars + sparkles, circles + rings)\n\n**Pay attention to colors**:\n- Use vibrant, complementary colors\n- Add contrast (dark outlines on light shapes, light outlines on dark shapes)\n- Consider the overall composition\n\n**For complex shapes** (hearts, snowflakes, etc.):\n- Use combinations of polygons and ellipses\n- Calculate points carefully for symmetry\n- Add details (a heart can have a highlight curve, snowflakes have intricate branches)\n\nBe creative and detailed! A good Slack GIF should look polished, not like placeholder graphics.\n\n## Available Utilities\n\n### GIFBuilder (`core.gif_builder`)\nAssembles frames and optimizes for Slack:\n```python\nbuilder = GIFBuilder(width=128, height=128, fps=10)\nbuilder.add_frame(frame) # Add PIL Image\nbuilder.add_frames(frames) # Add list of frames\nbuilder.save('out.gif', num_colors=48, optimize_for_emoji=True, remove_duplicates=True)\n```\n\n### Validators (`core.validators`)\nCheck if GIF meets Slack requirements:\n```python\nfrom core.validators import validate_gif, is_slack_ready\n\n# Detailed validation\npasses, info = validate_gif('my.gif', is_emoji=True, verbose=True)\n\n# Quick check\nif is_slack_ready('my.gif'):\n print(\"Ready!\")\n```\n\n### Easing Functions (`core.easing`)\nSmooth motion instead of linear:\n```python\nfrom core.easing import interpolate\n\n# Progress from 0.0 to 1.0\nt = i / (num_frames - 1)\n\n# Apply easing\ny = interpolate(start=0, end=400, t=t, easing='ease_out')\n\n# Available: linear, ease_in, ease_out, ease_in_out,\n# bounce_out, elastic_out, back_out\n```\n\n### Frame Helpers (`core.frame_composer`)\nConvenience functions for common needs:\n```python\nfrom core.frame_composer import (\n create_blank_frame, # Solid color background\n create_gradient_background, # Vertical gradient\n draw_circle, # Helper for circles\n draw_text, # Simple text rendering\n draw_star # 5-pointed star\n)\n```\n\n## Animation Concepts\n\n### Shake/Vibrate\nOffset object position with oscillation:\n- Use `math.sin()` or `math.cos()` with frame index\n- Add small random variations for natural feel\n- Apply to x and/or y position\n\n### Pulse/Heartbeat\nScale object size rhythmically:\n- Use `math.sin(t * frequency * 2 * math.pi)` for smooth pulse\n- For heartbeat: two quick pulses then pause (adjust sine wave)\n- Scale between 0.8 and 1.2 of base size\n\n### Bounce\nObject falls and bounces:\n- Use `interpolate()` with `easing='bounce_out'` for landing\n- Use `easing='ease_in'` for falling (accelerating)\n- Apply gravity by increasing y velocity each frame\n\n### Spin/Rotate\nRotate object around center:\n- PIL: `image.rotate(angle, resample=Image.BICUBIC)`\n- For wobble: use sine wave for angle instead of linear\n\n### Fade In/Out\nGradually appear or disappear:\n- Create RGBA image, adjust alpha channel\n- Or use `Image.blend(image1, image2, alpha)`\n- Fade in: alpha from 0 to 1\n- Fade out: alpha from 1 to 0\n\n### Slide\nMove object from off-screen to position:\n- Start position: outside frame bounds\n- End position: target location\n- Use `interpolate()` with `easing='ease_out'` for smooth stop\n- For overshoot: use `easing='back_out'`\n\n### Zoom\nScale and position for zoom effect:\n- Zoom in: scale from 0.1 to 2.0, crop center\n- Zoom out: scale from 2.0 to 1.0\n- Can add motion blur for drama (PIL filter)\n\n### Explode/Particle Burst\nCreate particles radiating outward:\n- Generate particles with random angles and velocities\n- Update each particle: `x += vx`, `y += vy`\n- Add gravity: `vy += gravity_constant`\n- Fade out particles over time (reduce alpha)\n\n## Optimization Strategies\n\nOnly when asked to make the file size smaller, implement a few of the following methods:\n\n1. **Fewer frames** - Lower FPS (10 instead of 20) or shorter duration\n2. **Fewer colors** - `num_colors=48` instead of 128\n3. **Smaller dimensions** - 128x128 instead of 480x480\n4. **Remove duplicates** - `remove_duplicates=True` in save()\n5. **Emoji mode** - `optimize_for_emoji=True` auto-optimizes\n\n```python\n# Maximum optimization for emoji\nbuilder.save(\n 'emoji.gif',\n num_colors=48,\n optimize_for_emoji=True,\n remove_duplicates=True\n)\n```\n\n## Philosophy\n\nThis skill provides:\n- **Knowledge**: Slack's requirements and animation concepts\n- **Utilities**: GIFBuilder, validators, easing functions\n- **Flexibility**: Create the animation logic using PIL primitives\n\nIt does NOT provide:\n- Rigid animation templates or pre-made functions\n- Emoji font rendering (unreliable across platforms)\n- A library of pre-packaged graphics built into the skill\n\n**Note on user uploads**: This skill doesn't include pre-built graphics, but if a user uploads an image, use PIL to load and work with it - interpret based on their request whether they want it used directly or just as inspiration.\n\nBe creative! Combine concepts (bouncing + rotating, pulsing + sliding, etc.) and use PIL's full capabilities.\n\n## Dependencies\n\n```bash\npip install pillow imageio numpy\n```\n","format":"legacy","source":"claude-code","last_sync":"2025-12-08T12:31:36.814Z","content_hash":"2efca615ce55a3edd8fc05c779068a8085816617991987e446606403cd3abb22"},{"uid":"content.frontend-design","name":"frontend-design","category":"content","description":"Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.","content":"---\nname: frontend-design\ndescription: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.\nlicense: Complete terms in LICENSE.txt\n---\n\nThis skill guides creation of distinctive, production-grade frontend interfaces that avoid generic \"AI slop\" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.\n\nThe user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.\n\n## Design Thinking\n\nBefore coding, understand the context and commit to a BOLD aesthetic direction:\n- **Purpose**: What problem does this interface solve? Who uses it?\n- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.\n- **Constraints**: Technical requirements (framework, performance, accessibility).\n- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?\n\n**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.\n\nThen implement working code (HTML/CSS/JS, React, Vue, etc.) that is:\n- Production-grade and functional\n- Visually striking and memorable\n- Cohesive with a clear aesthetic point-of-view\n- Meticulously refined in every detail\n\n## Frontend Aesthetics Guidelines\n\nFocus on:\n- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.\n- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.\n- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.\n- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.\n- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.\n\nNEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.\n\nInterpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.\n\n**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.\n\nRemember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.\n","format":"legacy","source":"claude-code","last_sync":"2025-12-08T12:31:36.814Z","content_hash":"8bf9905dbcd9b1edb47f2a44cadbb9bb66314f73a8e3631ec7feee913777ceb8"},{"uid":"content.brand-guidelines","name":"brand-guidelines","category":"content","description":"Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.","content":"---\nname: brand-guidelines\ndescription: Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.\nlicense: Complete terms in LICENSE.txt\n---\n\n# Anthropic Brand Styling\n\n## Overview\n\nTo access Anthropic's official brand identity and style resources, use this skill.\n\n**Keywords**: branding, corporate identity, visual identity, post-processing, styling, brand colors, typography, Anthropic brand, visual formatting, visual design\n\n## Brand Guidelines\n\n### Colors\n\n**Main Colors:**\n\n- Dark: `#141413` - Primary text and dark backgrounds\n- Light: `#faf9f5` - Light backgrounds and text on dark\n- Mid Gray: `#b0aea5` - Secondary elements\n- Light Gray: `#e8e6dc` - Subtle backgrounds\n\n**Accent Colors:**\n\n- Orange: `#d97757` - Primary accent\n- Blue: `#6a9bcc` - Secondary accent\n- Green: `#788c5d` - Tertiary accent\n\n### Typography\n\n- **Headings**: Poppins (with Arial fallback)\n- **Body Text**: Lora (with Georgia fallback)\n- **Note**: Fonts should be pre-installed in your environment for best results\n\n## Features\n\n### Smart Font Application\n\n- Applies Poppins font to headings (24pt and larger)\n- Applies Lora font to body text\n- Automatically falls back to Arial/Georgia if custom fonts unavailable\n- Preserves readability across all systems\n\n### Text Styling\n\n- Headings (24pt+): Poppins font\n- Body text: Lora font\n- Smart color selection based on background\n- Preserves text hierarchy and formatting\n\n### Shape and Accent Colors\n\n- Non-text shapes use accent colors\n- Cycles through orange, blue, and green accents\n- Maintains visual interest while staying on-brand\n\n## Technical Details\n\n### Font Management\n\n- Uses system-installed Poppins and Lora fonts when available\n- Provides automatic fallback to Arial (headings) and Georgia (body)\n- No font installation required - works with existing system fonts\n- For best results, pre-install Poppins and Lora fonts in your environment\n\n### Color Application\n\n- Uses RGB color values for precise brand matching\n- Applied via python-pptx's RGBColor class\n- Maintains color fidelity across different systems\n","format":"legacy","source":"claude-code","last_sync":"2025-12-08T12:31:36.814Z","content_hash":"1120b3769e2985cefb3d25be981b1f914abeba57ae079b83c20c666c164fa9fe"},{"uid":"content.ui-design-system","name":"ui-design-system","category":"content","description":"UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.","content":"---\nname: ui-design-system\ndescription: UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.\n---\n\n# UI Design System\n\nProfessional toolkit for creating and maintaining scalable design systems.\n\n## Core Capabilities\n- Design token generation (colors, typography, spacing)\n- Component system architecture\n- Responsive design calculations\n- Accessibility compliance\n- Developer handoff documentation\n\n## Key Scripts\n\n### design_token_generator.py\nGenerates complete design system tokens from brand colors.\n\n**Usage**: `python scripts/design_token_generator.py [brand_color] [style] [format]`\n- Styles: modern, classic, playful\n- Formats: json, css, scss\n\n**Features**:\n- Complete color palette generation\n- Modular typography scale\n- 8pt spacing grid system\n- Shadow and animation tokens\n- Responsive breakpoints\n- Multiple export formats\n","format":"legacy","source":"claude-code","last_sync":"2025-12-08T12:31:36.814Z","content_hash":"d2754b142e18ab5c51031fe6f1a4f807019b2e5346431a0c014baef22efd6aee"},{"uid":"content.docx","name":"docx","category":"content","description":"\"Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks\"","content":"---\nname: docx\ndescription: \"Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks\"\nlicense: Proprietary. LICENSE.txt has complete terms\n---\n\n# DOCX creation, editing, and analysis\n\n## Overview\n\nA user may ask you to create, edit, or analyze the contents of a .docx file. A .docx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks.\n\n## Workflow Decision Tree\n\n### Reading/Analyzing Content\nUse \"Text extraction\" or \"Raw XML access\" sections below\n\n### Creating New Document\nUse \"Creating a new Word document\" workflow\n\n### Editing Existing Document\n- **Your own document + simple changes**\n Use \"Basic OOXML editing\" workflow\n\n- **Someone else's document**\n Use **\"Redlining workflow\"** (recommended default)\n\n- **Legal, academic, business, or government docs**\n Use **\"Redlining workflow\"** (required)\n\n## Reading and analyzing content\n\n### Text extraction\nIf you just need to read the text contents of a document, you should convert the document to markdown using pandoc. Pandoc provides excellent support for preserving document structure and can show tracked changes:\n\n```bash\n# Convert document to markdown with tracked changes\npandoc --track-changes=all path-to-file.docx -o output.md\n# Options: --track-changes=accept/reject/all\n```\n\n### Raw XML access\nYou need raw XML access for: comments, complex formatting, document structure, embedded media, and metadata. For any of these features, you'll need to unpack a document and read its raw XML contents.\n\n#### Unpacking a file\n`python ooxml/scripts/unpack.py `\n\n#### Key file structures\n* `word/document.xml` - Main document contents\n* `word/comments.xml` - Comments referenced in document.xml\n* `word/media/` - Embedded images and media files\n* Tracked changes use `` (insertions) and `` (deletions) tags\n\n## Creating a new Word document\n\nWhen creating a new Word document from scratch, use **docx-js**, which allows you to create Word documents using JavaScript/TypeScript.\n\n### Workflow\n1. **MANDATORY - READ ENTIRE FILE**: Read [`docx-js.md`](docx-js.md) (~500 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for detailed syntax, critical formatting rules, and best practices before proceeding with document creation.\n2. Create a JavaScript/TypeScript file using Document, Paragraph, TextRun components (You can assume all dependencies are installed, but if not, refer to the dependencies section below)\n3. Export as .docx using Packer.toBuffer()\n\n## Editing an existing Word document\n\nWhen editing an existing Word document, use the **Document library** (a Python library for OOXML manipulation). The library automatically handles infrastructure setup and provides methods for document manipulation. For complex scenarios, you can access the underlying DOM directly through the library.\n\n### Workflow\n1. **MANDATORY - READ ENTIRE FILE**: Read [`ooxml.md`](ooxml.md) (~600 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for the Document library API and XML patterns for directly editing document files.\n2. Unpack the document: `python ooxml/scripts/unpack.py `\n3. Create and run a Python script using the Document library (see \"Document Library\" section in ooxml.md)\n4. Pack the final document: `python ooxml/scripts/pack.py `\n\nThe Document library provides both high-level methods for common operations and direct DOM access for complex scenarios.\n\n## Redlining workflow for document review\n\nThis workflow allows you to plan comprehensive tracked changes using markdown before implementing them in OOXML. **CRITICAL**: For complete tracked changes, you must implement ALL changes systematically.\n\n**Batching Strategy**: Group related changes into batches of 3-10 changes. This makes debugging manageable while maintaining efficiency. Test each batch before moving to the next.\n\n**Principle: Minimal, Precise Edits**\nWhen implementing tracked changes, only mark text that actually changes. Repeating unchanged text makes edits harder to review and appears unprofessional. Break replacements into: [unchanged text] + [deletion] + [insertion] + [unchanged text]. Preserve the original run's RSID for unchanged text by extracting the `` element from the original and reusing it.\n\nExample - Changing \"30 days\" to \"60 days\" in a sentence:\n```python\n# BAD - Replaces entire sentence\n'The term is 30 days.The term is 60 days.'\n\n# GOOD - Only marks what changed, preserves original for unchanged text\n'The term is 3060 days.'\n```\n\n### Tracked changes workflow\n\n1. **Get markdown representation**: Convert document to markdown with tracked changes preserved:\n ```bash\n pandoc --track-changes=all path-to-file.docx -o current.md\n ```\n\n2. **Identify and group changes**: Review the document and identify ALL changes needed, organizing them into logical batches:\n\n **Location methods** (for finding changes in XML):\n - Section/heading numbers (e.g., \"Section 3.2\", \"Article IV\")\n - Paragraph identifiers if numbered\n - Grep patterns with unique surrounding text\n - Document structure (e.g., \"first paragraph\", \"signature block\")\n - **DO NOT use markdown line numbers** - they don't map to XML structure\n\n **Batch organization** (group 3-10 related changes per batch):\n - By section: \"Batch 1: Section 2 amendments\", \"Batch 2: Section 5 updates\"\n - By type: \"Batch 1: Date corrections\", \"Batch 2: Party name changes\"\n - By complexity: Start with simple text replacements, then tackle complex structural changes\n - Sequential: \"Batch 1: Pages 1-3\", \"Batch 2: Pages 4-6\"\n\n3. **Read documentation and unpack**:\n - **MANDATORY - READ ENTIRE FILE**: Read [`ooxml.md`](ooxml.md) (~600 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Pay special attention to the \"Document Library\" and \"Tracked Change Patterns\" sections.\n - **Unpack the document**: `python ooxml/scripts/unpack.py `\n - **Note the suggested RSID**: The unpack script will suggest an RSID to use for your tracked changes. Copy this RSID for use in step 4b.\n\n4. **Implement changes in batches**: Group changes logically (by section, by type, or by proximity) and implement them together in a single script. This approach:\n - Makes debugging easier (smaller batch = easier to isolate errors)\n - Allows incremental progress\n - Maintains efficiency (batch size of 3-10 changes works well)\n\n **Suggested batch groupings:**\n - By document section (e.g., \"Section 3 changes\", \"Definitions\", \"Termination clause\")\n - By change type (e.g., \"Date changes\", \"Party name updates\", \"Legal term replacements\")\n - By proximity (e.g., \"Changes on pages 1-3\", \"Changes in first half of document\")\n\n For each batch of related changes:\n\n **a. Map text to XML**: Grep for text in `word/document.xml` to verify how text is split across `` elements.\n\n **b. Create and run script**: Use `get_node` to find nodes, implement changes, then `doc.save()`. See **\"Document Library\"** section in ooxml.md for patterns.\n\n **Note**: Always grep `word/document.xml` immediately before writing a script to get current line numbers and verify text content. Line numbers change after each script run.\n\n5. **Pack the document**: After all batches are complete, convert the unpacked directory back to .docx:\n ```bash\n python ooxml/scripts/pack.py unpacked reviewed-document.docx\n ```\n\n6. **Final verification**: Do a comprehensive check of the complete document:\n - Convert final document to markdown:\n ```bash\n pandoc --track-changes=all reviewed-document.docx -o verification.md\n ```\n - Verify ALL changes were applied correctly:\n ```bash\n grep \"original phrase\" verification.md # Should NOT find it\n grep \"replacement phrase\" verification.md # Should find it\n ```\n - Check that no unintended changes were introduced\n\n\n## Converting Documents to Images\n\nTo visually analyze Word documents, convert them to images using a two-step process:\n\n1. **Convert DOCX to PDF**:\n ```bash\n soffice --headless --convert-to pdf document.docx\n ```\n\n2. **Convert PDF pages to JPEG images**:\n ```bash\n pdftoppm -jpeg -r 150 document.pdf page\n ```\n This creates files like `page-1.jpg`, `page-2.jpg`, etc.\n\nOptions:\n- `-r 150`: Sets resolution to 150 DPI (adjust for quality/size balance)\n- `-jpeg`: Output JPEG format (use `-png` for PNG if preferred)\n- `-f N`: First page to convert (e.g., `-f 2` starts from page 2)\n- `-l N`: Last page to convert (e.g., `-l 5` stops at page 5)\n- `page`: Prefix for output files\n\nExample for specific range:\n```bash\npdftoppm -jpeg -r 150 -f 2 -l 5 document.pdf page # Converts only pages 2-5\n```\n\n## Code Style Guidelines\n**IMPORTANT**: When generating code for DOCX operations:\n- Write concise code\n- Avoid verbose variable names and redundant operations\n- Avoid unnecessary print statements\n\n## Dependencies\n\nRequired dependencies (install if not available):\n\n- **pandoc**: `sudo apt-get install pandoc` (for text extraction)\n- **docx**: `npm install -g docx` (for creating new documents)\n- **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)\n- **Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)\n- **defusedxml**: `pip install defusedxml` (for secure XML parsing)","format":"legacy","source":"claude-code","last_sync":"2025-12-08T12:31:36.814Z","content_hash":"0bd90681fcab2e282025ee14acf508b60bbd6c41ac6c3bf83c0dc14d52c37933"},{"uid":"content.web-artifacts-builder","name":"web-artifacts-builder","category":"content","description":"Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.","content":"---\nname: web-artifacts-builder\ndescription: Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.\nlicense: Complete terms in LICENSE.txt\n---\n\n# Web Artifacts Builder\n\nTo build powerful frontend claude.ai artifacts, follow these steps:\n1. Initialize the frontend repo using `scripts/init-artifact.sh`\n2. Develop your artifact by editing the generated code\n3. Bundle all code into a single HTML file using `scripts/bundle-artifact.sh`\n4. Display artifact to user\n5. (Optional) Test the artifact\n\n**Stack**: React 18 + TypeScript + Vite + Parcel (bundling) + Tailwind CSS + shadcn/ui\n\n## Design & Style Guidelines\n\nVERY IMPORTANT: To avoid what is often referred to as \"AI slop\", avoid using excessive centered layouts, purple gradients, uniform rounded corners, and Inter font.\n\n## Quick Start\n\n### Step 1: Initialize Project\n\nRun the initialization script to create a new React project:\n```bash\nbash scripts/init-artifact.sh \ncd \n```\n\nThis creates a fully configured project with:\n- ✅ React + TypeScript (via Vite)\n- ✅ Tailwind CSS 3.4.1 with shadcn/ui theming system\n- ✅ Path aliases (`@/`) configured\n- ✅ 40+ shadcn/ui components pre-installed\n- ✅ All Radix UI dependencies included\n- ✅ Parcel configured for bundling (via .parcelrc)\n- ✅ Node 18+ compatibility (auto-detects and pins Vite version)\n\n### Step 2: Develop Your Artifact\n\nTo build the artifact, edit the generated files. See **Common Development Tasks** below for guidance.\n\n### Step 3: Bundle to Single HTML File\n\nTo bundle the React app into a single HTML artifact:\n```bash\nbash scripts/bundle-artifact.sh\n```\n\nThis creates `bundle.html` - a self-contained artifact with all JavaScript, CSS, and dependencies inlined. This file can be directly shared in Claude conversations as an artifact.\n\n**Requirements**: Your project must have an `index.html` in the root directory.\n\n**What the script does**:\n- Installs bundling dependencies (parcel, @parcel/config-default, parcel-resolver-tspaths, html-inline)\n- Creates `.parcelrc` config with path alias support\n- Builds with Parcel (no source maps)\n- Inlines all assets into single HTML using html-inline\n\n### Step 4: Share Artifact with User\n\nFinally, share the bundled HTML file in conversation with the user so they can view it as an artifact.\n\n### Step 5: Testing/Visualizing the Artifact (Optional)\n\nNote: This is a completely optional step. Only perform if necessary or requested.\n\nTo test/visualize the artifact, use available tools (including other Skills or built-in tools like Playwright or Puppeteer). In general, avoid testing the artifact upfront as it adds latency between the request and when the finished artifact can be seen. Test later, after presenting the artifact, if requested or if issues arise.\n\n## Reference\n\n- **shadcn/ui components**: https://ui.shadcn.com/docs/components","format":"legacy","source":"claude-code","last_sync":"2025-12-08T12:31:36.814Z","content_hash":"81c5002c6643b0de7b8710b00e7a9038daa6fb9b68d59870ee6adb12da8d10f8"},{"uid":"product.agile-product-owner","name":"agile-product-owner","category":"product","description":"Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.","content":"---\nname: agile-product-owner\ndescription: Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.\n---\n\n# Agile Product Owner\n\nComplete toolkit for Product Owners to excel at backlog management and sprint execution.\n\n## Core Capabilities\n- INVEST-compliant user story generation\n- Automatic acceptance criteria creation\n- Sprint capacity planning\n- Backlog prioritization\n- Velocity tracking and metrics\n\n## Key Scripts\n\n### user_story_generator.py\nGenerates well-formed user stories with acceptance criteria from epics.\n\n**Usage**: \n- Generate stories: `python scripts/user_story_generator.py`\n- Plan sprint: `python scripts/user_story_generator.py sprint [capacity]`\n\n**Features**:\n- Breaks epics into stories\n- INVEST criteria validation\n- Automatic point estimation\n- Priority assignment\n- Sprint planning with capacity\n","format":"legacy","source":"claude-code","last_sync":"2025-12-08T12:31:36.814Z","content_hash":"aa16b5e372246cc063b083089d4164b97575f43d7d0beefb1cb390067bd8cfe8"},{"uid":"product.product-manager-toolkit","name":"product-manager-toolkit","category":"product","description":"Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.","content":"---\nname: product-manager-toolkit\ndescription: Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.\n---\n\n# Product Manager Toolkit\n\nEssential tools and frameworks for modern product management, from discovery to delivery.\n\n## Quick Start\n\n### For Feature Prioritization\n```bash\npython scripts/rice_prioritizer.py sample # Create sample CSV\npython scripts/rice_prioritizer.py sample_features.csv --capacity 15\n```\n\n### For Interview Analysis\n```bash\npython scripts/customer_interview_analyzer.py interview_transcript.txt\n```\n\n### For PRD Creation\n1. Choose template from `references/prd_templates.md`\n2. Fill in sections based on discovery work\n3. Review with stakeholders\n4. Version control in your PM tool\n\n## Core Workflows\n\n### Feature Prioritization Process\n\n1. **Gather Feature Requests**\n - Customer feedback\n - Sales requests\n - Technical debt\n - Strategic initiatives\n\n2. **Score with RICE**\n ```bash\n # Create CSV with: name,reach,impact,confidence,effort\n python scripts/rice_prioritizer.py features.csv\n ```\n - **Reach**: Users affected per quarter\n - **Impact**: massive/high/medium/low/minimal\n - **Confidence**: high/medium/low\n - **Effort**: xl/l/m/s/xs (person-months)\n\n3. **Analyze Portfolio**\n - Review quick wins vs big bets\n - Check effort distribution\n - Validate against strategy\n\n4. **Generate Roadmap**\n - Quarterly capacity planning\n - Dependency mapping\n - Stakeholder alignment\n\n### Customer Discovery Process\n\n1. **Conduct Interviews**\n - Use semi-structured format\n - Focus on problems, not solutions\n - Record with permission\n\n2. **Analyze Insights**\n ```bash\n python scripts/customer_interview_analyzer.py transcript.txt\n ```\n Extracts:\n - Pain points with severity\n - Feature requests with priority\n - Jobs to be done\n - Sentiment analysis\n - Key themes and quotes\n\n3. **Synthesize Findings**\n - Group similar pain points\n - Identify patterns across interviews\n - Map to opportunity areas\n\n4. **Validate Solutions**\n - Create solution hypotheses\n - Test with prototypes\n - Measure actual vs expected behavior\n\n### PRD Development Process\n\n1. **Choose Template**\n - **Standard PRD**: Complex features (6-8 weeks)\n - **One-Page PRD**: Simple features (2-4 weeks)\n - **Feature Brief**: Exploration phase (1 week)\n - **Agile Epic**: Sprint-based delivery\n\n2. **Structure Content**\n - Problem → Solution → Success Metrics\n - Always include out-of-scope\n - Clear acceptance criteria\n\n3. **Collaborate**\n - Engineering for feasibility\n - Design for experience\n - Sales for market validation\n - Support for operational impact\n\n## Key Scripts\n\n### rice_prioritizer.py\nAdvanced RICE framework implementation with portfolio analysis.\n\n**Features**:\n- RICE score calculation\n- Portfolio balance analysis (quick wins vs big bets)\n- Quarterly roadmap generation\n- Team capacity planning\n- Multiple output formats (text/json/csv)\n\n**Usage Examples**:\n```bash\n# Basic prioritization\npython scripts/rice_prioritizer.py features.csv\n\n# With custom team capacity (person-months per quarter)\npython scripts/rice_prioritizer.py features.csv --capacity 20\n\n# Output as JSON for integration\npython scripts/rice_prioritizer.py features.csv --output json\n```\n\n### customer_interview_analyzer.py\nNLP-based interview analysis for extracting actionable insights.\n\n**Capabilities**:\n- Pain point extraction with severity assessment\n- Feature request identification and classification\n- Jobs-to-be-done pattern recognition\n- Sentiment analysis\n- Theme extraction\n- Competitor mentions\n- Key quotes identification\n\n**Usage Examples**:\n```bash\n# Analyze single interview\npython scripts/customer_interview_analyzer.py interview.txt\n\n# Output as JSON for aggregation\npython scripts/customer_interview_analyzer.py interview.txt json\n```\n\n## Reference Documents\n\n### prd_templates.md\nMultiple PRD formats for different contexts:\n\n1. **Standard PRD Template**\n - Comprehensive 11-section format\n - Best for major features\n - Includes technical specs\n\n2. **One-Page PRD**\n - Concise format for quick alignment\n - Focus on problem/solution/metrics\n - Good for smaller features\n\n3. **Agile Epic Template**\n - Sprint-based delivery\n - User story mapping\n - Acceptance criteria focus\n\n4. **Feature Brief**\n - Lightweight exploration\n - Hypothesis-driven\n - Pre-PRD phase\n\n## Prioritization Frameworks\n\n### RICE Framework\n```\nScore = (Reach × Impact × Confidence) / Effort\n\nReach: # of users/quarter\nImpact: \n - Massive = 3x\n - High = 2x\n - Medium = 1x\n - Low = 0.5x\n - Minimal = 0.25x\nConfidence:\n - High = 100%\n - Medium = 80%\n - Low = 50%\nEffort: Person-months\n```\n\n### Value vs Effort Matrix\n```\n Low Effort High Effort\n \nHigh QUICK WINS BIG BETS\nValue [Prioritize] [Strategic]\n \nLow FILL-INS TIME SINKS\nValue [Maybe] [Avoid]\n```\n\n### MoSCoW Method\n- **Must Have**: Critical for launch\n- **Should Have**: Important but not critical\n- **Could Have**: Nice to have\n- **Won't Have**: Out of scope\n\n## Discovery Frameworks\n\n### Customer Interview Guide\n```\n1. Context Questions (5 min)\n - Role and responsibilities\n - Current workflow\n - Tools used\n\n2. Problem Exploration (15 min)\n - Pain points\n - Frequency and impact\n - Current workarounds\n\n3. Solution Validation (10 min)\n - Reaction to concepts\n - Value perception\n - Willingness to pay\n\n4. Wrap-up (5 min)\n - Other thoughts\n - Referrals\n - Follow-up permission\n```\n\n### Hypothesis Template\n```\nWe believe that [building this feature]\nFor [these users]\nWill [achieve this outcome]\nWe'll know we're right when [metric]\n```\n\n### Opportunity Solution Tree\n```\nOutcome\n├── Opportunity 1\n│ ├── Solution A\n│ └── Solution B\n└── Opportunity 2\n ├── Solution C\n └── Solution D\n```\n\n## Metrics & Analytics\n\n### North Star Metric Framework\n1. **Identify Core Value**: What's the #1 value to users?\n2. **Make it Measurable**: Quantifiable and trackable\n3. **Ensure It's Actionable**: Teams can influence it\n4. **Check Leading Indicator**: Predicts business success\n\n### Funnel Analysis Template\n```\nAcquisition → Activation → Retention → Revenue → Referral\n\nKey Metrics:\n- Conversion rate at each step\n- Drop-off points\n- Time between steps\n- Cohort variations\n```\n\n### Feature Success Metrics\n- **Adoption**: % of users using feature\n- **Frequency**: Usage per user per time period\n- **Depth**: % of feature capability used\n- **Retention**: Continued usage over time\n- **Satisfaction**: NPS/CSAT for feature\n\n## Best Practices\n\n### Writing Great PRDs\n1. Start with the problem, not solution\n2. Include clear success metrics upfront\n3. Explicitly state what's out of scope\n4. Use visuals (wireframes, flows)\n5. Keep technical details in appendix\n6. Version control changes\n\n### Effective Prioritization\n1. Mix quick wins with strategic bets\n2. Consider opportunity cost\n3. Account for dependencies\n4. Buffer for unexpected work (20%)\n5. Revisit quarterly\n6. Communicate decisions clearly\n\n### Customer Discovery Tips\n1. Ask \"why\" 5 times\n2. Focus on past behavior, not future intentions\n3. Avoid leading questions\n4. Interview in their environment\n5. Look for emotional reactions\n6. Validate with data\n\n### Stakeholder Management\n1. Identify RACI for decisions\n2. Regular async updates\n3. Demo over documentation\n4. Address concerns early\n5. Celebrate wins publicly\n6. Learn from failures openly\n\n## Common Pitfalls to Avoid\n\n1. **Solution-First Thinking**: Jumping to features before understanding problems\n2. **Analysis Paralysis**: Over-researching without shipping\n3. **Feature Factory**: Shipping features without measuring impact\n4. **Ignoring Technical Debt**: Not allocating time for platform health\n5. **Stakeholder Surprise**: Not communicating early and often\n6. **Metric Theater**: Optimizing vanity metrics over real value\n\n## Integration Points\n\nThis toolkit integrates with:\n- **Analytics**: Amplitude, Mixpanel, Google Analytics\n- **Roadmapping**: ProductBoard, Aha!, Roadmunk\n- **Design**: Figma, Sketch, Miro\n- **Development**: Jira, Linear, GitHub\n- **Research**: Dovetail, UserVoice, Pendo\n- **Communication**: Slack, Notion, Confluence\n\n## Quick Commands Cheat Sheet\n\n```bash\n# Prioritization\npython scripts/rice_prioritizer.py features.csv --capacity 15\n\n# Interview Analysis\npython scripts/customer_interview_analyzer.py interview.txt\n\n# Create sample data\npython scripts/rice_prioritizer.py sample\n\n# JSON outputs for integration\npython scripts/rice_prioritizer.py features.csv --output json\npython scripts/customer_interview_analyzer.py interview.txt json\n```\n","format":"legacy","source":"claude-code","references":{"prd_templates.md":"# Product Requirements Document (PRD) Templates\n\n## Standard PRD Template\n\n### 1. Executive Summary\n**Purpose**: One-page overview for executives and stakeholders\n\n#### Components:\n- **Problem Statement** (2-3 sentences)\n- **Proposed Solution** (2-3 sentences)\n- **Business Impact** (3 bullet points)\n- **Timeline** (High-level milestones)\n- **Resources Required** (Team size and budget)\n- **Success Metrics** (3-5 KPIs)\n\n### 2. Problem Definition\n\n#### 2.1 Customer Problem\n- **Who**: Target user persona(s)\n- **What**: Specific problem or need\n- **When**: Context and frequency\n- **Where**: Environment and touchpoints\n- **Why**: Root cause analysis\n- **Impact**: Cost of not solving\n\n#### 2.2 Market Opportunity\n- **Market Size**: TAM, SAM, SOM\n- **Growth Rate**: Annual growth percentage\n- **Competition**: Current solutions and gaps\n- **Timing**: Why now?\n\n#### 2.3 Business Case\n- **Revenue Potential**: Projected impact\n- **Cost Savings**: Efficiency gains\n- **Strategic Value**: Alignment with company goals\n- **Risk Assessment**: What if we don't do this?\n\n### 3. Solution Overview\n\n#### 3.1 Proposed Solution\n- **High-Level Description**: What we're building\n- **Key Capabilities**: Core functionality\n- **User Journey**: End-to-end flow\n- **Differentiation**: Unique value proposition\n\n#### 3.2 In Scope\n- Feature 1: Description and priority\n- Feature 2: Description and priority\n- Feature 3: Description and priority\n\n#### 3.3 Out of Scope\n- Explicitly what we're NOT doing\n- Future considerations\n- Dependencies on other teams\n\n#### 3.4 MVP Definition\n- **Core Features**: Minimum viable feature set\n- **Success Criteria**: Definition of \"working\"\n- **Timeline**: MVP delivery date\n- **Learning Goals**: What we want to validate\n\n### 4. User Stories & Requirements\n\n#### 4.1 User Stories\n```\nAs a [persona]\nI want to [action]\nSo that [outcome/benefit]\n\nAcceptance Criteria:\n- [ ] Criterion 1\n- [ ] Criterion 2\n- [ ] Criterion 3\n```\n\n#### 4.2 Functional Requirements\n| ID | Requirement | Priority | Notes |\n|----|------------|----------|-------|\n| FR1 | User can... | P0 | Critical for MVP |\n| FR2 | System should... | P1 | Important |\n| FR3 | Feature must... | P2 | Nice to have |\n\n#### 4.3 Non-Functional Requirements\n- **Performance**: Response times, throughput\n- **Scalability**: User/data growth targets\n- **Security**: Authentication, authorization, data protection\n- **Reliability**: Uptime targets, error rates\n- **Usability**: Accessibility standards, device support\n- **Compliance**: Regulatory requirements\n\n### 5. Design & User Experience\n\n#### 5.1 Design Principles\n- Principle 1: Description\n- Principle 2: Description\n- Principle 3: Description\n\n#### 5.2 Wireframes/Mockups\n- Link to Figma/Sketch files\n- Key screens and flows\n- Interaction patterns\n\n#### 5.3 Information Architecture\n- Navigation structure\n- Data organization\n- Content hierarchy\n\n### 6. Technical Specifications\n\n#### 6.1 Architecture Overview\n- System architecture diagram\n- Technology stack\n- Integration points\n- Data flow\n\n#### 6.2 API Design\n- Endpoints and methods\n- Request/response formats\n- Authentication approach\n- Rate limiting\n\n#### 6.3 Database Design\n- Data model\n- Key entities and relationships\n- Migration strategy\n\n#### 6.4 Security Considerations\n- Authentication method\n- Authorization model\n- Data encryption\n- PII handling\n\n### 7. Go-to-Market Strategy\n\n#### 7.1 Launch Plan\n- **Soft Launch**: Beta users, timeline\n- **Full Launch**: All users, timeline\n- **Marketing**: Campaigns and channels\n- **Support**: Documentation and training\n\n#### 7.2 Pricing Strategy\n- Pricing model\n- Competitive analysis\n- Value proposition\n\n#### 7.3 Success Metrics\n| Metric | Target | Measurement Method |\n|--------|--------|-------------------|\n| Adoption Rate | X% | Daily Active Users |\n| User Satisfaction | X/10 | NPS Score |\n| Revenue Impact | $X | Monthly Recurring Revenue |\n| Performance | target → Pause, optimize, relaunch\n3. If conversion rate drops >20% → Check landing page, offer fatigue\n4. Scale winners, kill losers fast (2-week test minimum)\n\n**HubSpot ROI Dashboard**:\n- Marketing → Reports → Create Custom Report\n- Metrics: Spend, Leads, MQLs, SQLs, CAC, ROAS, Pipeline $\n- Dimensions: Campaign, Channel, Region\n- Frequency: Daily review, weekly optimization\n\n---\n\n## 3. SEO Strategy\n\n### 3.1 Technical SEO Foundation (Must-Have)\n\n**Pre-Launch Checklist**:\n- [ ] XML sitemap submitted to Search Console\n- [ ] Robots.txt configured (allow crawling)\n- [ ] HTTPS enabled (SSL certificate)\n- [ ] Page speed >90 mobile (Google PageSpeed Insights)\n- [ ] Core Web Vitals passing (LCP, FID, CLS)\n- [ ] Structured data (Organization, Product, FAQ schema)\n- [ ] Canonical tags on all pages\n- [ ] Hreflang tags for international (en-US, en-GB, de-DE, etc.)\n\n**Technical Audit** (quarterly):\n```\n1. Crawl site with Screaming Frog\n2. Check for:\n - 404 errors (fix or redirect)\n - Redirect chains (consolidate)\n - Duplicate content (canonicalize)\n - Missing meta descriptions\n - Slow pages (>3s load time)\n - Mobile usability issues\n3. Fix issues in priority order: Critical → High → Medium\n```\n\n### 3.2 Keyword Strategy Framework\n\n**Keyword Research Process**:\n1. **Seed Keywords** - Your product category (e.g., \"project management software\")\n2. **Use Tools** - Ahrefs, SEMrush, or free: Google Keyword Planner + Search Console\n3. **Analyze** - Volume, difficulty, intent, SERP features\n4. **Prioritize** - Quick wins (low difficulty, high intent)\n\n**Keyword Tiers**:\n\n**Tier 1: High-Intent BOFU** (target first)\n- \"best [product category]\"\n- \"[product category] for [use case]\"\n- \"[competitor] alternative\"\n- Volume: 100-1k/mo, Difficulty: Medium, Intent: Commercial\n\n**Tier 2: Solution-Aware MOFU**\n- \"how to [solve problem]\"\n- \"[problem] solution\"\n- \"[use case] tools\"\n- Volume: 500-5k/mo, Difficulty: Medium-High, Intent: Informational-Commercial\n\n**Tier 3: Problem-Aware TOFU**\n- \"what is [concept]\"\n- \"[problem] examples\"\n- \"[industry] challenges\"\n- Volume: 1k-10k/mo, Difficulty: High, Intent: Informational\n\n**International Keyword Research**:\n- Use Ahrefs/SEMrush with language filters\n- Translate keywords, don't just localize (cultural nuances matter)\n- EU: Higher trust in localized content (domain.de > domain.com/de)\n- UK: Use British spelling (optimise vs. optimize)\n\n### 3.3 On-Page SEO Template\n\n**Page Optimization Checklist**:\n```\nURL: [/best-project-management-software]\nTitle Tag (60 chars): [Best Project Management Software 2025 | YourBrand]\nMeta Description (155 chars): [Compare top 10 PM tools. Features, pricing, reviews. Find the perfect fit for your team. Free trials available.]\n\nH1 (60 chars): [Best Project Management Software in 2025]\nH2s (structure):\n - What is Project Management Software?\n - Top 10 PM Tools Compared\n - Key Features to Look For\n - Pricing & Plans\n - How to Choose\n - FAQ\n\nContent:\n - Length: 2000-3000 words (comprehensive)\n - Keyword density: 1-2% (natural)\n - Internal links: 3-5 relevant pages\n - External links: 2-3 authoritative sources\n - Images: 3-5 with alt text\n - Schema: Product, FAQ, HowTo\n\nCTA:\n - Above fold: [Start Free Trial]\n - Mid-content: [Compare Plans]\n - End: [Book Demo]\n```\n\n**Content Refresh Schedule**:\n- Tier 1 pages: Update quarterly (rankings, pricing, features)\n- Tier 2 pages: Update semi-annually\n- Tier 3 pages: Update annually\n- All pages: Monitor Search Console for ranking drops, refresh immediately\n\n### 3.4 Link Building Strategy (2025 Best Practices)\n\n**Link Acquisition Tactics** (in priority order):\n\n**1. Digital PR** (highest ROI)\n- Publish original research/data\n- Create industry reports\n- Pitch journalists (use HARO, Terkel, Featured)\n- Target: Industry blogs, tech publications\n\n**2. Guest Posting** (quality over quantity)\n- Target: Domain Authority (DA) 40+ sites\n- Avoid: Link farms, PBNs, paid links (Google penalty risk)\n- Anchor text: Branded (70%), topical (20%), exact match (10%)\n\n**3. Partnerships & Co-Marketing**\n- Partner with complementary SaaS tools\n- Create co-branded content\n- Exchange homepage links (footer or partner section)\n\n**4. Community Engagement**\n- Answer questions on Reddit, Quora\n- Participate in industry forums\n- Create tools/calculators → natural backlinks\n\n**5. Broken Link Building**\n- Find broken links on competitor sites\n- Offer your content as replacement\n- Tools: Ahrefs' Broken Backlinks report\n\n**Link Velocity** (avoid penalties):\n- Natural: 5-10 links/month for new sites\n- Aggressive: 20-30 links/month after 6 months\n- Monitor: Google Search Console for manual actions\n\n### 3.5 Content Strategy for SEO\n\n**Content Types by Funnel Stage**:\n\n**TOFU (Awareness)**:\n- Blog posts: \"Ultimate Guide to [Topic]\"\n- Listicles: \"Top 10 [Category]\"\n- Industry reports: \"[Industry] State of 2025\"\n- Target: Broad keywords, thought leadership\n\n**MOFU (Consideration)**:\n- Comparison pages: \"[Your Product] vs [Competitor]\"\n- Best of lists: \"Best [Category] for [Use Case]\"\n- How-to guides: \"How to [Solve Problem] with [Product]\"\n- Target: Solution keywords, product education\n\n**BOFU (Decision)**:\n- Product pages: \"[Product] Features & Pricing\"\n- Case studies: \"How [Customer] Achieved [Result]\"\n- Landing pages: \"Start Free Trial\"\n- Target: Brand keywords, high-intent searches\n\n**Content Calendar** (Series A minimum):\n- TOFU: 4 posts/month (1 per week)\n- MOFU: 2 posts/month\n- BOFU: 1 post/month\n- Refresh: 2 existing posts/month\n\n### 3.6 Local SEO (For Regional Offices)\n\n**Google Business Profile Setup** (per location):\n- Complete all fields: Name, address, phone, hours, category\n- Upload photos: Office, team, product (10+ images)\n- Collect reviews: Ask customers, automate via HubSpot workflow\n- Post updates: Weekly posts about company news, events\n\n**Local Citations** (US/Canada/EU):\n- Submit to: Yelp, Yellow Pages, local directories\n- NAP consistency: Name, Address, Phone identical everywhere\n- Industry directories: Software review sites (G2, Capterra)\n\n---\n\n## 4. Partnerships & Affiliate Programs\n\n### 4.1 Partnership Types & Strategy\n\n**Partnership Tiers**:\n\n**Tier 1: Strategic Partnerships** (high impact, low volume)\n- Target: Complementary SaaS tools with overlapping ICPs\n- Structure: Co-marketing, product integrations, revenue share\n- Examples: Slack ↔ Asana, Shopify ↔ Klaviyo\n- Effort: High (6-12 months to establish)\n- ROI: Very high (100+ leads/month after ramp)\n\n**Tier 2: Affiliate Partners** (scalable)\n- Target: Bloggers, review sites, industry influencers\n- Structure: Commission per sale (10-30% first year)\n- Platform: Use PartnerStack, Impact, or Rewardful\n- Effort: Medium (setup once, ongoing management)\n- ROI: Medium-High (depends on partner quality)\n\n**Tier 3: Referral Partners** (customer-driven)\n- Target: Your existing customers\n- Structure: Referral bonus ($500-$1k per SQL)\n- Platform: Built into HubSpot or standalone (Friendbuy)\n- Effort: Low (automate via workflows)\n- ROI: Medium (5-10% of customers refer)\n\n**Tier 4: Marketplace Listings** (distribution)\n- Target: Shopify App Store, Salesforce AppExchange, HubSpot Marketplace\n- Structure: Free listing + revenue share\n- Effort: Medium (initial listing, ongoing updates)\n- ROI: Low-Medium (brand visibility + discovery)\n\n### 4.2 Partnership Playbook\n\n**Step 1: Identify Partners**\n```\nCriteria:\n- Similar ICP (overlapping audience, no direct competition)\n- Product fit (complementary, not substitute)\n- Scale (similar company size, funding stage)\n- Values alignment (culture, brand positioning)\n\nResearch:\n- Tools: BuiltWith, SimilarWeb, LinkedIn Sales Nav\n- Look for: Integration pages, partner pages, co-marketing history\n```\n\n**Step 2: Outreach Template**\n```\nSubject: [YourBrand] ↔ [TheirBrand] Partnership Idea\n\nHi [Name],\n\nI'm [Your Name] at [YourBrand] - we help [ICP] with [value prop].\n\nI noticed [TheirBrand] serves a similar audience, and I think our customers would benefit from an integration between [YourProduct] and [TheirProduct].\n\nWould you be open to exploring a partnership? I'm thinking:\n- Product integration (bi-directional sync)\n- Co-marketing (joint webinar, case study)\n- Revenue share (referral fees)\n\nLet me know if you'd like to chat. Happy to send more details.\n\nBest,\n[Your Name]\n```\n\n**Step 3: Partnership Agreement**\n- Define scope (integration depth, marketing commitment)\n- Revenue model (rev share %, referral fees, co-selling)\n- Success metrics (leads, pipeline, revenue)\n- Term (12-24 months, with renewal)\n- Exit clause (90-day notice)\n\n**Step 4: Activation & Enablement**\n- Create co-branded assets (landing page, webinar deck, one-pager)\n- Train partner sales team (product demo, pitch deck, objection handling)\n- Set up tracking (UTM parameters, partner portal in HubSpot)\n\n**Step 5: Ongoing Management**\n- Quarterly business reviews (QBRs)\n- Monthly check-ins (pipeline, blockers)\n- Co-marketing calendar (1-2 activities/quarter)\n- Reporting (HubSpot dashboard for partner-sourced pipeline)\n\n### 4.3 Affiliate Program Setup\n\n**Platform Selection**:\n- **PartnerStack** - Best for B2B SaaS, native integrations\n- **Impact** - Enterprise-grade, high control\n- **Rewardful** - Lightweight, Stripe integration\n- **FirstPromoter** - Budget-friendly, good analytics\n\n**Commission Structure** (Series A typical):\n```\nTier 1: Influencers/Publishers\n- 30% recurring for 12 months\n- Or: $500 flat per SQL\n- Bonus: $1k for 10+ referrals/quarter\n\nTier 2: Bloggers/Content Creators\n- 20% recurring for 12 months\n- Or: $300 flat per SQL\n\nTier 3: Customers (Referral Program)\n- $500 per closed deal\n- Or: 1 month free for both referrer + referee\n```\n\n**Recruitment Strategy**:\n1. **Outbound**: Find industry bloggers, YouTubers, newsletter writers\n2. **Inbound**: \"Become an Affiliate\" page, promote in product\n3. **Events**: Recruit at conferences, meetups\n4. **Communities**: Reddit, LinkedIn groups, Slack communities\n\n**Affiliate Enablement Kit**:\n- Brand assets (logos, product screenshots)\n- Pre-written content (blog post templates, social posts)\n- Tracking links (unique UTM codes per affiliate)\n- Sales collateral (one-pagers, case studies, demo videos)\n\n### 4.4 Co-Marketing Campaigns\n\n**Joint Webinar Playbook**:\n```\nPlanning (6 weeks out):\n- Define topic (audience pain point, not product pitch)\n- Assign roles (host, co-host, Q&A moderator)\n- Create landing page (co-branded, dual logos)\n- Design promo assets (social graphics, email templates)\n\nPromotion (4 weeks out):\n- Email: 3 sends (announcement, reminder, last chance)\n- Social: 8-10 posts per partner (LinkedIn, Twitter)\n- Paid: $2k budget for LinkedIn ads → landing page\n- Partners: Cross-promote to each other's audiences\n\nExecution (day of):\n- 60-min format: 5min intro, 40min content, 15min Q&A\n- Record for on-demand\n- Polls/CTAs: Mid-webinar poll, end with demo CTA\n\nFollow-up (1 week after):\n- Send recording to all registrants\n- Nurture sequence: 3 emails over 2 weeks\n- Split leads: Each partner owns their referred leads\n- Report: Attendees, pipeline generated, next steps\n```\n\n**Other Co-Marketing Tactics**:\n- **Co-branded Content**: eBook, report, guide\n- **Case Study**: Joint customer success story\n- **Bundle Offer**: \"Buy [YourProduct] + [TheirProduct], save 20%\"\n- **Cross-promotion**: Feature each other in newsletters\n- **Social Media Takeover**: Guest post on each other's channels\n\n### 4.5 HubSpot Partner Tracking\n\n**Setup**:\n1. **Create Partner Property**\n - Settings → Properties → Create \"Partner Source\" dropdown\n - Values: Partner A, Partner B, Affiliate Network, etc.\n\n2. **UTM Tracking**\n - Partner links: `?utm_source=partner-name&utm_medium=referral`\n - HubSpot auto-captures UTM parameters\n\n3. **Lead Assignment**\n - Workflow: If \"Partner Source\" is set → Assign to Partner Manager\n - Notification: Slack alert when partner lead arrives\n\n4. **Reporting**\n - Dashboard: Partner-sourced leads, pipeline, revenue\n - Report to partners: Monthly performance summary\n\n---\n\n## 5. Attribution & Reporting\n\n### 5.1 Attribution Models (HubSpot Native)\n\n**Model Selection** (use multi-touch for hybrid motion):\n\n**First-Touch** - Credit to first interaction\n- Use case: Awareness campaigns, brand building\n- Pro: Shows what drives discovery\n- Con: Ignores nurturing influence\n\n**Last-Touch** - Credit to last interaction before conversion\n- Use case: Direct response, BOFU campaigns\n- Pro: Shows what closes deals\n- Con: Ignores earlier touchpoints\n\n**Multi-Touch (W-Shaped)** - Credit to first, last, and middle (40-20-40 split)\n- Use case: Hybrid PLG/Sales-Led (recommended for Series A)\n- Pro: Full-funnel view\n- Con: More complex to explain to stakeholders\n\n**HubSpot Setup**:\n- Marketing → Reports → Attribution → Select Model\n- Default: Use Multi-Touch for holistic view\n- Compare: Run reports side-by-side to see differences\n\n### 5.2 Reporting Dashboard (HubSpot)\n\n**Weekly Performance Dashboard**:\n```\nMetrics to Track:\n1. Traffic: Visits, unique visitors, bounce rate\n2. Leads: MQLs, SQLs, conversion rates\n3. Pipeline: Opportunities created, value, velocity\n4. CAC: Spend ÷ customers acquired\n5. Channel Mix: % of leads by source\n\nDimensions:\n- By Channel: Organic, Paid, Email, Social, Referral\n- By Campaign: Individual campaign performance\n- By Region: US, CA, EU breakdown\n- By Stage: TOFU, MOFU, BOFU metrics\n```\n\n**Monthly Executive Dashboard**:\n```\nKPIs:\n1. Marketing-Sourced Pipeline: $[X]M (target: $[Y]M)\n2. Marketing-Sourced Revenue: $[X]k (target: $[Y]k)\n3. Blended CAC: $[X] (target: $[Y])\n4. MQL→SQL Rate: [X]% (target: [Y]%)\n5. Pipeline Velocity: [X] days (target: [Y] days)\n6. ROMI: [X]:1 (target: 3:1+)\n\nInsights:\n- Top performing campaigns\n- Underperforming channels (kill or optimize)\n- New experiments to test next month\n- Budget reallocation recommendations\n```\n\n### 5.3 Google Analytics Setup\n\n**Events to Track** (GA4):\n```\nEngagement:\n- page_view (auto-tracked)\n- scroll (75% depth)\n- video_play (product demos)\n- file_download (whitepapers, eBooks)\n\nConversions:\n- sign_up (free trial, account created)\n- demo_request (calendar booking)\n- contact_form (inbound interest)\n- pricing_view (pricing page visit)\n\nE-commerce (if applicable):\n- add_to_cart\n- begin_checkout\n- purchase\n```\n\n**Custom Dimensions**:\n- User Type: Free vs. Paid\n- Plan Type: Starter, Pro, Enterprise\n- HubSpot Lead Status: MQL, SQL, Customer\n- Campaign: HubSpot Campaign ID\n\n**Integration with HubSpot**:\n- Use HubSpot tracking code (includes GA4 by default)\n- Or: Google Tag Manager for advanced tracking\n- Sync: GA4 audiences → HubSpot lists for retargeting\n\n---\n\n## 6. Experimentation Framework\n\n### 6.1 A/B Testing Prioritization (ICE Score)\n\n**Formula**: ICE = (Impact × Confidence × Ease) ÷ 3\n\nRate each factor 1-10:\n- **Impact**: How much will this move the needle?\n- **Confidence**: How sure are you it will work?\n- **Ease**: How easy is it to implement?\n\n**Example Tests** (sorted by ICE score):\n\n| Test | Impact | Confidence | Ease | ICE | Priority |\n|------|--------|------------|------|-----|----------|\n| CTA button color (red vs. green) | 3 | 8 | 10 | 7.0 | Low |\n| Landing page headline rewrite | 8 | 7 | 8 | 7.7 | Medium |\n| Pricing page redesign | 9 | 6 | 4 | 6.3 | Medium |\n| New lead magnet offer | 9 | 8 | 7 | 8.0 | High |\n| Add live chat to pricing page | 7 | 9 | 8 | 8.0 | High |\n\n### 6.2 Test Design & Execution\n\n**Test Template**:\n```\nHypothesis: [Adding a case study carousel to the pricing page will increase demo requests by 20% because users need social proof before committing]\n\nMetric: [Demo requests from /pricing page]\nSample Size: [1000 visitors per variant]\nDuration: [2 weeks or until significance]\nSuccess Criteria: [20% lift, 95% confidence]\n\nVariant A (Control): [Current pricing page]\nVariant B (Treatment): [Pricing page + case study carousel]\n\nTools: [HubSpot A/B test, or Google Optimize]\n```\n\n**Statistical Significance**:\n- Minimum: 95% confidence, 1000 visitors/variant\n- Use calculator: Optimizely Sample Size Calculator\n- Don't stop tests early (false positives)\n\n**Test Velocity** (Series A target):\n- 4-6 tests/month across channels\n- 70% win rate not realistic (aim for 30-40%)\n- Document losers (learnings matter)\n\n### 6.3 Common Experiments\n\n**Landing Page Tests**:\n- Headline variations (problem-focused vs. solution-focused)\n- CTA copy (\"Start Free Trial\" vs. \"Get Started\" vs. \"Try Now\")\n- Form length (5 fields vs. 2 fields)\n- Social proof placement (above vs. below fold)\n- Hero image (product screenshot vs. people vs. abstract)\n\n**Ad Tests**:\n- Creative format (static vs. video vs. carousel)\n- Messaging angle (feature-led vs. benefit-led vs. outcome-led)\n- Audience targeting (broad vs. narrow)\n- Landing page destination (homepage vs. dedicated LP)\n\n**Email Tests**:\n- Subject line length (short vs. long)\n- Personalization (generic vs. first name vs. company name)\n- Send time (morning vs. afternoon vs. evening)\n- CTA placement (top vs. middle vs. bottom)\n\n---\n\n## 7. Handoff Protocols\n\n### 7.1 MQL → SQL Handoff (Marketing → Sales)\n\n**SQL Definition Criteria** (customize for your ICP):\n```\nRequired:\n✅ Job title: Director+ (or Budget Authority confirmed)\n✅ Company size: 50-5000 employees\n✅ Budget: $10k+ annual (or Qualified Need confirmed)\n✅ Timeline: Buying within 90 days\n✅ Engagement: Demo requested OR High intent action\n\nOptional:\n✅ Industry: Target verticals\n✅ Geography: US/CA/EU\n✅ Use case: Matches product capabilities\n```\n\n**HubSpot Workflow**:\n1. Lead reaches MQL threshold (lead score >75)\n2. Trigger: Automated email to SDR\n3. SDR qualification call (BANT: Budget, Authority, Need, Timeline)\n4. If qualified → Mark as SQL, assign to AE\n5. If not qualified → Recycle to nurture, adjust lead score\n\n**SLA** (Service Level Agreement):\n- SDR responds to MQL: 4 hours\n- AE books demo with SQL: 24 hours\n- First demo: Within 3 business days of SQL status\n\n### 7.2 SQL → Opportunity Handoff (Sales → RevOps)\n\n**Opportunity Creation**:\n- AE creates opportunity in HubSpot after first demo\n- Required fields: Company, Deal value, Close date, Stage\n- Pipeline stages: Discovery → Demo → Proposal → Negotiation → Closed Won/Lost\n\n**Marketing Support Post-SQL**:\n- Retargeting ads to target accounts (ABM)\n- Send case studies, ROI calculator\n- Invite to customer webinar\n- Executive briefing (for Enterprise deals)\n\n### 7.3 Lost Opportunity Handoff (Sales → Marketing)\n\n**Recycle to Nurture**:\n- Reason: No budget, bad timing, wrong fit\n- Action: Move to \"Nurture\" list in HubSpot\n- Sequence: Quarterly check-in emails, invite to webinars\n- Re-engage: After 6-12 months, SDR re-qualification\n\n**Closed Lost Reasons** (track in HubSpot):\n- Price too high\n- Missing features\n- Chose competitor\n- No budget\n- Bad timing\n- Champion left company\n\n**Use lost reasons to inform**:\n- Product roadmap\n- Pricing changes\n- Competitive positioning\n- Messaging adjustments\n\n---\n\n## 8. Quick Reference\n\n### 8.1 Channel-Specific Benchmarks (B2B SaaS Series A)\n\n| Metric | LinkedIn | Google Search | SEO | Email | Partnerships |\n|--------|----------|---------------|-----|-------|--------------|\n| CTR | 0.4-0.9% | 2-5% | 1-3% | 15-25% | N/A |\n| CVR | 1-3% | 3-7% | 2-5% | 2-5% | 5-10% |\n| CAC | $150-400 | $80-250 | $50-150 | $20-80 | $100-300 |\n| MQL→SQL | 10-20% | 15-25% | 12-22% | 8-15% | 20-35% |\n\n### 8.2 Budget Allocation (Recommended)\n\n**Series A ($40k-60k/month)**:\n- 40% Paid Acquisition (LinkedIn + Google)\n- 25% Content/SEO\n- 20% Partnerships\n- 10% Tools/Automation\n- 5% Experiments/Testing\n\n### 8.3 Team Handoff Quick Guide\n\n**Demand Gen → Sales**:\n- Deliver: SQLs with BANT qualification\n- Frequency: Real-time via HubSpot\n- SLA: 4-hour response time\n\n**Demand Gen → Product Marketing**:\n- Request: Product positioning, competitive intel, case studies\n- Frequency: Monthly sync\n- Deliverables: Updated messaging, new collateral\n\n**Demand Gen → Marketing Ops**:\n- Request: Campaign tracking setup, attribution reports, data cleaning\n- Frequency: Weekly check-in\n- SLA: 48-hour turnaround for new campaigns\n\n**Paid Media → Creative/Brand**:\n- Request: Ad creative (10-20 variants/month)\n- Format: Specs sheet with dimensions, copy length, brand guidelines\n- SLA: 5 business days per request\n\n**SEO → Content**:\n- Request: Content based on keyword research\n- Deliverables: Content brief with target keywords, structure, length\n- Frequency: Monthly editorial calendar\n\n**Partnerships → Sales**:\n- Deliver: Partner-sourced leads with partner context\n- Co-selling: Joint calls for strategic deals\n- Frequency: Weekly partner pipeline review\n\n---\n\n## Resources\n\n### references/\n\n- **hubspot-workflows.md** - Pre-built HubSpot workflow templates for lead scoring, nurture, assignment\n- **campaign-templates.md** - Ready-to-use campaign briefs for LinkedIn, Google, SEO\n- **international-playbooks.md** - Market-specific tactics for EU, US, Canada expansion\n- **attribution-guide.md** - Deep dive on multi-touch attribution setup and analysis\n\n### scripts/\n\n- **calculate_cac.py** - Calculate blended and channel-specific CAC\n- **experiment_calculator.py** - A/B test sample size and significance calculator\n\n### assets/\n\n- **campaign-brief-template.docx** - Editable campaign planning document\n- **dashboard-template.xlsx** - Pre-configured performance dashboard\n\n---\n\n**Last Updated**: October 2025 | **Version**: 1.0\n","format":"legacy","source":"claude-code","last_sync":"2025-12-08T12:31:36.814Z","content_hash":"846b7bf37fe36a88c2b2453024ca84c1b6380a88ce16e73e36b2519918df20d1"},{"uid":"marketing.marketing-strategy-pmm","name":"marketing-strategy-pmm","category":"marketing","description":"Product marketing, positioning, GTM strategy, and competitive intelligence. Includes ICP definition, April Dunford positioning methodology, launch playbooks, competitive battlecards, and international market entry guides. Use when developing positioning, planning product launches, creating messaging, analyzing competitors, entering new markets, enabling sales, or when user mentions product marketing, positioning, GTM, go-to-market, competitive analysis, market entry, or sales enablement.","content":"---\nname: marketing-strategy-pmm\ndescription: Product marketing, positioning, GTM strategy, and competitive intelligence. Includes ICP definition, April Dunford positioning methodology, launch playbooks, competitive battlecards, and international market entry guides. Use when developing positioning, planning product launches, creating messaging, analyzing competitors, entering new markets, enabling sales, or when user mentions product marketing, positioning, GTM, go-to-market, competitive analysis, market entry, or sales enablement.\nlicense: MIT\nmetadata:\n version: 1.0.0\n author: Alireza Rezvani\n category: marketing\n domain: product-marketing\n updated: 2025-10-20\n frameworks: April-Dunford-positioning, ICP-definition, messaging-hierarchy\n target-market: B2B-SaaS, international-expansion, Series-A+\n---\n\n# Marketing Strategy & Product Marketing\n\nExpert Product Marketing playbook for Series A+ startups expanding internationally with hybrid PLG/Sales-Led motion.\n\n## Keywords\nproduct marketing, positioning, GTM, go-to-market strategy, competitive analysis, competitive intelligence, battlecards, ICP, ideal customer profile, messaging, value proposition, product launch, market entry, international expansion, sales enablement, win loss analysis, PMM, product marketing manager, market positioning, competitive landscape, sales training\n\n## Role Coverage\n\nThis skill serves:\n- **Product Marketing Manager (PMM)** - Positioning, messaging, competitive intel, launches\n- **Head of Marketing** - Strategy, budget, org design, pipeline targets\n- **Head of Growth** - Experimentation, activation, retention, growth loops\n- **CMO/VP Marketing** - Executive strategy, board reporting, team leadership\n\n## Core KPIs by Role\n\n**PMM**: Product adoption rate, win rate vs. competitors, sales velocity, launch impact metrics, competitive win rate, deal size growth\n\n**Head of Marketing**: Marketing-sourced pipeline $, CAC/LTV ratio, ROMI (3:1+ target), brand awareness lift, market share growth\n\n**Head of Growth**: Activation rate, WAU/MAU, conversion rates across funnel, payback period, viral coefficient (PLG)\n\n**CMO**: Revenue growth %, pipeline coverage (3-4x), team productivity, budget efficiency, NPS/brand health\n\n## Tech Stack Integration\n\n**HubSpot** - CRM, deal tracking, competitive loss analysis, sales enablement content\n**Google Analytics** - Product usage, activation funnels, feature adoption\n**Gong/Chorus** - Sales call analysis, competitive intelligence, objection tracking\n**Productboard** - Feature requests, customer feedback, roadmap prioritization\n**Notion/Confluence** - Internal wiki, positioning docs, competitive battlecards\n\n---\n\n## 1. Strategic Foundation\n\n### 1.1 Company Strategy Framework (Series A Context)\n\n**Current State Analysis**:\n```\nStage: Series A\nFunding: $5-15M raised\nTeam Size: 20-50 people\nRevenue: $1-5M ARR\nMarket Position: Challenger/Niche leader\nGrowth Rate Target: 3-5x YoY\n\nKey Challenges:\n- Prove product-market fit at scale\n- Expand from early adopters → mainstream\n- Enter new markets (EU/US/Canada)\n- Compete against incumbents\n- Build repeatable sales motion\n```\n\n**Strategic Priorities** (in order):\n1. **Nail positioning** - Clear, differentiated value prop\n2. **Scale acquisition** - Repeatable, efficient channels\n3. **Prove retention** - Product stickiness, expansion revenue\n4. **Expand markets** - Geographic + vertical expansion\n5. **Build brand** - Awareness, trust, category leadership\n\n### 1.2 ICP (Ideal Customer Profile) Definition\n\n**B2B SaaS ICP Framework**:\n\n**Firmographics**:\n- Company size: 50-5000 employees (Series A sweet spot)\n- Industry: SaaS, Tech, Professional Services\n- Geography: US, Canada, UK, Germany, France (prioritize by TAM)\n- Revenue: $5M-$500M annual\n- Funding stage: Seed to Growth (avoid pre-product)\n\n**Technographics**:\n- Tech stack: Modern (cloud-first, API-driven)\n- Maturity: Growing fast, willing to adopt new tools\n- Existing tools: [List competitors + complementary products]\n- Integration needs: Must integrate with [Salesforce, Slack, etc.]\n\n**Psychographics**:\n- Pain level: 7-10/10 (acute pain, not nice-to-have)\n- Buyer motivation: Efficiency, cost savings, revenue growth\n- Decision process: 2-6 month sales cycle\n- Risk tolerance: Early majority (not bleeding edge)\n\n**Buyer Personas** (3-5 personas max):\n\n**Primary: Economic Buyer** (signs contract)\n- Title: VP, Director, Head of [Department]\n- Goals: ROI, team productivity, cost reduction\n- Fears: Implementation failure, team resistance, budget waste\n- Messaging: Business outcomes, ROI, case studies\n\n**Secondary: Technical Buyer** (evaluates product)\n- Title: Senior Engineer, Architect, Tech Lead\n- Goals: Solves technical problem, easy integration\n- Fears: Technical debt, vendor lock-in, poor support\n- Messaging: Technical capabilities, architecture, security\n\n**User/Champion** (advocates internally)\n- Title: Manager, Team Lead, Power User\n- Goals: Makes their job easier, team loves it\n- Fears: Learning curve, change management\n- Messaging: UX, ease of use, quick wins\n\n**ICP Validation Checklist**:\n- [ ] 5+ paying customers match this profile\n- [ ] Fastest sales cycles (< median time to close)\n- [ ] Highest LTV (> median customer value)\n- [ ] Lowest churn (< 5% annual)\n- [ ] Strong product engagement (daily/weekly usage)\n- [ ] Referenceable (NPS 9-10, willing to do case studies)\n\n**HubSpot ICP Tracking**:\n- Create \"ICP Fit\" property: A (perfect), B (good), C (okay), D (poor)\n- Score based on firmographics, engagement, product usage\n- Report: Win rate by ICP score, pipeline by ICP score\n- Action: Focus acquisition on ICP A/B, nurture C, disqualify D\n\n### 1.3 Market Segmentation Strategy\n\n**Segmentation Dimensions**:\n\n**By Company Size** (recommend starting with one):\n- **SMB** (10-200 employees) - Self-serve PLG, low touch, $100-$2k ACV\n- **Mid-Market** (200-2000 employees) - Hybrid, inside sales, $2k-$50k ACV\n- **Enterprise** (2000+ employees) - Sales-led, field sales, $50k+ ACV\n\n**By Vertical** (choose 2-3 focus verticals):\n- Horizontal: Broad appeal (e.g., project management for any industry)\n- Vertical: Industry-specific (e.g., healthcare CRM, fintech compliance)\n- Approach: Start horizontal, add verticals as you scale\n\n**By Use Case** (messaging varies):\n- Use Case A: [e.g., Team collaboration]\n- Use Case B: [e.g., Client management]\n- Use Case C: [e.g., Project tracking]\n- Each use case = different landing page, messaging, case studies\n\n**By Geography** (Series A focus):\n- **US/Canada**: Largest TAM, fastest sales cycles, highest willingness to pay\n- **UK**: English-speaking, gateway to EU, similar buying behavior to US\n- **Germany**: Largest EU economy, high data privacy standards (GDPR leader)\n- **France**: Second largest EU market, localization critical\n- **Nordics**: High tech adoption, English proficiency, smaller markets\n\n**Segmentation Priority Matrix**:\n```\nSegment: US Mid-Market SaaS Companies (200-2000 employees)\nPriority: 1 (Highest)\nRationale:\n - Largest TAM ($5B)\n - Fastest sales cycle (60 days avg)\n - Highest win rate (35%)\n - Strong product fit (use cases align)\n - Existing customer base (50% of customers)\nBudget Allocation: 50% of marketing spend\n```\n\n---\n\n## 2. Positioning & Messaging\n\n### 2.1 Positioning Framework (April Dunford Method)\n\n**Step 1: List Your True Competitive Alternatives**\n\nNot just direct competitors - what would customers do if your product didn't exist?\n\n```\nAlternatives:\n1. Competitor A (direct)\n2. Competitor B (direct)\n3. Spreadsheets + email (status quo)\n4. Build in-house (DIY)\n5. Do nothing (ignore problem)\n```\n\n**Step 2: Isolate Your Unique Attributes**\n\nWhat do you have that alternatives don't?\n\n```\nUnique Attributes:\n1. [Feature X that no one else has]\n2. [Integration Y that's exclusive]\n3. [Approach Z that's differentiated]\n4. [Performance metric better than all]\n```\n\n**Step 3: Map Attributes to Value**\n\nWhat value do these attributes provide to customers?\n\n```\nAttribute: [Real-time collaboration]\n→ Value: Teams can work together simultaneously\n→ Outcome: 50% faster project completion\n\nAttribute: [AI-powered automation]\n→ Value: Eliminates manual data entry\n→ Outcome: Save 10 hours/week per user\n```\n\n**Step 4: Define Your Best-Fit Customers**\n\nWho cares most about this value?\n\n```\nBest-Fit: Mid-market SaaS companies (200-1000 employees)\nWhy: They have distributed teams, need real-time collaboration\nEvidence: Fastest sales cycles, lowest churn, highest NPS\n```\n\n**Step 5: Nail Your Market Category**\n\nWhat market do you dominate?\n\n```\nOptions:\n- Head-to-head: Compete in existing category (e.g., \"CRM\")\n- Big fish, small pond: Own a niche (e.g., \"CRM for agencies\")\n- Create new: Define new category (risky, expensive)\n\nDecision: [Choose based on competitive strength and budget]\n```\n\n**Step 6: Layer on Trends**\n\nWhat trends make this the right time to buy?\n\n```\nTrends:\n- Remote work explosion (2020-2025)\n- AI/ML adoption in enterprise (2024-2025)\n- Data privacy regulations (GDPR, CCPA)\n```\n\n### 2.2 Messaging Architecture\n\n**Value Proposition (One-Liner)**:\n\nTemplate: `[Product] helps [Target Customer] [Achieve Goal] by [Unique Approach]`\n\nExample: \"Acme helps mid-market SaaS teams ship 2x faster by automating project workflows with AI\"\n\n**Messaging Hierarchy**:\n\n```\nLEVEL 1: Value Proposition (one-liner)\n[Your one-liner here]\n\nLEVEL 2: Key Benefits (3-5 bullet points)\n- Benefit 1: [Speed] → Ship products 2x faster\n- Benefit 2: [Quality] → Reduce bugs by 50%\n- Benefit 3: [Collaboration] → Align teams in real-time\n- Benefit 4: [Cost] → Save $100k/year on tools\n\nLEVEL 3: Features (supporting evidence)\n- Feature → Benefit → Outcome\n- AI automation → Eliminates manual work → Save 10 hrs/week\n- Real-time sync → No version conflicts → 50% fewer errors\n- Integrations → Connect existing tools → 80% faster onboarding\n\nLEVEL 4: Proof Points\n- Customer logos: [Microsoft, Shopify, Stripe]\n- Stats: Used by 10,000+ teams, 4.8/5 G2 rating\n- Case studies: How [Customer] achieved [Outcome]\n```\n\n**Messaging by Persona**:\n\n**Economic Buyer** (VP/Director):\n- Primary concern: ROI, business outcomes\n- Tone: Professional, data-driven, results-focused\n- Key message: \"Increase revenue by 25% while reducing costs by $200k/year\"\n- Proof: ROI calculator, case studies with $ impact\n\n**Technical Buyer** (Engineer/Architect):\n- Primary concern: Technical fit, security, scalability\n- Tone: Technical, detailed, objective\n- Key message: \"Enterprise-grade architecture with 99.99% uptime and SOC 2 compliance\"\n- Proof: Technical docs, security whitepaper, architecture diagram\n\n**End User** (Manager/Individual Contributor):\n- Primary concern: Ease of use, daily workflow\n- Tone: Friendly, empathetic, practical\n- Key message: \"Spend less time on busywork, more time on what matters\"\n- Proof: Product demo, free trial, customer testimonials\n\n### 2.3 Messaging Testing & Iteration\n\n**Message Testing Framework**:\n\n1. **Qualitative** (customer interviews):\n - Ask 10-15 target customers:\n - \"How would you describe [Product] to a colleague?\"\n - \"What's the main benefit you get from [Product]?\"\n - \"Why did you choose us over [Competitor]?\"\n\n2. **Quantitative** (A/B testing):\n - Test messaging variations on:\n - Landing page headlines\n - Ad copy (LinkedIn, Google)\n - Email subject lines\n - Measure: CTR, conversion rate, demo requests\n\n3. **Sales Feedback** (win/loss analysis):\n - Ask sales team monthly:\n - \"Which message resonates most with prospects?\"\n - \"What objections are we hearing?\"\n - \"How do we compare to [Competitor] in customer's eyes?\"\n\n**Iteration Cycle**:\n- Test new messaging: 2-4 weeks\n- Analyze results: 1 week\n- Update messaging docs: 1 week\n- Train sales team: 1 week\n- Repeat quarterly\n\n---\n\n## 3. Competitive Intelligence\n\n### 3.1 Competitive Analysis Framework\n\n**Tier 1: Direct Competitors** (head-to-head, same category)\n- [Competitor A]: Market leader, $100M+ ARR\n- [Competitor B]: Fast-growing challenger, Series B\n- [Competitor C]: Open-source alternative\n\n**Tier 2: Indirect Competitors** (adjacent solutions)\n- [Alt Solution D]: Different approach, overlapping use case\n- [Alt Solution E]: Broader platform, includes your feature\n\n**Tier 3: Status Quo** (what customers do today)\n- Spreadsheets + email\n- Build in-house\n- Do nothing\n\n**Competitive Intelligence Sources**:\n1. **Product trials**: Sign up for competitor products, use actively\n2. **Website monitoring**: Track changes to pricing, messaging, features\n3. **Customer interviews**: Ask \"What alternatives did you consider?\"\n4. **Sales call recordings** (Gong/Chorus): Listen for competitor mentions\n5. **Review sites** (G2, Capterra): Read competitor reviews (pros/cons)\n6. **Job postings**: Competitor hiring = roadmap insights\n7. **Financial filings** (if public): Revenue, growth, strategy\n8. **Social media**: Follow competitor execs, product teams\n9. **Partner channels**: Talk to shared implementation partners\n10. **Industry reports**: Gartner, Forrester, IDC\n\n### 3.2 Competitive Battlecards\n\n**Battlecard Template** (create one per competitor):\n\n```\nCOMPETITOR: [Competitor A]\n\nOVERVIEW:\n- Founded: 2015\n- Funding: Series C, $75M raised\n- HQ: San Francisco\n- Size: 200 employees\n- Customers: 5,000+ companies\n- Pricing: $50-$500/user/month\n\nPOSITIONING:\n- They say: \"All-in-one platform for modern teams\"\n- Reality: Broad but shallow, not deep in any use case\n\nKEY STRENGTHS (What They Do Well):\n1. Strong brand recognition (category leader)\n2. Large feature set (breadth over depth)\n3. Extensive integrations (2,000+ apps)\n\nKEY WEAKNESSES (Where They Fall Short):\n1. Complex UI (steep learning curve)\n2. Expensive (2x our price at scale)\n3. Poor support (low NPS in reviews)\n4. Legacy architecture (slow performance)\n\nOUR ADVANTAGES:\n1. 10x easier to use (time-to-value in minutes vs. days)\n2. 50% lower cost at 100+ users\n3. Superior performance (2x faster load times)\n4. White-glove onboarding (dedicated CSM)\n\nWHEN TO WIN:\n- Customer values ease of use over features\n- Budget-conscious (not enterprise)\n- Need fast time-to-value (<1 week)\n- Poor experience with competitor (switching)\n\nWHEN TO LOSE:\n- Enterprise (>5000 employees) with complex requirements\n- Need feature X that we don't have yet\n- Deep integration with competitor's ecosystem\n- Already invested heavily in competitor (sunk cost)\n\nTALK TRACKS:\n\nObjection: \"We're already using [Competitor A]\"\nResponse: \"That's great - many of our customers came from [Competitor A]. What prompted you to explore alternatives? [Listen for pain points] Typically teams switch to us because [ease of use / cost / performance]. Would it be helpful to see a side-by-side comparison?\"\n\nObjection: \"[Competitor A] has more features\"\nResponse: \"You're right - they've been around longer and have a broader feature set. Here's what we found: most teams only use 20% of those features. Our customers love that we focus on doing [core use case] exceptionally well rather than trying to do everything. What features are most critical for your team?\"\n\nPROOF POINTS:\n- Case study: \"[Customer] switched from [Competitor A], reduced costs by 60%\"\n- Review comparison: \"[4.8 vs. 4.2 G2 rating in 'Ease of Use']\"\n- Win rate: \"35% win rate in competitive deals\"\n\nCOMPETITIVE LANDSCAPE:\n[Link to competitive positioning map]\n[Link to feature comparison matrix]\n```\n\n**Battlecard Distribution**:\n- Store in: Notion, Confluence, or sales enablement platform\n- Update frequency: Monthly (or when competitor launches major feature)\n- Access: Sales, CS, Product, Marketing teams\n- Training: Monthly competitive update calls with sales\n\n### 3.3 Win/Loss Analysis\n\n**Win/Loss Interview Process**:\n\n**Goals**:\n- Understand why you won/lost\n- Validate positioning and messaging\n- Identify product gaps\n- Track competitive trends\n\n**Process**:\n1. **Identify deals** (closed won or lost in last 30 days)\n2. **Request interview** (email or HubSpot workflow)\n3. **Conduct interview** (30-45 min, record with permission)\n4. **Analyze data** (themes, patterns, trends)\n5. **Share insights** (monthly report to product, sales, marketing)\n\n**Interview Questions** (pick 8-10):\n\n**For Wins**:\n- What problem were you trying to solve?\n- What alternatives did you evaluate?\n- Why did you choose us over [Competitor]?\n- What almost made you choose someone else?\n- What could we improve?\n\n**For Losses**:\n- What problem were you trying to solve?\n- Who did you choose instead? Why?\n- What did we do well in the sales process?\n- What could we have done differently?\n- Would you consider us in the future? When?\n\n**Data Tracking** (in HubSpot or spreadsheet):\n\n| Deal | Outcome | Reason | Competitor | Price Factor | Product Gap | Messaging Issue |\n|------|---------|--------|------------|--------------|-------------|-----------------|\n| Acme Corp | Won | Best product fit | Competitor A | No | No | No |\n| Beta Inc | Lost | Price | Competitor B | Yes | No | No |\n| Gamma LLC | Lost | Missing feature X | Built in-house | No | Yes | No |\n\n**Monthly Insights Report**:\n```\nWin/Loss Summary (March 2025):\n- Total deals analyzed: 20 (12 wins, 8 losses)\n- Win rate: 60%\n- Top win reasons:\n 1. Ease of use (8 mentions)\n 2. Better support (6 mentions)\n 3. Price (4 mentions)\n- Top loss reasons:\n 1. Missing feature X (4 mentions)\n 2. Price (3 mentions)\n 3. Competitor relationship (2 mentions)\n\nAction Items:\n- Product: Prioritize feature X (lost 4 deals)\n- Sales: Update battlecard for Competitor A (won 5 competitive deals)\n- Marketing: Create case study on \"ease of use\" theme\n```\n\n---\n\n## 4. Go-To-Market (GTM) Strategy\n\n### 4.1 GTM Motion Types\n\n**PLG (Product-Led Growth)**:\n- Entry: Free trial or freemium\n- Buyer: End user → Manager → VP\n- Sales: Low touch or self-serve\n- ACV: <$10k\n- Example: Slack, Notion, Figma\n\n**Sales-Led Growth**:\n- Entry: Demo request → Sales qualification\n- Buyer: VP → C-level\n- Sales: High touch, consultative\n- ACV: $25k+\n- Example: Salesforce, Workday, SAP\n\n**Hybrid (PLG + Sales)**:\n- Entry: Free trial for SMB, demo for Enterprise\n- Buyer: End user (PLG) or Executive (Sales-Led)\n- Sales: Self-serve → Assisted → Enterprise\n- ACV: $5k-$100k\n- Example: HubSpot, Atlassian, Zoom\n\n**Series A Recommendation**: Start with **Hybrid**\n- Reason: Faster learning, broader TAM, efficient scaling\n- Approach:\n - Bottom-up (PLG): Free trial → Paid team plan → Upgrade to Enterprise\n - Top-down (Sales): Outbound to Enterprise → Demo → POC → Close\n\n### 4.2 GTM Launch Playbook (90-Day Plan)\n\n**Pre-Launch (Days -90 to -30)**:\n\nWeek 1-4: Foundation\n- [ ] Define ICP and buyer personas\n- [ ] Develop positioning and messaging\n- [ ] Create competitive battlecards\n- [ ] Set success metrics (pipeline $, MQLs, win rate)\n\nWeek 5-8: Content & Enablement\n- [ ] Build website pages (homepage, product, pricing)\n- [ ] Create sales deck and demo script\n- [ ] Produce launch assets (one-pager, case studies, FAQs)\n- [ ] Develop email nurture sequences\n- [ ] Train sales team on positioning and talk tracks\n\nWeek 9-12: Channel Setup\n- [ ] Launch paid campaigns (LinkedIn, Google)\n- [ ] Set up HubSpot tracking and attribution\n- [ ] Publish SEO content (blog posts, guides)\n- [ ] Activate partnerships (co-marketing plans)\n- [ ] Test conversion funnels (landing page → signup)\n\n**Launch (Days 1-30)**:\n\nWeek 1: Awareness\n- [ ] Press release distribution\n- [ ] Email announcement to existing database\n- [ ] Social media campaign (LinkedIn, Twitter)\n- [ ] Paid ads go live (awareness campaigns)\n- [ ] Outbound sales blitz (top 100 accounts)\n\nWeek 2-4: Activation\n- [ ] Monitor conversion rates (daily)\n- [ ] A/B test landing pages and ad copy\n- [ ] Sales follow-up on inbound leads (<4 hour SLA)\n- [ ] Customer interviews (feedback on positioning)\n- [ ] Adjust messaging based on early signals\n\n**Post-Launch (Days 31-90)**:\n\nWeek 5-8: Optimization\n- [ ] Analyze win/loss data (why did we win/lose?)\n- [ ] Optimize underperforming channels (pause or pivot)\n- [ ] Scale winning channels (20% weekly budget increase)\n- [ ] Publish post-launch case studies\n- [ ] Expand content (SEO, demand gen)\n\nWeek 9-12: Scale\n- [ ] Enter new market segments (vertical or geo)\n- [ ] Launch partnerships (co-marketing campaigns)\n- [ ] Build PLG loops (referral program, viral features)\n- [ ] Sales team expansion (hire based on pipeline)\n- [ ] Iterate positioning (quarterly messaging refresh)\n\n### 4.3 International Market Entry (EU/US/Canada)\n\n**Market Entry Priority** (Series A recommended order):\n\n**Phase 1: US Market** (Months 1-6)\n- Why: Largest TAM, fastest sales cycles, highest ACV\n- Entry strategy:\n - Hire US-based SDRs/AEs (or partner with US sales agency)\n - Localize website (USD pricing, US phone number)\n - Paid ads (Google + LinkedIn) targeting US companies\n - Partnerships with US-based tech companies\n- Budget: 50% of total marketing spend\n- Target: $1M ARR from US by Month 6\n\n**Phase 2: UK Market** (Months 4-9)\n- Why: English-speaking, gateway to EU, similar to US\n- Entry strategy:\n - Hire UK sales rep or partner with UK agency\n - Localize pricing (GBP), GDPR compliance\n - Content localization (British spelling, cultural nuances)\n - UK partnerships (local SaaS companies)\n- Budget: 20% of marketing spend\n- Target: $500k ARR from UK by Month 9\n\n**Phase 3: DACH (Germany/Austria/Switzerland)** (Months 7-12)\n- Why: Largest EU economy, high data privacy standards\n- Entry strategy:\n - Translate website and product (German)\n - Hire German-speaking sales rep\n - GDPR compliance (critical for German market)\n - Partnerships with German tech companies\n - Local case studies and testimonials\n- Budget: 15% of marketing spend\n- Target: $300k ARR from DACH by Month 12\n\n**Phase 4: France** (Months 10-15)\n- Why: Second largest EU market, localization critical\n- Entry strategy:\n - Full French translation (website, product, support)\n - Hire French-speaking sales and support\n - French partnerships and case studies\n - Comply with French data regulations\n- Budget: 10% of marketing spend\n- Target: $200k ARR from France by Month 15\n\n**Phase 5: Canada** (Months 7-12)\n- Why: Similar to US, easier entry, smaller market\n- Entry strategy:\n - Minimal localization (CAD pricing)\n - Leverage US sales team (similar buying behavior)\n - Canadian partnerships\n- Budget: 5% of marketing spend\n- Target: $100k ARR from Canada by Month 12\n\n**Localization Checklist (per market)**:\n\n- [ ] **Website**: Translate, localize currency, phone number\n- [ ] **Product**: UI translation (if needed for that market)\n- [ ] **Pricing**: Local currency, VAT/taxes displayed\n- [ ] **Support**: Local business hours, language support\n- [ ] **Legal**: Data privacy compliance (GDPR, CCPA)\n- [ ] **Sales**: Hire local reps or partner with local agency\n- [ ] **Marketing**: Localized ads, content, case studies\n- [ ] **Payments**: Local payment methods (SEPA, iDEAL, etc.)\n\n**Budget Allocation** (international expansion):\n```\nYear 1 (Series A):\n- US: 50% ($200k)\n- UK: 20% ($80k)\n- DACH: 15% ($60k)\n- France: 10% ($40k)\n- Canada: 5% ($20k)\n\nTotal: $400k marketing spend (international)\nExpected ROI: 3:1 (marketing-sourced pipeline : spend)\n```\n\n---\n\n## 5. Product Launch Framework\n\n### 5.1 Launch Tiers (Effort vs. Impact)\n\n**Tier 1: Major Launch** (quarterly, high impact)\n- Scope: New product, major feature, platform expansion\n- Audience: Existing customers + new prospects + press\n- Effort: 6-8 weeks prep, full cross-functional launch\n- Budget: $50k-$100k (Series A)\n- Activities: Press release, webinar, email series, paid ads, sales blitz\n\n**Tier 2: Standard Launch** (monthly, medium impact)\n- Scope: Significant feature, integration, improvement\n- Audience: Existing customers + select prospects\n- Effort: 3-4 weeks prep, core team involvement\n- Budget: $10k-$25k\n- Activities: Blog post, email announcement, product update, sales enablement\n\n**Tier 3: Minor Launch** (weekly, low impact)\n- Scope: Small feature, bug fix, optimization\n- Audience: Existing customers only\n- Effort: 1 week prep, product + marketing only\n- Budget: <$5k\n- Activities: In-app notification, changelog, support docs\n\n### 5.2 Major Launch Playbook (Tier 1)\n\n**8 Weeks Before Launch**:\n\nWeek -8:\n- [ ] Kickoff meeting (Product, Marketing, Sales, CS)\n- [ ] Define launch goals (pipeline $, MQLs, press coverage)\n- [ ] Identify target audience (ICP, personas)\n- [ ] Create positioning and messaging\n- [ ] Assign roles and responsibilities\n\nWeek -7:\n- [ ] Develop GTM strategy (channels, tactics, budget)\n- [ ] Create sales enablement (deck, demo script, FAQs)\n- [ ] Plan content (blog posts, case studies, videos)\n- [ ] Design creative assets (ads, social graphics, emails)\n\nWeek -6:\n- [ ] Build landing pages (product page, demo request)\n- [ ] Set up HubSpot campaigns and tracking\n- [ ] Write press release and pitch media\n- [ ] Create email nurture sequences\n- [ ] Produce demo video\n\nWeek -5:\n- [ ] Beta test with select customers (feedback)\n- [ ] Train sales team (positioning, demo, objection handling)\n- [ ] Train CS team (onboarding, support docs)\n- [ ] Finalize launch timeline and channel mix\n- [ ] Prepare customer case studies\n\n**4 Weeks Before Launch**:\n\nWeek -4:\n- [ ] Launch paid ad campaigns (LinkedIn, Google)\n- [ ] Publish teaser content (blog, social)\n- [ ] Send pre-launch email to customer base\n- [ ] Pitch press and influencers\n- [ ] Set up webinar registration\n\nWeek -3:\n- [ ] A/B test landing pages and ad copy\n- [ ] Ramp up content production (blog posts, videos)\n- [ ] Sales prospecting (outbound to target accounts)\n- [ ] Finalize webinar content and speakers\n- [ ] Prepare launch day checklist\n\nWeek -2:\n- [ ] Send reminder emails (webinar, launch countdown)\n- [ ] Increase paid ad spend (ramp up)\n- [ ] Sales follow-up on warmed leads\n- [ ] Dry run: Test all systems (website, forms, CRM)\n- [ ] Prepare launch day assets (social posts, emails)\n\nWeek -1:\n- [ ] Final review: All assets approved\n- [ ] Pre-launch email to VIP customers and partners\n- [ ] Sales team ready (trained, motivated, quotas set)\n- [ ] CS team ready (docs updated, chat support staffed)\n- [ ] Press embargo lifts (if applicable)\n\n**Launch Week**:\n\nDay 1 (Launch Day):\n- [ ] Press release goes live (distribute to media)\n- [ ] Email announcement to full database\n- [ ] Social media blitz (LinkedIn, Twitter, Facebook)\n- [ ] Paid ads at full budget\n- [ ] Sales outbound campaign (top 500 accounts)\n- [ ] Product update in-app (notify existing users)\n- [ ] Monitor metrics (signups, demos, press pickup)\n\nDays 2-5:\n- [ ] Daily monitoring (conversion rates, funnel drop-offs)\n- [ ] A/B test optimizations (headlines, CTAs)\n- [ ] Sales follow-up (4-hour SLA on inbound leads)\n- [ ] Respond to press inquiries\n- [ ] Post customer testimonials and early wins\n- [ ] Webinar (Day 3 or 4)\n\nWeek 2:\n- [ ] Analyze launch results (vs. goals)\n- [ ] Publish post-launch content (case studies, how-to guides)\n- [ ] Sales continue outbound (sustained momentum)\n- [ ] Optimize underperforming channels\n- [ ] Scale winning channels (increase budget)\n\nWeek 3-4:\n- [ ] Post-launch report (metrics, learnings, next steps)\n- [ ] Customer feedback interviews (product improvements)\n- [ ] Win/loss analysis (why did we win/lose deals?)\n- [ ] Adjust messaging and positioning (based on feedback)\n- [ ] Plan next launch (apply learnings)\n\n### 5.3 Launch Metrics Dashboard\n\n**Leading Indicators** (track daily):\n- Landing page visitors\n- Demo requests\n- Free trial signups\n- MQLs generated\n- Sales pipeline created ($)\n\n**Lagging Indicators** (track weekly/monthly):\n- SQLs generated\n- Deals closed (count + $)\n- Win rate (vs. pre-launch)\n- Customer adoption rate (% of customers using feature)\n- NPS score (feature-specific)\n\n**HubSpot Dashboard**:\n```\nLaunch Campaign: [Q2-2025-Product-X-Launch]\n\nWEEK 1 RESULTS:\nTraffic: 10,000 visitors (goal: 8,000) ✅\nMQLs: 250 (goal: 200) ✅\nSQLs: 40 (goal: 50) ⚠️\nPipeline: $800k (goal: $1M) ⚠️\nDemos: 80 (goal: 100) ⚠️\n\nTOP CHANNELS:\n1. LinkedIn Ads: 120 MQLs, $150 CPL\n2. Email: 80 MQLs, $25 CPL\n3. Organic: 40 MQLs, $0 CPL\n\nUNDERPERFORMING:\n- Google Search: 10 MQLs, $400 CPL (pause and optimize)\n- Webinar: 50 registrants, 20% show rate (improve email reminders)\n\nNEXT ACTIONS:\n- Increase LinkedIn Ads budget by 30%\n- A/B test new landing page headline\n- Sales follow-up blitz on 40 SQLs\n```\n\n---\n\n## 6. Sales Enablement & Collaboration\n\n### 6.1 Sales Enablement Assets (Must-Have)\n\n**Core Assets**:\n\n**1. Sales Deck** (15-20 slides)\n```\nSlide 1: Title slide (logo, tagline)\nSlide 2: Agenda\nSlide 3: Company intro (mission, vision, traction)\nSlide 4: Problem statement (customer pain points)\nSlide 5: Solution overview (your product)\nSlide 6: Key benefits (3-5 bullets)\nSlide 7: Product demo (screenshots or video)\nSlide 8: Differentiation (vs. competitors)\nSlide 9: Customer logos (social proof)\nSlide 10: Case study (results-focused)\nSlide 11: Pricing and plans\nSlide 12: Implementation timeline\nSlide 13: Support and success\nSlide 14: Next steps (CTA)\nSlide 15: Q&A\n\nGuidelines:\n- Visual-first (minimal text, large images)\n- Customer-centric (benefits > features)\n- Modular (easy to skip/reorder slides)\n- Updated quarterly (or after major product changes)\n```\n\n**2. One-Pagers** (1-page PDF)\n- Product overview (what it is, who it's for, key features)\n- Competitive comparison (vs. Competitor A, B, C)\n- Case study (customer story with metrics)\n- Pricing sheet (plans, features, add-ons)\n\n**3. Battlecards** (per competitor)\n- See Section 3.2 for detailed battlecard template\n\n**4. Demo Script** (30-45 min)\n```\nDemo Flow:\n1. Intro (2 min) - Who we are, what we'll cover\n2. Discovery (5 min) - Ask about their needs, pain points\n3. Demo (20 min) - Show product (focus on their use case)\n4. Q&A (10 min) - Address objections, questions\n5. Next steps (3 min) - Define trial or POC plan\n\nDemo Tips:\n- Show, don't tell (product in action > slides)\n- Use customer data (not \"Company XYZ\" examples)\n- Focus on outcomes (not features)\n- Address objections proactively (price, competition)\n- Always drive to next step (trial, POC, proposal)\n```\n\n**5. Email Templates** (HubSpot sequences)\n- Cold outreach (prospecting)\n- Demo follow-up\n- Trial conversion\n- Proposal sent\n- Closing sequence\n\n**6. ROI Calculator** (spreadsheet or web tool)\n- Input: Customer's current costs, time spent, team size\n- Output: Savings with your product, payback period, 3-year ROI\n- Example: \"Save $150k/year, 6-month payback, 500% ROI\"\n\n### 6.2 Sales Training Program\n\n**Monthly Sales Enablement Call** (60 min):\n- Product updates (new features, roadmap)\n- Competitive landscape (new competitors, battlecard updates)\n- Win/loss insights (why we're winning/losing)\n- Best practices (top performer shares tips)\n- Q&A (open forum for questions)\n\n**Quarterly Sales Training** (half-day workshop):\n- Deep dive: Positioning and messaging refresh\n- Role-playing: Objection handling, competitive demos\n- Product training: New features, advanced use cases\n- Customer panel: Hear directly from customers (why they bought)\n\n**Sales Onboarding** (new hires):\n- Week 1: Company, product, market overview\n- Week 2: ICP, personas, messaging\n- Week 3: Competitive intelligence, battlecards\n- Week 4: Demo certification (must pass to sell)\n\n### 6.3 Marketing ↔ Sales Handoffs\n\n**MQL → SQL Handoff** (see marketing-demand-acquisition skill for details)\n\n**Product Marketing → Sales**:\n\n**Weekly Sync** (30 min):\n- Review: Win/loss insights, competitive updates\n- Share: New assets (battlecards, case studies, one-pagers)\n- Feedback: What's working, what's not\n- Request: Sales asks for specific assets (e.g., \"Need competitor X battlecard\")\n\n**Quarterly Business Review** (QBR):\n- Results: Pipeline, win rate, deal size, sales velocity\n- Insights: Top win/loss reasons, competitive trends\n- Action items: Product gaps, messaging updates, enablement needs\n\n**Communication Channels**:\n- Slack: #sales-enablement (daily questions, quick updates)\n- HubSpot: Centralized asset library (decks, one-pagers, videos)\n- Notion: Internal wiki (positioning, messaging, competitive intel)\n\n---\n\n## 7. Metrics & Analytics\n\n### 7.1 PMM KPIs (Track Monthly)\n\n**Product Adoption**:\n- % of customers using new feature (within 30 days of launch)\n- Target: >40% adoption within 90 days\n\n**Sales Velocity**:\n- Days from SQL to closed won\n- Target: Decrease by 20% YoY\n\n**Win Rate**:\n- % of opportunities won (vs. competitors)\n- Target: >30% win rate (competitive deals)\n\n**Deal Size**:\n- Average contract value (ACV)\n- Target: Increase by 25% YoY\n\n**Launch Impact**:\n- Pipeline $ generated from launch campaigns\n- Target: 3:1 ROMI (pipeline $ : marketing spend)\n\n**Competitive Win Rate**:\n- % of deals won against Competitor A, B, C\n- Target: >35% win rate vs. top competitor\n\n### 7.2 HubSpot Reporting\n\n**Custom Reports**:\n\n**1. Product Launch Impact**\n```\nMetrics: Leads, MQLs, SQLs, Pipeline $, Closed Won $\nDimensions: Campaign, Channel, Region\nFilters: Campaign = \"Q2-2025-Product-X-Launch\"\nTime period: 90 days post-launch\n```\n\n**2. Competitive Win Rate**\n```\nMetrics: Opportunities, Closed Won, Win Rate %\nDimensions: Competitor (property)\nFilters: Deal stage = Closed Won or Closed Lost\nSegment by: Competitor A, B, C, Other\n```\n\n**3. Sales Enablement Usage**\n```\nMetrics: Asset downloads, views, shares\nDimensions: Asset type (deck, battlecard, case study)\nFilters: User = Sales team\nInsight: Which assets are most used by sales\n```\n\n### 7.3 Quarterly Business Review (QBR)\n\n**QBR Template** (present to executive team):\n\n**Slide 1: Executive Summary**\n```\nQ2 2025 Highlights:\n- Launched Product X (pipeline: $2M, 500 MQLs)\n- Entered UK market (20 new customers, $400k ARR)\n- Improved win rate by 15% (competitive positioning)\n- Published 3 case studies (2x sales usage vs. Q1)\n```\n\n**Slide 2: Metrics Dashboard**\n```\nKPI Q2 Target Q2 Actual Status\n─────────────────────────────────────────────\nMQLs 800 950 ✅ +19%\nSQLs 150 140 ⚠️ -7%\nPipeline $ $4M $3.8M ⚠️ -5%\nWin Rate 30% 35% ✅ +17%\nDeal Size $45k $52k ✅ +16%\nSales Velocity 75 days 68 days ✅ -9%\n```\n\n**Slide 3: Key Insights**\n```\nWhat Worked:\n1. Product X launch exceeded MQL target by 19%\n2. Improved competitive positioning → 35% win rate\n3. UK market entry on track ($400k ARR in 3 months)\n\nWhat Didn't Work:\n1. SQL conversion rate dropped from 20% to 15%\n2. Google Ads underperformed (paused and optimizing)\n3. Competitor A launched aggressive pricing (5 lost deals)\n\nAction Items:\n1. Improve SQL qualification criteria (work with sales)\n2. Update battlecard for Competitor A (new pricing)\n3. Double down on UK market (hire local AE)\n```\n\n**Slide 4: Next Quarter Plan**\n```\nQ3 2025 Priorities:\n1. Launch Product Y (pipeline target: $3M)\n2. Enter DACH market (Germany, Austria, Switzerland)\n3. Refresh messaging and website (new positioning)\n4. Scale partnerships (3 new strategic partners)\n5. Build customer advocacy program (10 case studies)\n\nBudget: $150k (up from $120k in Q2)\nHeadcount: +1 PMM, +1 Content Marketer\n```\n\n---\n\n## 8. Quick Reference\n\n### 8.1 PMM Monthly Checklist\n\n**Week 1** (Strategy & Planning):\n- [ ] Review previous month metrics (win rate, deal size, pipeline)\n- [ ] Analyze win/loss interviews (competitive trends)\n- [ ] Update competitive battlecards (if needed)\n- [ ] Plan next month campaigns and content\n\n**Week 2** (Content & Enablement):\n- [ ] Create new sales assets (1-pager, case study, deck update)\n- [ ] Publish content (blog post, video, webinar)\n- [ ] Train sales on new positioning or product updates\n- [ ] Review sales asset usage (what's working?)\n\n**Week 3** (Launches & Campaigns):\n- [ ] Support product launches (if any)\n- [ ] Monitor campaign performance (MQLs, SQLs, pipeline)\n- [ ] Optimize underperforming channels\n- [ ] Customer interviews (feedback on positioning)\n\n**Week 4** (Reporting & Iteration):\n- [ ] Monthly metrics report (for exec team)\n- [ ] Sales enablement call (updates, Q&A)\n- [ ] Win/loss analysis (themes, trends)\n- [ ] Plan next quarter launches and strategy\n\n### 8.2 Positioning Development Timeline\n\n**Week 1**: Research\n- Customer interviews (10-15)\n- Competitive analysis\n- Market trends\n\n**Week 2**: Framework\n- April Dunford positioning exercise\n- Define unique value\n- Identify best-fit customers\n\n**Week 3**: Messaging\n- Craft value proposition\n- Build messaging hierarchy\n- Create persona-specific messaging\n\n**Week 4**: Validation\n- Test with sales team\n- A/B test on landing pages\n- Customer feedback\n\n**Week 5-6**: Rollout\n- Update website, sales decks\n- Train sales and CS teams\n- Launch campaigns with new messaging\n\n### 8.3 Team Handoff Protocols\n\n**PMM → Demand Gen**:\n- Deliver: Positioning, messaging, competitive intel, launch plans\n- Frequency: Monthly sync + ad-hoc for launches\n- SLA: 2-week lead time for major campaigns\n\n**PMM → Sales**:\n- Deliver: Battlecards, sales decks, demo scripts, objection handling\n- Frequency: Monthly enablement call + weekly Slack updates\n- SLA: 48 hours for urgent competitive questions\n\n**PMM → Product**:\n- Deliver: Customer feedback, competitive feature gaps, win/loss insights\n- Frequency: Weekly product sync\n- SLA: Quarterly roadmap input (feature prioritization)\n\n**PMM → Customer Success**:\n- Deliver: Product positioning, adoption tactics, customer education content\n- Frequency: Monthly sync\n- SLA: 1 week for new product launch enablement\n\n---\n\n## Resources\n\n### references/\n\n- **positioning-frameworks.md** - Detailed guide on April Dunford, Geoffrey Moore positioning methods\n- **launch-checklists.md** - Tier 1/2/3 launch checklists and templates\n- **international-gtm.md** - Market-by-market expansion playbooks (US, UK, DACH, France, Canada)\n- **messaging-templates.md** - Ready-to-use messaging frameworks for different personas\n\n### scripts/\n\n- **competitor_tracker.py** - Track competitor website/pricing changes\n- **win_loss_analyzer.py** - Analyze win/loss interview data for trends\n\n### assets/\n\n- **sales-deck-template.pptx** - Editable master sales deck\n- **battlecard-template.docx** - Competitive battlecard template\n- **one-pager-template.pptx** - Product one-pager design template\n- **roi-calculator.xlsx** - ROI calculator spreadsheet\n\n---\n\n**Last Updated**: October 2025 | **Version**: 1.0\n","format":"legacy","source":"claude-code","last_sync":"2025-12-08T12:31:36.814Z","content_hash":"607560e13d4f035ae00e5758cddfcd8e05386258b6047c3b37ae4b47647d7634"},{"uid":"leadership.cto-advisor","name":"cto-advisor","category":"leadership","description":"Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.","content":"---\nname: cto-advisor\ndescription: Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.\nlicense: MIT\nmetadata:\n version: 1.0.0\n author: Alireza Rezvani\n category: c-level\n domain: cto-leadership\n updated: 2025-10-20\n python-tools: tech_debt_analyzer.py, team_scaling_calculator.py\n frameworks: DORA-metrics, architecture-decision-records, engineering-metrics\n tech-stack: engineering-management, team-organization\n---\n\n# CTO Advisor\n\nStrategic frameworks and tools for technology leadership, team scaling, and engineering excellence.\n\n## Keywords\nCTO, chief technology officer, technical leadership, tech debt, technical debt, engineering team, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, ADR, architecture decision records, technology strategy, engineering leadership, engineering organization, team structure, hiring plan, technical strategy, vendor evaluation, technology selection\n\n## Quick Start\n\n### For Technical Debt Assessment\n```bash\npython scripts/tech_debt_analyzer.py\n```\nAnalyzes system architecture and provides prioritized debt reduction plan.\n\n### For Team Scaling Planning\n```bash\npython scripts/team_scaling_calculator.py\n```\nCalculates optimal hiring plan and team structure for growth.\n\n### For Architecture Decisions\nReview `references/architecture_decision_records.md` for ADR templates and examples.\n\n### For Technology Evaluation\nUse framework in `references/technology_evaluation_framework.md` for vendor selection.\n\n### For Engineering Metrics\nImplement KPIs from `references/engineering_metrics.md` for team performance tracking.\n\n## Core Responsibilities\n\n### 1. Technology Strategy\n\n#### Vision & Roadmap\n- Define 3-5 year technology vision\n- Create quarterly roadmaps\n- Align with business strategy\n- Communicate to stakeholders\n\n#### Innovation Management\n- Allocate 20% time for innovation\n- Run hackathons quarterly\n- Evaluate emerging technologies\n- Build proof of concepts\n\n#### Technical Debt Strategy\n```bash\n# Assess current debt\npython scripts/tech_debt_analyzer.py\n\n# Allocate capacity\n- Critical debt: 40% capacity\n- High debt: 25% capacity \n- Medium debt: 15% capacity\n- Low debt: Ongoing maintenance\n```\n\n### 2. Team Leadership\n\n#### Scaling Engineering\n```bash\n# Calculate scaling needs\npython scripts/team_scaling_calculator.py\n\n# Key ratios to maintain:\n- Manager:Engineer = 1:8\n- Senior:Mid:Junior = 3:4:2\n- Product:Engineering = 1:10\n- QA:Engineering = 1.5:10\n```\n\n#### Performance Management\n- Set clear OKRs quarterly\n- Conduct 1:1s weekly\n- Review performance quarterly\n- Provide growth opportunities\n\n#### Culture Building\n- Define engineering values\n- Establish coding standards\n- Create learning programs\n- Foster collaboration\n\n### 3. Architecture Governance\n\n#### Decision Making\nUse ADR template from `references/architecture_decision_records.md`:\n1. Document context and problem\n2. List all options considered\n3. Record decision and rationale\n4. Track consequences\n\n#### Technology Standards\n- Language choices\n- Framework selection\n- Database standards\n- Security requirements\n- API design guidelines\n\n#### System Design Review\n- Weekly architecture reviews\n- Design documentation standards\n- Prototype requirements\n- Performance criteria\n\n### 4. Vendor Management\n\n#### Evaluation Process\nFollow framework in `references/technology_evaluation_framework.md`:\n1. Gather requirements (Week 1)\n2. Market research (Week 1-2)\n3. Deep evaluation (Week 2-4)\n4. Decision and documentation (Week 4)\n\n#### Vendor Relationships\n- Quarterly business reviews\n- SLA monitoring\n- Cost optimization\n- Strategic partnerships\n\n### 5. Engineering Excellence\n\n#### Metrics Implementation\nFrom `references/engineering_metrics.md`:\n\n**DORA Metrics** (Deploy to production targets):\n- Deployment Frequency: >1/day\n- Lead Time: <1 day\n- MTTR: <1 hour\n- Change Failure Rate: <15%\n\n**Quality Metrics**:\n- Test Coverage: >80%\n- Code Review: 100%\n- Technical Debt: <10%\n\n**Team Health**:\n- Sprint Velocity: ±10% variance\n- Unplanned Work: <20%\n- On-call Incidents: <5/week\n\n## Weekly Cadence\n\n### Monday\n- Leadership team sync\n- Review metrics dashboard\n- Address escalations\n\n### Tuesday\n- Architecture review\n- Technical interviews\n- 1:1s with directs\n\n### Wednesday\n- Cross-functional meetings\n- Vendor meetings\n- Strategy work\n\n### Thursday\n- Team all-hands (monthly)\n- Sprint reviews (bi-weekly)\n- Technical deep dives\n\n### Friday\n- Strategic planning\n- Innovation time\n- Week recap and planning\n\n## Quarterly Planning\n\n### Q1 Focus: Foundation\n- Annual planning\n- Budget allocation\n- Team goal setting\n- Technology assessment\n\n### Q2 Focus: Execution\n- Major initiatives launch\n- Mid-year hiring push\n- Performance reviews\n- Architecture evolution\n\n### Q3 Focus: Innovation\n- Hackathon\n- Technology exploration\n- Team development\n- Process optimization\n\n### Q4 Focus: Planning\n- Next year strategy\n- Budget planning\n- Promotion cycles\n- Debt reduction sprint\n\n## Crisis Management\n\n### Incident Response\n1. **Immediate** (0-15 min):\n - Assess severity\n - Activate incident team\n - Begin communication\n\n2. **Short-term** (15-60 min):\n - Implement fixes\n - Update stakeholders\n - Monitor systems\n\n3. **Resolution** (1-24 hours):\n - Verify fix\n - Document timeline\n - Customer communication\n\n4. **Post-mortem** (48-72 hours):\n - Root cause analysis\n - Action items\n - Process improvements\n\n### Types of Crises\n\n#### Security Breach\n- Isolate affected systems\n- Engage security team\n- Legal/compliance notification\n- Customer communication plan\n\n#### Major Outage\n- All-hands response\n- Status page updates\n- Executive briefings\n- Customer outreach\n\n#### Data Loss\n- Stop writes immediately\n- Assess recovery options\n- Begin restoration\n- Impact analysis\n\n## Stakeholder Management\n\n### Board/Executive Reporting\n**Monthly**:\n- KPI dashboard\n- Risk register\n- Major initiatives status\n\n**Quarterly**:\n- Technology strategy update\n- Team growth and health\n- Innovation highlights\n- Budget review\n\n### Cross-functional Partners\n\n#### Product Team\n- Weekly roadmap sync\n- Sprint planning participation\n- Technical feasibility reviews\n- Feature estimation\n\n#### Sales/Marketing\n- Technical sales support\n- Product capability briefings\n- Customer reference calls\n- Competitive analysis\n\n#### Finance\n- Budget management\n- Cost optimization\n- Vendor negotiations\n- Capex planning\n\n## Strategic Initiatives\n\n### Digital Transformation\n1. Assess current state\n2. Define target architecture\n3. Create migration plan\n4. Execute in phases\n5. Measure and adjust\n\n### Cloud Migration\n1. Application assessment\n2. Migration strategy (7Rs)\n3. Pilot applications\n4. Full migration\n5. Optimization\n\n### Platform Engineering\n1. Define platform vision\n2. Build core services\n3. Create self-service tools\n4. Enable team adoption\n5. Measure efficiency\n\n### AI/ML Integration\n1. Identify use cases\n2. Build data infrastructure\n3. Develop models\n4. Deploy and monitor\n5. Scale adoption\n\n## Communication Templates\n\n### Technology Strategy Presentation\n```\n1. Executive Summary (1 slide)\n2. Current State Assessment (2 slides)\n3. Vision & Strategy (2 slides)\n4. Roadmap & Milestones (3 slides)\n5. Investment Required (1 slide)\n6. Risks & Mitigation (1 slide)\n7. Success Metrics (1 slide)\n```\n\n### Team All-hands\n```\n1. Wins & Recognition (5 min)\n2. Metrics Review (5 min)\n3. Strategic Updates (10 min)\n4. Demo/Deep Dive (15 min)\n5. Q&A (10 min)\n```\n\n### Board Update Email\n```\nSubject: Engineering Update - [Month]\n\nHighlights:\n• [Major achievement]\n• [Key metric improvement]\n• [Strategic progress]\n\nChallenges:\n• [Issue and mitigation]\n\nNext Month:\n• [Priority 1]\n• [Priority 2]\n\nDetailed metrics attached.\n```\n\n## Tools & Resources\n\n### Essential Tools\n- **Architecture**: Draw.io, Lucidchart, C4 Model\n- **Metrics**: DataDog, Grafana, LinearB\n- **Planning**: Jira, Confluence, Notion\n- **Communication**: Slack, Zoom, Loom\n- **Development**: GitHub, GitLab, Bitbucket\n\n### Key Resources\n- **Books**: \n - \"The Manager's Path\" - Camille Fournier\n - \"Accelerate\" - Nicole Forsgren\n - \"Team Topologies\" - Skelton & Pais\n \n- **Frameworks**:\n - DORA metrics\n - SPACE framework\n - Team Topologies\n \n- **Communities**:\n - CTO Craft\n - Engineering Leadership Slack\n - LeadDev community\n\n## Success Indicators\n\n✅ **Technical Excellence**\n- System uptime >99.9%\n- Deploy multiple times daily\n- Technical debt <10% capacity\n- Security incidents = 0\n\n✅ **Team Success**\n- Team satisfaction >8/10\n- Attrition <10%\n- Filled positions >90%\n- Diversity improving\n\n✅ **Business Impact**\n- Features on-time >80%\n- Engineering enables revenue\n- Cost per transaction decreasing\n- Innovation driving growth\n\n## Red Flags to Watch\n\n⚠️ Increasing technical debt \n⚠️ Rising attrition rate \n⚠️ Slowing velocity \n⚠️ Growing incidents \n⚠️ Team morale declining \n⚠️ Budget overruns \n⚠️ Vendor dependencies \n⚠️ Security vulnerabilities\n","format":"legacy","source":"claude-code","references":{"engineering_metrics.md":"# Engineering Metrics & KPIs Guide\n\n## Metrics Framework\n\n### DORA Metrics (DevOps Research and Assessment)\n\n#### 1. Deployment Frequency\n- **Definition**: How often code is deployed to production\n- **Target**: \n - Elite: Multiple deploys per day\n - High: Weekly to monthly\n - Medium: Monthly to bi-annually\n - Low: Less than bi-annually\n- **Measurement**: Deployments per day/week/month\n- **Improvement**: Smaller batch sizes, feature flags, CI/CD\n\n#### 2. Lead Time for Changes\n- **Definition**: Time from code commit to production\n- **Target**:\n - Elite: Less than 1 hour\n - High: 1 day to 1 week\n - Medium: 1 week to 1 month\n - Low: More than 1 month\n- **Measurement**: Median time from commit to deploy\n- **Improvement**: Automation, parallel testing, smaller changes\n\n#### 3. Mean Time to Recovery (MTTR)\n- **Definition**: Time to restore service after incident\n- **Target**:\n - Elite: Less than 1 hour\n - High: Less than 1 day\n - Medium: 1 day to 1 week\n - Low: More than 1 week\n- **Measurement**: Average incident resolution time\n- **Improvement**: Monitoring, rollback capability, runbooks\n\n#### 4. Change Failure Rate\n- **Definition**: Percentage of changes causing failures\n- **Target**:\n - Elite: 0-15%\n - High: 16-30%\n - Medium/Low: >30%\n- **Measurement**: Failed deploys / Total deploys\n- **Improvement**: Testing, code review, gradual rollouts\n\n### Engineering Productivity Metrics\n\n#### Code Quality\n| Metric | Formula | Target | Action if Below |\n|--------|---------|--------|-----------------|\n| Test Coverage | Tests / Total Code | >80% | Add unit tests |\n| Code Review Coverage | Reviewed PRs / Total PRs | 100% | Enforce review policy |\n| Technical Debt Ratio | Debt / Development Time | <10% | Dedicate debt sprints |\n| Cyclomatic Complexity | Per function/method | <10 | Refactor complex code |\n| Code Duplication | Duplicate Lines / Total | <5% | Extract common code |\n\n#### Development Velocity\n| Metric | Formula | Target | Action if Below |\n|--------|---------|--------|-----------------|\n| Sprint Velocity | Story Points / Sprint | Stable ±10% | Review estimation |\n| Cycle Time | Start to Done Time | <5 days | Reduce WIP |\n| PR Merge Time | Open to Merge | <24 hours | Smaller PRs |\n| Build Time | Code to Artifact | <10 minutes | Optimize pipeline |\n| Test Execution Time | Full Test Suite | <30 minutes | Parallelize tests |\n\n#### Team Health\n| Metric | Formula | Target | Action if Below |\n|--------|---------|--------|-----------------|\n| On-call Incidents | Incidents / Week | <5 | Improve monitoring |\n| Bug Escape Rate | Prod Bugs / Release | <5% | Improve testing |\n| Unplanned Work | Unplanned / Total | <20% | Better planning |\n| Meeting Time | Meetings / Total Time | <20% | Reduce meetings |\n| Focus Time | Uninterrupted Hours | >4h/day | Block calendars |\n\n### Business Impact Metrics\n\n#### System Performance\n| Metric | Description | Target | Business Impact |\n|--------|-------------|--------|-----------------|\n| Uptime | System availability | 99.9%+ | Revenue protection |\n| Page Load Time | Time to interactive | <3s | User retention |\n| API Response Time | P95 latency | <200ms | User experience |\n| Error Rate | Errors / Requests | <0.1% | Customer satisfaction |\n| Throughput | Requests / Second | Per requirement | Scalability |\n\n#### Product Delivery\n| Metric | Description | Target | Business Impact |\n|--------|-------------|--------|-----------------|\n| Feature Delivery Rate | Features / Quarter | Per roadmap | Market competitiveness |\n| Time to Market | Idea to Production | <3 months | First mover advantage |\n| Customer Defect Rate | Customer Bugs / Month | <10 | Customer satisfaction |\n| Feature Adoption | Users / Feature | >50% | ROI validation |\n| NPS from Engineering | Customer Score | >50 | Product quality |\n\n## Metrics Dashboards\n\n### Executive Dashboard (Weekly)\n```\n┌─────────────────────────────────────┐\n│ EXECUTIVE METRICS │\n├─────────────────────────────────────┤\n│ Uptime: 99.97% ✓ │\n│ Sprint Velocity: 142 pts ✓ │\n│ Deployment Frequency: 3.2/day ✓ │\n│ Lead Time: 4.2 hrs ✓ │\n│ MTTR: 47 min ✓ │\n│ Change Failure Rate: 8.3% ✓ │\n│ │\n│ Team Health: 8.2/10 │\n│ Tech Debt Ratio: 12% ⚠ │\n│ Feature Delivery: 85% ✓ │\n└─────────────────────────────────────┘\n```\n\n### Team Dashboard (Daily)\n```\n┌─────────────────────────────────────┐\n│ TEAM METRICS │\n├─────────────────────────────────────┤\n│ Current Sprint: │\n│ Completed: 65/100 pts (65%) │\n│ In Progress: 20 pts │\n│ Days Left: 3 │\n│ │\n│ PR Queue: 8 pending │\n│ Build Status: ✓ Passing │\n│ Test Coverage: 82.3% │\n│ Open Incidents: 2 (P2, P3) │\n│ │\n│ On-call Load: 3 pages this week │\n└─────────────────────────────────────┘\n```\n\n### Individual Dashboard (Daily)\n```\n┌─────────────────────────────────────┐\n│ DEVELOPER METRICS │\n├─────────────────────────────────────┤\n│ This Week: │\n│ PRs Merged: 8 │\n│ Code Reviews: 12 │\n│ Commits: 23 │\n│ Focus Time: 22.5 hrs │\n│ │\n│ Quality: │\n│ Test Coverage: 87% │\n│ Code Review Feedback: 95% ✓ │\n│ Bug Introduction Rate: 0% │\n└─────────────────────────────────────┘\n```\n\n## Implementation Guide\n\n### Phase 1: Foundation (Month 1)\n1. **Basic Metrics**\n - Deployment frequency\n - Build success rate\n - Uptime/availability\n - Team velocity\n\n2. **Tools Setup**\n - CI/CD instrumentation\n - Basic monitoring\n - Time tracking\n\n### Phase 2: Quality (Month 2)\n1. **Quality Metrics**\n - Test coverage\n - Code review metrics\n - Bug rates\n - Technical debt\n\n2. **Tool Integration**\n - Static analysis\n - Test reporting\n - Code quality gates\n\n### Phase 3: Performance (Month 3)\n1. **Performance Metrics**\n - DORA metrics complete\n - System performance\n - API metrics\n - Database metrics\n\n2. **Advanced Monitoring**\n - APM tools\n - Distributed tracing\n - Custom dashboards\n\n### Phase 4: Optimization (Ongoing)\n1. **Advanced Analytics**\n - Predictive metrics\n - Trend analysis\n - Anomaly detection\n - Correlation analysis\n\n## Metric Anti-patterns\n\n### What NOT to Measure\n\n❌ **Lines of Code**: Encourages bloat \n❌ **Hours Worked**: Promotes presenteeism \n❌ **Individual Velocity**: Creates competition \n❌ **Bug Count Without Context**: Discourages risk-taking \n❌ **Commit Count**: Encourages tiny commits \n\n### Goodhart's Law\n\"When a measure becomes a target, it ceases to be a good measure\"\n\n**Examples**:\n- Optimizing test coverage → Writing meaningless tests\n- Reducing bug count → Not reporting bugs\n- Increasing velocity → Inflating estimates\n- Reducing meeting time → Skipping important discussions\n\n### How to Avoid Gaming\n\n1. **Use Multiple Metrics**: No single metric tells the whole story\n2. **Focus on Trends**: Not absolute numbers\n3. **Combine Leading and Lagging**: Balance predictive and historical\n4. **Regular Review**: Adjust metrics that are being gamed\n5. **Team Ownership**: Let teams choose their metrics\n\n## OKR Framework for Engineering\n\n### Company Level OKRs\n**Objective**: Deliver exceptional product quality\n\n**Key Results**:\n- KR1: Achieve 99.95% uptime (from 99.9%)\n- KR2: Reduce customer-reported bugs by 50%\n- KR3: Improve deployment frequency to 10x/day\n\n### Engineering OKRs\n**Objective**: Build scalable, reliable infrastructure\n\n**Key Results**:\n- KR1: Migrate 80% of services to Kubernetes\n- KR2: Reduce MTTR to <30 minutes\n- KR3: Achieve 85% test coverage\n\n### Team OKRs\n**Objective**: Improve developer productivity\n\n**Key Results**:\n- KR1: Reduce build time to <5 minutes\n- KR2: Automate 90% of deployment process\n- KR3: Reduce PR review time to <4 hours\n\n## Reporting Templates\n\n### Monthly Engineering Report\n\n```markdown\n# Engineering Report - [Month Year]\n\n## Executive Summary\n- Key Achievement: [Highlight]\n- Main Challenge: [Issue and resolution]\n- Next Month Focus: [Priority]\n\n## DORA Metrics\n| Metric | This Month | Last Month | Target | Status |\n|--------|------------|------------|--------|--------|\n| Deploy Frequency | X/day | Y/day | Z/day | ✓/⚠/✗ |\n| Lead Time | X hrs | Y hrs | 8/10 \n✓ Attrition <10% annually \n✓ On-time delivery >80% \n✓ Technical debt <15% of capacity \n✓ Innovation time >20% \n\n### Warning Signs\n⚠️ Increasing MTTR trend \n⚠️ Declining velocity \n⚠️ Rising bug escape rate \n⚠️ Increasing unplanned work \n⚠️ Growing PR queue \n⚠️ Decreasing test coverage \n\n### Crisis Indicators\n🚨 Multiple production incidents per week \n🚨 Team satisfaction <6/10 \n🚨 Attrition >20% \n🚨 Technical debt >30% \n🚨 No deployments for >1 week \n🚨 Customer escalations increasing\n","technology_evaluation_framework.md":"# Technology Evaluation Framework\n\n## Evaluation Process\n\n### Phase 1: Requirements Gathering (Week 1)\n\n#### Functional Requirements\n- Core features needed\n- Integration requirements\n- Performance requirements\n- Scalability needs\n- Security requirements\n\n#### Non-Functional Requirements\n- Usability/Developer experience\n- Documentation quality\n- Community support\n- Vendor stability\n- Compliance needs\n\n#### Constraints\n- Budget limitations\n- Timeline constraints\n- Team expertise\n- Existing technology stack\n- Regulatory requirements\n\n### Phase 2: Market Research (Week 1-2)\n\n#### Identify Candidates\n1. Industry leaders (Gartner Magic Quadrant)\n2. Open-source alternatives\n3. Emerging solutions\n4. Build vs Buy analysis\n\n#### Initial Filtering\n- Eliminate options not meeting hard requirements\n- Remove options outside budget\n- Focus on 3-5 top candidates\n\n### Phase 3: Deep Evaluation (Week 2-4)\n\n#### Technical Evaluation\n- Proof of Concept (PoC)\n- Performance benchmarks\n- Security assessment\n- Integration testing\n- Scalability testing\n\n#### Business Evaluation\n- Total Cost of Ownership (TCO)\n- Return on Investment (ROI)\n- Vendor assessment\n- Risk analysis\n- Exit strategy\n\n### Phase 4: Decision (Week 4)\n\n## Evaluation Criteria Matrix\n\n### Technical Criteria (40%)\n\n| Criterion | Weight | Description | Scoring Guide |\n|-----------|--------|-------------|---------------|\n| **Performance** | 10% | Speed, throughput, latency | 5: Exceeds requirements
3: Meets requirements
1: Below requirements |\n| **Scalability** | 10% | Ability to grow with needs | 5: Linear scalability
3: Some limitations
1: Hard limits |\n| **Reliability** | 8% | Uptime, fault tolerance | 5: 99.99% SLA
3: 99.9% SLA
1: <99% SLA |\n| **Security** | 8% | Security features, compliance | 5: Exceeds standards
3: Meets standards
1: Concerns exist |\n| **Integration** | 4% | API quality, compatibility | 5: Native integration
3: Good APIs
1: Limited integration |\n\n### Business Criteria (30%)\n\n| Criterion | Weight | Description | Scoring Guide |\n|-----------|--------|-------------|---------------|\n| **Cost** | 10% | TCO including licenses, operation | 5: Under budget by >20%
3: Within budget
1: Over budget |\n| **ROI** | 8% | Value generation potential | 5: <6 month payback
3: <12 month payback
1: >24 month payback |\n| **Vendor Stability** | 6% | Financial health, market position | 5: Market leader
3: Established player
1: Startup/uncertain |\n| **Support Quality** | 6% | Support availability, SLAs | 5: 24/7 premium support
3: Business hours
1: Community only |\n\n### Operational Criteria (30%)\n\n| Criterion | Weight | Description | Scoring Guide |\n|-----------|--------|-------------|---------------|\n| **Ease of Use** | 8% | Learning curve, UX | 5: Intuitive
3: Moderate learning
1: Steep curve |\n| **Documentation** | 7% | Quality, completeness | 5: Excellent docs
3: Adequate docs
1: Poor docs |\n| **Community** | 7% | Size, activity, resources | 5: Large, active
3: Moderate
1: Small/inactive |\n| **Maintenance** | 8% | Operational overhead | 5: Fully managed
3: Some maintenance
1: High maintenance |\n\n## Vendor Evaluation Template\n\n### Vendor Profile\n- **Company Name**:\n- **Founded**:\n- **Headquarters**:\n- **Employees**:\n- **Revenue**:\n- **Funding** (if applicable):\n- **Key Customers**:\n\n### Product Assessment\n\n#### Strengths\n- [ ] Market leader position\n- [ ] Strong feature set\n- [ ] Good performance\n- [ ] Excellent support\n- [ ] Active development\n\n#### Weaknesses\n- [ ] Price point\n- [ ] Learning curve\n- [ ] Limited customization\n- [ ] Vendor lock-in\n- [ ] Missing features\n\n#### Opportunities\n- [ ] Roadmap alignment\n- [ ] Partnership potential\n- [ ] Training availability\n- [ ] Professional services\n\n#### Threats\n- [ ] Competitive alternatives\n- [ ] Market changes\n- [ ] Technology shifts\n- [ ] Acquisition risk\n\n### Financial Analysis\n\n#### Cost Breakdown\n| Component | Year 1 | Year 2 | Year 3 | Total |\n|-----------|--------|--------|--------|-------|\n| Licensing | $ | $ | $ | $ |\n| Implementation | $ | $ | $ | $ |\n| Training | $ | $ | $ | $ |\n| Support | $ | $ | $ | $ |\n| Infrastructure | $ | $ | $ | $ |\n| **Total** | **$** | **$** | **$** | **$** |\n\n#### ROI Calculation\n- **Cost Savings**: \n - Reduced manual work: $/year\n - Efficiency gains: $/year\n - Error reduction: $/year\n- **Revenue Impact**:\n - New capabilities: $/year\n - Faster time to market: $/year\n- **Payback Period**: X months\n\n### Risk Assessment\n\n| Risk | Probability | Impact | Mitigation |\n|------|------------|--------|------------|\n| Vendor goes out of business | Low/Med/High | Low/Med/High | Strategy |\n| Technology becomes obsolete | | | |\n| Integration difficulties | | | |\n| Team adoption challenges | | | |\n| Budget overrun | | | |\n| Performance issues | | | |\n\n## Build vs Buy Decision Framework\n\n### When to Build\n\n**Advantages**:\n- Full control over features\n- No vendor lock-in\n- Potential competitive advantage\n- Perfect fit for requirements\n- No licensing costs\n\n**Build when**:\n- Core business differentiator\n- Unique requirements\n- Long-term investment\n- Have expertise in-house\n- No suitable solutions exist\n\n**Hidden Costs**:\n- Development time\n- Maintenance burden\n- Security responsibility\n- Documentation needs\n- Training requirements\n\n### When to Buy\n\n**Advantages**:\n- Faster time to market\n- Proven solution\n- Vendor support\n- Regular updates\n- Shared development costs\n\n**Buy when**:\n- Commodity functionality\n- Standard requirements\n- Limited internal resources\n- Need quick solution\n- Good options available\n\n**Hidden Costs**:\n- Customization limits\n- Vendor lock-in\n- Integration effort\n- Training needs\n- Scaling costs\n\n### When to Adopt Open Source\n\n**Advantages**:\n- No licensing costs\n- Community support\n- Transparency\n- Customizable\n- No vendor lock-in\n\n**Adopt when**:\n- Strong community exists\n- Standard solution needed\n- Have technical expertise\n- Can contribute back\n- Long-term stability needed\n\n**Hidden Costs**:\n- Support costs\n- Security responsibility\n- Upgrade management\n- Integration effort\n- Potential consulting needs\n\n## Proof of Concept Guidelines\n\n### PoC Scope\n1. **Duration**: 2-4 weeks\n2. **Team**: 2-3 engineers\n3. **Environment**: Isolated/sandbox\n4. **Data**: Representative sample\n\n### Success Criteria\n- [ ] Core use cases demonstrated\n- [ ] Performance benchmarks met\n- [ ] Integration points tested\n- [ ] Security requirements validated\n- [ ] Team feedback positive\n\n### PoC Checklist\n- [ ] Environment setup documented\n- [ ] Test scenarios defined\n- [ ] Metrics collection automated\n- [ ] Team training completed\n- [ ] Results documented\n\n### PoC Report Template\n\n```markdown\n# PoC Report: [Technology Name]\n\n## Executive Summary\n- **Recommendation**: [Proceed/Stop/Investigate Further]\n- **Confidence Level**: [High/Medium/Low]\n- **Key Finding**: [One sentence summary]\n\n## Test Results\n\n### Functional Tests\n| Test Case | Result | Notes |\n|-----------|--------|-------|\n| | Pass/Fail | |\n\n### Performance Tests\n| Metric | Target | Actual | Status |\n|--------|--------|--------|---------|\n| Response Time | <100ms | Xms | ✓/✗ |\n| Throughput | >1000 req/s | X req/s | ✓/✗ |\n| CPU Usage | <70% | X% | ✓/✗ |\n| Memory Usage | <4GB | XGB | ✓/✗ |\n\n### Integration Tests\n| System | Status | Effort |\n|--------|--------|--------|\n| Database | ✓/✗ | Low/Med/High |\n| API Gateway | ✓/✗ | Low/Med/High |\n| Authentication | ✓/✗ | Low/Med/High |\n\n## Team Feedback\n- **Ease of Use**: [1-5 rating]\n- **Documentation**: [1-5 rating]\n- **Would Recommend**: [Yes/No]\n\n## Risks Identified\n1. [Risk and mitigation]\n2. [Risk and mitigation]\n\n## Next Steps\n1. [Action item]\n2. [Action item]\n```\n\n## Technology Categories\n\n### Development Platforms\n- **Languages**: TypeScript, Python, Go, Rust, Java\n- **Frameworks**: React, Node.js, Spring, Django, FastAPI\n- **Mobile**: React Native, Flutter, Swift, Kotlin\n- **Evaluation Focus**: Developer productivity, ecosystem, performance\n\n### Databases\n- **SQL**: PostgreSQL, MySQL, SQL Server\n- **NoSQL**: MongoDB, Cassandra, DynamoDB\n- **NewSQL**: CockroachDB, Vitess, TiDB\n- **Evaluation Focus**: Performance, scalability, consistency, operations\n\n### Infrastructure\n- **Cloud**: AWS, GCP, Azure\n- **Containers**: Docker, Kubernetes, Nomad\n- **Serverless**: Lambda, Cloud Functions, Vercel\n- **Evaluation Focus**: Cost, scalability, vendor lock-in, operations\n\n### Monitoring & Observability\n- **APM**: DataDog, New Relic, AppDynamics\n- **Logging**: ELK Stack, Splunk, CloudWatch\n- **Metrics**: Prometheus, Grafana, CloudWatch\n- **Evaluation Focus**: Coverage, cost, integration, insights\n\n### Security\n- **SAST**: Sonarqube, Checkmarx, Veracode\n- **DAST**: OWASP ZAP, Burp Suite\n- **Secrets**: Vault, AWS Secrets Manager\n- **Evaluation Focus**: Coverage, false positives, integration\n\n### DevOps Tools\n- **CI/CD**: Jenkins, GitLab CI, GitHub Actions\n- **IaC**: Terraform, CloudFormation, Pulumi\n- **Configuration**: Ansible, Chef, Puppet\n- **Evaluation Focus**: Flexibility, integration, learning curve\n\n## Continuous Evaluation\n\n### Quarterly Reviews\n- Technology landscape changes\n- Performance against expectations\n- Cost optimization opportunities\n- Team satisfaction\n- Market alternatives\n\n### Annual Assessment\n- Full technology stack review\n- Vendor relationship evaluation\n- Strategic alignment check\n- Technical debt assessment\n- Roadmap planning\n\n### Deprecation Planning\n- Migration strategy\n- Timeline definition\n- Risk assessment\n- Communication plan\n- Success metrics\n\n## Decision Documentation\n\nAlways document:\n1. **Why** the technology was chosen\n2. **Who** was involved in the decision\n3. **When** the decision was made\n4. **What** alternatives were considered\n5. **How** success will be measured\n\nUse Architecture Decision Records (ADRs) for significant technology choices.\n","architecture_decision_records.md":"# Architecture Decision Records (ADR) Framework\n\n## What is an ADR?\n\nArchitecture Decision Records capture important architectural decisions made along with their context and consequences. They help maintain institutional knowledge and explain why systems are built the way they are.\n\n## ADR Template\n\n### ADR-[NUMBER]: [TITLE]\n\n**Date**: YYYY-MM-DD \n**Status**: [Proposed | Accepted | Deprecated | Superseded] \n**Deciders**: [List of people involved in decision] \n**Technical Story**: [Ticket/Issue reference]\n\n#### Context and Problem Statement\n\n[Describe the context and problem that needs to be solved. What are we trying to achieve?]\n\n#### Decision Drivers\n\n- [Driver 1: e.g., Performance requirements]\n- [Driver 2: e.g., Time to market]\n- [Driver 3: e.g., Team expertise]\n- [Driver 4: e.g., Cost constraints]\n\n#### Considered Options\n\n1. **Option 1: [Name]**\n2. **Option 2: [Name]**\n3. **Option 3: [Name]**\n\n#### Decision Outcome\n\n**Chosen option**: \"[Option Name]\", because [justification]\n\n##### Positive Consequences\n- [Consequence 1]\n- [Consequence 2]\n\n##### Negative Consequences\n- [Risk 1 and mitigation]\n- [Risk 2 and mitigation]\n\n#### Pros and Cons of Options\n\n##### Option 1: [Name]\n- **Pros**:\n - [Advantage 1]\n - [Advantage 2]\n- **Cons**:\n - [Disadvantage 1]\n - [Disadvantage 2]\n\n##### Option 2: [Name]\n[Repeat structure]\n\n#### Links\n- [Related ADRs]\n- [Documentation]\n- [Research/PoCs]\n\n---\n\n## Example ADRs\n\n### ADR-001: Microservices Architecture\n\n**Date**: 2024-01-15 \n**Status**: Accepted \n**Deciders**: CTO, VP Engineering, Tech Leads \n**Technical Story**: ARCH-001\n\n#### Context and Problem Statement\n\nOur monolithic application is becoming difficult to scale and deploy. Different teams are stepping on each other's toes, and deployment cycles are getting longer. We need to decide on our architectural approach for the next 3-5 years.\n\n#### Decision Drivers\n\n- Need for independent team deployment\n- Requirement to scale different components independently\n- Different components have different performance characteristics\n- Team size growing from 25 to 75+ engineers\n- Need to support multiple technology stacks\n\n#### Considered Options\n\n1. **Keep Monolith**: Continue with current architecture\n2. **Modular Monolith**: Break into modules but single deployment\n3. **Microservices**: Full service-oriented architecture\n4. **Serverless**: Function-as-a-Service approach\n\n#### Decision Outcome\n\n**Chosen option**: \"Microservices\", because it best supports our team autonomy needs and scaling requirements, despite added complexity.\n\n##### Positive Consequences\n- Teams can deploy independently\n- Services can scale based on individual needs\n- Technology diversity is possible\n- Fault isolation improved\n\n##### Negative Consequences\n- Increased operational complexity - Mitigated by investing in DevOps\n- Network latency between services - Mitigated by careful service boundaries\n- Data consistency challenges - Mitigated by event sourcing patterns\n\n---\n\n### ADR-002: Container Orchestration Platform\n\n**Date**: 2024-02-01 \n**Status**: Accepted \n**Deciders**: CTO, DevOps Lead, Platform Team \n**Technical Story**: INFRA-045\n\n#### Context and Problem Statement\n\nWith the move to microservices (ADR-001), we need a container orchestration platform to manage deployment, scaling, and operations of application containers.\n\n#### Decision Drivers\n\n- Need for automated deployment and scaling\n- High availability requirements (99.9% SLA)\n- Multi-cloud strategy (avoid vendor lock-in)\n- Team familiarity and ecosystem maturity\n- Cost considerations\n\n#### Considered Options\n\n1. **Kubernetes**: Industry standard, self-managed\n2. **Amazon ECS**: AWS-native solution\n3. **Docker Swarm**: Simpler alternative\n4. **Nomad**: HashiCorp solution\n\n#### Decision Outcome\n\n**Chosen option**: \"Kubernetes\", because of its maturity, ecosystem, and multi-cloud support.\n\n##### Positive Consequences\n- Industry standard with huge ecosystem\n- Multi-cloud compatible\n- Strong community support\n- Extensive tooling available\n\n##### Negative Consequences\n- Steep learning curve - Mitigated by training and hiring\n- Operational complexity - Mitigated by managed Kubernetes (EKS/GKE)\n\n---\n\n### ADR-003: API Gateway Strategy\n\n**Date**: 2024-03-15 \n**Status**: Accepted \n**Deciders**: CTO, Security Lead, API Team \n**Technical Story**: API-101\n\n#### Context and Problem Statement\n\nWith multiple microservices, we need a unified entry point for external clients that handles cross-cutting concerns like authentication, rate limiting, and monitoring.\n\n#### Decision Drivers\n\n- Security requirements (OAuth2, API keys)\n- Need for rate limiting and throttling\n- Monitoring and analytics requirements\n- Developer experience for API consumers\n- Performance (sub-100ms overhead)\n\n#### Considered Options\n\n1. **Kong**: Open-source, plugin ecosystem\n2. **AWS API Gateway**: Managed service\n3. **Istio/Envoy**: Service mesh approach\n4. **Build Custom**: In-house solution\n\n#### Decision Outcome\n\n**Chosen option**: \"Kong\", because of its flexibility and plugin ecosystem while avoiding vendor lock-in.\n\n---\n\n## Common Architecture Decisions\n\n### 1. Frontend Architecture\n- **Single Page Application (SPA)** vs **Server-Side Rendering (SSR)** vs **Static Site Generation (SSG)**\n- **React** vs **Vue** vs **Angular** vs **Svelte**\n- **Monorepo** vs **Polyrepo**\n- **Micro-frontends** vs **Monolithic frontend**\n\n### 2. Backend Architecture\n- **Monolith** vs **Microservices** vs **Serverless**\n- **REST** vs **GraphQL** vs **gRPC**\n- **Synchronous** vs **Asynchronous** communication\n- **Event-driven** vs **Request-response**\n\n### 3. Data Architecture\n- **SQL** vs **NoSQL** vs **NewSQL**\n- **Single database** vs **Database per service**\n- **CQRS** vs **Traditional CRUD**\n- **Event Sourcing** vs **State-based storage**\n\n### 4. Infrastructure Decisions\n- **Cloud provider**: AWS vs Azure vs GCP vs Multi-cloud\n- **Containers** vs **VMs** vs **Serverless**\n- **Kubernetes** vs **ECS** vs **Cloud Run**\n- **Self-hosted** vs **Managed services**\n\n### 5. Development Practices\n- **Continuous Deployment** vs **Continuous Delivery**\n- **Feature flags** vs **Branch-based deployment**\n- **Blue-green** vs **Canary** vs **Rolling deployment**\n- **GitFlow** vs **GitHub Flow** vs **GitLab Flow**\n\n## ADR Best Practices\n\n### Writing Good ADRs\n\n1. **Keep them short**: 1-2 pages maximum\n2. **Be specific**: Include concrete examples\n3. **Document why, not what**: Focus on reasoning\n4. **Include all options**: Even obviously bad ones\n5. **Be honest about drawbacks**: Every decision has trade-offs\n\n### When to Write ADRs\n\nWrite an ADR when:\n- The decision has significant impact\n- Multiple options were seriously considered\n- The decision is hard to reverse\n- You find yourself explaining the same decision repeatedly\n- There's disagreement about the approach\n\n### ADR Lifecycle\n\n1. **Proposed**: Under discussion\n2. **Accepted**: Decision made and being implemented\n3. **Deprecated**: No longer relevant but kept for history\n4. **Superseded**: Replaced by another ADR\n\n### Storage and Discovery\n\n- Store ADRs in your main repository under `docs/architecture/decisions/`\n- Use consistent numbering (ADR-001, ADR-002, etc.)\n- Create an index file linking all ADRs\n- Reference ADRs in code comments where relevant\n- Review ADRs regularly (quarterly) for relevance\n\n## Decision Evaluation Framework\n\n### Technical Factors (40%)\n- Performance impact\n- Scalability potential\n- Security implications\n- Maintainability\n- Technical debt\n\n### Business Factors (30%)\n- Time to market\n- Cost (initial and ongoing)\n- Revenue impact\n- Competitive advantage\n- Regulatory compliance\n\n### Team Factors (30%)\n- Current expertise\n- Learning curve\n- Hiring availability\n- Team preference\n- Training requirements\n\n## Anti-patterns to Avoid\n\n1. **Decision by Committee**: Too many stakeholders leading to compromise solutions\n2. **Analysis Paralysis**: Over-analyzing instead of deciding\n3. **Resume-Driven Development**: Choosing tech for personal goals\n4. **Hype-Driven Development**: Choosing the newest/coolest tech\n5. **Not-Invented-Here**: Rejecting external solutions by default\n6. **Vendor Lock-in**: Over-dependence on proprietary solutions\n7. **Premature Optimization**: Solving problems you don't have yet\n8. **Under-documentation**: Not capturing the \"why\" behind decisions\n\n## Review Checklist\n\nBefore finalizing an ADR, ensure:\n- [ ] Problem is clearly stated\n- [ ] All realistic options are considered\n- [ ] Trade-offs are honestly evaluated\n- [ ] Decision rationale is clear\n- [ ] Consequences are identified\n- [ ] Mitigation strategies are defined\n- [ ] Success metrics are established\n- [ ] Review date is set (if applicable)\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"4d093a539810d06cd6b430ee5dfca3e9251551c153dba45a6e3041c41a992a17"},{"uid":"leadership.ceo-advisor","name":"ceo-advisor","category":"leadership","description":"Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Includes strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.","content":"---\nname: ceo-advisor\ndescription: Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Includes strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.\nlicense: MIT\nmetadata:\n version: 1.0.0\n author: Alireza Rezvani\n category: c-level\n domain: ceo-leadership\n updated: 2025-10-20\n python-tools: strategy_analyzer.py, financial_scenario_analyzer.py\n frameworks: executive-decision-framework, board-governance, investor-relations\n---\n\n# CEO Advisor\n\nStrategic frameworks and tools for chief executive leadership, organizational transformation, and stakeholder management.\n\n## Keywords\nCEO, chief executive officer, executive leadership, strategic planning, board governance, investor relations, board meetings, board presentations, financial modeling, strategic decisions, organizational culture, company culture, leadership development, stakeholder management, executive strategy, crisis management, organizational transformation, investor updates, strategic initiatives, company vision\n\n## Quick Start\n\n### For Strategic Planning\n```bash\npython scripts/strategy_analyzer.py\n```\nAnalyzes strategic position and generates actionable recommendations.\n\n### For Financial Scenarios\n```bash\npython scripts/financial_scenario_analyzer.py\n```\nModels different business scenarios with risk-adjusted projections.\n\n### For Decision Making\nReview `references/executive_decision_framework.md` for structured decision processes.\n\n### For Board Management\nUse templates in `references/board_governance_investor_relations.md` for board packages.\n\n### For Culture Building\nImplement frameworks from `references/leadership_organizational_culture.md` for transformation.\n\n## Core CEO Responsibilities\n\n### 1. Vision & Strategy\n\n#### Setting Direction\n- **Vision Development**: Define 10-year aspirational future\n- **Mission Articulation**: Clear purpose and why we exist\n- **Strategy Formulation**: 3-5 year competitive positioning\n- **Value Definition**: Core beliefs and principles\n\n#### Strategic Planning Cycle\n```\nQ1: Environmental Scan\n- Market analysis\n- Competitive intelligence\n- Technology trends\n- Regulatory landscape\n\nQ2: Strategy Development\n- Strategic options generation\n- Scenario planning\n- Resource allocation\n- Risk assessment\n\nQ3: Planning & Budgeting\n- Annual operating plan\n- Budget allocation\n- OKR setting\n- Initiative prioritization\n\nQ4: Communication & Launch\n- Board approval\n- Investor communication\n- Employee cascade\n- Partner alignment\n```\n\n### 2. Capital & Resource Management\n\n#### Capital Allocation Framework\n```python\n# Run financial scenario analysis\npython scripts/financial_scenario_analyzer.py\n\n# Allocation priorities:\n1. Core Operations (40-50%)\n2. Growth Investments (25-35%)\n3. Innovation/R&D (10-15%)\n4. Strategic Reserve (10-15%)\n5. Shareholder Returns (varies)\n```\n\n#### Fundraising Strategy\n- **Seed/Series A**: Product-market fit focus\n- **Series B/C**: Growth acceleration\n- **Late Stage**: Market expansion\n- **IPO**: Public market access\n- **Debt**: Non-dilutive growth\n\n### 3. Stakeholder Leadership\n\n#### Stakeholder Priority Matrix\n```\n Influence →\n Low High\n High ┌─────────┬─────────┐\nInterest │ Keep │ Manage │\n ↑ │Informed │ Closely │\n ├─────────┼─────────┤\n Low │Monitor │ Keep │\n │ │Satisfied│\n └─────────┴─────────┘\n\nPrimary Stakeholders:\n- Board of Directors\n- Investors\n- Employees\n- Customers\n\nSecondary Stakeholders:\n- Partners\n- Community\n- Media\n- Regulators\n```\n\n### 4. Organizational Leadership\n\n#### Culture Development\nFrom `references/leadership_organizational_culture.md`:\n\n**Culture Transformation Timeline**:\n- Months 1-2: Assessment\n- Months 2-3: Design\n- Months 4-12: Implementation\n- Months 12+: Embedding\n\n**Key Levers**:\n- Leadership modeling\n- Communication\n- Systems alignment\n- Recognition\n- Accountability\n\n### 5. External Representation\n\n#### CEO Communication Calendar\n\n**Daily**:\n- Customer touchpoint\n- Team check-in\n- Metric review\n\n**Weekly**:\n- Executive team meeting\n- Board member update\n- Key customer/partner call\n- Media opportunity\n\n**Monthly**:\n- All-hands meeting\n- Board report\n- Investor update\n- Industry engagement\n\n**Quarterly**:\n- Board meeting\n- Earnings call\n- Strategy review\n- Town hall\n\n## Executive Routines\n\n### Daily CEO Schedule Template\n\n```\n6:00 AM - Personal development (reading, exercise)\n7:00 AM - Day planning & priority review\n8:00 AM - Metric dashboard review\n8:30 AM - Customer/market intelligence\n9:00 AM - Strategic work block\n10:30 AM - Meetings block\n12:00 PM - Lunch (networking/thinking)\n1:00 PM - External meetings\n3:00 PM - Internal meetings\n4:30 PM - Email/communication\n5:30 PM - Team walk-around\n6:00 PM - Transition/reflection\n```\n\n### Weekly Leadership Rhythm\n\n**Monday**: Strategy & Planning\n- Executive team meeting\n- Metrics review\n- Week planning\n\n**Tuesday**: External Focus\n- Customer meetings\n- Partner discussions\n- Investor relations\n\n**Wednesday**: Operations\n- Deep dives\n- Problem solving\n- Process review\n\n**Thursday**: People & Culture\n- 1-on-1s\n- Talent reviews\n- Culture initiatives\n\n**Friday**: Innovation & Future\n- Strategic projects\n- Learning time\n- Planning ahead\n\n## Critical CEO Decisions\n\n### Go/No-Go Decision Framework\n\nUse framework from `references/executive_decision_framework.md`:\n\n**Major Decisions Requiring Framework**:\n- M&A opportunities\n- Market expansion\n- Major pivots\n- Large investments\n- Restructuring\n- Leadership changes\n\n**Decision Checklist**:\n- [ ] Problem clearly defined\n- [ ] Data/evidence gathered\n- [ ] Options evaluated\n- [ ] Stakeholders consulted\n- [ ] Risks assessed\n- [ ] Implementation planned\n- [ ] Success metrics defined\n- [ ] Communication prepared\n\n### Crisis Management\n\n#### Crisis Leadership Playbook\n\n**Level 1 Crisis** (Department)\n- Monitor situation\n- Support as needed\n- Review afterwards\n\n**Level 2 Crisis** (Company)\n- Activate crisis team\n- Lead response\n- Communicate frequently\n\n**Level 3 Crisis** (Existential)\n- Take direct control\n- Board engagement\n- All-hands focus\n- External communication\n\n## Board Management\n\n### Board Meeting Success\n\nFrom `references/board_governance_investor_relations.md`:\n\n**Preparation Timeline**:\n- T-4 weeks: Agenda development\n- T-2 weeks: Material preparation\n- T-1 week: Package distribution\n- T-0: Meeting execution\n\n**Board Package Components**:\n1. CEO Letter (1-2 pages)\n2. Dashboard (1 page)\n3. Financial review (5 pages)\n4. Strategic updates (10 pages)\n5. Risk register (2 pages)\n6. Appendices\n\n### Managing Board Dynamics\n\n**Building Trust**:\n- Regular communication\n- No surprises\n- Transparency\n- Follow-through\n- Respect expertise\n\n**Difficult Conversations**:\n- Prepare thoroughly\n- Lead with facts\n- Own responsibility\n- Present solutions\n- Seek alignment\n\n## Investor Relations\n\n### Investor Communication\n\n**Earnings Cycle**:\n1. Pre-announcement quiet period\n2. Earnings release\n3. Conference call\n4. Follow-up meetings\n5. Conference participation\n\n**Key Messages**:\n- Growth trajectory\n- Competitive position\n- Financial performance\n- Strategic progress\n- Future outlook\n\n### Fundraising Excellence\n\n**Pitch Deck Structure**:\n1. Problem (1 slide)\n2. Solution (1-2 slides)\n3. Market (1-2 slides)\n4. Product (2-3 slides)\n5. Business Model (1 slide)\n6. Go-to-Market (1-2 slides)\n7. Competition (1 slide)\n8. Team (1 slide)\n9. Financials (2 slides)\n10. Ask (1 slide)\n\n## Performance Management\n\n### Company Scorecard\n\n**Financial Metrics**:\n- Revenue growth\n- Gross margin\n- EBITDA\n- Cash flow\n- Runway\n\n**Customer Metrics**:\n- Acquisition\n- Retention\n- NPS\n- LTV/CAC\n\n**Operational Metrics**:\n- Productivity\n- Quality\n- Efficiency\n- Innovation\n\n**People Metrics**:\n- Engagement\n- Retention\n- Diversity\n- Development\n\n### CEO Self-Assessment\n\n**Quarterly Reflection**:\n- What went well?\n- What could improve?\n- Key learnings?\n- Priority adjustments?\n\n**Annual 360 Review**:\n- Board feedback\n- Executive team input\n- Skip-level insights\n- Self-evaluation\n- Development plan\n\n## Succession Planning\n\n### CEO Succession Timeline\n\n**Ongoing**:\n- Identify internal candidates\n- Develop high potentials\n- External benchmarking\n\n**T-3 Years**:\n- Formal succession planning\n- Candidate assessment\n- Development acceleration\n\n**T-1 Year**:\n- Final selection\n- Transition planning\n- Communication strategy\n\n**Transition**:\n- Knowledge transfer\n- Stakeholder handoff\n- Gradual transition\n\n## Personal Development\n\n### CEO Learning Agenda\n\n**Core Competencies**:\n- Strategic thinking\n- Financial acumen\n- Leadership presence\n- Communication\n- Decision making\n\n**Development Activities**:\n- Executive coaching\n- Peer networking (YPO/EO)\n- Board service\n- Industry involvement\n- Continuous education\n\n### Work-Life Integration\n\n**Sustainability Practices**:\n- Protected family time\n- Exercise routine\n- Mental health support\n- Vacation planning\n- Delegation discipline\n\n**Energy Management**:\n- Know peak hours\n- Block deep work time\n- Batch similar tasks\n- Take breaks\n- Reflect daily\n\n## Tools & Resources\n\n### Essential CEO Tools\n\n**Strategy & Planning**:\n- Strategy frameworks (Porter, BCG, McKinsey)\n- Scenario planning tools\n- OKR management systems\n\n**Financial Management**:\n- Financial modeling\n- Cap table management\n- Investor CRM\n\n**Communication**:\n- Board portal\n- Investor relations platform\n- Employee communication tools\n\n**Personal Productivity**:\n- Calendar management\n- Task management\n- Note-taking system\n\n### Key Resources\n\n**Books**:\n- \"Good to Great\" - Jim Collins\n- \"The Hard Thing About Hard Things\" - Ben Horowitz\n- \"High Output Management\" - Andy Grove\n- \"The Lean Startup\" - Eric Ries\n\n**Frameworks**:\n- Jobs-to-be-Done\n- Blue Ocean Strategy\n- Balanced Scorecard\n- OKRs\n\n**Networks**:\n- YPO (Young Presidents' Organization)\n- EO (Entrepreneurs' Organization)\n- Industry associations\n- CEO peer groups\n\n## Success Metrics\n\n### CEO Effectiveness Indicators\n\n✅ **Strategic Success**\n- Vision clarity and buy-in\n- Strategy execution on track\n- Market position improving\n- Innovation pipeline strong\n\n✅ **Financial Success**\n- Revenue growth targets met\n- Profitability improving\n- Cash position strong\n- Valuation increasing\n\n✅ **Organizational Success**\n- Culture thriving\n- Talent retained\n- Engagement high\n- Succession ready\n\n✅ **Stakeholder Success**\n- Board confidence high\n- Investor satisfaction\n- Customer NPS strong\n- Employee approval rating\n\n## Red Flags\n\n⚠️ Missing targets consistently \n⚠️ High executive turnover \n⚠️ Board relationship strained \n⚠️ Culture deteriorating \n⚠️ Market share declining \n⚠️ Cash burn increasing \n⚠️ Innovation stalling \n⚠️ Personal burnout signs\n","format":"legacy","source":"claude-code","references":{"board_governance_investor_relations.md":"# Board Governance & Investor Relations Guide\n\n## Board of Directors Management\n\n### Board Composition\n\n#### Ideal Board Structure\n- **Size**: 7-9 members (odd number for voting)\n- **Independence**: Majority independent directors\n- **Diversity**: Gender, ethnicity, expertise, experience\n- **Term**: 3-year terms, staggered renewal\n\n#### Board Roles\n\n| Role | Responsibilities | Typical Background |\n|------|-----------------|-------------------|\n| Chairman | Board leadership, CEO liaison | Former CEO, Industry veteran |\n| Lead Independent Director | Independent voice, executive sessions | Senior executive experience |\n| Audit Committee Chair | Financial oversight, auditor relationship | CFO/CPA background |\n| Compensation Committee Chair | Executive compensation, succession | HR/Executive experience |\n| Nominating Committee Chair | Board composition, governance | Governance expertise |\n\n### Board Meeting Management\n\n#### Annual Board Calendar\n\n**Q1 Meeting**\n- Annual strategy review\n- Previous year performance\n- Current year priorities\n- Risk assessment update\n\n**Q2 Meeting** \n- Q1 results review\n- Strategic initiative progress\n- Competitive landscape\n- Talent review\n\n**Q3 Meeting**\n- Mid-year performance\n- Budget preview\n- Strategic planning session\n- Succession planning\n\n**Q4 Meeting**\n- Annual budget approval\n- Executive compensation\n- Board evaluation\n- Upcoming year calendar\n\n#### Meeting Preparation Timeline\n\n**T-4 Weeks**\n- Agenda draft to Chairman\n- Pre-read preparation begins\n- Committee meetings scheduled\n\n**T-2 Weeks**\n- Materials to review committee\n- Final agenda confirmation\n- Logistics coordination\n\n**T-1 Week**\n- Board package distribution\n- Pre-meeting calls as needed\n- Final preparations\n\n**T-0 Meeting Day**\n- Executive session (start)\n- Board meeting\n- Executive session (end)\n- Follow-up actions defined\n\n### Board Package Template\n\n#### Standard Package Contents\n\n1. **Cover Memo** (1 page)\n - Meeting agenda\n - Key decisions required\n - Time allocations\n\n2. **CEO Report** (3-5 pages)\n - Executive summary\n - Performance highlights\n - Strategic progress\n - Key challenges\n - Asks of the board\n\n3. **Financial Report** (5-10 pages)\n - Financial statements\n - KPI dashboard\n - Variance analysis\n - Cash position\n - Forecast update\n\n4. **Strategic Updates** (10-15 pages)\n - Initiative status\n - Market analysis\n - Competitive intelligence\n - Product roadmap\n\n5. **Committee Reports** (2-3 pages each)\n - Audit Committee\n - Compensation Committee\n - Other committees\n\n6. **Appendices**\n - Detailed financials\n - Supporting analysis\n - Previous minutes\n\n### Board Communication Best Practices\n\n#### Between Meetings\n\n**Monthly Update Email**\n```\nSubject: [Company] CEO Update - [Month Year]\n\nBoard Members,\n\nQuick update on [Month] performance:\n\nHeadlines:\n• [Key achievement]\n• [Important metric]\n• [Strategic progress]\n\nChallenges:\n• [Issue and mitigation]\n\nLooking Ahead:\n• [Upcoming milestone]\n\nDetailed dashboard attached.\n\nBest,\n[CEO Name]\n```\n\n**Flash Reports** (When needed)\n- Material events\n- Major wins/losses\n- Press coverage\n- Regulatory matters\n\n#### Managing Difficult Conversations\n\n**Delivering Bad News**\n1. Don't delay - inform promptly\n2. Lead with facts\n3. Own the responsibility\n4. Present action plan\n5. Set realistic timeline\n\n**Handling Dissent**\n1. Listen fully\n2. Acknowledge concerns\n3. Provide data/rationale\n4. Seek common ground\n5. Document decisions\n\n## Investor Relations\n\n### Investor Segmentation\n\n#### Institutional Investors\n\n**Types**:\n- Mutual funds\n- Pension funds\n- Hedge funds\n- Private equity\n- Sovereign wealth funds\n\n**Engagement Strategy**:\n- Quarterly earnings calls\n- Annual investor day\n- Conference participation\n- One-on-one meetings\n- Site visits\n\n#### Retail Investors\n\n**Channels**:\n- Website IR section\n- Annual reports\n- Proxy statements\n- Social media\n- Shareholder meetings\n\n### Earnings Communications\n\n#### Earnings Release Template\n\n```\n[COMPANY] REPORTS [QUARTER] [YEAR] RESULTS\n\n[City, Date] - [Company] (TICKER) today reported results for [quarter]:\n\nFinancial Highlights:\n• Revenue: $X (±Y% YoY)\n• Net Income: $X (±Y% YoY) \n• EPS: $X (±Y% YoY)\n• [Other key metric]\n\nCEO Commentary:\n\"[Quote about performance and outlook]\"\n\nCFO Commentary:\n\"[Quote about financial details]\"\n\nGuidance:\n[Forward-looking statements]\n\nConference Call:\nDate/Time: [Details]\nWebcast: [Link]\n\nAbout [Company]:\n[Boilerplate]\n\nContact:\n[IR contact information]\n```\n\n#### Earnings Call Script Structure\n\n**CEO Opening (5 minutes)**\n```\nGood [morning/afternoon], and welcome to [Company's] \n[Quarter] earnings call.\n\nToday I'll cover:\n1. Quarter highlights\n2. Strategic progress\n3. Market dynamics\n4. Outlook\n\n[Key points with supporting data]\n\nI'll now turn it over to our CFO...\n```\n\n**CFO Section (10 minutes)**\n```\nThank you [CEO name].\n\nFinancial Performance:\n- Revenue details by segment\n- Margin analysis\n- Cash flow review\n- Balance sheet highlights\n\nGuidance:\n- Next quarter expectations\n- Full year outlook\n- Key assumptions\n\nNow back to [CEO] for closing remarks...\n```\n\n**Q&A Management**\n- Anticipate top 10 questions\n- Prepare fact sheets\n- Designate responders\n- Bridge to key messages\n- Time management\n\n### Investor Messaging Framework\n\n#### Value Proposition\n\n**Investment Thesis Elements**:\n1. Market opportunity size\n2. Competitive advantages\n3. Growth strategy\n4. Financial model\n5. Management team\n6. Risk factors\n\n#### Key Messages Architecture\n\n**Primary Messages** (Memorize)\n1. [Core value proposition]\n2. [Differentiation]\n3. [Growth trajectory]\n\n**Supporting Points** (Have ready)\n- Market data\n- Customer proof points\n- Financial metrics\n- Strategic initiatives\n\n**Proof Points** (Document)\n- Case studies\n- Metrics\n- Third-party validation\n- Awards/recognition\n\n### Investor Day Planning\n\n#### 6-Month Planning Timeline\n\n**T-6 Months**\n- Set date and venue\n- Define objectives\n- Identify speakers\n- Begin content development\n\n**T-4 Months**\n- Develop presentations\n- Coordinate logistics\n- Begin rehearsals\n- Create save-the-date\n\n**T-2 Months**\n- Finalize content\n- Complete rehearsals\n- Send invitations\n- Prepare materials\n\n**T-1 Month**\n- Final preparations\n- Media training\n- Q&A preparation\n- Technology testing\n\n**T-0 Event Day**\n- Execute program\n- Manage Q&A\n- Network sessions\n- Follow-up plan\n\n#### Agenda Template\n\n```\n8:00 AM - Registration & Breakfast\n8:30 AM - CEO Welcome & Vision\n9:00 AM - Market Opportunity\n9:30 AM - Product Strategy & Demo\n10:00 AM - Break\n10:15 AM - Go-to-Market Strategy\n10:45 AM - Financial Overview\n11:15 AM - Q&A Panel\n12:00 PM - Networking Lunch\n1:00 PM - Facility Tour (Optional)\n```\n\n### Shareholder Activism Defense\n\n#### Early Warning Signs\n- Stake building (13D/13G filings)\n- Public criticism\n- Media campaigns\n- Proxy solicitation\n- Shareholder proposals\n\n#### Response Playbook\n\n**1. Preparation Phase**\n- Vulnerability assessment\n- Response team formation\n- Advisor engagement\n- Board alignment\n\n**2. Engagement Phase**\n- Direct dialogue\n- Understanding demands\n- Finding common ground\n- Negotiation strategy\n\n**3. Defense Phase** (if needed)\n- Public response\n- Proxy fight preparation\n- Shareholder outreach\n- Media strategy\n\n**4. Resolution Phase**\n- Settlement negotiations\n- Implementation planning\n- Communication strategy\n- Monitoring plan\n\n### Regulatory Compliance\n\n#### Key Filings\n\n| Form | Purpose | Timing |\n|------|---------|--------|\n| 10-K | Annual report | 60-90 days after FY end |\n| 10-Q | Quarterly report | 40-45 days after Q end |\n| 8-K | Material events | 4 business days |\n| DEF 14A | Proxy statement | Before annual meeting |\n| S-1/S-3 | Securities registration | As needed |\n\n#### Disclosure Requirements\n\n**Material Information**:\n- Financial results\n- Major transactions\n- Leadership changes\n- Strategic shifts\n- Legal proceedings\n- Risk changes\n\n**Regulation FD Compliance**:\n- No selective disclosure\n- Simultaneous public release\n- Documented procedures\n- Training program\n\n### Crisis Communication\n\n#### IR Crisis Response\n\n**Hour 1: Assessment**\n- Gather facts\n- Assess materiality\n- Consult legal\n- Prepare holding statement\n\n**Hours 2-4: Response**\n- Draft 8-K if required\n- Prepare FAQ\n- Update website\n- Notify exchanges\n\n**Hours 4-8: Communication**\n- Issue press release\n- Update analysts\n- Employee communication\n- Monitor reactions\n\n**Day 2+: Follow-up**\n- Investor calls\n- Media interviews\n- Ongoing updates\n- Impact assessment\n\n### Performance Metrics\n\n#### IR Effectiveness KPIs\n\n**Quantitative Metrics**:\n- Share price performance vs peers\n- Trading volume/liquidity\n- Analyst coverage\n- Institutional ownership %\n- Valuation multiples vs peers\n\n**Qualitative Metrics**:\n- Analyst sentiment\n- Media coverage tone\n- Investor feedback\n- Award recognition\n- Perception studies\n\n#### Shareholder Analysis\n\n**Ownership Tracking**:\n- Top 20 shareholders\n- Ownership changes\n- Peer ownership overlap\n- Geographic distribution\n- Investment style mix\n\n**Engagement Metrics**:\n- Meeting count\n- Conference participation\n- Earnings call attendance\n- Website analytics\n- Email engagement\n\n## Governance Best Practices\n\n### Board Effectiveness\n\n#### Annual Board Evaluation\n\n**Process**:\n1. Anonymous surveys\n2. Individual interviews\n3. Peer feedback\n4. Results compilation\n5. Action planning\n6. Progress monitoring\n\n**Evaluation Areas**:\n- Board composition\n- Meeting effectiveness\n- Information quality\n- Strategic oversight\n- Risk management\n- CEO relationship\n- Committee performance\n\n### Executive Session Management\n\n**Frequency**: Every board meeting\n**Duration**: 30-60 minutes\n**Participants**: Independent directors only\n\n**Typical Topics**:\n- CEO performance\n- Succession planning\n- Board dynamics\n- Sensitive matters\n- Executive compensation\n\n### D&O Insurance & Indemnification\n\n**Coverage Levels**:\n- Primary: $10-25M\n- Excess: $25-100M+\n- Side A: Individual protection\n- Side B: Company reimbursement\n- Side C: Securities claims\n\n**Best Practices**:\n- Annual review\n- Competitive benchmarking\n- Claims history analysis\n- Policy optimization\n- Personal coverage consideration\n\n### ESG Governance\n\n#### ESG Integration\n\n**Board Oversight**:\n- ESG committee or full board\n- Regular ESG updates\n- Metrics in dashboard\n- Risk assessment\n- Stakeholder feedback\n\n**Reporting Framework**:\n- SASB standards\n- TCFD recommendations\n- GRI guidelines\n- UN SDGs alignment\n- Integrated reporting\n\n**Investor Communication**:\n- ESG highlights in earnings\n- Dedicated ESG report\n- Website ESG section\n- ESG investor days\n- Rating agency engagement\n\n## Templates & Tools\n\n### Board Resolution Template\n\n```\nBOARD RESOLUTION\n\nWHEREAS, [background/context];\n\nWHEREAS, [additional context];\n\nNOW, THEREFORE, BE IT RESOLVED, that [specific action];\n\nFURTHER RESOLVED, that [additional actions];\n\nFURTHER RESOLVED, that [authorization].\n\nApproved this [date].\n\n_____________________\n[Secretary Name]\nCorporate Secretary\n```\n\n### Insider Trading Policy Outline\n\n1. **Scope**: All directors, officers, employees\n2. **Prohibited Activities**: Trading on MNPI\n3. **Trading Windows**: Quarterly schedule\n4. **Pre-clearance**: Required for all trades\n5. **Blackout Periods**: Defined schedule\n6. **10b5-1 Plans**: Permitted with approval\n7. **Violations**: Disciplinary action\n8. **Training**: Annual requirement\n\n### Proxy Statement Checklist\n\n- [ ] Executive compensation (CD&A)\n- [ ] Director nominees\n- [ ] Governance structure\n- [ ] Shareholder proposals\n- [ ] Audit matters\n- [ ] Related party transactions\n- [ ] Risk oversight\n- [ ] Succession planning\n- [ ] ESG disclosure\n- [ ] Virtual meeting details\n","leadership_organizational_culture.md":"# Leadership & Organizational Culture Guide\n\n## Leadership Philosophy\n\n### The Five Dimensions of CEO Leadership\n\n1. **Visionary Leadership**\n - Define compelling future state\n - Communicate vision consistently\n - Inspire action toward vision\n - Measure progress systematically\n\n2. **Strategic Leadership**\n - Set clear priorities\n - Allocate resources optimally\n - Make tough trade-offs\n - Drive execution excellence\n\n3. **Operational Leadership**\n - Establish performance standards\n - Build scalable systems\n - Drive continuous improvement\n - Ensure accountability\n\n4. **People Leadership**\n - Attract top talent\n - Develop future leaders\n - Foster engagement\n - Build inclusive culture\n\n5. **External Leadership**\n - Represent company publicly\n - Build strategic partnerships\n - Engage stakeholders effectively\n - Shape industry direction\n\n## Organizational Culture Framework\n\n### Culture Definition & Assessment\n\n#### Cultural Dimensions Model\n\n**Innovation ← → Stability**\n- Risk tolerance level\n- Change readiness\n- Experimentation mindset\n- Learning from failure\n\n**Competition ← → Collaboration**\n- Internal dynamics\n- Knowledge sharing\n- Team vs individual rewards\n- Cross-functional cooperation\n\n**Customer ← → Operations**\n- External vs internal focus\n- Customer centricity\n- Process emphasis\n- Quality standards\n\n**Short-term ← → Long-term**\n- Planning horizons\n- Investment philosophy\n- Performance metrics\n- Stakeholder balance\n\n### Culture Transformation Roadmap\n\n#### Phase 1: Assessment (Months 1-2)\n\n**Current State Analysis**:\n- Employee survey (engagement, values alignment)\n- Culture assessment (competing values framework)\n- Leadership 360 feedback\n- Exit interview analysis\n- Customer feedback integration\n\n**Gap Analysis**:\n- Current vs desired culture\n- Behavioral gaps\n- System misalignments\n- Leadership gaps\n- Communication gaps\n\n#### Phase 2: Design (Months 2-3)\n\n**Target Culture Definition**:\n- Core values articulation\n- Behavioral standards\n- Leadership principles\n- Decision principles\n- Performance expectations\n\n**Change Strategy**:\n- Stakeholder mapping\n- Communication plan\n- Training requirements\n- System changes needed\n- Quick wins identification\n\n#### Phase 3: Implementation (Months 4-12)\n\n**Launch Activities**:\n- Leadership alignment sessions\n- All-hands kickoff\n- Values workshops\n- Behavioral training\n- System updates\n\n**Reinforcement Mechanisms**:\n- Recognition programs\n- Performance integration\n- Hiring/promotion criteria\n- Story collection\n- Celebration events\n\n#### Phase 4: Embedding (Months 12+)\n\n**Sustainability Actions**:\n- Regular pulse surveys\n- Culture champions network\n- Continuous reinforcement\n- System alignment\n- Leadership modeling\n\n## Leadership Development\n\n### Executive Team Development\n\n#### Team Effectiveness Model\n\n**Foundation Elements**:\n1. **Trust** - Vulnerability-based trust\n2. **Conflict** - Healthy debate\n3. **Commitment** - Buy-in to decisions\n4. **Accountability** - Peer accountability\n5. **Results** - Collective outcomes\n\n#### Executive Team Charter\n\n```\nOur Executive Team Charter\n\nPurpose:\nLead [Company] to achieve its vision of [Vision Statement]\n\nResponsibilities:\n• Set strategic direction\n• Allocate resources\n• Drive performance\n• Develop talent\n• Shape culture\n\nOperating Principles:\n• Debate in private, unite in public\n• Challenge ideas, support people\n• Company first, function second\n• Transparency with trust\n• Accountability without blame\n\nMeeting Cadence:\n• Weekly tactical (2 hours)\n• Monthly strategic (4 hours)\n• Quarterly offsite (2 days)\n• Annual planning (3 days)\n\nDecision Rights:\n• CEO: Final decision after consultation\n• Consensus: Strategic initiatives\n• Individual: Functional operations\n• Escalation: Board-level matters\n\nSuccess Metrics:\n• Company performance vs plan\n• Employee engagement score\n• Customer satisfaction (NPS)\n• Team effectiveness rating\n```\n\n### Succession Planning\n\n#### Succession Planning Framework\n\n**CEO Succession Timeline**:\n\n**Ongoing**:\n- Identify potential successors\n- Development plan execution\n- Board exposure\n- External benchmarking\n\n**T-3 Years**:\n- Formal succession planning\n- Candidate assessment\n- Development acceleration\n- Emergency plan update\n\n**T-1 Year**:\n- Final candidate selection\n- Transition planning\n- Communication strategy\n- Onboarding preparation\n\n**Transition**:\n- Announcement\n- Knowledge transfer\n- Stakeholder introductions\n- Gradual handover\n\n#### Talent Pipeline Development\n\n**9-Box Grid for Talent Review**:\n\n```\nPerformance →\n ↑\n │ Rising │ High │ Star\nHigh│ Star │Performer│ Performer\n ├─────────┼─────────┼──────────\n │Solid │ Core │ High\nMed │Performer│Performer│ Potential\n ├─────────┼─────────┼──────────\n │ Under │Inconsist│ New/\nLow │Performer│ -ent │ Learning\n └─────────┴─────────┴──────────\n Low Medium High\n Potential →\n```\n\n**Development Strategies by Box**:\n- **Stars**: Accelerated development, stretch assignments\n- **High Performers**: Retention focus, leadership opportunities\n- **High Potentials**: Intensive coaching, skill building\n- **Core Performers**: Engagement, incremental growth\n- **Underperformers**: Performance improvement or exit\n\n### Leadership Competency Model\n\n#### Core Leadership Competencies\n\n**Strategic Thinking**\n- Vision development\n- Systems thinking\n- Innovation mindset\n- External awareness\n- Long-term planning\n\n**Execution Excellence**\n- Results orientation\n- Decision quality\n- Problem solving\n- Process management\n- Risk management\n\n**People Leadership**\n- Team building\n- Talent development\n- Communication\n- Influence\n- Emotional intelligence\n\n**Personal Excellence**\n- Integrity\n- Resilience\n- Continuous learning\n- Self-awareness\n- Adaptability\n\n## Communication & Engagement\n\n### Internal Communication Strategy\n\n#### Communication Channels\n\n| Channel | Frequency | Purpose | Audience |\n|---------|-----------|---------|----------|\n| All-hands meeting | Monthly | Updates, Q&A | All employees |\n| Leadership cascade | Weekly | Alignment | Managers |\n| CEO email | Bi-weekly | Vision, recognition | All employees |\n| Town halls | Quarterly | Deep dives | All employees |\n| Skip-levels | Monthly | Direct feedback | Various levels |\n| Intranet | Daily | News, resources | All employees |\n| Slack/Teams | Real-time | Collaboration | All employees |\n\n#### CEO Communication Calendar\n\n**Weekly**:\n- Executive team meeting\n- Leadership message cascade\n- Customer/partner touchpoint\n\n**Bi-weekly**:\n- Company-wide email\n- Skip-level meetings\n- Media/analyst interaction\n\n**Monthly**:\n- All-hands meeting\n- Board member touchpoint\n- Employee roundtable\n\n**Quarterly**:\n- Earnings communication\n- Town hall deep-dive\n- Strategy review\n- Culture celebration\n\n### Employee Engagement\n\n#### Engagement Survey Framework\n\n**Dimensions Measured**:\n1. Purpose & Vision (alignment, inspiration)\n2. Leadership (trust, communication)\n3. Management (support, development)\n4. Work Environment (tools, processes)\n5. Growth (career, learning)\n6. Recognition (appreciation, fairness)\n7. Wellbeing (balance, benefits)\n8. Belonging (inclusion, connection)\n\n**Action Planning Process**:\n1. Share results transparently\n2. Identify 2-3 focus areas\n3. Create action teams\n4. Define success metrics\n5. Implement changes\n6. Communicate progress\n7. Measure impact\n\n#### Engagement Initiatives\n\n**Recognition Programs**:\n- Spot awards (peer-nominated)\n- Quarterly achievements\n- Annual excellence awards\n- Values champions\n- Innovation celebrations\n- Customer hero awards\n\n**Development Programs**:\n- Leadership academy\n- Mentorship program\n- Rotation opportunities\n- Tuition reimbursement\n- Conference attendance\n- Skill workshops\n\n**Wellbeing Initiatives**:\n- Flexible work arrangements\n- Mental health support\n- Wellness programs\n- Time-off policies\n- Family support\n- Financial wellness\n\n## Performance Management\n\n### OKR Framework\n\n#### OKR Setting Process\n\n**Company OKRs** (Annual)\n↓\n**Department OKRs** (Quarterly)\n↓\n**Team OKRs** (Quarterly)\n↓\n**Individual OKRs** (Quarterly)\n\n#### OKR Template\n\n**Objective**: [Qualitative, inspirational goal]\n\n**Key Results**:\n1. [Quantitative outcome] from [X] to [Y]\n2. [Quantitative outcome] from [X] to [Y]\n3. [Quantitative outcome] from [X] to [Y]\n\n**Example**:\n```\nObjective: Become the market leader in customer satisfaction\n\nKey Results:\n1. Increase NPS from 45 to 70\n2. Reduce support ticket resolution from 48h to 24h\n3. Achieve 95% customer retention rate (from 87%)\n```\n\n### Performance Review System\n\n#### Continuous Performance Management\n\n**Weekly**: 1-on-1 check-ins (30 min)\n- Progress on priorities\n- Obstacles/support needed\n- Feedback exchange\n- Next week focus\n\n**Monthly**: Development discussion (60 min)\n- Skill development\n- Career aspirations\n- Stretch opportunities\n- Learning plan\n\n**Quarterly**: Performance review (90 min)\n- OKR assessment\n- Competency evaluation\n- 360 feedback review\n- Development planning\n\n**Annual**: Compensation review\n- Performance rating\n- Compensation adjustment\n- Promotion decisions\n- Succession planning\n\n## Change Management\n\n### Change Leadership Model\n\n#### Eight-Step Change Process\n\n1. **Create Urgency**\n - Share compelling data\n - Highlight risks of status quo\n - Create dissatisfaction with current state\n\n2. **Build Coalition**\n - Identify change champions\n - Ensure executive alignment\n - Engage influential supporters\n\n3. **Form Vision**\n - Define clear end state\n - Create inspiring narrative\n - Develop strategy\n\n4. **Communicate Vision**\n - Multi-channel communication\n - Repetition and consistency\n - Two-way dialogue\n\n5. **Empower Action**\n - Remove barriers\n - Change systems/processes\n - Encourage risk-taking\n\n6. **Create Quick Wins**\n - Identify early victories\n - Celebrate visibly\n - Build momentum\n\n7. **Consolidate Gains**\n - Don't declare victory early\n - Continue driving change\n - Address deeper issues\n\n8. **Anchor in Culture**\n - Reinforce through systems\n - Celebrate new behaviors\n - Ensure leadership continuity\n\n### Organizational Design\n\n#### Design Principles\n\n**Customer-Centric**\n- Organize around customer needs\n- Minimize handoffs\n- Clear ownership\n- Fast decision-making\n\n**Scalable**\n- Consistent structures\n- Clear roles/responsibilities\n- Repeatable processes\n- Growth-ready\n\n**Agile**\n- Cross-functional teams\n- Rapid iteration\n- Continuous learning\n- Adaptive planning\n\n**Efficient**\n- Appropriate spans of control (5-7)\n- Minimal layers (max 5-6)\n- Clear decision rights\n- Eliminated redundancy\n\n#### Reorganization Playbook\n\n**Pre-announcement** (4-6 weeks)\n- Design new structure\n- Identify leadership\n- Plan communication\n- Prepare materials\n\n**Announcement** (Day 0)\n- All-hands meeting\n- Written communication\n- Q&A sessions\n- Manager toolkit\n\n**Transition** (30 days)\n- Role clarifications\n- Team formations\n- Process updates\n- System changes\n\n**Stabilization** (60-90 days)\n- Monitor progress\n- Address issues\n- Refine as needed\n- Celebrate success\n\n## Crisis Leadership\n\n### Crisis Response Framework\n\n#### Leadership During Crisis\n\n**Immediate Response** (0-24 hours)\n- Establish command center\n- Assess situation\n- Communicate frequently\n- Make rapid decisions\n- Show visible leadership\n\n**Stabilization** (1-7 days)\n- Implement solutions\n- Maintain communication\n- Support teams\n- Monitor progress\n- Adjust approach\n\n**Recovery** (1-4 weeks)\n- Execute recovery plan\n- Address long-term impacts\n- Learn from crisis\n- Strengthen resilience\n- Recognize heroes\n\n#### Crisis Communication\n\n**Internal Communication**:\n- Frequency: 2x daily minimum\n- Channels: Email, video, town halls\n- Content: Facts, actions, support\n- Tone: Calm, confident, caring\n\n**External Communication**:\n- Stakeholders: Customers, partners, investors, media\n- Frequency: As needed\n- Channels: Website, press, social\n- Content: Impact, response, timeline\n- Tone: Transparent, responsible\n\n## Innovation Culture\n\n### Innovation Framework\n\n#### Innovation Portfolio\n\n**Horizon 1** (70% resources)\n- Core business innovation\n- Incremental improvements\n- 6-18 month timeline\n- Lower risk\n\n**Horizon 2** (20% resources)\n- Emerging opportunities\n- Adjacent markets\n- 18-36 month timeline\n- Moderate risk\n\n**Horizon 3** (10% resources)\n- Transformational bets\n- New business models\n- 3-5 year timeline\n- Higher risk\n\n#### Innovation Programs\n\n**Innovation Time**\n- 20% time for projects\n- Hackathons quarterly\n- Innovation challenges\n- Idea platforms\n- Patent incentives\n\n**Innovation Metrics**\n- % revenue from new products\n- Ideas generated/implemented\n- Time to market\n- Innovation ROI\n- Patent applications\n\n## Diversity, Equity & Inclusion\n\n### DEI Strategy Framework\n\n#### Four Pillars of DEI\n\n1. **Representation**\n - Diverse hiring\n - Promotion equity\n - Leadership diversity\n - Board diversity\n\n2. **Inclusion**\n - Belonging index\n - Psychological safety\n - Equitable practices\n - Bias mitigation\n\n3. **Development**\n - Sponsorship programs\n - ERG support\n - Leadership development\n - Career pathways\n\n4. **Accountability**\n - DEI metrics\n - Leader goals\n - Regular reporting\n - Transparency\n\n#### DEI Metrics Dashboard\n\n| Metric | Current | Target | Timeline |\n|--------|---------|--------|----------|\n| Women in leadership | X% | Y% | Z years |\n| Ethnic diversity | X% | Y% | Z years |\n| Pay equity gap | X% | 0% | Z years |\n| Inclusion index | X/100 | Y/100 | Z years |\n| Retention equality | X% diff | 0% diff | Z years |\n\n## Executive Presence\n\n### CEO Personal Brand\n\n#### Brand Elements\n\n**Vision**: What future you're creating\n**Values**: What you stand for\n**Voice**: How you communicate\n**Visibility**: Where you show up\n**Value**: What you deliver\n\n#### Executive Communication\n\n**Speaking Frameworks**:\n\n**PREP Method**:\n- **P**oint: Main message\n- **R**eason: Why it matters\n- **E**xample: Concrete illustration\n- **P**oint: Restate message\n\n**STAR Method** (for stories):\n- **S**ituation: Context\n- **T**ask: Challenge\n- **A**ction: What was done\n- **R**esult: Outcome\n\n#### Media Training Essentials\n\n**Key Message Discipline**:\n- 3 key messages maximum\n- Bridge to messages\n- Sound bites ready\n- Avoid speculation\n- Stay on record\n\n**Interview Techniques**:\n- Pause before answering\n- Bridge to key messages\n- Use examples/stories\n- Maintain eye contact\n- Control pace\n","executive_decision_framework.md":"# Executive Decision Framework\n\n## Decision-Making Process\n\n### The DECIDE Framework\n\n**D** - Define the problem clearly \n**E** - Establish criteria for solutions \n**C** - Consider alternatives \n**I** - Identify best alternatives \n**D** - Develop and implement action plan \n**E** - Evaluate and monitor solution \n\n## Strategic Decision Categories\n\n### 1. Growth Decisions\n\n#### Market Expansion\n**Evaluation Criteria**:\n- Market size and growth rate\n- Competitive landscape\n- Regulatory environment\n- Cultural fit\n- Required investment\n- Expected ROI\n\n**Decision Matrix**:\n| Factor | Weight | Score (1-10) | Weighted Score |\n|--------|--------|--------------|----------------|\n| Market Size | 25% | | |\n| Competition | 20% | | |\n| Fit with Core | 20% | | |\n| Investment Required | 15% | | |\n| Risk Level | 10% | | |\n| Timeline to Profit | 10% | | |\n\n#### Product Development\n**Go/No-Go Criteria**:\n- Customer demand validation (>70% interest)\n- Technical feasibility confirmed\n- Positive unit economics\n- Strategic alignment\n- Available resources\n\n#### Mergers & Acquisitions\n**Due Diligence Framework**:\n1. **Strategic Fit**\n - Synergies identification\n - Cultural alignment\n - Market position enhancement\n \n2. **Financial Analysis**\n - Valuation models (DCF, Multiples, Precedent)\n - ROI projections\n - Integration costs\n \n3. **Risk Assessment**\n - Legal/regulatory issues\n - Technology compatibility\n - Talent retention\n \n4. **Integration Planning**\n - 100-day plan\n - Communication strategy\n - Success metrics\n\n### 2. Resource Allocation\n\n#### Capital Allocation Framework\n\n**Priority Levels**:\n1. **Essential** - Core operations, compliance, security\n2. **Strategic** - Growth initiatives, competitive advantage\n3. **Efficiency** - Cost reduction, productivity\n4. **Experimental** - Innovation, R&D\n\n**Allocation Guidelines**:\n- Essential: 40-50%\n- Strategic: 30-40%\n- Efficiency: 10-15%\n- Experimental: 5-10%\n\n#### Budget Decision Tree\n```\nIs it required for operations?\n├─ Yes → Essential (Auto-approve if <$X)\n└─ No → Does it drive growth?\n ├─ Yes → What's the ROI?\n │ ├─ >30% → Strategic (Approve)\n │ └─ <30% → Defer/Reject\n └─ No → Does it reduce costs?\n ├─ Yes → Payback period?\n │ ├─ <12 months → Efficiency (Approve)\n │ └─ >12 months → Defer\n └─ No → Experimental (Limited budget)\n```\n\n### 3. Organizational Decisions\n\n#### Restructuring Framework\n\n**Triggers for Restructuring**:\n- Performance below targets for 2+ quarters\n- Major strategic shift\n- M&A integration\n- Market disruption\n- Efficiency opportunity >20%\n\n**Evaluation Process**:\n1. Current state assessment\n2. Future state design\n3. Gap analysis\n4. Impact assessment\n5. Implementation planning\n6. Communication strategy\n\n#### Leadership Changes\n\n**Performance Evaluation Matrix**:\n| Dimension | Weight | Indicators |\n|-----------|--------|------------|\n| Results Delivery | 40% | KPIs, OKRs achievement |\n| Team Leadership | 25% | Engagement, retention, development |\n| Strategic Thinking | 20% | Innovation, vision, planning |\n| Culture Fit | 15% | Values alignment, collaboration |\n\n**Succession Planning**:\n- Identify 2-3 potential successors for each key role\n- Development plans for high-potentials\n- Emergency succession protocols\n- Knowledge transfer processes\n\n### 4. Crisis Management\n\n#### Crisis Response Protocol\n\n**Immediate (0-2 hours)**:\n1. Activate crisis team\n2. Assess severity and impact\n3. Implement containment measures\n4. Initial stakeholder notification\n\n**Short-term (2-24 hours)**:\n1. Develop response strategy\n2. Prepare public statements\n3. Engage legal/regulatory as needed\n4. Employee communication\n\n**Recovery (24+ hours)**:\n1. Implement solution\n2. Monitor progress\n3. Stakeholder updates\n4. Post-crisis review\n\n#### Crisis Decision Authority\n\n| Crisis Level | Decision Authority | Response Team |\n|--------------|-------------------|---------------|\n| Level 1 (Minor) | Department Head | Local team |\n| Level 2 (Moderate) | C-Suite Member | Cross-functional |\n| Level 3 (Major) | CEO | Executive team |\n| Level 4 (Critical) | CEO + Board | All hands |\n\n## Decision Support Tools\n\n### 1. SWOT-TOWS Matrix\n\n```\n Internal →\n ↓ Strengths (S) Weaknesses (W)\nExternal\n \nO SO Strategies WO Strategies\np (Leverage) (Improve)\np\no\nr\nt\n\nT ST Strategies WT Strategies\nh (Protect) (Survive)\nr\ne\na\nt\ns\n```\n\n### 2. BCG Growth-Share Matrix\n\n```\nMarket Growth Rate\n ↑\nHigh │ Stars │ Question │\n │ │ Marks │\n ├─────────┼──────────┤\nLow │ Cash │ Dogs │\n │ Cows │ │\n └─────────┴──────────┘\n High Low →\n Market Share\n```\n\n### 3. Risk-Impact Matrix\n\n```\nImpact\n ↑\nHigh │ Mitigate │ Critical │\n │ │ Focus │\n ├──────────┼──────────┤\nLow │ Accept │ Monitor │\n │ │ │\n └──────────┴──────────┘\n Low High →\n Probability\n```\n\n### 4. Eisenhower Matrix\n\n```\nUrgency\n ↑\nHigh │ Do │ Schedule │\n │ First │ │\n ├─────────┼──────────┤\nLow │ Delegate│ Eliminate│\n │ │ │\n └─────────┴──────────┘\n High Low →\n Importance\n```\n\n## Strategic Options Framework\n\n### Porter's Generic Strategies\n\n1. **Cost Leadership**\n - Operational excellence\n - Economy of scale\n - Process optimization\n - Supply chain efficiency\n\n2. **Differentiation**\n - Unique value proposition\n - Premium positioning\n - Innovation focus\n - Brand strength\n\n3. **Focus**\n - Niche markets\n - Specialized offerings\n - Deep expertise\n - Customer intimacy\n\n### Blue Ocean Strategy\n\n**Four Actions Framework**:\n- **Eliminate**: Which factors can be eliminated?\n- **Reduce**: Which factors should be reduced below industry standard?\n- **Raise**: Which factors should be raised above industry standard?\n- **Create**: Which factors should be created that the industry has never offered?\n\n## Stakeholder Management\n\n### Stakeholder Mapping\n\n```\nInfluence/Power\n ↑\nHigh │ Manage │ Key │\n │ Closely │ Players │\n ├──────────┼──────────┤\nLow │ Monitor │ Keep │\n │ │ Informed │\n └──────────┴──────────┘\n Low High →\n Interest\n```\n\n### Communication Strategy\n\n| Stakeholder | Frequency | Format | Key Messages |\n|------------|-----------|--------|--------------|\n| Board | Monthly | Report + Meeting | Strategy, Risk, Performance |\n| Investors | Quarterly | Earnings Call | Financial, Growth, Outlook |\n| Employees | Weekly | All-hands | Vision, Updates, Recognition |\n| Customers | Continuous | Multi-channel | Value, Innovation, Support |\n| Media | As needed | Press Release | Milestones, Position, Vision |\n\n## Performance Metrics\n\n### Balanced Scorecard\n\n#### Financial Perspective\n- Revenue growth rate\n- EBITDA margin\n- ROE/ROA\n- Cash conversion cycle\n- Market capitalization\n\n#### Customer Perspective\n- Customer satisfaction (NPS)\n- Market share\n- Customer retention rate\n- Customer acquisition cost\n- Customer lifetime value\n\n#### Internal Process\n- Operational efficiency\n- Time to market\n- Quality metrics\n- Innovation rate\n- Process cycle time\n\n#### Learning & Growth\n- Employee engagement\n- Talent retention\n- Training hours per employee\n- Leadership pipeline\n- Innovation index\n\n## Decision Biases to Avoid\n\n### Cognitive Biases\n\n1. **Confirmation Bias**\n - Mitigation: Seek contrarian views\n - Tool: Devil's advocate process\n\n2. **Anchoring Bias**\n - Mitigation: Multiple estimates\n - Tool: Range forecasting\n\n3. **Sunk Cost Fallacy**\n - Mitigation: Zero-based thinking\n - Tool: Regular portfolio review\n\n4. **Overconfidence Bias**\n - Mitigation: Outside view\n - Tool: Reference class forecasting\n\n5. **Availability Heuristic**\n - Mitigation: Data-driven decisions\n - Tool: Systematic analysis\n\n### Decision Hygiene Checklist\n\n- [ ] Problem clearly defined\n- [ ] All stakeholders identified\n- [ ] Data/evidence gathered\n- [ ] Multiple options generated\n- [ ] Biases checked\n- [ ] Risks assessed\n- [ ] Implementation plan created\n- [ ] Success metrics defined\n- [ ] Review process established\n\n## Executive Communication\n\n### Board Presentation Template\n\n1. **Executive Summary** (1 slide)\n - Key achievements\n - Critical issues\n - Decisions needed\n\n2. **Performance Review** (3-4 slides)\n - Financial results\n - Operational metrics\n - Strategic progress\n\n3. **Market & Competition** (2 slides)\n - Market dynamics\n - Competitive position\n\n4. **Strategic Initiatives** (3-4 slides)\n - Current initiatives\n - Results to date\n - Next steps\n\n5. **Risk & Mitigation** (2 slides)\n - Risk register\n - Mitigation actions\n\n6. **Ask of the Board** (1 slide)\n - Decisions required\n - Support needed\n\n### Investor Relations Framework\n\n**Earnings Call Structure**:\n1. Opening remarks (CEO) - 5 min\n2. Financial review (CFO) - 10 min\n3. Strategic update (CEO) - 10 min\n4. Q&A - 30 min\n\n**Key Messages**:\n- Performance vs guidance\n- Market position\n- Growth strategy\n- Capital allocation\n- Outlook\n\n## Strategic Planning Cycle\n\n### Annual Planning Process\n\n**Q3 - Strategic Review**\n- Environmental scan\n- Competitive analysis\n- Capability assessment\n- Strategy refinement\n\n**Q4 - Planning**\n- Goal setting\n- Budget allocation\n- Resource planning\n- OKR development\n\n**Q1 - Launch**\n- Communication cascade\n- Initiative kickoff\n- Quick wins\n- Baseline metrics\n\n**Q2 - Review**\n- Progress assessment\n- Course correction\n- Mid-year planning\n- Performance review\n\n## Exit Strategy Planning\n\n### Exit Options Evaluation\n\n1. **IPO**\n - Pros: Maximum valuation, maintain control\n - Cons: Regulatory burden, public scrutiny\n - Timeline: 12-24 months\n\n2. **Strategic Acquisition**\n - Pros: Synergies, quick process\n - Cons: Loss of independence, integration risk\n - Timeline: 6-12 months\n\n3. **Private Equity**\n - Pros: Growth capital, expertise\n - Cons: Pressure for returns, loss of control\n - Timeline: 3-6 months\n\n4. **Management Buyout**\n - Pros: Continuity, culture preservation\n - Cons: Limited price, financing challenge\n - Timeline: 6-9 months\n\n### Value Creation Levers\n\n1. **Revenue Growth**\n - Organic expansion\n - Market development\n - Product innovation\n - Pricing optimization\n\n2. **Margin Improvement**\n - Operational efficiency\n - Cost reduction\n - Mix optimization\n - Pricing power\n\n3. **Multiple Expansion**\n - Market positioning\n - Growth trajectory\n - Risk reduction\n - Story telling\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"9d3f78c6a91752bd2ebd434699b442a9c595e06ba42f117dbb8d8ac1b6e19cbc"},{"uid":"technical.senior-security","name":"senior-security","category":"technical","description":"Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.","content":"---\nname: senior-security\ndescription: Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.\n---\n\n# Senior Security\n\nComplete toolkit for senior security with modern tools and best practices.\n\n## Quick Start\n\n### Main Capabilities\n\nThis skill provides three core capabilities through automated scripts:\n\n```bash\n# Script 1: Threat Modeler\npython scripts/threat_modeler.py [options]\n\n# Script 2: Security Auditor\npython scripts/security_auditor.py [options]\n\n# Script 3: Pentest Automator\npython scripts/pentest_automator.py [options]\n```\n\n## Core Capabilities\n\n### 1. Threat Modeler\n\nAutomated tool for threat modeler tasks.\n\n**Features:**\n- Automated scaffolding\n- Best practices built-in\n- Configurable templates\n- Quality checks\n\n**Usage:**\n```bash\npython scripts/threat_modeler.py [options]\n```\n\n### 2. Security Auditor\n\nComprehensive analysis and optimization tool.\n\n**Features:**\n- Deep analysis\n- Performance metrics\n- Recommendations\n- Automated fixes\n\n**Usage:**\n```bash\npython scripts/security_auditor.py [--verbose]\n```\n\n### 3. Pentest Automator\n\nAdvanced tooling for specialized tasks.\n\n**Features:**\n- Expert-level automation\n- Custom configurations\n- Integration ready\n- Production-grade output\n\n**Usage:**\n```bash\npython scripts/pentest_automator.py [arguments] [options]\n```\n\n## Reference Documentation\n\n### Security Architecture Patterns\n\nComprehensive guide available in `references/security_architecture_patterns.md`:\n\n- Detailed patterns and practices\n- Code examples\n- Best practices\n- Anti-patterns to avoid\n- Real-world scenarios\n\n### Penetration Testing Guide\n\nComplete workflow documentation in `references/penetration_testing_guide.md`:\n\n- Step-by-step processes\n- Optimization strategies\n- Tool integrations\n- Performance tuning\n- Troubleshooting guide\n\n### Cryptography Implementation\n\nTechnical reference guide in `references/cryptography_implementation.md`:\n\n- Technology stack details\n- Configuration examples\n- Integration patterns\n- Security considerations\n- Scalability guidelines\n\n## Tech Stack\n\n**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin\n**Frontend:** React, Next.js, React Native, Flutter\n**Backend:** Node.js, Express, GraphQL, REST APIs\n**Database:** PostgreSQL, Prisma, NeonDB, Supabase\n**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI\n**Cloud:** AWS, GCP, Azure\n\n## Development Workflow\n\n### 1. Setup and Configuration\n\n```bash\n# Install dependencies\nnpm install\n# or\npip install -r requirements.txt\n\n# Configure environment\ncp .env.example .env\n```\n\n### 2. Run Quality Checks\n\n```bash\n# Use the analyzer script\npython scripts/security_auditor.py .\n\n# Review recommendations\n# Apply fixes\n```\n\n### 3. Implement Best Practices\n\nFollow the patterns and practices documented in:\n- `references/security_architecture_patterns.md`\n- `references/penetration_testing_guide.md`\n- `references/cryptography_implementation.md`\n\n## Best Practices Summary\n\n### Code Quality\n- Follow established patterns\n- Write comprehensive tests\n- Document decisions\n- Review regularly\n\n### Performance\n- Measure before optimizing\n- Use appropriate caching\n- Optimize critical paths\n- Monitor in production\n\n### Security\n- Validate all inputs\n- Use parameterized queries\n- Implement proper authentication\n- Keep dependencies updated\n\n### Maintainability\n- Write clear code\n- Use consistent naming\n- Add helpful comments\n- Keep it simple\n\n## Common Commands\n\n```bash\n# Development\nnpm run dev\nnpm run build\nnpm run test\nnpm run lint\n\n# Analysis\npython scripts/security_auditor.py .\npython scripts/pentest_automator.py --analyze\n\n# Deployment\ndocker build -t app:latest .\ndocker-compose up -d\nkubectl apply -f k8s/\n```\n\n## Troubleshooting\n\n### Common Issues\n\nCheck the comprehensive troubleshooting section in `references/cryptography_implementation.md`.\n\n### Getting Help\n\n- Review reference documentation\n- Check script output messages\n- Consult tech stack documentation\n- Review error logs\n\n## Resources\n\n- Pattern Reference: `references/security_architecture_patterns.md`\n- Workflow Guide: `references/penetration_testing_guide.md`\n- Technical Guide: `references/cryptography_implementation.md`\n- Tool Scripts: `scripts/` directory\n","format":"legacy","source":"claude-code","references":{"penetration_testing_guide.md":"# Penetration Testing Guide\n\n## Overview\n\nThis reference guide provides comprehensive information for senior security.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior security.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","security_architecture_patterns.md":"# Security Architecture Patterns\n\n## Overview\n\nThis reference guide provides comprehensive information for senior security.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior security.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","cryptography_implementation.md":"# Cryptography Implementation\n\n## Overview\n\nThis reference guide provides comprehensive information for senior security.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior security.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"d7e26f159d81a9e5ca9a7bc9ff3af116876068349d727b894c6b50020efbd7a7"},{"uid":"technical.senior-frontend","name":"senior-frontend","category":"technical","description":"Comprehensive frontend development skill for building modern, performant web applications using ReactJS, NextJS, TypeScript, Tailwind CSS. Includes component scaffolding, performance optimization, bundle analysis, and UI best practices. Use when developing frontend features, optimizing performance, implementing UI/UX designs, managing state, or reviewing frontend code.","content":"---\nname: senior-frontend\ndescription: Comprehensive frontend development skill for building modern, performant web applications using ReactJS, NextJS, TypeScript, Tailwind CSS. Includes component scaffolding, performance optimization, bundle analysis, and UI best practices. Use when developing frontend features, optimizing performance, implementing UI/UX designs, managing state, or reviewing frontend code.\n---\n\n# Senior Frontend\n\nComplete toolkit for senior frontend with modern tools and best practices.\n\n## Quick Start\n\n### Main Capabilities\n\nThis skill provides three core capabilities through automated scripts:\n\n```bash\n# Script 1: Component Generator\npython scripts/component_generator.py [options]\n\n# Script 2: Bundle Analyzer\npython scripts/bundle_analyzer.py [options]\n\n# Script 3: Frontend Scaffolder\npython scripts/frontend_scaffolder.py [options]\n```\n\n## Core Capabilities\n\n### 1. Component Generator\n\nAutomated tool for component generator tasks.\n\n**Features:**\n- Automated scaffolding\n- Best practices built-in\n- Configurable templates\n- Quality checks\n\n**Usage:**\n```bash\npython scripts/component_generator.py [options]\n```\n\n### 2. Bundle Analyzer\n\nComprehensive analysis and optimization tool.\n\n**Features:**\n- Deep analysis\n- Performance metrics\n- Recommendations\n- Automated fixes\n\n**Usage:**\n```bash\npython scripts/bundle_analyzer.py [--verbose]\n```\n\n### 3. Frontend Scaffolder\n\nAdvanced tooling for specialized tasks.\n\n**Features:**\n- Expert-level automation\n- Custom configurations\n- Integration ready\n- Production-grade output\n\n**Usage:**\n```bash\npython scripts/frontend_scaffolder.py [arguments] [options]\n```\n\n## Reference Documentation\n\n### React Patterns\n\nComprehensive guide available in `references/react_patterns.md`:\n\n- Detailed patterns and practices\n- Code examples\n- Best practices\n- Anti-patterns to avoid\n- Real-world scenarios\n\n### Nextjs Optimization Guide\n\nComplete workflow documentation in `references/nextjs_optimization_guide.md`:\n\n- Step-by-step processes\n- Optimization strategies\n- Tool integrations\n- Performance tuning\n- Troubleshooting guide\n\n### Frontend Best Practices\n\nTechnical reference guide in `references/frontend_best_practices.md`:\n\n- Technology stack details\n- Configuration examples\n- Integration patterns\n- Security considerations\n- Scalability guidelines\n\n## Tech Stack\n\n**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin\n**Frontend:** React, Next.js, React Native, Flutter\n**Backend:** Node.js, Express, GraphQL, REST APIs\n**Database:** PostgreSQL, Prisma, NeonDB, Supabase\n**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI\n**Cloud:** AWS, GCP, Azure\n\n## Development Workflow\n\n### 1. Setup and Configuration\n\n```bash\n# Install dependencies\nnpm install\n# or\npip install -r requirements.txt\n\n# Configure environment\ncp .env.example .env\n```\n\n### 2. Run Quality Checks\n\n```bash\n# Use the analyzer script\npython scripts/bundle_analyzer.py .\n\n# Review recommendations\n# Apply fixes\n```\n\n### 3. Implement Best Practices\n\nFollow the patterns and practices documented in:\n- `references/react_patterns.md`\n- `references/nextjs_optimization_guide.md`\n- `references/frontend_best_practices.md`\n\n## Best Practices Summary\n\n### Code Quality\n- Follow established patterns\n- Write comprehensive tests\n- Document decisions\n- Review regularly\n\n### Performance\n- Measure before optimizing\n- Use appropriate caching\n- Optimize critical paths\n- Monitor in production\n\n### Security\n- Validate all inputs\n- Use parameterized queries\n- Implement proper authentication\n- Keep dependencies updated\n\n### Maintainability\n- Write clear code\n- Use consistent naming\n- Add helpful comments\n- Keep it simple\n\n## Common Commands\n\n```bash\n# Development\nnpm run dev\nnpm run build\nnpm run test\nnpm run lint\n\n# Analysis\npython scripts/bundle_analyzer.py .\npython scripts/frontend_scaffolder.py --analyze\n\n# Deployment\ndocker build -t app:latest .\ndocker-compose up -d\nkubectl apply -f k8s/\n```\n\n## Troubleshooting\n\n### Common Issues\n\nCheck the comprehensive troubleshooting section in `references/frontend_best_practices.md`.\n\n### Getting Help\n\n- Review reference documentation\n- Check script output messages\n- Consult tech stack documentation\n- Review error logs\n\n## Resources\n\n- Pattern Reference: `references/react_patterns.md`\n- Workflow Guide: `references/nextjs_optimization_guide.md`\n- Technical Guide: `references/frontend_best_practices.md`\n- Tool Scripts: `scripts/` directory\n","format":"legacy","source":"claude-code","references":{"nextjs_optimization_guide.md":"# Nextjs Optimization Guide\n\n## Overview\n\nThis reference guide provides comprehensive information for senior frontend.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior frontend.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","frontend_best_practices.md":"# Frontend Best Practices\n\n## Overview\n\nThis reference guide provides comprehensive information for senior frontend.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior frontend.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","react_patterns.md":"# React Patterns\n\n## Overview\n\nThis reference guide provides comprehensive information for senior frontend.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior frontend.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"08e49de11a2623de9c841732922e1c63c76829ffd2b7133b0958d98089e0421b"},{"uid":"technical.senior-secops","name":"senior-secops","category":"technical","description":"Comprehensive SecOps skill for application security, vulnerability management, compliance, and secure development practices. Includes security scanning, vulnerability assessment, compliance checking, and security automation. Use when implementing security controls, conducting security audits, responding to vulnerabilities, or ensuring compliance requirements.","content":"---\nname: senior-secops\ndescription: Comprehensive SecOps skill for application security, vulnerability management, compliance, and secure development practices. Includes security scanning, vulnerability assessment, compliance checking, and security automation. Use when implementing security controls, conducting security audits, responding to vulnerabilities, or ensuring compliance requirements.\n---\n\n# Senior Secops\n\nComplete toolkit for senior secops with modern tools and best practices.\n\n## Quick Start\n\n### Main Capabilities\n\nThis skill provides three core capabilities through automated scripts:\n\n```bash\n# Script 1: Security Scanner\npython scripts/security_scanner.py [options]\n\n# Script 2: Vulnerability Assessor\npython scripts/vulnerability_assessor.py [options]\n\n# Script 3: Compliance Checker\npython scripts/compliance_checker.py [options]\n```\n\n## Core Capabilities\n\n### 1. Security Scanner\n\nAutomated tool for security scanner tasks.\n\n**Features:**\n- Automated scaffolding\n- Best practices built-in\n- Configurable templates\n- Quality checks\n\n**Usage:**\n```bash\npython scripts/security_scanner.py [options]\n```\n\n### 2. Vulnerability Assessor\n\nComprehensive analysis and optimization tool.\n\n**Features:**\n- Deep analysis\n- Performance metrics\n- Recommendations\n- Automated fixes\n\n**Usage:**\n```bash\npython scripts/vulnerability_assessor.py [--verbose]\n```\n\n### 3. Compliance Checker\n\nAdvanced tooling for specialized tasks.\n\n**Features:**\n- Expert-level automation\n- Custom configurations\n- Integration ready\n- Production-grade output\n\n**Usage:**\n```bash\npython scripts/compliance_checker.py [arguments] [options]\n```\n\n## Reference Documentation\n\n### Security Standards\n\nComprehensive guide available in `references/security_standards.md`:\n\n- Detailed patterns and practices\n- Code examples\n- Best practices\n- Anti-patterns to avoid\n- Real-world scenarios\n\n### Vulnerability Management Guide\n\nComplete workflow documentation in `references/vulnerability_management_guide.md`:\n\n- Step-by-step processes\n- Optimization strategies\n- Tool integrations\n- Performance tuning\n- Troubleshooting guide\n\n### Compliance Requirements\n\nTechnical reference guide in `references/compliance_requirements.md`:\n\n- Technology stack details\n- Configuration examples\n- Integration patterns\n- Security considerations\n- Scalability guidelines\n\n## Tech Stack\n\n**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin\n**Frontend:** React, Next.js, React Native, Flutter\n**Backend:** Node.js, Express, GraphQL, REST APIs\n**Database:** PostgreSQL, Prisma, NeonDB, Supabase\n**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI\n**Cloud:** AWS, GCP, Azure\n\n## Development Workflow\n\n### 1. Setup and Configuration\n\n```bash\n# Install dependencies\nnpm install\n# or\npip install -r requirements.txt\n\n# Configure environment\ncp .env.example .env\n```\n\n### 2. Run Quality Checks\n\n```bash\n# Use the analyzer script\npython scripts/vulnerability_assessor.py .\n\n# Review recommendations\n# Apply fixes\n```\n\n### 3. Implement Best Practices\n\nFollow the patterns and practices documented in:\n- `references/security_standards.md`\n- `references/vulnerability_management_guide.md`\n- `references/compliance_requirements.md`\n\n## Best Practices Summary\n\n### Code Quality\n- Follow established patterns\n- Write comprehensive tests\n- Document decisions\n- Review regularly\n\n### Performance\n- Measure before optimizing\n- Use appropriate caching\n- Optimize critical paths\n- Monitor in production\n\n### Security\n- Validate all inputs\n- Use parameterized queries\n- Implement proper authentication\n- Keep dependencies updated\n\n### Maintainability\n- Write clear code\n- Use consistent naming\n- Add helpful comments\n- Keep it simple\n\n## Common Commands\n\n```bash\n# Development\nnpm run dev\nnpm run build\nnpm run test\nnpm run lint\n\n# Analysis\npython scripts/vulnerability_assessor.py .\npython scripts/compliance_checker.py --analyze\n\n# Deployment\ndocker build -t app:latest .\ndocker-compose up -d\nkubectl apply -f k8s/\n```\n\n## Troubleshooting\n\n### Common Issues\n\nCheck the comprehensive troubleshooting section in `references/compliance_requirements.md`.\n\n### Getting Help\n\n- Review reference documentation\n- Check script output messages\n- Consult tech stack documentation\n- Review error logs\n\n## Resources\n\n- Pattern Reference: `references/security_standards.md`\n- Workflow Guide: `references/vulnerability_management_guide.md`\n- Technical Guide: `references/compliance_requirements.md`\n- Tool Scripts: `scripts/` directory\n","format":"legacy","source":"claude-code","references":{"security_standards.md":"# Security Standards\n\n## Overview\n\nThis reference guide provides comprehensive information for senior secops.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior secops.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","vulnerability_management_guide.md":"# Vulnerability Management Guide\n\n## Overview\n\nThis reference guide provides comprehensive information for senior secops.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior secops.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","compliance_requirements.md":"# Compliance Requirements\n\n## Overview\n\nThis reference guide provides comprehensive information for senior secops.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior secops.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"ef4c19c2f4172ce22ee83755f41b7ca1765032f189667baed9e74b51c4aeac45"},{"uid":"technical.senior-prompt-engineer","name":"senior-prompt-engineer","category":"technical","description":"World-class prompt engineering skill for LLM optimization, prompt patterns, structured outputs, and AI product development. Expertise in Claude, GPT-4, prompt design patterns, few-shot learning, chain-of-thought, and AI evaluation. Includes RAG optimization, agent design, and LLM system architecture. Use when building AI products, optimizing LLM performance, designing agentic systems, or implementing advanced prompting techniques.","content":"---\nname: senior-prompt-engineer\ndescription: World-class prompt engineering skill for LLM optimization, prompt patterns, structured outputs, and AI product development. Expertise in Claude, GPT-4, prompt design patterns, few-shot learning, chain-of-thought, and AI evaluation. Includes RAG optimization, agent design, and LLM system architecture. Use when building AI products, optimizing LLM performance, designing agentic systems, or implementing advanced prompting techniques.\n---\n\n# Senior Prompt Engineer\n\nWorld-class senior prompt engineer skill for production-grade AI/ML/Data systems.\n\n## Quick Start\n\n### Main Capabilities\n\n```bash\n# Core Tool 1\npython scripts/prompt_optimizer.py --input data/ --output results/\n\n# Core Tool 2 \npython scripts/rag_evaluator.py --target project/ --analyze\n\n# Core Tool 3\npython scripts/agent_orchestrator.py --config config.yaml --deploy\n```\n\n## Core Expertise\n\nThis skill covers world-class capabilities in:\n\n- Advanced production patterns and architectures\n- Scalable system design and implementation\n- Performance optimization at scale\n- MLOps and DataOps best practices\n- Real-time processing and inference\n- Distributed computing frameworks\n- Model deployment and monitoring\n- Security and compliance\n- Cost optimization\n- Team leadership and mentoring\n\n## Tech Stack\n\n**Languages:** Python, SQL, R, Scala, Go\n**ML Frameworks:** PyTorch, TensorFlow, Scikit-learn, XGBoost\n**Data Tools:** Spark, Airflow, dbt, Kafka, Databricks\n**LLM Frameworks:** LangChain, LlamaIndex, DSPy\n**Deployment:** Docker, Kubernetes, AWS/GCP/Azure\n**Monitoring:** MLflow, Weights & Biases, Prometheus\n**Databases:** PostgreSQL, BigQuery, Snowflake, Pinecone\n\n## Reference Documentation\n\n### 1. Prompt Engineering Patterns\n\nComprehensive guide available in `references/prompt_engineering_patterns.md` covering:\n\n- Advanced patterns and best practices\n- Production implementation strategies\n- Performance optimization techniques\n- Scalability considerations\n- Security and compliance\n- Real-world case studies\n\n### 2. Llm Evaluation Frameworks\n\nComplete workflow documentation in `references/llm_evaluation_frameworks.md` including:\n\n- Step-by-step processes\n- Architecture design patterns\n- Tool integration guides\n- Performance tuning strategies\n- Troubleshooting procedures\n\n### 3. Agentic System Design\n\nTechnical reference guide in `references/agentic_system_design.md` with:\n\n- System design principles\n- Implementation examples\n- Configuration best practices\n- Deployment strategies\n- Monitoring and observability\n\n## Production Patterns\n\n### Pattern 1: Scalable Data Processing\n\nEnterprise-scale data processing with distributed computing:\n\n- Horizontal scaling architecture\n- Fault-tolerant design\n- Real-time and batch processing\n- Data quality validation\n- Performance monitoring\n\n### Pattern 2: ML Model Deployment\n\nProduction ML system with high availability:\n\n- Model serving with low latency\n- A/B testing infrastructure\n- Feature store integration\n- Model monitoring and drift detection\n- Automated retraining pipelines\n\n### Pattern 3: Real-Time Inference\n\nHigh-throughput inference system:\n\n- Batching and caching strategies\n- Load balancing\n- Auto-scaling\n- Latency optimization\n- Cost optimization\n\n## Best Practices\n\n### Development\n\n- Test-driven development\n- Code reviews and pair programming\n- Documentation as code\n- Version control everything\n- Continuous integration\n\n### Production\n\n- Monitor everything critical\n- Automate deployments\n- Feature flags for releases\n- Canary deployments\n- Comprehensive logging\n\n### Team Leadership\n\n- Mentor junior engineers\n- Drive technical decisions\n- Establish coding standards\n- Foster learning culture\n- Cross-functional collaboration\n\n## Performance Targets\n\n**Latency:**\n- P50: < 50ms\n- P95: < 100ms\n- P99: < 200ms\n\n**Throughput:**\n- Requests/second: > 1000\n- Concurrent users: > 10,000\n\n**Availability:**\n- Uptime: 99.9%\n- Error rate: < 0.1%\n\n## Security & Compliance\n\n- Authentication & authorization\n- Data encryption (at rest & in transit)\n- PII handling and anonymization\n- GDPR/CCPA compliance\n- Regular security audits\n- Vulnerability management\n\n## Common Commands\n\n```bash\n# Development\npython -m pytest tests/ -v --cov\npython -m black src/\npython -m pylint src/\n\n# Training\npython scripts/train.py --config prod.yaml\npython scripts/evaluate.py --model best.pth\n\n# Deployment\ndocker build -t service:v1 .\nkubectl apply -f k8s/\nhelm upgrade service ./charts/\n\n# Monitoring\nkubectl logs -f deployment/service\npython scripts/health_check.py\n```\n\n## Resources\n\n- Advanced Patterns: `references/prompt_engineering_patterns.md`\n- Implementation Guide: `references/llm_evaluation_frameworks.md`\n- Technical Reference: `references/agentic_system_design.md`\n- Automation Scripts: `scripts/` directory\n\n## Senior-Level Responsibilities\n\nAs a world-class senior professional:\n\n1. **Technical Leadership**\n - Drive architectural decisions\n - Mentor team members\n - Establish best practices\n - Ensure code quality\n\n2. **Strategic Thinking**\n - Align with business goals\n - Evaluate trade-offs\n - Plan for scale\n - Manage technical debt\n\n3. **Collaboration**\n - Work across teams\n - Communicate effectively\n - Build consensus\n - Share knowledge\n\n4. **Innovation**\n - Stay current with research\n - Experiment with new approaches\n - Contribute to community\n - Drive continuous improvement\n\n5. **Production Excellence**\n - Ensure high availability\n - Monitor proactively\n - Optimize performance\n - Respond to incidents\n","format":"legacy","source":"claude-code","references":{"prompt_engineering_patterns.md":"# Prompt Engineering Patterns\n\n## Overview\n\nWorld-class prompt engineering patterns for senior prompt engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n","agentic_system_design.md":"# Agentic System Design\n\n## Overview\n\nWorld-class agentic system design for senior prompt engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n","llm_evaluation_frameworks.md":"# Llm Evaluation Frameworks\n\n## Overview\n\nWorld-class llm evaluation frameworks for senior prompt engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"504c1ee82323d26fc07ba9ef5c954e08ba18f77340dd1c77c4bae97a23aa98c6"},{"uid":"technical.senior-architect","name":"senior-architect","category":"technical","description":"Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. Includes architecture diagram generation, system design patterns, tech stack decision frameworks, and dependency analysis. Use when designing system architecture, making technical decisions, creating architecture diagrams, evaluating trade-offs, or defining integration patterns.","content":"---\nname: senior-architect\ndescription: Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. Includes architecture diagram generation, system design patterns, tech stack decision frameworks, and dependency analysis. Use when designing system architecture, making technical decisions, creating architecture diagrams, evaluating trade-offs, or defining integration patterns.\n---\n\n# Senior Architect\n\nComplete toolkit for senior architect with modern tools and best practices.\n\n## Quick Start\n\n### Main Capabilities\n\nThis skill provides three core capabilities through automated scripts:\n\n```bash\n# Script 1: Architecture Diagram Generator\npython scripts/architecture_diagram_generator.py [options]\n\n# Script 2: Project Architect\npython scripts/project_architect.py [options]\n\n# Script 3: Dependency Analyzer\npython scripts/dependency_analyzer.py [options]\n```\n\n## Core Capabilities\n\n### 1. Architecture Diagram Generator\n\nAutomated tool for architecture diagram generator tasks.\n\n**Features:**\n- Automated scaffolding\n- Best practices built-in\n- Configurable templates\n- Quality checks\n\n**Usage:**\n```bash\npython scripts/architecture_diagram_generator.py [options]\n```\n\n### 2. Project Architect\n\nComprehensive analysis and optimization tool.\n\n**Features:**\n- Deep analysis\n- Performance metrics\n- Recommendations\n- Automated fixes\n\n**Usage:**\n```bash\npython scripts/project_architect.py [--verbose]\n```\n\n### 3. Dependency Analyzer\n\nAdvanced tooling for specialized tasks.\n\n**Features:**\n- Expert-level automation\n- Custom configurations\n- Integration ready\n- Production-grade output\n\n**Usage:**\n```bash\npython scripts/dependency_analyzer.py [arguments] [options]\n```\n\n## Reference Documentation\n\n### Architecture Patterns\n\nComprehensive guide available in `references/architecture_patterns.md`:\n\n- Detailed patterns and practices\n- Code examples\n- Best practices\n- Anti-patterns to avoid\n- Real-world scenarios\n\n### System Design Workflows\n\nComplete workflow documentation in `references/system_design_workflows.md`:\n\n- Step-by-step processes\n- Optimization strategies\n- Tool integrations\n- Performance tuning\n- Troubleshooting guide\n\n### Tech Decision Guide\n\nTechnical reference guide in `references/tech_decision_guide.md`:\n\n- Technology stack details\n- Configuration examples\n- Integration patterns\n- Security considerations\n- Scalability guidelines\n\n## Tech Stack\n\n**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin\n**Frontend:** React, Next.js, React Native, Flutter\n**Backend:** Node.js, Express, GraphQL, REST APIs\n**Database:** PostgreSQL, Prisma, NeonDB, Supabase\n**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI\n**Cloud:** AWS, GCP, Azure\n\n## Development Workflow\n\n### 1. Setup and Configuration\n\n```bash\n# Install dependencies\nnpm install\n# or\npip install -r requirements.txt\n\n# Configure environment\ncp .env.example .env\n```\n\n### 2. Run Quality Checks\n\n```bash\n# Use the analyzer script\npython scripts/project_architect.py .\n\n# Review recommendations\n# Apply fixes\n```\n\n### 3. Implement Best Practices\n\nFollow the patterns and practices documented in:\n- `references/architecture_patterns.md`\n- `references/system_design_workflows.md`\n- `references/tech_decision_guide.md`\n\n## Best Practices Summary\n\n### Code Quality\n- Follow established patterns\n- Write comprehensive tests\n- Document decisions\n- Review regularly\n\n### Performance\n- Measure before optimizing\n- Use appropriate caching\n- Optimize critical paths\n- Monitor in production\n\n### Security\n- Validate all inputs\n- Use parameterized queries\n- Implement proper authentication\n- Keep dependencies updated\n\n### Maintainability\n- Write clear code\n- Use consistent naming\n- Add helpful comments\n- Keep it simple\n\n## Common Commands\n\n```bash\n# Development\nnpm run dev\nnpm run build\nnpm run test\nnpm run lint\n\n# Analysis\npython scripts/project_architect.py .\npython scripts/dependency_analyzer.py --analyze\n\n# Deployment\ndocker build -t app:latest .\ndocker-compose up -d\nkubectl apply -f k8s/\n```\n\n## Troubleshooting\n\n### Common Issues\n\nCheck the comprehensive troubleshooting section in `references/tech_decision_guide.md`.\n\n### Getting Help\n\n- Review reference documentation\n- Check script output messages\n- Consult tech stack documentation\n- Review error logs\n\n## Resources\n\n- Pattern Reference: `references/architecture_patterns.md`\n- Workflow Guide: `references/system_design_workflows.md`\n- Technical Guide: `references/tech_decision_guide.md`\n- Tool Scripts: `scripts/` directory\n","format":"legacy","source":"claude-code","references":{"tech_decision_guide.md":"# Tech Decision Guide\n\n## Overview\n\nThis reference guide provides comprehensive information for senior architect.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior architect.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","system_design_workflows.md":"# System Design Workflows\n\n## Overview\n\nThis reference guide provides comprehensive information for senior architect.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior architect.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","architecture_patterns.md":"# Architecture Patterns\n\n## Overview\n\nThis reference guide provides comprehensive information for senior architect.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior architect.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"59c6829066912ad8db5a8ca0a95407a86c990a5638e348fb2c0a31d9dc118268"},{"uid":"technical.senior-devops","name":"senior-devops","category":"technical","description":"Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup, infrastructure as code, deployment automation, and monitoring. Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes.","content":"---\nname: senior-devops\ndescription: Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup, infrastructure as code, deployment automation, and monitoring. Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes.\n---\n\n# Senior Devops\n\nComplete toolkit for senior devops with modern tools and best practices.\n\n## Quick Start\n\n### Main Capabilities\n\nThis skill provides three core capabilities through automated scripts:\n\n```bash\n# Script 1: Pipeline Generator\npython scripts/pipeline_generator.py [options]\n\n# Script 2: Terraform Scaffolder\npython scripts/terraform_scaffolder.py [options]\n\n# Script 3: Deployment Manager\npython scripts/deployment_manager.py [options]\n```\n\n## Core Capabilities\n\n### 1. Pipeline Generator\n\nAutomated tool for pipeline generator tasks.\n\n**Features:**\n- Automated scaffolding\n- Best practices built-in\n- Configurable templates\n- Quality checks\n\n**Usage:**\n```bash\npython scripts/pipeline_generator.py [options]\n```\n\n### 2. Terraform Scaffolder\n\nComprehensive analysis and optimization tool.\n\n**Features:**\n- Deep analysis\n- Performance metrics\n- Recommendations\n- Automated fixes\n\n**Usage:**\n```bash\npython scripts/terraform_scaffolder.py [--verbose]\n```\n\n### 3. Deployment Manager\n\nAdvanced tooling for specialized tasks.\n\n**Features:**\n- Expert-level automation\n- Custom configurations\n- Integration ready\n- Production-grade output\n\n**Usage:**\n```bash\npython scripts/deployment_manager.py [arguments] [options]\n```\n\n## Reference Documentation\n\n### Cicd Pipeline Guide\n\nComprehensive guide available in `references/cicd_pipeline_guide.md`:\n\n- Detailed patterns and practices\n- Code examples\n- Best practices\n- Anti-patterns to avoid\n- Real-world scenarios\n\n### Infrastructure As Code\n\nComplete workflow documentation in `references/infrastructure_as_code.md`:\n\n- Step-by-step processes\n- Optimization strategies\n- Tool integrations\n- Performance tuning\n- Troubleshooting guide\n\n### Deployment Strategies\n\nTechnical reference guide in `references/deployment_strategies.md`:\n\n- Technology stack details\n- Configuration examples\n- Integration patterns\n- Security considerations\n- Scalability guidelines\n\n## Tech Stack\n\n**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin\n**Frontend:** React, Next.js, React Native, Flutter\n**Backend:** Node.js, Express, GraphQL, REST APIs\n**Database:** PostgreSQL, Prisma, NeonDB, Supabase\n**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI\n**Cloud:** AWS, GCP, Azure\n\n## Development Workflow\n\n### 1. Setup and Configuration\n\n```bash\n# Install dependencies\nnpm install\n# or\npip install -r requirements.txt\n\n# Configure environment\ncp .env.example .env\n```\n\n### 2. Run Quality Checks\n\n```bash\n# Use the analyzer script\npython scripts/terraform_scaffolder.py .\n\n# Review recommendations\n# Apply fixes\n```\n\n### 3. Implement Best Practices\n\nFollow the patterns and practices documented in:\n- `references/cicd_pipeline_guide.md`\n- `references/infrastructure_as_code.md`\n- `references/deployment_strategies.md`\n\n## Best Practices Summary\n\n### Code Quality\n- Follow established patterns\n- Write comprehensive tests\n- Document decisions\n- Review regularly\n\n### Performance\n- Measure before optimizing\n- Use appropriate caching\n- Optimize critical paths\n- Monitor in production\n\n### Security\n- Validate all inputs\n- Use parameterized queries\n- Implement proper authentication\n- Keep dependencies updated\n\n### Maintainability\n- Write clear code\n- Use consistent naming\n- Add helpful comments\n- Keep it simple\n\n## Common Commands\n\n```bash\n# Development\nnpm run dev\nnpm run build\nnpm run test\nnpm run lint\n\n# Analysis\npython scripts/terraform_scaffolder.py .\npython scripts/deployment_manager.py --analyze\n\n# Deployment\ndocker build -t app:latest .\ndocker-compose up -d\nkubectl apply -f k8s/\n```\n\n## Troubleshooting\n\n### Common Issues\n\nCheck the comprehensive troubleshooting section in `references/deployment_strategies.md`.\n\n### Getting Help\n\n- Review reference documentation\n- Check script output messages\n- Consult tech stack documentation\n- Review error logs\n\n## Resources\n\n- Pattern Reference: `references/cicd_pipeline_guide.md`\n- Workflow Guide: `references/infrastructure_as_code.md`\n- Technical Guide: `references/deployment_strategies.md`\n- Tool Scripts: `scripts/` directory\n","format":"legacy","source":"claude-code","references":{"infrastructure_as_code.md":"# Infrastructure As Code\n\n## Overview\n\nThis reference guide provides comprehensive information for senior devops.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior devops.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","deployment_strategies.md":"# Deployment Strategies\n\n## Overview\n\nThis reference guide provides comprehensive information for senior devops.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior devops.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","cicd_pipeline_guide.md":"# Cicd Pipeline Guide\n\n## Overview\n\nThis reference guide provides comprehensive information for senior devops.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior devops.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"478aed6e0ef1a629cd1e7b8d3805935ab154a15ed83a9fd928c1114d16abcaad"},{"uid":"technical.senior-fullstack","name":"senior-fullstack","category":"technical","description":"Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.","content":"---\nname: senior-fullstack\ndescription: Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.\n---\n\n# Senior Fullstack\n\nComplete toolkit for senior fullstack with modern tools and best practices.\n\n## Quick Start\n\n### Main Capabilities\n\nThis skill provides three core capabilities through automated scripts:\n\n```bash\n# Script 1: Fullstack Scaffolder\npython scripts/fullstack_scaffolder.py [options]\n\n# Script 2: Project Scaffolder\npython scripts/project_scaffolder.py [options]\n\n# Script 3: Code Quality Analyzer\npython scripts/code_quality_analyzer.py [options]\n```\n\n## Core Capabilities\n\n### 1. Fullstack Scaffolder\n\nAutomated tool for fullstack scaffolder tasks.\n\n**Features:**\n- Automated scaffolding\n- Best practices built-in\n- Configurable templates\n- Quality checks\n\n**Usage:**\n```bash\npython scripts/fullstack_scaffolder.py [options]\n```\n\n### 2. Project Scaffolder\n\nComprehensive analysis and optimization tool.\n\n**Features:**\n- Deep analysis\n- Performance metrics\n- Recommendations\n- Automated fixes\n\n**Usage:**\n```bash\npython scripts/project_scaffolder.py [--verbose]\n```\n\n### 3. Code Quality Analyzer\n\nAdvanced tooling for specialized tasks.\n\n**Features:**\n- Expert-level automation\n- Custom configurations\n- Integration ready\n- Production-grade output\n\n**Usage:**\n```bash\npython scripts/code_quality_analyzer.py [arguments] [options]\n```\n\n## Reference Documentation\n\n### Tech Stack Guide\n\nComprehensive guide available in `references/tech_stack_guide.md`:\n\n- Detailed patterns and practices\n- Code examples\n- Best practices\n- Anti-patterns to avoid\n- Real-world scenarios\n\n### Architecture Patterns\n\nComplete workflow documentation in `references/architecture_patterns.md`:\n\n- Step-by-step processes\n- Optimization strategies\n- Tool integrations\n- Performance tuning\n- Troubleshooting guide\n\n### Development Workflows\n\nTechnical reference guide in `references/development_workflows.md`:\n\n- Technology stack details\n- Configuration examples\n- Integration patterns\n- Security considerations\n- Scalability guidelines\n\n## Tech Stack\n\n**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin\n**Frontend:** React, Next.js, React Native, Flutter\n**Backend:** Node.js, Express, GraphQL, REST APIs\n**Database:** PostgreSQL, Prisma, NeonDB, Supabase\n**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI\n**Cloud:** AWS, GCP, Azure\n\n## Development Workflow\n\n### 1. Setup and Configuration\n\n```bash\n# Install dependencies\nnpm install\n# or\npip install -r requirements.txt\n\n# Configure environment\ncp .env.example .env\n```\n\n### 2. Run Quality Checks\n\n```bash\n# Use the analyzer script\npython scripts/project_scaffolder.py .\n\n# Review recommendations\n# Apply fixes\n```\n\n### 3. Implement Best Practices\n\nFollow the patterns and practices documented in:\n- `references/tech_stack_guide.md`\n- `references/architecture_patterns.md`\n- `references/development_workflows.md`\n\n## Best Practices Summary\n\n### Code Quality\n- Follow established patterns\n- Write comprehensive tests\n- Document decisions\n- Review regularly\n\n### Performance\n- Measure before optimizing\n- Use appropriate caching\n- Optimize critical paths\n- Monitor in production\n\n### Security\n- Validate all inputs\n- Use parameterized queries\n- Implement proper authentication\n- Keep dependencies updated\n\n### Maintainability\n- Write clear code\n- Use consistent naming\n- Add helpful comments\n- Keep it simple\n\n## Common Commands\n\n```bash\n# Development\nnpm run dev\nnpm run build\nnpm run test\nnpm run lint\n\n# Analysis\npython scripts/project_scaffolder.py .\npython scripts/code_quality_analyzer.py --analyze\n\n# Deployment\ndocker build -t app:latest .\ndocker-compose up -d\nkubectl apply -f k8s/\n```\n\n## Troubleshooting\n\n### Common Issues\n\nCheck the comprehensive troubleshooting section in `references/development_workflows.md`.\n\n### Getting Help\n\n- Review reference documentation\n- Check script output messages\n- Consult tech stack documentation\n- Review error logs\n\n## Resources\n\n- Pattern Reference: `references/tech_stack_guide.md`\n- Workflow Guide: `references/architecture_patterns.md`\n- Technical Guide: `references/development_workflows.md`\n- Tool Scripts: `scripts/` directory\n","format":"legacy","source":"claude-code","references":{"development_workflows.md":"# Development Workflows\n\n## Overview\n\nThis reference guide provides comprehensive information for senior fullstack.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior fullstack.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","tech_stack_guide.md":"# Tech Stack Guide\n\n## Overview\n\nThis reference guide provides comprehensive information for senior fullstack.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior fullstack.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","architecture_patterns.md":"# Architecture Patterns\n\n## Overview\n\nThis reference guide provides comprehensive information for senior fullstack.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior fullstack.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"0c3156f38215b792e032abf5708b33b572448837346e5ec110a5c74522ed2c5a"},{"uid":"technical.senior-computer-vision","name":"senior-computer-vision","category":"technical","description":"World-class computer vision skill for image/video processing, object detection, segmentation, and visual AI systems. Expertise in PyTorch, OpenCV, YOLO, SAM, diffusion models, and vision transformers. Includes 3D vision, video analysis, real-time processing, and production deployment. Use when building vision AI systems, implementing object detection, training custom vision models, or optimizing inference pipelines.","content":"---\nname: senior-computer-vision\ndescription: World-class computer vision skill for image/video processing, object detection, segmentation, and visual AI systems. Expertise in PyTorch, OpenCV, YOLO, SAM, diffusion models, and vision transformers. Includes 3D vision, video analysis, real-time processing, and production deployment. Use when building vision AI systems, implementing object detection, training custom vision models, or optimizing inference pipelines.\n---\n\n# Senior Computer Vision Engineer\n\nWorld-class senior computer vision engineer skill for production-grade AI/ML/Data systems.\n\n## Quick Start\n\n### Main Capabilities\n\n```bash\n# Core Tool 1\npython scripts/vision_model_trainer.py --input data/ --output results/\n\n# Core Tool 2 \npython scripts/inference_optimizer.py --target project/ --analyze\n\n# Core Tool 3\npython scripts/dataset_pipeline_builder.py --config config.yaml --deploy\n```\n\n## Core Expertise\n\nThis skill covers world-class capabilities in:\n\n- Advanced production patterns and architectures\n- Scalable system design and implementation\n- Performance optimization at scale\n- MLOps and DataOps best practices\n- Real-time processing and inference\n- Distributed computing frameworks\n- Model deployment and monitoring\n- Security and compliance\n- Cost optimization\n- Team leadership and mentoring\n\n## Tech Stack\n\n**Languages:** Python, SQL, R, Scala, Go\n**ML Frameworks:** PyTorch, TensorFlow, Scikit-learn, XGBoost\n**Data Tools:** Spark, Airflow, dbt, Kafka, Databricks\n**LLM Frameworks:** LangChain, LlamaIndex, DSPy\n**Deployment:** Docker, Kubernetes, AWS/GCP/Azure\n**Monitoring:** MLflow, Weights & Biases, Prometheus\n**Databases:** PostgreSQL, BigQuery, Snowflake, Pinecone\n\n## Reference Documentation\n\n### 1. Computer Vision Architectures\n\nComprehensive guide available in `references/computer_vision_architectures.md` covering:\n\n- Advanced patterns and best practices\n- Production implementation strategies\n- Performance optimization techniques\n- Scalability considerations\n- Security and compliance\n- Real-world case studies\n\n### 2. Object Detection Optimization\n\nComplete workflow documentation in `references/object_detection_optimization.md` including:\n\n- Step-by-step processes\n- Architecture design patterns\n- Tool integration guides\n- Performance tuning strategies\n- Troubleshooting procedures\n\n### 3. Production Vision Systems\n\nTechnical reference guide in `references/production_vision_systems.md` with:\n\n- System design principles\n- Implementation examples\n- Configuration best practices\n- Deployment strategies\n- Monitoring and observability\n\n## Production Patterns\n\n### Pattern 1: Scalable Data Processing\n\nEnterprise-scale data processing with distributed computing:\n\n- Horizontal scaling architecture\n- Fault-tolerant design\n- Real-time and batch processing\n- Data quality validation\n- Performance monitoring\n\n### Pattern 2: ML Model Deployment\n\nProduction ML system with high availability:\n\n- Model serving with low latency\n- A/B testing infrastructure\n- Feature store integration\n- Model monitoring and drift detection\n- Automated retraining pipelines\n\n### Pattern 3: Real-Time Inference\n\nHigh-throughput inference system:\n\n- Batching and caching strategies\n- Load balancing\n- Auto-scaling\n- Latency optimization\n- Cost optimization\n\n## Best Practices\n\n### Development\n\n- Test-driven development\n- Code reviews and pair programming\n- Documentation as code\n- Version control everything\n- Continuous integration\n\n### Production\n\n- Monitor everything critical\n- Automate deployments\n- Feature flags for releases\n- Canary deployments\n- Comprehensive logging\n\n### Team Leadership\n\n- Mentor junior engineers\n- Drive technical decisions\n- Establish coding standards\n- Foster learning culture\n- Cross-functional collaboration\n\n## Performance Targets\n\n**Latency:**\n- P50: < 50ms\n- P95: < 100ms\n- P99: < 200ms\n\n**Throughput:**\n- Requests/second: > 1000\n- Concurrent users: > 10,000\n\n**Availability:**\n- Uptime: 99.9%\n- Error rate: < 0.1%\n\n## Security & Compliance\n\n- Authentication & authorization\n- Data encryption (at rest & in transit)\n- PII handling and anonymization\n- GDPR/CCPA compliance\n- Regular security audits\n- Vulnerability management\n\n## Common Commands\n\n```bash\n# Development\npython -m pytest tests/ -v --cov\npython -m black src/\npython -m pylint src/\n\n# Training\npython scripts/train.py --config prod.yaml\npython scripts/evaluate.py --model best.pth\n\n# Deployment\ndocker build -t service:v1 .\nkubectl apply -f k8s/\nhelm upgrade service ./charts/\n\n# Monitoring\nkubectl logs -f deployment/service\npython scripts/health_check.py\n```\n\n## Resources\n\n- Advanced Patterns: `references/computer_vision_architectures.md`\n- Implementation Guide: `references/object_detection_optimization.md`\n- Technical Reference: `references/production_vision_systems.md`\n- Automation Scripts: `scripts/` directory\n\n## Senior-Level Responsibilities\n\nAs a world-class senior professional:\n\n1. **Technical Leadership**\n - Drive architectural decisions\n - Mentor team members\n - Establish best practices\n - Ensure code quality\n\n2. **Strategic Thinking**\n - Align with business goals\n - Evaluate trade-offs\n - Plan for scale\n - Manage technical debt\n\n3. **Collaboration**\n - Work across teams\n - Communicate effectively\n - Build consensus\n - Share knowledge\n\n4. **Innovation**\n - Stay current with research\n - Experiment with new approaches\n - Contribute to community\n - Drive continuous improvement\n\n5. **Production Excellence**\n - Ensure high availability\n - Monitor proactively\n - Optimize performance\n - Respond to incidents\n","format":"legacy","source":"claude-code","references":{"object_detection_optimization.md":"# Object Detection Optimization\n\n## Overview\n\nWorld-class object detection optimization for senior computer vision engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n","computer_vision_architectures.md":"# Computer Vision Architectures\n\n## Overview\n\nWorld-class computer vision architectures for senior computer vision engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n","production_vision_systems.md":"# Production Vision Systems\n\n## Overview\n\nWorld-class production vision systems for senior computer vision engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"d09567decd928b5d70650a5ef8102fdb94083c68f436bef3b3221a4421fc5ee7"},{"uid":"technical.senior-ml-engineer","name":"senior-ml-engineer","category":"technical","description":"World-class ML engineering skill for productionizing ML models, MLOps, and building scalable ML systems. Expertise in PyTorch, TensorFlow, model deployment, feature stores, model monitoring, and ML infrastructure. Includes LLM integration, fine-tuning, RAG systems, and agentic AI. Use when deploying ML models, building ML platforms, implementing MLOps, or integrating LLMs into production systems.","content":"---\nname: senior-ml-engineer\ndescription: World-class ML engineering skill for productionizing ML models, MLOps, and building scalable ML systems. Expertise in PyTorch, TensorFlow, model deployment, feature stores, model monitoring, and ML infrastructure. Includes LLM integration, fine-tuning, RAG systems, and agentic AI. Use when deploying ML models, building ML platforms, implementing MLOps, or integrating LLMs into production systems.\n---\n\n# Senior ML/AI Engineer\n\nWorld-class senior ml/ai engineer skill for production-grade AI/ML/Data systems.\n\n## Quick Start\n\n### Main Capabilities\n\n```bash\n# Core Tool 1\npython scripts/model_deployment_pipeline.py --input data/ --output results/\n\n# Core Tool 2 \npython scripts/rag_system_builder.py --target project/ --analyze\n\n# Core Tool 3\npython scripts/ml_monitoring_suite.py --config config.yaml --deploy\n```\n\n## Core Expertise\n\nThis skill covers world-class capabilities in:\n\n- Advanced production patterns and architectures\n- Scalable system design and implementation\n- Performance optimization at scale\n- MLOps and DataOps best practices\n- Real-time processing and inference\n- Distributed computing frameworks\n- Model deployment and monitoring\n- Security and compliance\n- Cost optimization\n- Team leadership and mentoring\n\n## Tech Stack\n\n**Languages:** Python, SQL, R, Scala, Go\n**ML Frameworks:** PyTorch, TensorFlow, Scikit-learn, XGBoost\n**Data Tools:** Spark, Airflow, dbt, Kafka, Databricks\n**LLM Frameworks:** LangChain, LlamaIndex, DSPy\n**Deployment:** Docker, Kubernetes, AWS/GCP/Azure\n**Monitoring:** MLflow, Weights & Biases, Prometheus\n**Databases:** PostgreSQL, BigQuery, Snowflake, Pinecone\n\n## Reference Documentation\n\n### 1. Mlops Production Patterns\n\nComprehensive guide available in `references/mlops_production_patterns.md` covering:\n\n- Advanced patterns and best practices\n- Production implementation strategies\n- Performance optimization techniques\n- Scalability considerations\n- Security and compliance\n- Real-world case studies\n\n### 2. Llm Integration Guide\n\nComplete workflow documentation in `references/llm_integration_guide.md` including:\n\n- Step-by-step processes\n- Architecture design patterns\n- Tool integration guides\n- Performance tuning strategies\n- Troubleshooting procedures\n\n### 3. Rag System Architecture\n\nTechnical reference guide in `references/rag_system_architecture.md` with:\n\n- System design principles\n- Implementation examples\n- Configuration best practices\n- Deployment strategies\n- Monitoring and observability\n\n## Production Patterns\n\n### Pattern 1: Scalable Data Processing\n\nEnterprise-scale data processing with distributed computing:\n\n- Horizontal scaling architecture\n- Fault-tolerant design\n- Real-time and batch processing\n- Data quality validation\n- Performance monitoring\n\n### Pattern 2: ML Model Deployment\n\nProduction ML system with high availability:\n\n- Model serving with low latency\n- A/B testing infrastructure\n- Feature store integration\n- Model monitoring and drift detection\n- Automated retraining pipelines\n\n### Pattern 3: Real-Time Inference\n\nHigh-throughput inference system:\n\n- Batching and caching strategies\n- Load balancing\n- Auto-scaling\n- Latency optimization\n- Cost optimization\n\n## Best Practices\n\n### Development\n\n- Test-driven development\n- Code reviews and pair programming\n- Documentation as code\n- Version control everything\n- Continuous integration\n\n### Production\n\n- Monitor everything critical\n- Automate deployments\n- Feature flags for releases\n- Canary deployments\n- Comprehensive logging\n\n### Team Leadership\n\n- Mentor junior engineers\n- Drive technical decisions\n- Establish coding standards\n- Foster learning culture\n- Cross-functional collaboration\n\n## Performance Targets\n\n**Latency:**\n- P50: < 50ms\n- P95: < 100ms\n- P99: < 200ms\n\n**Throughput:**\n- Requests/second: > 1000\n- Concurrent users: > 10,000\n\n**Availability:**\n- Uptime: 99.9%\n- Error rate: < 0.1%\n\n## Security & Compliance\n\n- Authentication & authorization\n- Data encryption (at rest & in transit)\n- PII handling and anonymization\n- GDPR/CCPA compliance\n- Regular security audits\n- Vulnerability management\n\n## Common Commands\n\n```bash\n# Development\npython -m pytest tests/ -v --cov\npython -m black src/\npython -m pylint src/\n\n# Training\npython scripts/train.py --config prod.yaml\npython scripts/evaluate.py --model best.pth\n\n# Deployment\ndocker build -t service:v1 .\nkubectl apply -f k8s/\nhelm upgrade service ./charts/\n\n# Monitoring\nkubectl logs -f deployment/service\npython scripts/health_check.py\n```\n\n## Resources\n\n- Advanced Patterns: `references/mlops_production_patterns.md`\n- Implementation Guide: `references/llm_integration_guide.md`\n- Technical Reference: `references/rag_system_architecture.md`\n- Automation Scripts: `scripts/` directory\n\n## Senior-Level Responsibilities\n\nAs a world-class senior professional:\n\n1. **Technical Leadership**\n - Drive architectural decisions\n - Mentor team members\n - Establish best practices\n - Ensure code quality\n\n2. **Strategic Thinking**\n - Align with business goals\n - Evaluate trade-offs\n - Plan for scale\n - Manage technical debt\n\n3. **Collaboration**\n - Work across teams\n - Communicate effectively\n - Build consensus\n - Share knowledge\n\n4. **Innovation**\n - Stay current with research\n - Experiment with new approaches\n - Contribute to community\n - Drive continuous improvement\n\n5. **Production Excellence**\n - Ensure high availability\n - Monitor proactively\n - Optimize performance\n - Respond to incidents\n","format":"legacy","source":"claude-code","references":{"rag_system_architecture.md":"# Rag System Architecture\n\n## Overview\n\nWorld-class rag system architecture for senior ml/ai engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n","mlops_production_patterns.md":"# Mlops Production Patterns\n\n## Overview\n\nWorld-class mlops production patterns for senior ml/ai engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n","llm_integration_guide.md":"# Llm Integration Guide\n\n## Overview\n\nWorld-class llm integration guide for senior ml/ai engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"bed820ec0af0ab3f89e204c3236174bbe7c97aec7568b2f7e04455061637864b"},{"uid":"technical.senior-data-engineer","name":"senior-data-engineer","category":"technical","description":"World-class data engineering skill for building scalable data pipelines, ETL/ELT systems, and data infrastructure. Expertise in Python, SQL, Spark, Airflow, dbt, Kafka, and modern data stack. Includes data modeling, pipeline orchestration, data quality, and DataOps. Use when designing data architectures, building data pipelines, optimizing data workflows, or implementing data governance.","content":"---\nname: senior-data-engineer\ndescription: World-class data engineering skill for building scalable data pipelines, ETL/ELT systems, and data infrastructure. Expertise in Python, SQL, Spark, Airflow, dbt, Kafka, and modern data stack. Includes data modeling, pipeline orchestration, data quality, and DataOps. Use when designing data architectures, building data pipelines, optimizing data workflows, or implementing data governance.\n---\n\n# Senior Data Engineer\n\nWorld-class senior data engineer skill for production-grade AI/ML/Data systems.\n\n## Quick Start\n\n### Main Capabilities\n\n```bash\n# Core Tool 1\npython scripts/pipeline_orchestrator.py --input data/ --output results/\n\n# Core Tool 2 \npython scripts/data_quality_validator.py --target project/ --analyze\n\n# Core Tool 3\npython scripts/etl_performance_optimizer.py --config config.yaml --deploy\n```\n\n## Core Expertise\n\nThis skill covers world-class capabilities in:\n\n- Advanced production patterns and architectures\n- Scalable system design and implementation\n- Performance optimization at scale\n- MLOps and DataOps best practices\n- Real-time processing and inference\n- Distributed computing frameworks\n- Model deployment and monitoring\n- Security and compliance\n- Cost optimization\n- Team leadership and mentoring\n\n## Tech Stack\n\n**Languages:** Python, SQL, R, Scala, Go\n**ML Frameworks:** PyTorch, TensorFlow, Scikit-learn, XGBoost\n**Data Tools:** Spark, Airflow, dbt, Kafka, Databricks\n**LLM Frameworks:** LangChain, LlamaIndex, DSPy\n**Deployment:** Docker, Kubernetes, AWS/GCP/Azure\n**Monitoring:** MLflow, Weights & Biases, Prometheus\n**Databases:** PostgreSQL, BigQuery, Snowflake, Pinecone\n\n## Reference Documentation\n\n### 1. Data Pipeline Architecture\n\nComprehensive guide available in `references/data_pipeline_architecture.md` covering:\n\n- Advanced patterns and best practices\n- Production implementation strategies\n- Performance optimization techniques\n- Scalability considerations\n- Security and compliance\n- Real-world case studies\n\n### 2. Data Modeling Patterns\n\nComplete workflow documentation in `references/data_modeling_patterns.md` including:\n\n- Step-by-step processes\n- Architecture design patterns\n- Tool integration guides\n- Performance tuning strategies\n- Troubleshooting procedures\n\n### 3. Dataops Best Practices\n\nTechnical reference guide in `references/dataops_best_practices.md` with:\n\n- System design principles\n- Implementation examples\n- Configuration best practices\n- Deployment strategies\n- Monitoring and observability\n\n## Production Patterns\n\n### Pattern 1: Scalable Data Processing\n\nEnterprise-scale data processing with distributed computing:\n\n- Horizontal scaling architecture\n- Fault-tolerant design\n- Real-time and batch processing\n- Data quality validation\n- Performance monitoring\n\n### Pattern 2: ML Model Deployment\n\nProduction ML system with high availability:\n\n- Model serving with low latency\n- A/B testing infrastructure\n- Feature store integration\n- Model monitoring and drift detection\n- Automated retraining pipelines\n\n### Pattern 3: Real-Time Inference\n\nHigh-throughput inference system:\n\n- Batching and caching strategies\n- Load balancing\n- Auto-scaling\n- Latency optimization\n- Cost optimization\n\n## Best Practices\n\n### Development\n\n- Test-driven development\n- Code reviews and pair programming\n- Documentation as code\n- Version control everything\n- Continuous integration\n\n### Production\n\n- Monitor everything critical\n- Automate deployments\n- Feature flags for releases\n- Canary deployments\n- Comprehensive logging\n\n### Team Leadership\n\n- Mentor junior engineers\n- Drive technical decisions\n- Establish coding standards\n- Foster learning culture\n- Cross-functional collaboration\n\n## Performance Targets\n\n**Latency:**\n- P50: < 50ms\n- P95: < 100ms\n- P99: < 200ms\n\n**Throughput:**\n- Requests/second: > 1000\n- Concurrent users: > 10,000\n\n**Availability:**\n- Uptime: 99.9%\n- Error rate: < 0.1%\n\n## Security & Compliance\n\n- Authentication & authorization\n- Data encryption (at rest & in transit)\n- PII handling and anonymization\n- GDPR/CCPA compliance\n- Regular security audits\n- Vulnerability management\n\n## Common Commands\n\n```bash\n# Development\npython -m pytest tests/ -v --cov\npython -m black src/\npython -m pylint src/\n\n# Training\npython scripts/train.py --config prod.yaml\npython scripts/evaluate.py --model best.pth\n\n# Deployment\ndocker build -t service:v1 .\nkubectl apply -f k8s/\nhelm upgrade service ./charts/\n\n# Monitoring\nkubectl logs -f deployment/service\npython scripts/health_check.py\n```\n\n## Resources\n\n- Advanced Patterns: `references/data_pipeline_architecture.md`\n- Implementation Guide: `references/data_modeling_patterns.md`\n- Technical Reference: `references/dataops_best_practices.md`\n- Automation Scripts: `scripts/` directory\n\n## Senior-Level Responsibilities\n\nAs a world-class senior professional:\n\n1. **Technical Leadership**\n - Drive architectural decisions\n - Mentor team members\n - Establish best practices\n - Ensure code quality\n\n2. **Strategic Thinking**\n - Align with business goals\n - Evaluate trade-offs\n - Plan for scale\n - Manage technical debt\n\n3. **Collaboration**\n - Work across teams\n - Communicate effectively\n - Build consensus\n - Share knowledge\n\n4. **Innovation**\n - Stay current with research\n - Experiment with new approaches\n - Contribute to community\n - Drive continuous improvement\n\n5. **Production Excellence**\n - Ensure high availability\n - Monitor proactively\n - Optimize performance\n - Respond to incidents\n","format":"legacy","source":"claude-code","references":{"data_modeling_patterns.md":"# Data Modeling Patterns\n\n## Overview\n\nWorld-class data modeling patterns for senior data engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n","data_pipeline_architecture.md":"# Data Pipeline Architecture\n\n## Overview\n\nWorld-class data pipeline architecture for senior data engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n","dataops_best_practices.md":"# Dataops Best Practices\n\n## Overview\n\nWorld-class dataops best practices for senior data engineer.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"59006c81d5a257005e9b1867d5e3dc0764cec492220ae92733a76ec295028104"},{"uid":"technical.senior-backend","name":"senior-backend","category":"technical","description":"Comprehensive backend development skill for building scalable backend systems using NodeJS, Express, Go, Python, Postgres, GraphQL, REST APIs. Includes API scaffolding, database optimization, security implementation, and performance tuning. Use when designing APIs, optimizing database queries, implementing business logic, handling authentication/authorization, or reviewing backend code.","content":"---\nname: senior-backend\ndescription: Comprehensive backend development skill for building scalable backend systems using NodeJS, Express, Go, Python, Postgres, GraphQL, REST APIs. Includes API scaffolding, database optimization, security implementation, and performance tuning. Use when designing APIs, optimizing database queries, implementing business logic, handling authentication/authorization, or reviewing backend code.\n---\n\n# Senior Backend\n\nComplete toolkit for senior backend with modern tools and best practices.\n\n## Quick Start\n\n### Main Capabilities\n\nThis skill provides three core capabilities through automated scripts:\n\n```bash\n# Script 1: Api Scaffolder\npython scripts/api_scaffolder.py [options]\n\n# Script 2: Database Migration Tool\npython scripts/database_migration_tool.py [options]\n\n# Script 3: Api Load Tester\npython scripts/api_load_tester.py [options]\n```\n\n## Core Capabilities\n\n### 1. Api Scaffolder\n\nAutomated tool for api scaffolder tasks.\n\n**Features:**\n- Automated scaffolding\n- Best practices built-in\n- Configurable templates\n- Quality checks\n\n**Usage:**\n```bash\npython scripts/api_scaffolder.py [options]\n```\n\n### 2. Database Migration Tool\n\nComprehensive analysis and optimization tool.\n\n**Features:**\n- Deep analysis\n- Performance metrics\n- Recommendations\n- Automated fixes\n\n**Usage:**\n```bash\npython scripts/database_migration_tool.py [--verbose]\n```\n\n### 3. Api Load Tester\n\nAdvanced tooling for specialized tasks.\n\n**Features:**\n- Expert-level automation\n- Custom configurations\n- Integration ready\n- Production-grade output\n\n**Usage:**\n```bash\npython scripts/api_load_tester.py [arguments] [options]\n```\n\n## Reference Documentation\n\n### Api Design Patterns\n\nComprehensive guide available in `references/api_design_patterns.md`:\n\n- Detailed patterns and practices\n- Code examples\n- Best practices\n- Anti-patterns to avoid\n- Real-world scenarios\n\n### Database Optimization Guide\n\nComplete workflow documentation in `references/database_optimization_guide.md`:\n\n- Step-by-step processes\n- Optimization strategies\n- Tool integrations\n- Performance tuning\n- Troubleshooting guide\n\n### Backend Security Practices\n\nTechnical reference guide in `references/backend_security_practices.md`:\n\n- Technology stack details\n- Configuration examples\n- Integration patterns\n- Security considerations\n- Scalability guidelines\n\n## Tech Stack\n\n**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin\n**Frontend:** React, Next.js, React Native, Flutter\n**Backend:** Node.js, Express, GraphQL, REST APIs\n**Database:** PostgreSQL, Prisma, NeonDB, Supabase\n**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI\n**Cloud:** AWS, GCP, Azure\n\n## Development Workflow\n\n### 1. Setup and Configuration\n\n```bash\n# Install dependencies\nnpm install\n# or\npip install -r requirements.txt\n\n# Configure environment\ncp .env.example .env\n```\n\n### 2. Run Quality Checks\n\n```bash\n# Use the analyzer script\npython scripts/database_migration_tool.py .\n\n# Review recommendations\n# Apply fixes\n```\n\n### 3. Implement Best Practices\n\nFollow the patterns and practices documented in:\n- `references/api_design_patterns.md`\n- `references/database_optimization_guide.md`\n- `references/backend_security_practices.md`\n\n## Best Practices Summary\n\n### Code Quality\n- Follow established patterns\n- Write comprehensive tests\n- Document decisions\n- Review regularly\n\n### Performance\n- Measure before optimizing\n- Use appropriate caching\n- Optimize critical paths\n- Monitor in production\n\n### Security\n- Validate all inputs\n- Use parameterized queries\n- Implement proper authentication\n- Keep dependencies updated\n\n### Maintainability\n- Write clear code\n- Use consistent naming\n- Add helpful comments\n- Keep it simple\n\n## Common Commands\n\n```bash\n# Development\nnpm run dev\nnpm run build\nnpm run test\nnpm run lint\n\n# Analysis\npython scripts/database_migration_tool.py .\npython scripts/api_load_tester.py --analyze\n\n# Deployment\ndocker build -t app:latest .\ndocker-compose up -d\nkubectl apply -f k8s/\n```\n\n## Troubleshooting\n\n### Common Issues\n\nCheck the comprehensive troubleshooting section in `references/backend_security_practices.md`.\n\n### Getting Help\n\n- Review reference documentation\n- Check script output messages\n- Consult tech stack documentation\n- Review error logs\n\n## Resources\n\n- Pattern Reference: `references/api_design_patterns.md`\n- Workflow Guide: `references/database_optimization_guide.md`\n- Technical Guide: `references/backend_security_practices.md`\n- Tool Scripts: `scripts/` directory\n","format":"legacy","source":"claude-code","references":{"backend_security_practices.md":"# Backend Security Practices\n\n## Overview\n\nThis reference guide provides comprehensive information for senior backend.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior backend.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","database_optimization_guide.md":"# Database Optimization Guide\n\n## Overview\n\nThis reference guide provides comprehensive information for senior backend.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior backend.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","api_design_patterns.md":"# Api Design Patterns\n\n## Overview\n\nThis reference guide provides comprehensive information for senior backend.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior backend.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"de1c35674ab09c38b0895ab29eddfaf501ceff19ecf4db39617d7fb1cbf8762d"},{"uid":"technical.code-reviewer","name":"code-reviewer","category":"technical","description":"Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go. Includes automated code analysis, best practice checking, security scanning, and review checklist generation. Use when reviewing pull requests, providing code feedback, identifying issues, or ensuring code quality standards.","content":"---\nname: code-reviewer\ndescription: Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go. Includes automated code analysis, best practice checking, security scanning, and review checklist generation. Use when reviewing pull requests, providing code feedback, identifying issues, or ensuring code quality standards.\n---\n\n# Code Reviewer\n\nComplete toolkit for code reviewer with modern tools and best practices.\n\n## Quick Start\n\n### Main Capabilities\n\nThis skill provides three core capabilities through automated scripts:\n\n```bash\n# Script 1: Pr Analyzer\npython scripts/pr_analyzer.py [options]\n\n# Script 2: Code Quality Checker\npython scripts/code_quality_checker.py [options]\n\n# Script 3: Review Report Generator\npython scripts/review_report_generator.py [options]\n```\n\n## Core Capabilities\n\n### 1. Pr Analyzer\n\nAutomated tool for pr analyzer tasks.\n\n**Features:**\n- Automated scaffolding\n- Best practices built-in\n- Configurable templates\n- Quality checks\n\n**Usage:**\n```bash\npython scripts/pr_analyzer.py [options]\n```\n\n### 2. Code Quality Checker\n\nComprehensive analysis and optimization tool.\n\n**Features:**\n- Deep analysis\n- Performance metrics\n- Recommendations\n- Automated fixes\n\n**Usage:**\n```bash\npython scripts/code_quality_checker.py [--verbose]\n```\n\n### 3. Review Report Generator\n\nAdvanced tooling for specialized tasks.\n\n**Features:**\n- Expert-level automation\n- Custom configurations\n- Integration ready\n- Production-grade output\n\n**Usage:**\n```bash\npython scripts/review_report_generator.py [arguments] [options]\n```\n\n## Reference Documentation\n\n### Code Review Checklist\n\nComprehensive guide available in `references/code_review_checklist.md`:\n\n- Detailed patterns and practices\n- Code examples\n- Best practices\n- Anti-patterns to avoid\n- Real-world scenarios\n\n### Coding Standards\n\nComplete workflow documentation in `references/coding_standards.md`:\n\n- Step-by-step processes\n- Optimization strategies\n- Tool integrations\n- Performance tuning\n- Troubleshooting guide\n\n### Common Antipatterns\n\nTechnical reference guide in `references/common_antipatterns.md`:\n\n- Technology stack details\n- Configuration examples\n- Integration patterns\n- Security considerations\n- Scalability guidelines\n\n## Tech Stack\n\n**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin\n**Frontend:** React, Next.js, React Native, Flutter\n**Backend:** Node.js, Express, GraphQL, REST APIs\n**Database:** PostgreSQL, Prisma, NeonDB, Supabase\n**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI\n**Cloud:** AWS, GCP, Azure\n\n## Development Workflow\n\n### 1. Setup and Configuration\n\n```bash\n# Install dependencies\nnpm install\n# or\npip install -r requirements.txt\n\n# Configure environment\ncp .env.example .env\n```\n\n### 2. Run Quality Checks\n\n```bash\n# Use the analyzer script\npython scripts/code_quality_checker.py .\n\n# Review recommendations\n# Apply fixes\n```\n\n### 3. Implement Best Practices\n\nFollow the patterns and practices documented in:\n- `references/code_review_checklist.md`\n- `references/coding_standards.md`\n- `references/common_antipatterns.md`\n\n## Best Practices Summary\n\n### Code Quality\n- Follow established patterns\n- Write comprehensive tests\n- Document decisions\n- Review regularly\n\n### Performance\n- Measure before optimizing\n- Use appropriate caching\n- Optimize critical paths\n- Monitor in production\n\n### Security\n- Validate all inputs\n- Use parameterized queries\n- Implement proper authentication\n- Keep dependencies updated\n\n### Maintainability\n- Write clear code\n- Use consistent naming\n- Add helpful comments\n- Keep it simple\n\n## Common Commands\n\n```bash\n# Development\nnpm run dev\nnpm run build\nnpm run test\nnpm run lint\n\n# Analysis\npython scripts/code_quality_checker.py .\npython scripts/review_report_generator.py --analyze\n\n# Deployment\ndocker build -t app:latest .\ndocker-compose up -d\nkubectl apply -f k8s/\n```\n\n## Troubleshooting\n\n### Common Issues\n\nCheck the comprehensive troubleshooting section in `references/common_antipatterns.md`.\n\n### Getting Help\n\n- Review reference documentation\n- Check script output messages\n- Consult tech stack documentation\n- Review error logs\n\n## Resources\n\n- Pattern Reference: `references/code_review_checklist.md`\n- Workflow Guide: `references/coding_standards.md`\n- Technical Guide: `references/common_antipatterns.md`\n- Tool Scripts: `scripts/` directory\n","format":"legacy","source":"claude-code","references":{"common_antipatterns.md":"# Common Antipatterns\n\n## Overview\n\nThis reference guide provides comprehensive information for code reviewer.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for code reviewer.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","coding_standards.md":"# Coding Standards\n\n## Overview\n\nThis reference guide provides comprehensive information for code reviewer.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for code reviewer.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","code_review_checklist.md":"# Code Review Checklist\n\n## Overview\n\nThis reference guide provides comprehensive information for code reviewer.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for code reviewer.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"777841d763d199f85c64e3fd38189443505db6e1443e0a7e8a52a5f228c43ab1"},{"uid":"technical.webapp-testing","name":"webapp-testing","category":"technical","description":"Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","content":"---\nname: webapp-testing\ndescription: Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.\nlicense: Complete terms in LICENSE.txt\n---\n\n# Web Application Testing\n\nTo test local web applications, write native Python Playwright scripts.\n\n**Helper Scripts Available**:\n- `scripts/with_server.py` - Manages server lifecycle (supports multiple servers)\n\n**Always run scripts with `--help` first** to see usage. DO NOT read the source until you try running the script first and find that a customized solution is abslutely necessary. These scripts can be very large and thus pollute your context window. They exist to be called directly as black-box scripts rather than ingested into your context window.\n\n## Decision Tree: Choosing Your Approach\n\n```\nUser task → Is it static HTML?\n ├─ Yes → Read HTML file directly to identify selectors\n │ ├─ Success → Write Playwright script using selectors\n │ └─ Fails/Incomplete → Treat as dynamic (below)\n │\n └─ No (dynamic webapp) → Is the server already running?\n ├─ No → Run: python scripts/with_server.py --help\n │ Then use the helper + write simplified Playwright script\n │\n └─ Yes → Reconnaissance-then-action:\n 1. Navigate and wait for networkidle\n 2. Take screenshot or inspect DOM\n 3. Identify selectors from rendered state\n 4. Execute actions with discovered selectors\n```\n\n## Example: Using with_server.py\n\nTo start a server, run `--help` first, then use the helper:\n\n**Single server:**\n```bash\npython scripts/with_server.py --server \"npm run dev\" --port 5173 -- python your_automation.py\n```\n\n**Multiple servers (e.g., backend + frontend):**\n```bash\npython scripts/with_server.py \\\n --server \"cd backend && python server.py\" --port 3000 \\\n --server \"cd frontend && npm run dev\" --port 5173 \\\n -- python your_automation.py\n```\n\nTo create an automation script, include only Playwright logic (servers are managed automatically):\n```python\nfrom playwright.sync_api import sync_playwright\n\nwith sync_playwright() as p:\n browser = p.chromium.launch(headless=True) # Always launch chromium in headless mode\n page = browser.new_page()\n page.goto('http://localhost:5173') # Server already running and ready\n page.wait_for_load_state('networkidle') # CRITICAL: Wait for JS to execute\n # ... your automation logic\n browser.close()\n```\n\n## Reconnaissance-Then-Action Pattern\n\n1. **Inspect rendered DOM**:\n ```python\n page.screenshot(path='/tmp/inspect.png', full_page=True)\n content = page.content()\n page.locator('button').all()\n ```\n\n2. **Identify selectors** from inspection results\n\n3. **Execute actions** using discovered selectors\n\n## Common Pitfall\n\n❌ **Don't** inspect the DOM before waiting for `networkidle` on dynamic apps\n✅ **Do** wait for `page.wait_for_load_state('networkidle')` before inspection\n\n## Best Practices\n\n- **Use bundled scripts as black boxes** - To accomplish a task, consider whether one of the scripts available in `scripts/` can help. These scripts handle common, complex workflows reliably without cluttering the context window. Use `--help` to see usage, then invoke directly. \n- Use `sync_playwright()` for synchronous scripts\n- Always close the browser when done\n- Use descriptive selectors: `text=`, `role=`, CSS selectors, or IDs\n- Add appropriate waits: `page.wait_for_selector()` or `page.wait_for_timeout()`\n\n## Reference Files\n\n- **examples/** - Examples showing common patterns:\n - `element_discovery.py` - Discovering buttons, links, and inputs on a page\n - `static_html_automation.py` - Using file:// URLs for local HTML\n - `console_logging.py` - Capturing console logs during automation","format":"legacy","source":"claude-code","last_sync":"2025-12-08T12:31:36.814Z","content_hash":"51b7349e77ec63b7744a6f63647e7566a0b4d2e301121cc10e8c2113af6556a2"},{"uid":"technical.senior-qa","name":"senior-qa","category":"technical","description":"Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications. Includes test suite generation, coverage analysis, E2E testing setup, and quality metrics. Use when designing test strategies, writing test cases, implementing test automation, performing manual testing, or analyzing test coverage.","content":"---\nname: senior-qa\ndescription: Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications. Includes test suite generation, coverage analysis, E2E testing setup, and quality metrics. Use when designing test strategies, writing test cases, implementing test automation, performing manual testing, or analyzing test coverage.\n---\n\n# Senior Qa\n\nComplete toolkit for senior qa with modern tools and best practices.\n\n## Quick Start\n\n### Main Capabilities\n\nThis skill provides three core capabilities through automated scripts:\n\n```bash\n# Script 1: Test Suite Generator\npython scripts/test_suite_generator.py [options]\n\n# Script 2: Coverage Analyzer\npython scripts/coverage_analyzer.py [options]\n\n# Script 3: E2E Test Scaffolder\npython scripts/e2e_test_scaffolder.py [options]\n```\n\n## Core Capabilities\n\n### 1. Test Suite Generator\n\nAutomated tool for test suite generator tasks.\n\n**Features:**\n- Automated scaffolding\n- Best practices built-in\n- Configurable templates\n- Quality checks\n\n**Usage:**\n```bash\npython scripts/test_suite_generator.py [options]\n```\n\n### 2. Coverage Analyzer\n\nComprehensive analysis and optimization tool.\n\n**Features:**\n- Deep analysis\n- Performance metrics\n- Recommendations\n- Automated fixes\n\n**Usage:**\n```bash\npython scripts/coverage_analyzer.py [--verbose]\n```\n\n### 3. E2E Test Scaffolder\n\nAdvanced tooling for specialized tasks.\n\n**Features:**\n- Expert-level automation\n- Custom configurations\n- Integration ready\n- Production-grade output\n\n**Usage:**\n```bash\npython scripts/e2e_test_scaffolder.py [arguments] [options]\n```\n\n## Reference Documentation\n\n### Testing Strategies\n\nComprehensive guide available in `references/testing_strategies.md`:\n\n- Detailed patterns and practices\n- Code examples\n- Best practices\n- Anti-patterns to avoid\n- Real-world scenarios\n\n### Test Automation Patterns\n\nComplete workflow documentation in `references/test_automation_patterns.md`:\n\n- Step-by-step processes\n- Optimization strategies\n- Tool integrations\n- Performance tuning\n- Troubleshooting guide\n\n### Qa Best Practices\n\nTechnical reference guide in `references/qa_best_practices.md`:\n\n- Technology stack details\n- Configuration examples\n- Integration patterns\n- Security considerations\n- Scalability guidelines\n\n## Tech Stack\n\n**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin\n**Frontend:** React, Next.js, React Native, Flutter\n**Backend:** Node.js, Express, GraphQL, REST APIs\n**Database:** PostgreSQL, Prisma, NeonDB, Supabase\n**DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI\n**Cloud:** AWS, GCP, Azure\n\n## Development Workflow\n\n### 1. Setup and Configuration\n\n```bash\n# Install dependencies\nnpm install\n# or\npip install -r requirements.txt\n\n# Configure environment\ncp .env.example .env\n```\n\n### 2. Run Quality Checks\n\n```bash\n# Use the analyzer script\npython scripts/coverage_analyzer.py .\n\n# Review recommendations\n# Apply fixes\n```\n\n### 3. Implement Best Practices\n\nFollow the patterns and practices documented in:\n- `references/testing_strategies.md`\n- `references/test_automation_patterns.md`\n- `references/qa_best_practices.md`\n\n## Best Practices Summary\n\n### Code Quality\n- Follow established patterns\n- Write comprehensive tests\n- Document decisions\n- Review regularly\n\n### Performance\n- Measure before optimizing\n- Use appropriate caching\n- Optimize critical paths\n- Monitor in production\n\n### Security\n- Validate all inputs\n- Use parameterized queries\n- Implement proper authentication\n- Keep dependencies updated\n\n### Maintainability\n- Write clear code\n- Use consistent naming\n- Add helpful comments\n- Keep it simple\n\n## Common Commands\n\n```bash\n# Development\nnpm run dev\nnpm run build\nnpm run test\nnpm run lint\n\n# Analysis\npython scripts/coverage_analyzer.py .\npython scripts/e2e_test_scaffolder.py --analyze\n\n# Deployment\ndocker build -t app:latest .\ndocker-compose up -d\nkubectl apply -f k8s/\n```\n\n## Troubleshooting\n\n### Common Issues\n\nCheck the comprehensive troubleshooting section in `references/qa_best_practices.md`.\n\n### Getting Help\n\n- Review reference documentation\n- Check script output messages\n- Consult tech stack documentation\n- Review error logs\n\n## Resources\n\n- Pattern Reference: `references/testing_strategies.md`\n- Workflow Guide: `references/test_automation_patterns.md`\n- Technical Guide: `references/qa_best_practices.md`\n- Tool Scripts: `scripts/` directory\n","format":"legacy","source":"claude-code","references":{"test_automation_patterns.md":"# Test Automation Patterns\n\n## Overview\n\nThis reference guide provides comprehensive information for senior qa.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior qa.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","qa_best_practices.md":"# Qa Best Practices\n\n## Overview\n\nThis reference guide provides comprehensive information for senior qa.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior qa.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n","testing_strategies.md":"# Testing Strategies\n\n## Overview\n\nThis reference guide provides comprehensive information for senior qa.\n\n## Patterns and Practices\n\n### Pattern 1: Best Practice Implementation\n\n**Description:**\nDetailed explanation of the pattern.\n\n**When to Use:**\n- Scenario 1\n- Scenario 2\n- Scenario 3\n\n**Implementation:**\n```typescript\n// Example code implementation\nexport class Example {\n // Implementation details\n}\n```\n\n**Benefits:**\n- Benefit 1\n- Benefit 2\n- Benefit 3\n\n**Trade-offs:**\n- Consider 1\n- Consider 2\n- Consider 3\n\n### Pattern 2: Advanced Technique\n\n**Description:**\nAnother important pattern for senior qa.\n\n**Implementation:**\n```typescript\n// Advanced example\nasync function advancedExample() {\n // Code here\n}\n```\n\n## Guidelines\n\n### Code Organization\n- Clear structure\n- Logical separation\n- Consistent naming\n- Proper documentation\n\n### Performance Considerations\n- Optimization strategies\n- Bottleneck identification\n- Monitoring approaches\n- Scaling techniques\n\n### Security Best Practices\n- Input validation\n- Authentication\n- Authorization\n- Data protection\n\n## Common Patterns\n\n### Pattern A\nImplementation details and examples.\n\n### Pattern B\nImplementation details and examples.\n\n### Pattern C\nImplementation details and examples.\n\n## Anti-Patterns to Avoid\n\n### Anti-Pattern 1\nWhat not to do and why.\n\n### Anti-Pattern 2\nWhat not to do and why.\n\n## Tools and Resources\n\n### Recommended Tools\n- Tool 1: Purpose\n- Tool 2: Purpose\n- Tool 3: Purpose\n\n### Further Reading\n- Resource 1\n- Resource 2\n- Resource 3\n\n## Conclusion\n\nKey takeaways for using this reference guide effectively.\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"4453b4aa9bf923a911ee0c44249e74a95b91b5da7daee16c61652a8a7c8595ae"},{"uid":"technical.senior-data-scientist","name":"senior-data-scientist","category":"technical","description":"World-class data science skill for statistical modeling, experimentation, causal inference, and advanced analytics. Expertise in Python (NumPy, Pandas, Scikit-learn), R, SQL, statistical methods, A/B testing, time series, and business intelligence. Includes experiment design, feature engineering, model evaluation, and stakeholder communication. Use when designing experiments, building predictive models, performing causal analysis, or driving data-driven decisions.","content":"---\nname: senior-data-scientist\ndescription: World-class data science skill for statistical modeling, experimentation, causal inference, and advanced analytics. Expertise in Python (NumPy, Pandas, Scikit-learn), R, SQL, statistical methods, A/B testing, time series, and business intelligence. Includes experiment design, feature engineering, model evaluation, and stakeholder communication. Use when designing experiments, building predictive models, performing causal analysis, or driving data-driven decisions.\n---\n\n# Senior Data Scientist\n\nWorld-class senior data scientist skill for production-grade AI/ML/Data systems.\n\n## Quick Start\n\n### Main Capabilities\n\n```bash\n# Core Tool 1\npython scripts/experiment_designer.py --input data/ --output results/\n\n# Core Tool 2 \npython scripts/feature_engineering_pipeline.py --target project/ --analyze\n\n# Core Tool 3\npython scripts/model_evaluation_suite.py --config config.yaml --deploy\n```\n\n## Core Expertise\n\nThis skill covers world-class capabilities in:\n\n- Advanced production patterns and architectures\n- Scalable system design and implementation\n- Performance optimization at scale\n- MLOps and DataOps best practices\n- Real-time processing and inference\n- Distributed computing frameworks\n- Model deployment and monitoring\n- Security and compliance\n- Cost optimization\n- Team leadership and mentoring\n\n## Tech Stack\n\n**Languages:** Python, SQL, R, Scala, Go\n**ML Frameworks:** PyTorch, TensorFlow, Scikit-learn, XGBoost\n**Data Tools:** Spark, Airflow, dbt, Kafka, Databricks\n**LLM Frameworks:** LangChain, LlamaIndex, DSPy\n**Deployment:** Docker, Kubernetes, AWS/GCP/Azure\n**Monitoring:** MLflow, Weights & Biases, Prometheus\n**Databases:** PostgreSQL, BigQuery, Snowflake, Pinecone\n\n## Reference Documentation\n\n### 1. Statistical Methods Advanced\n\nComprehensive guide available in `references/statistical_methods_advanced.md` covering:\n\n- Advanced patterns and best practices\n- Production implementation strategies\n- Performance optimization techniques\n- Scalability considerations\n- Security and compliance\n- Real-world case studies\n\n### 2. Experiment Design Frameworks\n\nComplete workflow documentation in `references/experiment_design_frameworks.md` including:\n\n- Step-by-step processes\n- Architecture design patterns\n- Tool integration guides\n- Performance tuning strategies\n- Troubleshooting procedures\n\n### 3. Feature Engineering Patterns\n\nTechnical reference guide in `references/feature_engineering_patterns.md` with:\n\n- System design principles\n- Implementation examples\n- Configuration best practices\n- Deployment strategies\n- Monitoring and observability\n\n## Production Patterns\n\n### Pattern 1: Scalable Data Processing\n\nEnterprise-scale data processing with distributed computing:\n\n- Horizontal scaling architecture\n- Fault-tolerant design\n- Real-time and batch processing\n- Data quality validation\n- Performance monitoring\n\n### Pattern 2: ML Model Deployment\n\nProduction ML system with high availability:\n\n- Model serving with low latency\n- A/B testing infrastructure\n- Feature store integration\n- Model monitoring and drift detection\n- Automated retraining pipelines\n\n### Pattern 3: Real-Time Inference\n\nHigh-throughput inference system:\n\n- Batching and caching strategies\n- Load balancing\n- Auto-scaling\n- Latency optimization\n- Cost optimization\n\n## Best Practices\n\n### Development\n\n- Test-driven development\n- Code reviews and pair programming\n- Documentation as code\n- Version control everything\n- Continuous integration\n\n### Production\n\n- Monitor everything critical\n- Automate deployments\n- Feature flags for releases\n- Canary deployments\n- Comprehensive logging\n\n### Team Leadership\n\n- Mentor junior engineers\n- Drive technical decisions\n- Establish coding standards\n- Foster learning culture\n- Cross-functional collaboration\n\n## Performance Targets\n\n**Latency:**\n- P50: < 50ms\n- P95: < 100ms\n- P99: < 200ms\n\n**Throughput:**\n- Requests/second: > 1000\n- Concurrent users: > 10,000\n\n**Availability:**\n- Uptime: 99.9%\n- Error rate: < 0.1%\n\n## Security & Compliance\n\n- Authentication & authorization\n- Data encryption (at rest & in transit)\n- PII handling and anonymization\n- GDPR/CCPA compliance\n- Regular security audits\n- Vulnerability management\n\n## Common Commands\n\n```bash\n# Development\npython -m pytest tests/ -v --cov\npython -m black src/\npython -m pylint src/\n\n# Training\npython scripts/train.py --config prod.yaml\npython scripts/evaluate.py --model best.pth\n\n# Deployment\ndocker build -t service:v1 .\nkubectl apply -f k8s/\nhelm upgrade service ./charts/\n\n# Monitoring\nkubectl logs -f deployment/service\npython scripts/health_check.py\n```\n\n## Resources\n\n- Advanced Patterns: `references/statistical_methods_advanced.md`\n- Implementation Guide: `references/experiment_design_frameworks.md`\n- Technical Reference: `references/feature_engineering_patterns.md`\n- Automation Scripts: `scripts/` directory\n\n## Senior-Level Responsibilities\n\nAs a world-class senior professional:\n\n1. **Technical Leadership**\n - Drive architectural decisions\n - Mentor team members\n - Establish best practices\n - Ensure code quality\n\n2. **Strategic Thinking**\n - Align with business goals\n - Evaluate trade-offs\n - Plan for scale\n - Manage technical debt\n\n3. **Collaboration**\n - Work across teams\n - Communicate effectively\n - Build consensus\n - Share knowledge\n\n4. **Innovation**\n - Stay current with research\n - Experiment with new approaches\n - Contribute to community\n - Drive continuous improvement\n\n5. **Production Excellence**\n - Ensure high availability\n - Monitor proactively\n - Optimize performance\n - Respond to incidents\n","format":"legacy","source":"claude-code","references":{"statistical_methods_advanced.md":"# Statistical Methods Advanced\n\n## Overview\n\nWorld-class statistical methods advanced for senior data scientist.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n","experiment_design_frameworks.md":"# Experiment Design Frameworks\n\n## Overview\n\nWorld-class experiment design frameworks for senior data scientist.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n","feature_engineering_patterns.md":"# Feature Engineering Patterns\n\n## Overview\n\nWorld-class feature engineering patterns for senior data scientist.\n\n## Core Principles\n\n### Production-First Design\n\nAlways design with production in mind:\n- Scalability: Handle 10x current load\n- Reliability: 99.9% uptime target\n- Maintainability: Clear, documented code\n- Observability: Monitor everything\n\n### Performance by Design\n\nOptimize from the start:\n- Efficient algorithms\n- Resource awareness\n- Strategic caching\n- Batch processing\n\n### Security & Privacy\n\nBuild security in:\n- Input validation\n- Data encryption\n- Access control\n- Audit logging\n\n## Advanced Patterns\n\n### Pattern 1: Distributed Processing\n\nEnterprise-scale data processing with fault tolerance.\n\n### Pattern 2: Real-Time Systems\n\nLow-latency, high-throughput systems.\n\n### Pattern 3: ML at Scale\n\nProduction ML with monitoring and automation.\n\n## Best Practices\n\n### Code Quality\n- Comprehensive testing\n- Clear documentation\n- Code reviews\n- Type hints\n\n### Performance\n- Profile before optimizing\n- Monitor continuously\n- Cache strategically\n- Batch operations\n\n### Reliability\n- Design for failure\n- Implement retries\n- Use circuit breakers\n- Monitor health\n\n## Tools & Technologies\n\nEssential tools for this domain:\n- Development frameworks\n- Testing libraries\n- Deployment platforms\n- Monitoring solutions\n\n## Further Reading\n\n- Research papers\n- Industry blogs\n- Conference talks\n- Open source projects\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"1e6974ea60451055b3b11ff8b12d6bbb8ef90ab2bf973830718271c8ed53de06"},{"uid":"technical.zed-editor","name":"zed-editor","category":"technical","description":"Use this skill for Zed editor configuration, troubleshooting, and remote development. Primary focus on SSH remote debugging, log analysis, connection issues, and remote server diagnostics. Also covers settings, LSP, keybindings, extensions, and AI integration. Trigger on \"zed\", \"zed editor\", \"zed remote\", \"zed ssh\", \"zed logs\", \"zed troubleshoot\".","content":"---\nname: zed-editor\ndescription: Use this skill for Zed editor configuration, troubleshooting, and remote development. Primary focus on SSH remote debugging, log analysis, connection issues, and remote server diagnostics. Also covers settings, LSP, keybindings, extensions, and AI integration. Trigger on \"zed\", \"zed editor\", \"zed remote\", \"zed ssh\", \"zed logs\", \"zed troubleshoot\".\n---\n\n# Zed Editor\n\nConfiguration and troubleshooting guide for Zed on macOS. **See `references/remote-troubleshooting.md` for comprehensive remote/SSH debugging.**\n\n## Quick Log Commands\n\n```bash\n# Tail live logs\ntail -f ~/Library/Logs/Zed/Zed.log\n\n# SSH/remote issues only\ntail -f ~/Library/Logs/Zed/Zed.log | grep -iE \"(ssh|remote|server|connection)\"\n\n# Errors only\ngrep -iE \"(error|fail|panic|crash)\" ~/Library/Logs/Zed/Zed.log | tail -50\n\n# Recent errors with context\ngrep -B5 -A5 \"ERROR\" ~/Library/Logs/Zed/Zed.log | tail -100\n```\n\n## Log Locations\n\n```\n~/Library/Logs/Zed/Zed.log # Main log\n~/Library/Logs/Zed/server-*.log # Remote server logs\n~/Library/Logs/DiagnosticReports/Zed* # Crash reports\n~/Library/Application Support/Zed/ # State/database\n~/Library/Caches/Zed/ # Cache\n```\n\n## Configuration Files\n\n### Locations\n\n```\n~/.config/zed/settings.json # Main settings\n~/.config/zed/keymap.json # Custom keybindings\n~/.config/zed/themes/ # Custom themes\n.zed/settings.json # Project-specific settings\n```\n\n### Edit Settings\n\n```bash\n# Open in Zed\nzed ~/.config/zed/settings.json\n\n# Or use Cmd+, in Zed to open settings UI\n```\n\n## Common Configuration Tasks\n\n### Hide Files from Project Panel\n\nAdd to `file_scan_exclusions` (this overrides defaults, so include them):\n\n```json\n{\n \"file_scan_exclusions\": [\n \"**/.git\",\n \"**/.svn\",\n \"**/.hg\",\n \"**/.jj\",\n \"**/CVS\",\n \"**/.DS_Store\",\n \"**/Thumbs.db\",\n \"**/.classpath\",\n \"**/.settings\",\n \"**/.Trashes\",\n \"**/.TemporaryItems\",\n \"**/.Spotlight-V100\",\n \"**/.fseventsd\",\n \"**/node_modules\",\n \"**/.next\",\n \"**/dist\",\n \"**/build\"\n ]\n}\n```\n\n### Include Gitignored Files\n\n```json\n{\n \"file_scan_inclusions\": [\n \".env.example\",\n \".github/**\"\n ]\n}\n```\n\n### Theme Configuration\n\n```json\n{\n \"theme\": {\n \"mode\": \"dark\",\n \"light\": \"One Light\",\n \"dark\": \"Ayu Dark\"\n }\n}\n```\n\n### Font Settings\n\n```json\n{\n \"ui_font_size\": 14,\n \"buffer_font_size\": 16,\n \"ui_font_family\": \"MesloLGS Nerd Font Mono\",\n \"buffer_font_family\": \"JetBrains Mono\",\n \"terminal\": {\n \"font_family\": \"MesloLGS Nerd Font Mono\",\n \"font_size\": 14\n }\n}\n```\n\n### Autosave Options\n\n```json\n{\n \"autosave\": \"on_focus_change\"\n}\n```\n\nOptions: `\"off\"`, `\"on_focus_change\"`, `\"on_window_change\"`, `{\"after_delay\": {\"milliseconds\": 1000}}`\n\n### Disable Telemetry\n\n```json\n{\n \"telemetry\": {\n \"diagnostics\": false,\n \"metrics\": false\n }\n}\n```\n\n## LSP Configuration\n\n### Disable Specific Language Servers\n\n```json\n{\n \"lsp\": {\n \"ruby-lsp\": { \"enabled\": false },\n \"solargraph\": { \"enabled\": false },\n \"sourcekit-lsp\": { \"enabled\": false },\n \"zls\": { \"enabled\": false }\n }\n}\n```\n\n### Configure LSP Initialization\n\n```json\n{\n \"lsp\": {\n \"astro-language-server\": {\n \"initialization_options\": {\n \"lazy_load\": true\n }\n },\n \"typescript-language-server\": {\n \"initialization_options\": {\n \"preferences\": {\n \"importModuleSpecifierPreference\": \"relative\"\n }\n }\n }\n }\n}\n```\n\n## SSH Remote Development\n\n### Configure SSH Connections\n\n```json\n{\n \"ssh_connections\": [\n {\n \"host\": \"server.example.com\",\n \"username\": \"user\",\n \"port\": 22,\n \"args\": [\"-i\", \"~/.ssh/id_ed25519\"],\n \"nickname\": \"my-server\",\n \"upload_binary_over_ssh\": true,\n \"projects\": [\n { \"paths\": [\"/home/user/project\"] }\n ]\n }\n ]\n}\n```\n\n### Connect via Command Palette\n\n1. `Cmd+Shift+P`\n2. Type \"ssh\"\n3. Select \"Connect to SSH Host\"\n\n## AI / Agent Configuration\n\n### Claude Agent Settings\n\n```json\n{\n \"agent_servers\": {\n \"claude\": {\n \"default_mode\": \"bypassPermissions\"\n }\n },\n \"agent\": {\n \"notify_when_agent_waiting\": \"all_screens\",\n \"enable_feedback\": false,\n \"always_allow_tool_actions\": true,\n \"play_sound_when_agent_done\": true,\n \"default_model\": {\n \"provider\": \"anthropic\",\n \"model\": \"claude-sonnet-4-20250514\"\n }\n }\n}\n```\n\n### MCP Context Servers\n\n```json\n{\n \"context_servers\": {\n \"mcp-server-github\": {\n \"enabled\": true,\n \"settings\": {}\n }\n }\n}\n```\n\n## Keybindings\n\n### Custom Keybindings File\n\nCreate `~/.config/zed/keymap.json`:\n\n```json\n[\n {\n \"context\": \"Editor\",\n \"bindings\": {\n \"cmd-shift-d\": \"editor::DuplicateLine\",\n \"cmd-l\": \"editor::SelectLine\"\n }\n },\n {\n \"context\": \"Workspace\",\n \"bindings\": {\n \"cmd-k cmd-s\": \"zed::OpenKeymap\"\n }\n }\n]\n```\n\n## Project-Specific Settings\n\nCreate `.zed/settings.json` in project root:\n\n```json\n{\n \"tab_size\": 2,\n \"formatter\": \"language_server\",\n \"format_on_save\": \"on\",\n \"languages\": {\n \"Python\": {\n \"tab_size\": 4,\n \"formatter\": {\n \"external\": {\n \"command\": \"black\",\n \"arguments\": [\"-\"]\n }\n }\n }\n }\n}\n```\n\n## Extensions\n\n### Install via Command Palette\n\n1. `Cmd+Shift+P`\n2. Type \"extensions\"\n3. Search and install\n\n### Popular Extensions\n\n- **Material Icon Theme** - File icons\n- **GitLens** - Git integration\n- **Error Lens** - Inline error display\n- **Rainbow CSV** - CSV highlighting\n\n## Troubleshooting\n\n**For comprehensive remote/SSH troubleshooting, see `references/remote-troubleshooting.md`**\n\n### Quick Remote Fixes\n\n```bash\n# Test SSH connection\nssh -v user@host \"echo ok\"\n\n# Kill stale remote server\nssh user@host \"pkill -f zed-remote-server\"\n\n# Full remote reset\nssh user@host \"rm -rf ~/.local/share/zed\"\n\n# Check remote disk space\nssh user@host \"df -h ~\"\n```\n\n### Reset Zed State\n\n```bash\n# Clear Zed cache\nrm -rf ~/Library/Caches/Zed\nrm -rf ~/Library/Application\\ Support/Zed\n\n# Keep settings, clear state only\nrm -rf ~/Library/Application\\ Support/Zed/db\n\n# Clear remote server state\nrm -rf ~/Library/Application\\ Support/Zed/remote_servers\n```\n\n### Debug Mode\n\n```bash\n# Launch with verbose logging\nRUST_LOG=debug /Applications/Zed.app/Contents/MacOS/zed\n\n# SSH-specific debug\nRUST_LOG=zed::ssh=debug /Applications/Zed.app/Contents/MacOS/zed\n```\n\n### Debug LSP Issues\n\n1. `Cmd+Shift+P` → \"Debug: Open Language Server Logs\"\n2. Check for initialization errors\n3. Verify LSP binary is in PATH\n\n### Common Issues\n\n**SSH connection failing:**\n- Test: `ssh -v user@host`\n- Enable: `\"upload_binary_over_ssh\": true`\n- Fix permissions: `chmod 600 ~/.ssh/id_*`\n- See `references/remote-troubleshooting.md` for more\n\n**Remote LSP not working:**\n- Check LSP installed on remote: `ssh host \"which node\"`\n- Check PATH in non-interactive shell\n- Install on remote: `npm install -g typescript-language-server`\n\n**LSP not starting (local):**\n- Check if language server is installed\n- Verify PATH includes the binary location\n- Check LSP logs for errors\n\n**Extensions not loading:**\n- Restart Zed completely\n- Clear extension cache: `rm -rf ~/Library/Application\\ Support/Zed/extensions`\n\n## Keyboard Shortcuts Reference\n\n| Action | Shortcut |\n|--------|----------|\n| Command Palette | `Cmd+Shift+P` |\n| Go to File | `Cmd+P` |\n| Go to Symbol | `Cmd+Shift+O` |\n| Go to Line | `Ctrl+G` |\n| Toggle Terminal | `Ctrl+`` |\n| Split Right | `Cmd+K Cmd+\\` |\n| Close Tab | `Cmd+W` |\n| Settings | `Cmd+,` |\n| Find in Files | `Cmd+Shift+F` |\n| Toggle Sidebar | `Cmd+B` |\n\n## Resources\n\n**Skill References:**\n- `references/remote-troubleshooting.md` - SSH debugging, log analysis, connection fixes\n- `references/settings-reference.md` - Complete settings documentation\n\n**External:**\n- [Zed Documentation](https://zed.dev/docs)\n- [Configuring Zed](https://zed.dev/docs/configuring-zed)\n- [Zed GitHub](https://github.com/zed-industries/zed)\n","format":"legacy","source":"claude-code","references":{"settings-reference.md":"# Zed Settings Reference\n\nComplete reference for all major Zed settings categories.\n\n## Editor Settings\n\n```json\n{\n \"cursor_blink\": true,\n \"hover_popover_enabled\": true,\n \"show_completions_on_input\": true,\n \"show_completion_documentation\": true,\n \"completion_documentation_secondary_query_debounce\": 300,\n \"show_inline_completions\": true,\n \"inline_completions_mode\": \"suggest\",\n \"use_autoclose\": true,\n \"use_auto_surround\": true,\n \"always_treat_brackets_as_autoclosed\": false,\n \"show_wrap_guides\": true,\n \"wrap_guides\": [],\n \"tab_size\": 4,\n \"hard_tabs\": false,\n \"soft_wrap\": \"none\",\n \"preferred_line_length\": 80,\n \"format_on_save\": \"off\",\n \"formatter\": \"language_server\",\n \"remove_trailing_whitespace_on_save\": true,\n \"ensure_final_newline_on_save\": true,\n \"tab_bar\": {\n \"show\": true,\n \"show_nav_history_buttons\": true\n },\n \"toolbar\": {\n \"breadcrumbs\": true,\n \"quick_actions\": true\n },\n \"scrollbar\": {\n \"show\": \"auto\",\n \"cursors\": true,\n \"git_diff\": true,\n \"search_results\": true,\n \"selected_symbol\": true,\n \"diagnostics\": true\n },\n \"gutter\": {\n \"line_numbers\": true,\n \"code_actions\": true,\n \"runnables\": true,\n \"folds\": true\n },\n \"vertical_scroll_margin\": 3,\n \"scroll_sensitivity\": 1.0,\n \"relative_line_numbers\": false,\n \"seed_search_query_from_cursor\": \"always\",\n \"multi_cursor_modifier\": \"alt\",\n \"redact_private_values\": false\n}\n```\n\n## Project Panel Settings\n\n```json\n{\n \"project_panel\": {\n \"button\": true,\n \"dock\": \"left\",\n \"git_status\": true,\n \"default_width\": 240,\n \"auto_reveal_entries\": true,\n \"auto_fold_dirs\": true,\n \"scrollbar\": {\n \"show\": \"auto\"\n },\n \"indent_size\": 20\n }\n}\n```\n\n## Terminal Settings\n\n```json\n{\n \"terminal\": {\n \"shell\": \"system\",\n \"dock\": \"bottom\",\n \"default_width\": 640,\n \"default_height\": 320,\n \"working_directory\": \"current_project_directory\",\n \"blinking\": \"terminal_controlled\",\n \"alternate_scroll\": \"on\",\n \"option_as_meta\": false,\n \"copy_on_select\": false,\n \"button\": true,\n \"env\": {},\n \"line_height\": \"comfortable\",\n \"detect_venv\": {\n \"on\": {\n \"directories\": [\".env\", \"env\", \".venv\", \"venv\"],\n \"activate_script\": \"default\"\n }\n },\n \"toolbar\": {\n \"title\": true\n },\n \"font_size\": null,\n \"font_family\": null,\n \"font_features\": null,\n \"font_fallbacks\": null\n }\n}\n```\n\n## Git Settings\n\n```json\n{\n \"git\": {\n \"git_gutter\": \"tracked_files\",\n \"inline_blame\": {\n \"enabled\": true,\n \"delay_ms\": 600\n }\n }\n}\n```\n\n## Collaboration Settings\n\n```json\n{\n \"collaboration_panel\": {\n \"button\": true,\n \"dock\": \"left\",\n \"default_width\": 240\n },\n \"chat_panel\": {\n \"button\": true,\n \"dock\": \"right\",\n \"default_width\": 240\n },\n \"notification_panel\": {\n \"button\": true,\n \"dock\": \"right\",\n \"default_width\": 380\n }\n}\n```\n\n## Language-Specific Settings\n\n```json\n{\n \"languages\": {\n \"JavaScript\": {\n \"tab_size\": 2,\n \"formatter\": \"prettier\",\n \"format_on_save\": \"on\"\n },\n \"TypeScript\": {\n \"tab_size\": 2,\n \"formatter\": \"prettier\",\n \"format_on_save\": \"on\"\n },\n \"Python\": {\n \"tab_size\": 4,\n \"formatter\": {\n \"external\": {\n \"command\": \"black\",\n \"arguments\": [\"-\"]\n }\n },\n \"format_on_save\": \"on\"\n },\n \"Rust\": {\n \"tab_size\": 4,\n \"formatter\": \"language_server\",\n \"format_on_save\": \"on\"\n },\n \"Go\": {\n \"tab_size\": 4,\n \"hard_tabs\": true,\n \"formatter\": \"language_server\",\n \"format_on_save\": \"on\"\n },\n \"Markdown\": {\n \"soft_wrap\": \"preferred_line_length\",\n \"preferred_line_length\": 100\n },\n \"JSON\": {\n \"tab_size\": 2\n },\n \"YAML\": {\n \"tab_size\": 2\n }\n }\n}\n```\n\n## File Types\n\nOverride language detection for specific file patterns:\n\n```json\n{\n \"file_types\": {\n \"Shell Script\": [\"zshrc\", \"zprofile\", \"zshenv\"],\n \"JSON\": [\"*.jsonc\", \".prettierrc\", \".eslintrc\"],\n \"YAML\": [\"*.yml\"]\n }\n}\n```\n\n## Inlay Hints\n\n```json\n{\n \"inlay_hints\": {\n \"enabled\": true,\n \"show_type_hints\": true,\n \"show_parameter_hints\": true,\n \"show_other_hints\": true,\n \"edit_debounce_ms\": 700,\n \"scroll_debounce_ms\": 50\n }\n}\n```\n\n## Diagnostics\n\n```json\n{\n \"diagnostics\": {\n \"include_warnings\": true\n }\n}\n```\n\n## Assistant / AI Settings\n\n```json\n{\n \"assistant\": {\n \"enabled\": true,\n \"button\": true,\n \"dock\": \"right\",\n \"default_width\": 640,\n \"default_height\": 320,\n \"default_model\": {\n \"provider\": \"anthropic\",\n \"model\": \"claude-sonnet-4-20250514\"\n }\n }\n}\n```\n\n## Vim Mode\n\n```json\n{\n \"vim_mode\": false,\n \"vim\": {\n \"use_system_clipboard\": \"always\",\n \"use_multiline_find\": false,\n \"use_smartcase_find\": false\n }\n}\n```\n\n## Journal Settings\n\n```json\n{\n \"journal\": {\n \"path\": \"~\",\n \"hour_format\": \"hour12\"\n }\n}\n```\n\n## Auto-Update\n\n```json\n{\n \"auto_update\": true,\n \"auto_install_extensions\": {\n \"html\": true\n }\n}\n```\n\n## Window Settings\n\n```json\n{\n \"when_closing_with_no_tabs\": \"close_window\",\n \"restore_on_startup\": \"last_workspace\",\n \"on_last_window_closed\": \"quit_app\",\n \"confirm_quit\": false,\n \"centered_layout\": {\n \"left_padding\": 0.2,\n \"right_padding\": 0.2\n }\n}\n```\n\n## Proxy Settings\n\n```json\n{\n \"proxy\": \"http://proxy.example.com:8080\",\n \"server_url\": \"https://zed.dev\"\n}\n```\n","remote-troubleshooting.md":"# Zed Remote Development Troubleshooting\n\nComprehensive guide for diagnosing and fixing Zed SSH remote development issues.\n\n## Log Locations\n\n### Local (macOS)\n\n```bash\n# Main Zed log\n~/Library/Logs/Zed/Zed.log\n\n# Crash reports\n~/Library/Logs/DiagnosticReports/Zed*.ips\n\n# Application support (state, db)\n~/Library/Application\\ Support/Zed/\n\n# Cache\n~/Library/Caches/Zed/\n```\n\n### Remote Server\n\n```bash\n# Zed remote server binary location\n~/.local/share/zed/\n\n# Remote server logs (written to local)\n~/Library/Logs/Zed/server-*.log\n\n# Check if Zed server is running\nps aux | grep zed\npgrep -f \"zed.*server\"\n```\n\n## Log Analysis Commands\n\n### Tail Live Logs\n\n```bash\n# Follow main log\ntail -f ~/Library/Logs/Zed/Zed.log\n\n# Filter for SSH/remote issues\ntail -f ~/Library/Logs/Zed/Zed.log | grep -iE \"(ssh|remote|server|connection)\"\n\n# Filter for errors only\ntail -f ~/Library/Logs/Zed/Zed.log | grep -iE \"(error|fail|panic|crash)\"\n\n# Watch all Zed logs\ntail -f ~/Library/Logs/Zed/*.log\n```\n\n### Search Historical Logs\n\n```bash\n# Find connection failures\ngrep -i \"connection\" ~/Library/Logs/Zed/Zed.log | tail -50\n\n# Find SSH errors\ngrep -iE \"(ssh|remote)\" ~/Library/Logs/Zed/Zed.log | grep -i error\n\n# Find timeouts\ngrep -i \"timeout\" ~/Library/Logs/Zed/Zed.log\n\n# Find binary upload issues\ngrep -i \"upload\" ~/Library/Logs/Zed/Zed.log\n\n# Recent errors with context\ngrep -B5 -A5 \"ERROR\" ~/Library/Logs/Zed/Zed.log | tail -100\n```\n\n### Log Rotation / Cleanup\n\n```bash\n# Check log sizes\ndu -sh ~/Library/Logs/Zed/*\n\n# Clear old logs (keep recent)\nfind ~/Library/Logs/Zed -name \"*.log\" -mtime +7 -delete\n\n# Archive logs before clearing\ntar -czvf ~/zed-logs-$(date +%Y%m%d).tar.gz ~/Library/Logs/Zed/\n```\n\n## Common Remote Issues\n\n### 1. Binary Upload Fails\n\n**Symptoms:**\n- \"Failed to upload remote server binary\"\n- Connection hangs during initial setup\n- Timeout during first connection\n\n**Diagnosis:**\n```bash\n# Check remote disk space\nssh user@host \"df -h ~\"\n\n# Check remote architecture\nssh user@host \"uname -m\"\n\n# Check if binary exists\nssh user@host \"ls -la ~/.local/share/zed/\"\n\n# Check binary permissions\nssh user@host \"file ~/.local/share/zed/zed-remote-server-*\"\n```\n\n**Solutions:**\n```json\n// Ensure upload is enabled\n{\n \"ssh_connections\": [\n {\n \"host\": \"server\",\n \"upload_binary_over_ssh\": true\n }\n ]\n}\n```\n\n```bash\n# Manual cleanup on remote\nssh user@host \"rm -rf ~/.local/share/zed\"\n\n# Retry connection in Zed\n```\n\n### 2. Connection Timeout\n\n**Symptoms:**\n- \"Connection timed out\"\n- Spinning indicator forever\n- \"Failed to connect to remote server\"\n\n**Diagnosis:**\n```bash\n# Test basic SSH\nssh -v user@host \"echo ok\"\n\n# Test with Zed's typical args\nssh -o ConnectTimeout=30 -o ServerAliveInterval=15 user@host \"echo ok\"\n\n# Check SSH config\ncat ~/.ssh/config\n\n# Test port\nnc -zv host 22\n```\n\n**Solutions:**\n```bash\n# Add to ~/.ssh/config\nHost server\n HostName server.example.com\n User user\n ConnectTimeout 60\n ServerAliveInterval 30\n ServerAliveCountMax 3\n TCPKeepAlive yes\n```\n\n### 3. Authentication Failures\n\n**Symptoms:**\n- \"Permission denied\"\n- \"Authentication failed\"\n- Repeated password prompts\n\n**Diagnosis:**\n```bash\n# Verbose SSH test\nssh -vvv user@host \"echo ok\"\n\n# Check key permissions\nls -la ~/.ssh/\n\n# Test specific key\nssh -i ~/.ssh/id_ed25519 user@host \"echo ok\"\n\n# Check agent\nssh-add -l\n```\n\n**Solutions:**\n```bash\n# Fix key permissions\nchmod 700 ~/.ssh\nchmod 600 ~/.ssh/id_*\nchmod 644 ~/.ssh/*.pub\n\n# Add key to agent\nssh-add ~/.ssh/id_ed25519\n\n# Specify key in Zed config\n```\n\n```json\n{\n \"ssh_connections\": [\n {\n \"host\": \"server\",\n \"args\": [\"-i\", \"~/.ssh/id_ed25519\"]\n }\n ]\n}\n```\n\n### 4. Remote Server Crashes\n\n**Symptoms:**\n- Sudden disconnection\n- \"Remote server exited unexpectedly\"\n- Features stop working mid-session\n\n**Diagnosis:**\n```bash\n# Check remote server process\nssh user@host \"ps aux | grep zed\"\n\n# Check remote system resources\nssh user@host \"free -h && df -h\"\n\n# Check for OOM kills\nssh user@host \"dmesg | grep -i 'out of memory' | tail -10\"\nssh user@host \"journalctl -k | grep -i oom | tail -10\"\n\n# Check remote server logs\ngrep \"server\" ~/Library/Logs/Zed/Zed.log | tail -50\n```\n\n**Solutions:**\n```bash\n# Kill stale remote processes\nssh user@host \"pkill -f zed-remote-server\"\n\n# Clear remote state\nssh user@host \"rm -rf ~/.local/share/zed\"\n\n# Reconnect in Zed\n```\n\n### 5. LSP Not Working Remotely\n\n**Symptoms:**\n- No autocompletion\n- No go-to-definition\n- \"Language server not running\"\n\n**Diagnosis:**\n```bash\n# Check if LSP binary exists on remote\nssh user@host \"which node typescript-language-server rust-analyzer\"\n\n# Check remote PATH\nssh user@host \"echo \\$PATH\"\n\n# Check remote shell initialization\nssh user@host \"bash -l -c 'which node'\"\n```\n\n**Solutions:**\n```bash\n# Install LSP on remote\nssh user@host \"npm install -g typescript typescript-language-server\"\n\n# Ensure PATH is set in non-interactive shell\n# Add to remote ~/.bashrc or ~/.profile:\nexport PATH=\"$HOME/.local/bin:$HOME/.cargo/bin:$PATH\"\n```\n\n### 6. File Sync Issues\n\n**Symptoms:**\n- Changes not saving\n- \"File has been modified externally\"\n- Stale file contents\n\n**Diagnosis:**\n```bash\n# Check file permissions on remote\nssh user@host \"ls -la /path/to/file\"\n\n# Check filesystem type\nssh user@host \"df -T /path/to/project\"\n\n# Check for NFS/network filesystem issues\nssh user@host \"mount | grep nfs\"\n```\n\n**Solutions:**\n```bash\n# Fix permissions\nssh user@host \"chmod -R u+rw /path/to/project\"\n\n# Check for file locks\nssh user@host \"lsof +D /path/to/project\"\n```\n\n## Debug Mode\n\n### Enable Verbose Logging\n\nSet environment variable before launching Zed:\n\n```bash\n# Maximum verbosity\nRUST_LOG=debug /Applications/Zed.app/Contents/MacOS/zed\n\n# SSH-specific debug\nRUST_LOG=zed::ssh=debug /Applications/Zed.app/Contents/MacOS/zed\n\n# Remote server debug\nRUST_LOG=remote=debug /Applications/Zed.app/Contents/MacOS/zed\n```\n\n### Debug SSH Connection\n\n```bash\n# Create debug wrapper script\ncat > ~/zed-ssh-debug.sh << 'EOF'\n#!/bin/bash\necho \"SSH args: $@\" >> /tmp/zed-ssh-debug.log\nssh -v \"$@\" 2>> /tmp/zed-ssh-debug.log\nEOF\nchmod +x ~/zed-ssh-debug.sh\n\n# Point Zed to use it (temporary test)\n# Then check /tmp/zed-ssh-debug.log\n```\n\n## Network Diagnostics\n\n```bash\n# Test connectivity\nping -c 3 server.example.com\n\n# Test SSH port\nnc -zv server.example.com 22\n\n# Trace route\ntraceroute server.example.com\n\n# Check DNS\nnslookup server.example.com\n\n# Test throughput (if scp works)\ndd if=/dev/zero bs=1M count=10 | ssh user@host \"cat > /dev/null\"\n```\n\n## Reset Remote State\n\n### Full Reset\n\n```bash\n# Local: Clear Zed remote state\nrm -rf ~/Library/Application\\ Support/Zed/remote_servers\n\n# Remote: Clear server installation\nssh user@host \"rm -rf ~/.local/share/zed\"\n\n# Restart Zed and reconnect\n```\n\n### Soft Reset\n\n```bash\n# Kill remote processes only\nssh user@host \"pkill -9 -f zed-remote-server\"\n\n# Disconnect and reconnect in Zed (Cmd+Shift+P → \"Disconnect\")\n```\n\n## Useful Aliases\n\nAdd to `~/.config/fish/config.fish` or shell config:\n\n```fish\n# Tail Zed logs\nalias zed-logs=\"tail -f ~/Library/Logs/Zed/Zed.log\"\n\n# Zed errors only\nalias zed-errors=\"grep -iE '(error|fail|panic)' ~/Library/Logs/Zed/Zed.log | tail -50\"\n\n# SSH issues\nalias zed-ssh-debug=\"grep -iE '(ssh|remote|server)' ~/Library/Logs/Zed/Zed.log | tail -100\"\n\n# Clean remote state\nfunction zed-remote-reset\n ssh $argv[1] \"rm -rf ~/.local/share/zed && pkill -f zed-remote-server\"\n echo \"Remote state cleared for $argv[1]\"\nend\n```\n\n## Quick Reference\n\n| Issue | First Check | Quick Fix |\n|-------|-------------|-----------|\n| Can't connect | `ssh -v user@host` | Check SSH config/keys |\n| Binary upload fails | Remote disk space | `rm -rf ~/.local/share/zed` on remote |\n| Timeout | Network/firewall | Increase `ConnectTimeout` |\n| LSP broken | LSP installed on remote? | Install LSP, check PATH |\n| Random disconnects | Server resources | Check memory, increase swap |\n| Auth fails | Key permissions | `chmod 600 ~/.ssh/id_*` |\n"},"last_sync":"2025-12-08T12:31:36.814Z","content_hash":"70a92659e44698991c48c5f8138da5cbe994c7663526751e4b595f2ab0e85187"}]; let currentCategory = 'all'; function filterSkills() { const search = document.getElementById('search').value.toLowerCase(); document.querySelectorAll('.skill-item').forEach(item => { const uid = item.dataset.uid; const skill = skills.find(s => s.uid === uid); const matchesSearch = !search || skill.name.toLowerCase().includes(search) || skill.description.toLowerCase().includes(search) || skill.uid.toLowerCase().includes(search); const matchesCategory = currentCategory === 'all' || item.dataset.category === currentCategory; item.style.display = matchesSearch && matchesCategory ? 'block' : 'none'; }); } function setCategory(cat) { currentCategory = cat; document.querySelectorAll('.filter-btn').forEach(btn => { btn.classList.toggle('active', btn.dataset.category === cat); }); filterSkills(); } function showSkill(uid) { const skill = skills.find(s => s.uid === uid); if (!skill) return; document.getElementById('modal-title').textContent = skill.name; document.getElementById('modal-content').textContent = skill.content; document.getElementById('modal').classList.add('active'); } function closeModal() { document.getElementById('modal').classList.remove('active'); } document.addEventListener('keydown', e => { if (e.key === 'Escape') closeModal(); });