Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

rasengan-optimizing

Étoiles120

Forks8

Mis à jour6 juin 2026 à 23:30

Optimization patterns for Rasengan.js. Covers static assets via the public/ directory, asset handling best practices, and performance optimization. Use when managing static files, serving assets, or optimizing resource delivery in a Rasengan.js project.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

rasengan-dev

rasengan-dev/rasenganjs

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	rasengan-optimizing
description	Optimization patterns for Rasengan.js. Covers static assets via the public/ directory, asset handling best practices, and performance optimization. Use when managing static files, serving assets, or optimizing resource delivery in a Rasengan.js project.
license	MIT
metadata	{"author":"dilane3","framework":"rasengan","version":"1.0.0"}

Rasengan.js Optimization Patterns

When to Activate

Serving static files (images, fonts, icons) from the public/ directory
Referencing assets in components or templates
Optimizing images and static resources for production
Configuring metadata for SEO (title, description, Open Graph, Twitter)
Enabling React Compiler via Sage Mode for automatic memoization

Static Assets — public/ Directory

Any file placed inside the public/ directory is automatically served at the base URL (/). No imports or special loaders needed.

File Placement

public/
├── favicon.ico
├── robots.txt
├── og-image.png
└── avatars/
    └── 1.png

Referencing in Code

// Public assets use root-relative paths
<img src="/avatars/1.png" alt="Avatar" />;

// With @rasenganjs/image
import { Image } from '@rasenganjs/image';
<Image src="/avatars/1.png" alt="Avatar" width={64} height={64} />;

// In the HTML template (src/template.tsx)
import { type TemplateProps } from 'rasengan';

export default function Template({ Head, Body, Script }: TemplateProps) {
  return (
    <html lang="en">
      <Head>
        <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
      </Head>
      <Body>
        <Script />
      </Body>
    </html>
  );
}

src/assets/ Directory

For assets that need bundling, transformation, or import-based references, use src/assets/ instead:

import logo from '@/assets/logo.svg';

function Header() {
  return <img src={logo} alt="Logo" />;
}

Metadata & SEO

SEO metadata is defined as a static property on page or layout components:

Home.metadata = {
  title: 'Home',
  description: 'Home page description',
  openGraph: {
    title: 'Home',
    description: 'Home page',
    url: 'https://example.com',
    image: 'https://example.com/og.png',
  },
  twitter: {
    card: 'summary_large_image',
    image: 'https://example.com/twitter.png',
    title: 'Home',
  },
};

Rules:

Page metadata takes priority over layout metadata (merged, page wins)
Loader-returned meta overrides static metadata at runtime
openGraph.url and openGraph.image are required when using Open Graph
twitter.card, twitter.image, twitter.title are required when using Twitter cards

React Compiler (Sage Mode)

Enable automatic memoization in rasengan.config.js:

export default defineConfig({
  sageMode: {
    reactCompiler: true, // auto-memoize all components
    // reactCompiler: { compilationMode: 'annotation' }, // only components with "use memo"
  },
});

true — applies React Compiler to all components automatically
{ compilationMode: 'annotation' } — only compiles components with a "use memo" directive

Bundle Optimization

Build output structure:

dist/
  client/        # Client bundle + manifest.json
    assets/      # JS, CSS, config.json
    .vite/       # Vite manifest
  server/        # SSR server bundle
static/          # Pre-rendered HTML (SSG)

Rules

Use public/ for assets that need a fixed URL path (favicon, robots.txt, og-images)
Use src/assets/ for assets that benefit from bundling, hashing, and import references
Always provide width and height on images to prevent Cumulative Layout Shift (CLS)
Place SEO-critical images (Open Graph, Twitter cards) in public/ for stable URLs
Enable sageMode.reactCompiler to reduce unnecessary re-renders in production
The public/ directory contents are copied as-is during build (no transformation)

Plus depuis ce dépôt

même dépôt

rasengan-config

rasengan-dev/rasenganjs

Project configuration and rendering mode patterns for Rasengan.js. Covers rasengan.config.js, AppConfig interface, SSR/SSG/SPA modes, CLI commands, build output, Vite overrides, TypeScript setup, environment variables, module aliases, and styling (CSS Modules, Tailwind, preprocessors). Use when configuring a Rasengan.js project or switching rendering strategies.

2026-06-06120

rasengan-data-fetching

rasengan-dev/rasenganjs

Data fetching and SSG static path patterns for Rasengan.js. Covers LoaderFunction, route-level data fetching with params/request, loader return types (props, redirect, meta, source), defineStaticPaths, and generatePaths for SSG. Use when adding loaders to pages, generating static paths for prerendered dynamic routes, or handling data loading states.

2026-06-06120

rasengan-deployment

rasengan-dev/rasenganjs

Deployment patterns for Rasengan.js. Covers Vercel deployment with @rasenganjs/vercel adapter and self-hosting on Node.js with @rasenganjs/serve. Use when deploying a Rasengan.js application to production.

2026-06-06120

rasengan-ecosystem

rasengan-dev/rasenganjs

Rasengan.js ecosystem package patterns. Covers @rasenganjs/kurama (state management), @rasenganjs/image (optimized images), @rasenganjs/theme (light/dark/system), @rasenganjs/i18n (internationalization), @rasenganjs/kage-demo (guided tours), and @rasenganjs/mdx (MDX content). Use when integrating ecosystem packages into a Rasengan.js project.

2026-06-06120

rasengan-pages

rasengan-dev/rasenganjs

Page and layout component patterns for Rasengan.js. Covers page components, layouts, metadata, MDX pages, entry point setup, HTML template, navigation, error boundaries, and 404 handling. Use when creating or modifying .page.tsx, .page.mdx, layout.tsx, main.tsx, template.tsx, or index.ts files.

2026-06-06120

rasengan-project-setup

rasengan-dev/rasenganjs

Project setup and scaffolding patterns for Rasengan.js. Covers create-rasengan CLI, manual installation, required project files and directories, TypeScript configuration, and project structure conventions. Use when starting a new Rasengan.js project or understanding the required file structure.

2026-06-06120

name	rasengan-optimizing
description	Optimization patterns for Rasengan.js. Covers static assets via the public/ directory, asset handling best practices, and performance optimization. Use when managing static files, serving assets, or optimizing resource delivery in a Rasengan.js project.
license	MIT
metadata	{"author":"dilane3","framework":"rasengan","version":"1.0.0"}

Rasengan.js Optimization Patterns

When to Activate

Serving static files (images, fonts, icons) from the public/ directory
Referencing assets in components or templates
Optimizing images and static resources for production
Configuring metadata for SEO (title, description, Open Graph, Twitter)
Enabling React Compiler via Sage Mode for automatic memoization

Static Assets — public/ Directory

Any file placed inside the public/ directory is automatically served at the base URL (/). No imports or special loaders needed.

File Placement

public/
├── favicon.ico
├── robots.txt
├── og-image.png
└── avatars/
    └── 1.png

Referencing in Code

// Public assets use root-relative paths
<img src="/avatars/1.png" alt="Avatar" />;

// With @rasenganjs/image
import { Image } from '@rasenganjs/image';
<Image src="/avatars/1.png" alt="Avatar" width={64} height={64} />;

// In the HTML template (src/template.tsx)
import { type TemplateProps } from 'rasengan';

export default function Template({ Head, Body, Script }: TemplateProps) {
  return (
    <html lang="en">
      <Head>
        <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
      </Head>
      <Body>
        <Script />
      </Body>
    </html>
  );
}

src/assets/ Directory

For assets that need bundling, transformation, or import-based references, use src/assets/ instead:

import logo from '@/assets/logo.svg';

function Header() {
  return <img src={logo} alt="Logo" />;
}

Metadata & SEO

SEO metadata is defined as a static property on page or layout components:

Home.metadata = {
  title: 'Home',
  description: 'Home page description',
  openGraph: {
    title: 'Home',
    description: 'Home page',
    url: 'https://example.com',
    image: 'https://example.com/og.png',
  },
  twitter: {
    card: 'summary_large_image',
    image: 'https://example.com/twitter.png',
    title: 'Home',
  },
};

Rules:

Page metadata takes priority over layout metadata (merged, page wins)
Loader-returned meta overrides static metadata at runtime
openGraph.url and openGraph.image are required when using Open Graph
twitter.card, twitter.image, twitter.title are required when using Twitter cards

React Compiler (Sage Mode)

Enable automatic memoization in rasengan.config.js:

export default defineConfig({
  sageMode: {
    reactCompiler: true, // auto-memoize all components
    // reactCompiler: { compilationMode: 'annotation' }, // only components with "use memo"
  },
});

true — applies React Compiler to all components automatically
{ compilationMode: 'annotation' } — only compiles components with a "use memo" directive

Bundle Optimization

Build output structure:

dist/
  client/        # Client bundle + manifest.json
    assets/      # JS, CSS, config.json
    .vite/       # Vite manifest
  server/        # SSR server bundle
static/          # Pre-rendered HTML (SSG)

Rules

Use public/ for assets that need a fixed URL path (favicon, robots.txt, og-images)
Use src/assets/ for assets that benefit from bundling, hashing, and import references
Always provide width and height on images to prevent Cumulative Layout Shift (CLS)
Place SEO-critical images (Open Graph, Twitter cards) in public/ for stable URLs
Enable sageMode.reactCompiler to reduce unnecessary re-renders in production
The public/ directory contents are copied as-is during build (no transformation)