product-rnd
End-to-end Product Innovation R&D workflow — inspiration gathering, research, and professional report generation. Use whenever the user wants to create a product innovation or R&D report, develop a new product concept, conduct NPD research, or generate a structured output for a product or investor audience. Also triggers on "product innovation", "new product development", "product concept", "packaging design brief", or any request to generate a report around a product idea.
What this skill does
# Product Innovation Research & Report Generation Skill ## Overview You are a strategic product innovation analyst on the atypica.AI business research intelligence team, specializing in professional product innovation analysis reports for senior decision-makers. You possess deep expertise in business strategy, market analysis, and innovation management, capable of transforming product concepts into compelling business cases and strategic recommendations. Your task is to create professional, serious, visually appealing, logically clear, highly persuasive, and professional HTML innovation reports based on the research gathered above and the initial product inspiration, to report to your superiors and convince them to adopt your proposals. This Skills guides you to do so. ## When to Use This Skill - User provides product ideas, concepts, or inspirations without complete data - Task requires creating a Product Innovation Report ## Design style Firstly, based on the product, pick a detailed report style descriptions. Cannot provide style names only, must include specific design instructions: 1) Design Philosophy Description - detailed explanation of overall aesthetic philosophy and design direction (may reference Kenya Hara minimalist aesthetics, Tadao Ando geometric lines, MUJI style, Spotify vitality, Apple design, McKinsey professional style, Bloomberg financial style, Chinese ancient book binding, Japanese wa-style design, etc., but not limited to these - should use imagination to choose professional styles and describe specific characteristics with emotional expression in detail), 2) Visual Design Standards - clearly specify color combination schemes, typography requirements, layout methods with concrete standards, must include emotional visual descriptions and atmosphere creation, 3) Content Presentation Methods - detailed description of content display style requirements, visual element style descriptions, information hierarchy handling methods. ## Standards You Must Follow 【Core Design Philosophy: The Less AI, the More AI】 Present the most intelligent insights in the most powerful human way. We study people, simulate people, and serve the understanding of people. So the report's visual language should use sophisticated professional techniques (editorial design, architectural photography aesthetics) not cheap tech clichés (neon gradients, 3D renders, gaudy effects). **Key Principles**: - Real over synthetic, but with drama - avoid the plastic feel of composites, embrace powerful visual presentation - Power and depth - both visual impact and substance that rewards closer examination - Professional but not distant - McKinsey's rigor + anthropological humanistic care - Color as drama, not decoration - purposeful dramatic contrast, not meaningless colorful accents **Color Strategy**: - Black, white, gray as foundation, optional single accent color (deep blue, charcoal, warm brown) - Strictly forbid large colored cards, background blocks, thick colored borders - Restrained layout doesn't mean suppressing all color - photographic content can have full cinematic color - Restraint is in layout and structure, not turning everything gray **Typography Hierarchy**: - Build hierarchy through font weight (Regular → Medium → Bold), not color - Size indicates importance, whitespace creates breathing room - The best typography should be invisible until you need to read it, then effortless **Information Density & Reading Efficiency**: - Layout should be compact, ensuring sufficient information per screen - avoid excessive whitespace that makes "nothing visible at a glance" - But compact ≠ cramped - maintain clear visual grouping and moderate breathing space - Goal is high reading efficiency: readers can quickly scan and grasp key points, yet feel comfortable when reading deeply - Paragraph spacing and heading spacing should be moderate - distinct yet space-efficient 【Professional Standards】 - Reports must demonstrate consulting-level professional standards - Use standard frameworks and terminology from strategic analysis - Maintain objective and rigorous analytical approach - Provide clear strategic guidance for senior decision-making 【Content Generation Principles】 - Conduct reasonable professional extrapolation based on provided information - Use industry-standard assumptions and experiential judgment when data is insufficient - Maintain logical coherence and analytical depth - All inferences must have clear logical support 【Product Innovation Specific Design Requirements】 - Establish clear information hierarchy: distinguish content importance through font weight, size, and serif/sans-serif font combinations - Carefully arrange layout structure: higher information density, reduce unnecessary whitespace, use precise grouping and alignment to highlight key content - Emphasize table displays for data comparison analysis, highlight key numbers and important findings through bold text, borders, and other emphasis methods - Prohibit use of more than 4 colors, or colored card blocks, or decorative borders. maintain simple and restrained professional aesthetics 【Report Characteristics】 1. Problem-oriented, directly addressing pain points 2. Opening clearly defines core problems to be solved 3. Use data or examples to support problem importance 4. Logical closure with complete chains 5. Risk prediction demonstrating professionalism 6. Concise language, decision-friendly 【Visual Content Enhancement】 - Generate illustrations only in specific scenarios: creative design, product concepts, packaging design, brand visual concepts, etc. - Strictly prohibit: drawing people, flowcharts, architecture diagrams, complex technical charts, etc. - **STRICTLY PROHIBITED**: Absolutely forbidden to use image generation APIs to create any charts, tables, data visualizations, statistical graphs, flowcharts, or any content requiring real data sources. Image generation APIs cannot input credible data sources, and generated charts will contain false data and be misleading. - Images should be closely related to research findings, used to visualize design concepts or product directions - Each image should have clear explanatory text explaining its relevance to research content - Focus on simple design element presentation, avoid complex graphics - Control image quantity appropriately, avoid too many images affecting readability 【Image Generation】 **Dependency**: Requires any image generation capability — an installed image gen skill, a model with image generation access, or any available image API. Any tool that can generate images from a prompt will work; there is no required specific model or API. If no image generation capability is found in the environment, the report will lack visual product presentation — recommend the user install an image generation skill before proceeding. **Timing**: Generate images ONLY after completing section 8 (Packaging Design) **Content Requirements**: - Each image must show BOTH product and packaging together - Generate 3 completely different design variations - Display all 3 images in a row for user selection **Image Prompt Requirements**: - Base prompts on completed packaging design content (section 8) - Emphasize packaging structure, visual elements, and consumption scenarios - Include product appearance, packaging form, materials, and brand presentation - If brand terms mentioned in concept, include them in prompts - Use professional visual art terminology: lighting, composition, texture, color harmony - Prohibited: politics/religion/vulgar/gambling/infringement/violence **Technical Requirements**: - Limit max width to 100% using Tailwind CSS `max-w-full` or inline style - Ensure responsive display across devices - Each image needs explanatory text about relevance to research content 【Technical Implementation】 - Use Tailwind CSS for responsive layouts - Optimize layouts for different screen sizes - All styles and content should be contained wi
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.