@rankcli/agent-runtime 0.0.14 → 0.0.16

package/src/frameworks/recipes/laravel.yaml

@@ -1,137 +0,0 @@
-# Laravel SEO Recipe
-# Laravel is the most popular PHP framework
-
-framework: laravel
-display_name: Laravel
-category: server-rendered
-ssr_default: true
-
-seo_strengths:
-  - "Server-rendered HTML by default"
-  - "Blade templates for clean SEO markup"
-  - "Route caching for fast responses"
-  - "Built-in CSRF and security"
-
-checks:
-  - code: LARAVEL_NO_META_PACKAGE
-    severity: warning
-    title: "No SEO package detected"
-    description: "Laravel benefits from an SEO package like artesaos/seotools."
-    howToFix: |
-      Install artesaos/seotools:
-
-      ```bash
-      composer require artesaos/seotools
-      ```
-
-      ```php
-      // In controller
-      use Artesaos\SEOTools\Facades\SEOMeta;
-
-      SEOMeta::setTitle('Page Title');
-      SEOMeta::setDescription('Description');
-
-      // In Blade
-      {!! SEOMeta::generate() !!}
-      ```
-
-  - code: LARAVEL_NO_SITEMAP
-    severity: warning
-    title: "No sitemap package detected"
-    description: "Use spatie/laravel-sitemap for automatic sitemaps."
-    howToFix: |
-      ```bash
-      composer require spatie/laravel-sitemap
-      ```
-
-      ```php
-      // Generate sitemap
-      use Spatie\Sitemap\SitemapGenerator;
-
-      SitemapGenerator::create('https://yoursite.com')
-          ->writeToFile(public_path('sitemap.xml'));
-
-      // Or build manually
-      use Spatie\Sitemap\Sitemap;
-      use Spatie\Sitemap\Tags\Url;
-
-      Sitemap::create()
-          ->add(Url::create('/')->setPriority(1.0))
-          ->add(Url::create('/about'))
-          ->writeToFile(public_path('sitemap.xml'));
-      ```
-
-  - code: LARAVEL_INERTIA_NO_SSR
-    severity: error
-    title: "Inertia.js without SSR"
-    description: "Inertia apps are client-rendered by default, losing SEO benefits."
-    howToFix: |
-      Enable Inertia SSR:
-
-      ```bash
-      php artisan inertia:start-ssr
-      ```
-
-      Configure in config/inertia.php:
-      ```php
-      'ssr' => [
-          'enabled' => true,
-          'url' => 'http://127.0.0.1:13714',
-      ],
-      ```
-
-  - code: LARAVEL_NO_RESPONSE_CACHE
-    severity: notice
-    title: "Response caching not configured"
-    description: "Cache full responses for better performance."
-    howToFix: |
-      Install spatie/laravel-responsecache:
-
-      ```bash
-      composer require spatie/laravel-responsecache
-      ```
-
-      Add middleware:
-      ```php
-      // app/Http/Kernel.php
-      protected $middlewareGroups = [
-          'web' => [
-              \Spatie\ResponseCache\Middlewares\CacheResponse::class,
-          ],
-      ];
-      ```
-
-  - code: LARAVEL_LIVEWIRE_SEO
-    severity: warning
-    title: "Livewire components may affect SEO"
-    description: "Livewire content loads via JavaScript after initial page load."
-    howToFix: |
-      For SEO-critical content, use wire:init to load immediately:
-
-      ```blade
-      <div wire:init="loadData">
-          @if($data)
-              {{-- Content --}}
-          @else
-              {{-- Loading skeleton --}}
-          @endif
-      </div>
-      ```
-
-      Or use Alpine.js for client-only interactions.
-
-performance_tips:
-  - "Enable route caching: php artisan route:cache"
-  - "Enable config caching: php artisan config:cache"
-  - "Use query caching with remember()"
-  - "Optimize autoloader: composer dump-autoload -o"
-  - "Use Laravel Octane for high performance"
-
-recommended_packages:
-  seo:
-    - "artesaos/seotools - Meta tag management"
-    - "spatie/laravel-sitemap - Sitemap generation"
-    - "spatie/schema-org - Structured data"
-  performance:
-    - "spatie/laravel-responsecache - Full page caching"
-    - "barryvdh/laravel-debugbar - Development profiling"

package/src/frameworks/recipes/nextjs.yaml

@@ -1,268 +0,0 @@
-# Next.js SEO Recipe
-# Next.js has excellent SEO by default, but there are still common mistakes
-
-framework: nextjs
-display_name: Next.js
-category: meta-framework
-base_framework: react
-ssr_default: true
-
-seo_strengths:
-  - "Server-side rendering by default"
-  - "Static site generation support"
-  - "Built-in Image component with optimization"
-  - "Automatic code splitting"
-  - "File-based routing"
-  - "Built-in metadata API (App Router)"
-
-checks:
-  # App Router specific
-  - code: NEXTJS_NO_METADATA_API
-    severity: warning
-    title: "Not using Next.js Metadata API"
-    description: "Next.js 13+ has a built-in Metadata API that's better than react-helmet."
-    howToFix: |
-      Use the Metadata API in your layout or page:
-
-      ```tsx
-      // app/page.tsx
-      import { Metadata } from 'next';
-
-      export const metadata: Metadata = {
-        title: 'Page Title',
-        description: 'Page description',
-        openGraph: {
-          title: 'OG Title',
-          description: 'OG Description',
-          images: ['/og-image.jpg'],
-        },
-      };
-
-      // For dynamic metadata
-      export async function generateMetadata({ params }): Promise<Metadata> {
-        const product = await getProduct(params.id);
-        return {
-          title: product.name,
-          description: product.description,
-        };
-      }
-      ```
-    app_router_only: true
-
-  - code: NEXTJS_GENERATESTATICPARAMS_MISSING
-    severity: warning
-    title: "Dynamic routes without generateStaticParams"
-    description: "Dynamic routes like [id] should pre-generate static pages for SEO."
-    howToFix: |
-      Add generateStaticParams to pre-render dynamic pages:
-
-      ```tsx
-      // app/products/[id]/page.tsx
-      export async function generateStaticParams() {
-        const products = await getProducts();
-        return products.map((product) => ({
-          id: product.id.toString(),
-        }));
-      }
-      ```
-    app_router_only: true
-
-  # Pages Router specific
-  - code: NEXTJS_NO_GETSTATICPROPS
-    severity: warning
-    title: "Pages without getStaticProps/getServerSideProps"
-    description: "Pages fetching data client-side miss SEO benefits of SSR/SSG."
-    howToFix: |
-      Move data fetching to getStaticProps (for static) or getServerSideProps (for dynamic):
-
-      ```tsx
-      // pages/products.tsx
-      export async function getStaticProps() {
-        const products = await fetchProducts();
-        return {
-          props: { products },
-          revalidate: 3600, // ISR: regenerate every hour
-        };
-      }
-      ```
-    pages_router_only: true
-
-  # Common issues
-  - code: NEXTJS_IMAGE_NOT_USED
-    severity: warning
-    title: "Using <img> instead of next/image"
-    description: "The next/image component provides automatic optimization, lazy loading, and prevents CLS."
-    howToFix: |
-      Replace <img> with next/image:
-
-      ```tsx
-      import Image from 'next/image';
-
-      // Before
-      <img src="/hero.jpg" alt="Hero" />
-
-      // After
-      <Image
-        src="/hero.jpg"
-        alt="Hero"
-        width={1200}
-        height={630}
-        priority // for above-the-fold images
-      />
-      ```
-
-  - code: NEXTJS_NO_PRIORITY_IMAGE
-    severity: notice
-    title: "LCP image missing priority prop"
-    description: "The largest image above the fold should have priority={true} for faster LCP."
-    howToFix: |
-      Add priority to your hero/LCP image:
-
-      ```tsx
-      <Image
-        src="/hero.jpg"
-        alt="Hero"
-        width={1200}
-        height={630}
-        priority
-      />
-      ```
-
-  - code: NEXTJS_LINK_NO_PREFETCH
-    severity: notice
-    title: "Link without prefetch consideration"
-    description: "Next.js prefetches all links by default, which can waste bandwidth."
-    howToFix: |
-      Disable prefetch for less important links:
-
-      ```tsx
-      <Link href="/terms" prefetch={false}>
-        Terms of Service
-      </Link>
-      ```
-
-  - code: NEXTJS_NO_ROBOTS_TXT
-    severity: warning
-    title: "Missing robots.txt configuration"
-    description: "Next.js can generate robots.txt automatically."
-    howToFix: |
-      App Router - create app/robots.ts:
-      ```tsx
-      import { MetadataRoute } from 'next';
-
-      export default function robots(): MetadataRoute.Robots {
-        return {
-          rules: {
-            userAgent: '*',
-            allow: '/',
-            disallow: '/api/',
-          },
-          sitemap: 'https://yoursite.com/sitemap.xml',
-        };
-      }
-      ```
-
-      Pages Router - create public/robots.txt or use next-sitemap package.
-
-  - code: NEXTJS_NO_SITEMAP
-    severity: warning
-    title: "Missing sitemap configuration"
-    description: "Next.js can generate sitemaps automatically."
-    howToFix: |
-      App Router - create app/sitemap.ts:
-      ```tsx
-      import { MetadataRoute } from 'next';
-
-      export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
-        const products = await getProducts();
-
-        return [
-          { url: 'https://yoursite.com', lastModified: new Date() },
-          { url: 'https://yoursite.com/about', lastModified: new Date() },
-          ...products.map((product) => ({
-            url: `https://yoursite.com/products/${product.id}`,
-            lastModified: product.updatedAt,
-          })),
-        ];
-      }
-      ```
-
-  - code: NEXTJS_USE_CLIENT_OVERUSE
-    severity: warning
-    title: "Overusing 'use client' directive"
-    description: "Too many client components reduces SSR benefits."
-    howToFix: |
-      Keep 'use client' at the leaf level:
-
-      ```tsx
-      // Bad - entire page is client-rendered
-      'use client';
-      export default function Page() { ... }
-
-      // Good - only interactive parts are client
-      // page.tsx (Server Component)
-      import ClientButton from './ClientButton';
-      export default function Page() {
-        return <div>
-          <h1>Server rendered content</h1>
-          <ClientButton /> {/* Only this is client */}
-        </div>
-      }
-      ```
-
-  - code: NEXTJS_FONT_NOT_OPTIMIZED
-    severity: notice
-    title: "Not using next/font for fonts"
-    description: "next/font automatically optimizes fonts and prevents CLS."
-    howToFix: |
-      Use next/font for Google Fonts or local fonts:
-
-      ```tsx
-      import { Inter } from 'next/font/google';
-
-      const inter = Inter({ subsets: ['latin'] });
-
-      export default function RootLayout({ children }) {
-        return (
-          <html lang="en" className={inter.className}>
-            <body>{children}</body>
-          </html>
-        );
-      }
-      ```
-
-  - code: NEXTJS_NO_TRAILING_SLASH_CONFIG
-    severity: notice
-    title: "Inconsistent trailing slash handling"
-    description: "Inconsistent URLs can cause duplicate content issues."
-    howToFix: |
-      Configure trailingSlash in next.config.js:
-
-      ```js
-      module.exports = {
-        trailingSlash: true, // or false
-      };
-      ```
-
-performance_tips:
-  - "Use React Server Components for static content"
-  - "Add priority to LCP images"
-  - "Use next/font for fonts"
-  - "Enable ISR for frequently updated pages"
-  - "Use Route Handlers instead of API routes for server-only logic"
-
-structured_data:
-  - type: "JSON-LD in metadata"
-    example: |
-      ```tsx
-      export const metadata: Metadata = {
-        other: {
-          'script:ld+json': JSON.stringify({
-            '@context': 'https://schema.org',
-            '@type': 'Organization',
-            name: 'Your Company',
-            url: 'https://yoursite.com',
-          }),
-        },
-      };
-      ```

package/src/frameworks/recipes/nuxt.yaml

@@ -1,175 +0,0 @@
-# Nuxt SEO Recipe
-# Nuxt has excellent SEO capabilities, similar to Next.js for Vue
-
-framework: nuxt
-display_name: Nuxt
-category: meta-framework
-base_framework: vue
-ssr_default: true
-
-seo_strengths:
-  - "Universal rendering (SSR) by default"
-  - "Static site generation support"
-  - "Built-in useSeoMeta composable"
-  - "Automatic code splitting"
-  - "File-based routing"
-  - "NuxtImage for image optimization"
-
-checks:
-  - code: NUXT_NO_USESEOMETA
-    severity: warning
-    title: "Not using useSeoMeta composable"
-    description: "Nuxt 3 has built-in SEO meta composables that are cleaner than useHead."
-    howToFix: |
-      Use useSeoMeta for SEO tags:
-
-      ```vue
-      <script setup>
-      useSeoMeta({
-        title: 'Page Title',
-        description: 'Page description',
-        ogTitle: 'OG Title',
-        ogDescription: 'OG Description',
-        ogImage: '/og-image.jpg',
-        twitterCard: 'summary_large_image',
-      });
-      </script>
-      ```
-
-  - code: NUXT_USEFETCH_CLIENT_ONLY
-    severity: warning
-    title: "Data fetching only on client side"
-    description: "Using onMounted for data fetching bypasses SSR benefits."
-    howToFix: |
-      Use useFetch or useAsyncData instead:
-
-      ```vue
-      <script setup>
-      // Bad - client only
-      const data = ref(null);
-      onMounted(async () => {
-        data.value = await $fetch('/api/data');
-      });
-
-      // Good - SSR friendly
-      const { data } = await useFetch('/api/data');
-      </script>
-      ```
-
-  - code: NUXT_NO_NUXT_IMAGE
-    severity: warning
-    title: "Not using NuxtImage for images"
-    description: "@nuxt/image provides automatic optimization and responsive images."
-    howToFix: |
-      Install and use NuxtImage:
-
-      ```bash
-      npx nuxi module add image
-      ```
-
-      ```vue
-      <template>
-        <NuxtImg
-          src="/hero.jpg"
-          alt="Hero"
-          width="1200"
-          height="630"
-          preload
-        />
-      </template>
-      ```
-
-  - code: NUXT_NO_ROBOTS
-    severity: warning
-    title: "Missing robots.txt configuration"
-    description: "Use @nuxtjs/robots module for robots.txt."
-    howToFix: |
-      Install and configure robots module:
-
-      ```bash
-      npm install @nuxtjs/robots
-      ```
-
-      ```ts
-      // nuxt.config.ts
-      export default defineNuxtConfig({
-        modules: ['@nuxtjs/robots'],
-        robots: {
-          rules: [
-            { UserAgent: '*', Allow: '/' },
-            { UserAgent: '*', Disallow: '/api/' },
-          ],
-          sitemap: 'https://yoursite.com/sitemap.xml',
-        },
-      });
-      ```
-
-  - code: NUXT_NO_SITEMAP
-    severity: warning
-    title: "Missing sitemap configuration"
-    description: "Use @nuxtjs/sitemap module for automatic sitemap."
-    howToFix: |
-      Install sitemap module:
-
-      ```bash
-      npm install @nuxtjs/sitemap
-      ```
-
-      ```ts
-      // nuxt.config.ts
-      export default defineNuxtConfig({
-        modules: ['@nuxtjs/sitemap'],
-        sitemap: {
-          hostname: 'https://yoursite.com',
-        },
-      });
-      ```
-
-  - code: NUXT_SPA_MODE
-    severity: error
-    title: "Nuxt running in SPA mode"
-    description: "SPA mode disables SSR, losing SEO benefits."
-    howToFix: |
-      Remove ssr: false from nuxt.config.ts:
-
-      ```ts
-      export default defineNuxtConfig({
-        // Remove this line
-        // ssr: false,
-      });
-      ```
-
-      If you need client-only components, use <ClientOnly>:
-      ```vue
-      <ClientOnly>
-        <BrowserOnlyWidget />
-      </ClientOnly>
-      ```
-
-  - code: NUXT_NO_PRERENDER
-    severity: notice
-    title: "Static pages not pre-rendered"
-    description: "Static pages could be pre-rendered for better performance."
-    howToFix: |
-      Enable route prerendering in nuxt.config.ts:
-
-      ```ts
-      export default defineNuxtConfig({
-        routeRules: {
-          '/about': { prerender: true },
-          '/blog/**': { prerender: true },
-        },
-      });
-      ```
-
-      Or generate a fully static site:
-      ```bash
-      nuxt generate
-      ```
-
-performance_tips:
-  - "Use useLazyFetch for non-critical data"
-  - "Add preload prop to NuxtImg for LCP images"
-  - "Use Nuxt DevTools to identify performance issues"
-  - "Configure image provider for CDN delivery"
-  - "Use route rules for caching strategies"