all publishers

mevans2120

@mevans2120 source repo

6 published skills

  1. ▌
    Project Manager · mevans2120 bundle
    Manages complete feature lifecycle from planning to production. Creates/updates features in registry, generates roadmaps, manages GitHub issues with screenshots and visual documentation, and produces comprehensive reports. Use this for feature management, roadmap generation, issue automation, and project tracking.
    0 installs
  2. ▌
    Project Planner · mevans2120
    Discovers features from codebases, manages feature registries, and exports roadmaps. Analyzes React routes, Express endpoints, component structures, and generates CSV/Markdown roadmaps. Use this for feature discovery from code, roadmap generation, and feature registry management.
    3 installs
  3. ▌
    Project Analyzer · mevans2120
    Discovers and analyzes features across code, web applications, and production environments. Identifies features from code structure, live websites, TODOs, and verifies production deployments. Use this for feature discovery, production verification, visual testing, and deployment validation.
    3 installs
  4. ▌
    Design Concepts · mevans2120
    Creates conceptual designs that illustrate design strategy and approach. Use when user says "mockup", "wireframe", "concept", "mood board", "visual direction", "design options", "explore designs", "UI design", "prototype", "design this", "show me designs", "create a design", "look and feel", or "design variations". Leverages research insights and design briefs to develop UI concepts, mood boards, and interactive prototypes. Do NOT use when user needs to understand users first (use design-research), or is writing code.
    2 installs
  5. ▌
    Design Research · mevans2120
    Design - Research
    3 installs
  6. ▌
    Design Components · mevans2120
    Designs components and sections within an existing design system. Creates 3 composition variations that use the project's actual tokens, colors, typography, and component primitives. Use when user says "design a component", "component variations", "design a card", "design a hero", "design a section", "component options", "design within our system", "new component", "component concept", or wants to explore how a component could look using their existing design system. Also use when designing larger composed sections (dashboards, settings pages, feature panels) that build on existing primitives. Do NOT use when the project has no design system yet (use design-system-init), or when exploring entirely new visual directions (use design-concepts).
    3 installs