메뉴
Use when editing Rocket Pages, config, layouts, component reference Pages, or build behavior in this project.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | rocket |
| description | Use when editing Rocket Pages, config, layouts, component reference Pages, or build behavior in this project. |
rocket-config.js first; Page discovery follows includeGlobs.config.path; put general docs in docs/pages and component docs next to the component.js demo when readers benefit from trying the UI.atlasDocLayout for docs, atlasHeroLayout for a standalone docs home, with matching components exports.components export; use Atlas component maps or rocketDemoComponents.menu.iconName to Atlas docs navigation Pages so the left navigation has icons.stylesheets and centralized CSS variables instead of per-Page style injection.docs/pages/name.rocket.md, set config.path, metadata, menu.iconName, and use the shared docs layout.rocket-icon need addBootstrapIconLibrary(pageData) before document().render: 'server'.js demo, verify the parent Page and Standalone Demo URL /page/_demo/demoName/.rocket init fails because package.json has "type": "commonjs", change it to "type": "module" or rerun npx rocket init --yes.EMFILE, run npm start -- --no-watch --no-open and use Ctrl+R for manual restarts.Accept: text/html: curl -H 'Accept: text/html' http://localhost:8888/path.npm run build passing; record Rocket package issues separately from local workarounds.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.
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.
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.
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.