メニュー
Diagnose layout issues in Gridland components. Spawns the layout-debugger agent with the relevant component. Use when a component renders incorrectly or layout looks wrong.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Guide for creating a new UI component in @gridland/ui. Covers file structure, focus integration, keyboard handling, theme usage, JSDoc, export registration, and documentation.
Review a component for production readiness as a UI framework. Assesses code quality, patterns, tests, docs, and API design. Produces a prioritized fix plan. Use before shipping a new or updated component to users.
Update context files to reflect current codebase state — new components, changed APIs, new patterns, and reasoning behind non-obvious decisions. Routes updates to the correct file based on what changed. Run after any significant design change before committing.
Audit the browser rendering pipeline for scissor/clipping bypass bugs. Use when touching browser-buffer.ts, canvas-painter.ts, or adding new visual features.
Pre-release checklist. Runs all 4 agents plus snapshot regression test, TypeScript check, and semver confirmation. Run before publishing a new package version.
Documentation-focused review. Runs docs-mirror and dependency-auditor in parallel. Use after writing or updating documentation, demo components, or MDX pages.
| name | debug-layout |
| description | Diagnose layout issues in Gridland components. Spawns the layout-debugger agent with the relevant component. Use when a component renders incorrectly or layout looks wrong. |
Diagnose layout issues in a Gridland component.
If $ARGUMENTS provided, find the component file matching the argument (component name or file path).
If no argument, ask which component has the layout issue.
Read the component file to understand its JSX structure.
Spawn the layout-debugger agent with the component file path and a description of the visual problem.
Present the diagnosis: what's wrong, why, and how to fix it.
Suggest running bun run demo <component-name> to visually verify the fix.
