メニュー
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate ASCII block-art banner images for social posts and OG images. Dark midnight aesthetic with faded {company} text on near-black background. Two sizes — 1080x1080 (social) and 1200x630 (OG). Use for product announcements, project launches, concept visuals, and repo OG images.
Explore approaches and tradeoffs before committing to a PRD. Research HQ context, compare options, surface unknowns, generate brainstorm.md with recommendation.
Post-ship documentation sync — updates README, CLAUDE.md, architecture docs, and INDEX files to match what actually shipped. Use after merging a PR, completing a project, or deploying a release. Triggers on "update docs", "sync documentation", "docs are stale", "document what shipped".
Execute a single PRD story through coordinated worker phases (Ralph pattern). Each worker handles its domain, passes context to the next, with back-pressure (tests/lint/typecheck) keeping code on rails.
Prepare for a new session to continue this work. Captures session learnings, syncs domain knowledge and insights, commits dirty repos, writes a thread file and handoff.json, updates INDEX files, and refreshes the search index. Ensures continuity across sessions.
Capture and classify learnings, route to structured policy files (rules) or insight files (educational knowledge). Deduplicates via qmd (Grep fallback), rebuilds policy digest after policy changes. Callable manually or from /execute-task, /run-project, /handoff, /checkpoint. Use --hard flag for hard-enforcement rules.
| name | adapt |
| description | Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments. |
| user-invokable | true |
| args | [{"name":"target","description":"The feature or component to adapt (optional)","required":false},{"name":"context","description":"What to adapt for (mobile, tablet, desktop, print, email, etc.)","required":false}] |
Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases.
Use the frontend-design skill — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first. Additionally gather: target platforms/devices and usage contexts.
Understand what needs adaptation and why:
Identify the source context:
Understand target context:
Identify adaptation challenges:
CRITICAL: Adaptation is not just scaling - it's rethinking the experience for the new context.
Create context-appropriate strategy:
Layout Strategy:
Interaction Strategy:
Content Strategy:
Navigation Strategy:
Layout Strategy:
Interaction Strategy:
Layout Strategy:
Interaction Strategy:
Content Strategy:
Layout Strategy:
Content Strategy:
Layout Strategy:
Interaction Strategy:
Apply changes systematically:
Choose appropriate breakpoints:
clamp(): Fluid sizing between min and maxdisplay: none sparingly (still downloads)srcset, picture element)IMPORTANT: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect.
NEVER:
Test thoroughly across contexts:
Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly.