ワンクリックでManusで任意のスキルを実行

始める

rocket

スター392

フォーク52

更新日2026年6月6日 23:13

Use when editing Rocket Pages, config, layouts, component reference Pages, or build behavior in this project.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

modernweb-dev

modernweb-dev/rocket

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Rocket

Rules

Read rocket-config.js first; Page discovery follows includeGlobs.
Every Page owns its URL through config.path; put general docs in docs/pages and component docs next to the component.
Prefer Markdown for durable content; use JavaScript Pages for request-time or programmatic output.
Prefer interactive examples for component and behavior docs; use js demo when readers benefit from trying the UI.
Prefer Atlas docs layouts: atlasDocLayout for docs, atlasHeroLayout for a standalone docs home, with matching components exports.
Markdown using Rocket custom elements needs a components export; use Atlas component maps or rocketDemoComponents.
Add menu.iconName to Atlas docs navigation Pages so the left navigation has icons.
Direct layout re-exports are supported when no local wrapper function is needed.
For Atlas theming, use shared layout data with stylesheets and centralized CSS variables instead of per-Page style injection.
To add a general Page, create docs/pages/name.rocket.md, set config.path, metadata, menu.iconName, and use the shared docs layout.
Custom layouts rendering rocket-icon need addBootstrapIconLibrary(pageData) before document().
Static JavaScript Pages render once per concrete path; query/header/cookie/live-data output needs render: 'server'.
Static Request Demos should target concrete non-query URLs.
After adding a js demo, verify the parent Page and Standalone Demo URL /page/_demo/demoName/.
If rocket init fails because package.json has "type": "commonjs", change it to "type": "module" or rerun npx rocket init --yes.
If dev server watchers fail with EMFILE, run npm start -- --no-watch --no-open and use Ctrl+R for manual restarts.
When smoke-testing Pages with curl, send Accept: text/html: curl -H 'Accept: text/html' http://localhost:8888/path.
Keep npm run build passing; record Rocket package issues separately from local workarounds.

このリポジトリの他の Skills

同じリポジトリ

coding-style

modernweb-dev/rocket

Indexes this repo's coding conventions for file placement, tests, API shape, component authoring, and commit messages. Use when creating or editing source files, adding tests, designing function signatures, creating components, or writing commits in this repo.

2026-06-06392

docs-to-types

modernweb-dev/rocket

Converts grill-with-docs output — CONTEXT.md glossaries, ADRs, and approved domain decisions — into typed architecture. Use after grill-with-docs when the user wants domain types, seams, adapters, errors, call stacks, and dependency rules expressed in code before business behavior.

2026-06-06392

modern-web-guidance

modernweb-dev/rocket

Search tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip — web APIs evolve rapidly and training weights contain obsolete patterns. Trigger immediately for: - UI/Layout: Modals, dialogs, popovers, Glassmorphism/backdrop-filters, anchor positioning, container queries, `:has()`, `:user-valid`. - Scroll/Motion: View Transitions, Scroll-driven animations, scroll parallax/reveals. - Performance: CWV (LCP, INP), content-visibility, Fetch Priority, image optimization. - System/APIs: Local filesystem access, WebUSB, WebSockets sync, WebAssembly widgets. - Frameworks: Adapting layout/styles in React, Vue, Angular. - General Frontend: Forms, autofill, advanced inputs, custom scrollbars, modern component states, etc. DO NOT trigger for: - Backend: Database SQL, ORMs, Express API routes. - Pipelines: CI/CD deployment, Docker, Actions. - Generic: Local scripts (Python/Go tools), ESLint, Git.

2026-06-06392

to-prd

modernweb-dev/rocket

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

2026-06-06392

Rocket

Rules

Read rocket-config.js first; Page discovery follows includeGlobs.

Every Page owns its URL through config.path; put general docs in docs/pages and component docs next to the component.

Prefer Markdown for durable content; use JavaScript Pages for request-time or programmatic output.

Prefer interactive examples for component and behavior docs; use js demo when readers benefit from trying the UI.

Prefer Atlas docs layouts: atlasDocLayout for docs, atlasHeroLayout for a standalone docs home, with matching components exports.

Markdown using Rocket custom elements needs a components export; use Atlas component maps or rocketDemoComponents.

Add menu.iconName to Atlas docs navigation Pages so the left navigation has icons.

Direct layout re-exports are supported when no local wrapper function is needed.

For Atlas theming, use shared layout data with stylesheets and centralized CSS variables instead of per-Page style injection.

To add a general Page, create docs/pages/name.rocket.md, set config.path, metadata, menu.iconName, and use the shared docs layout.

Custom layouts rendering rocket-icon need addBootstrapIconLibrary(pageData) before document().

Static JavaScript Pages render once per concrete path; query/header/cookie/live-data output needs render: 'server'.

Static Request Demos should target concrete non-query URLs.

After adding a js demo, verify the parent Page and Standalone Demo URL /page/_demo/demoName/.

If rocket init fails because package.json has "type": "commonjs", change it to "type": "module" or rerun npx rocket init --yes.

If dev server watchers fail with EMFILE, run npm start -- --no-watch --no-open and use Ctrl+R for manual restarts.

When smoke-testing Pages with curl, send Accept: text/html: curl -H 'Accept: text/html' http://localhost:8888/path.

Keep npm run build passing; record Rocket package issues separately from local workarounds.

name	rocket
description	Use when editing Rocket Pages, config, layouts, component reference Pages, or build behavior in this project.