Minu Portal Skill

Generate static landing pages for Next.js 15 App Router sites with SEO metadata.

Updated Nov 27, 2025
One-click install
npx skills add https://github.com/IDEA-on-Action/Minu-Shared --skill minu-portal-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Minu Portal Skill
Source: https://github.com/IDEA-on-Action/Minu-Shared/tree/main/claude-skills/minu-portal
Command: npx skills add https://github.com/IDEA-on-Action/Minu-Shared --skill minu-portal-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing a marketing website that needs to be fast, scalable, and easily discoverable by search engines can be complex. This skill outlines the architecture for Minu's static, SEO-optimized landing page, ensuring high performance and effective outreach.

Core Features & Use Cases

  • High-Performance Static Site Generation (SSG): Built with Next.js 15 and output: 'export' for lightning-fast load times and cost-effective static hosting.
  • Comprehensive Service Overview: Dedicated pages for each Minu service (Find, Frame, Build, Keep) to clearly introduce their value propositions.
  • Robust SEO Configuration: Includes generateMetadata, robots.txt, and sitemap.xml to ensure maximum visibility and discoverability on search engines.
  • Streamlined Deployment Workflow: Utilizes a main/canary branch strategy with Vercel for efficient and reliable deployments.
  • Use Case: Quickly update the marketing content for Minu services or add a new service detail page, knowing it will be deployed as a highly performant, SEO-friendly static site that effectively communicates Minu's offerings.

Quick Start

How do I add a new service detail page to the Minu Portal, ensuring it's SEO-optimized with correct metadata and sitemap entry?

Frequently Asked Questions about Minu Portal Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a static marketing website with Next.js that's optimized for search engines?

Static site generation with Next.js 15 using `output: 'export'` creates fast, SEO-optimized landing pages. Configure `generateMetadata` for page-level SEO, include `robots.txt` and `sitemap.xml`, and use `generateStaticParams` to pre-render all routes at build time for maximum search visibility.

Can I add a new service page to a Next.js static site and have it automatically indexed by search engines?

Yes. Create a new route with `generateStaticParams` to pre-render it and `generateMetadata` to set SEO tags. The static export automatically generates an updated `sitemap.xml`, ensuring search engines discover and index the new service page during the next deployment.

What's the difference between static site generation and server-side rendering for a marketing website?

Static site generation (SSG) pre-renders pages at build time, delivering faster load speeds and lower hosting costs—ideal for marketing sites with stable content. Server-side rendering generates pages on request, adding latency and server overhead; it's unnecessary for marketing content that doesn't require real-time personalization.

Can I call external APIs in a statically exported Next.js site?

Yes, but only from client components. External API calls on the client execute in the browser after the page loads. Avoid API routes and server logic entirely; static export prohibits server-side functionality, so all dynamic data fetching must happen client-side or at build time.

Do I need server-side logic or API routes for a Next.js static marketing site?

No. Static export (`output: 'export'`) disallows server logic, API routes, and server components. All functionality must use client components, pre-rendered static pages, and client-side external API calls. This constraint enforces a pure static deployment suitable for cost-effective, scalable hosting.

How do I deploy a static Next.js site with continuous updates to marketing content?

Use a main/canary branch strategy with Vercel. Commit content changes to a branch, trigger a preview deployment to test SEO and rendering, then merge to main for production. Vercel rebuilds and re-exports all static pages, updating metadata and sitemaps automatically.