froggugugugu

This skill should be used when the user asks to "audit design tokens", "unify spacing", "standardize typography", or mentions "デザイントークン", "余白統一", "デザインがバラバラ", "比率", "デザイン整合性監査". Validates design tokens (spacing, typography, color) against ratio principles…

This skill should be used when the user asks to "refine the harness", "self-improve the blueprint", "restructure .claude/ to match best practices", "audit harness configuration", or mentions "ハーネス補正", "ベストプラクティス準拠", "self-refine", "セルフリファイン", "ハーネス自己点検",…

This skill should be used when the user asks to "check HIG compliance", "unify button labels", "fix icon consistency", or mentions "HIG準拠", "UI一貫性", "ボタン統一", "アイコン統一", "用語統一", "画面間の整合性", "横断UIチェック". Apple Human Interface Guidelines (HIG) based system-wide UI…

This skill should be used when the user asks to "run security scan", "check vulnerabilities", "audit dependencies", or mentions "セキュリティスキャン", "脆弱性", "OWASP", "npm audit", "シークレット検出", "CVE". Source-code read-only — never modifies source code or test files.…

This skill should be used when the user asks to "review UI design", "improve styling", "add dark mode", "fix accessibility", "make responsive", or mentions "デザインレビュー", "UI改善", "デザイン整合性". Covers visual consistency, design system compliance, accessibility,…

This skill should be used when the user asks to "audit design tokens", "unify spacing", "standardize typography", or mentions "design tokens", "spacing inconsistency", "design is inconsistent", "ratio", "design consistency audit". Validates design tokens…

This skill should be used when the user asks to "refine the harness", "self-improve the blueprint", "restructure .claude/ to match best practices", "audit harness configuration", or mentions "harness refine", "best-practice alignment", "self-refine", "harness…

This skill should be used when the user asks to "check HIG compliance", "unify button labels", "fix icon consistency", or mentions "HIG compliance", "UI consistency", "button unification", "icon unification", "terminology unification", "cross-screen…

This skill should be used when the user asks to "review code", "check code quality", "validate changes", or mentions "コードレビュー", "品質チェック", "レビュー". Source-code read-only — never modifies source code or test files. Outputs review report to output/reports/review/…

This skill should be used when the user asks to "create E2E tests", "write scenario tests", "test user flow", or mentions "E2Eテスト", "シナリオテスト", "Playwright". Creates and maintains Playwright E2E tests. Covers Page Object design, test data management, stability…

This skill should be used when the user asks to "implement a feature", "fix a bug", "create a component", or mentions "実装", "機能追加", "バグ修正", "コンポーネント作成". Follows TDD workflow. Covers components, stores, schemas, utilities, styling, docs/ and project-config.md…

This skill should be used when the user asks to "plan implementation", "decompose tasks", "analyze impact", or mentions "設計", "タスク分解", "影響分析". Source-code read-only — never modifies source code or test files. Outputs structured plan to output/tasks/ (requires…

This skill should be used when the user asks to "review UI design", "improve styling", "add dark mode", "fix accessibility", "make responsive", or mentions "デザインレビュー", "UI改善", "デザイン整合性". Covers visual consistency, design system compliance, accessibility,…

「設計判断を記録して」「ADRを作成して」「アーキテクチャ決定を記録して」などの依頼、 または「ADR」「設計判断記録」「アーキテクチャ決定記録」「設計の経緯」「なぜこの設計にしたか」 というキーワードが含まれる場合にこのスキルを使用する。 Architecture Decision Records (ADR) を作成・管理し、設計判断のコンテキスト・根拠・影響を記録する。 引数は省略可能: /adr <判断タイトル or 指示>

This skill should be used when the user asks to "design architecture", "create system design", or mentions "アーキテクチャ", "システム設計", "構成設計", "レイヤー設計". Source-code read-only — never modifies source code or test files. Outputs structured architecture document to…

曖昧な要求メモから前提を Socratic 質問で炙り出す `/prd` 前段スキル。ブレスト・前提整理・質問駆動・曖昧さ・想定外・pre-prd で起動。読取専用、出力は `output/brainstorm/` のみ。

Designs system architecture from Japanese requirement notes and generates architecture.md. Triggers: architecture, アーキテクチャ, システム設計, 構成設計, レイヤー設計. Source-code read-only — never modifies source code or test files. Outputs structured architecture document to…

Reviews code changes for quality, conventions compliance, performance, and security. Triggers: review, check, validate, inspect, audit code quality. Source-code read-only — never modifies source code or test files. Outputs review report to…

Creates and maintains Playwright E2E tests for SPAs. Triggers: E2E test, scenario test, user flow, cross-feature, Playwright. Covers: Page Object design, test data management, stability patterns, and reporting. Takes optional argument: /e2e-testing…

Implements features, fixes bugs, and refactors code following TDD workflow. Triggers: implement, create, fix, modify, add, refactor, build, develop, change functionality. Covers: components, stores, schemas, utilities, styling, docs/ and project-config.md…

Reviews code, documents, and configurations for IT legal compliance. Triggers: legal, license, compliance, privacy, GDPR, copyright, terms, contract, OSS license, intellectual property, data protection. Source-code read-only — never modifies source code or…

Measures and optimizes application performance using a measurement-first approach. Triggers: performance, optimize, slow, bundle size, re-render, memory, profiler, lazy load, memoize. Covers: bundle optimization, rendering, state management, memory/storage…

Generates design documents and task breakdowns for feature implementation. Triggers: plan, design, decompose, analyze impact, task breakdown. Source-code read-only — never modifies source code or test files. Outputs structured plan to output/tasks/ (requires…

Generates a PRD (Product Requirements Document) from Japanese requirement notes or memos. Triggers: prd, requirements, 要件定義, PRD作成, 要求仕様. Source-code read-only — never modifies source code or test files. Outputs structured PRD to output/prd/ (requires Write…

意匠(美的センス)を扱う横断スキル。利用者の自然言語要求(「未来感を出したい」「ファンシーに」「角を丸めて」「ヘキサ柄を表面に」「アニメ ○○ のイメージで」)を case-config.yaml の `style:` セクションに翻訳する。/design 前後どちらでも呼べる。

段階 2-3 — input/objects/*.yaml と project-config.yaml を統合し、case-spec.yaml(ケース全体仕様)を生成。続いて CadQuery の generator.py と validator.py を出力し、STEP/STL に書き出す。

ケース設計プロジェクトを進行するプロジェクトリード(PdM 相当)。5 段階ワークフロー(measure / design / review-fix / fit-check / export)+ 横断スキル(hinged-lid 機構特化、style 意匠)を統合し、現状把握 → 次の一手の提示 → skill 起動 を反復する。利用者の意図を都度確認し、方針転換を柔軟に受け入れる。

段階 4-5 の橋渡し — パーツ間の嵌合・接合面・蝶番組合せの干渉/クリアランスを点検する。リップ嵌合、蝶番ナックル組み合わせ、ねじ穴・差し込み・スナップ等の突合機構を CAD 干渉解析+ルールベースで検証。

段階 5 — 確定済みの設計から最終プリント用 STL/3MF を出力し、スライサー設定の推奨を slicer-notes.md に記述する。

段階 1 — ケースに収納するオブジェクトを対話的に採寸し、input/objects/<id>.yaml に 1 ファイル 1 オブジェクトで保存する。座標軸と「正面」の基準を提示してから採寸を促す。

段階 4 — 可視化レビューループ。利用者からのフィードバック(自然言語 or YAML 直接編集)を取り込み、case-spec.yaml / case-config.yaml / generator.py を更新して再実行する。

ヒンジ蓋ケース特化スキル(機構特化・横断)— 軸ピン+レバー式ラッチの3部品構成(本体/蓋/レバー)。M2 ピン+ねじの長尺セットをデフォルトに、`hardware:` プリセット差替えで幅狭ラッチ・別径構成にも転用可。`/design` 確定後の closure 詳細を埋める。

Reviews code changes for quality, conventions compliance, performance, and security. Applies when the user asks to review code, check implementation quality, or validate changes against project standards. Read-only — never modifies source code.

Creates and maintains Playwright E2E tests for React SPAs. Applies when the user asks to write E2E tests, create scenario tests, automate user flows, or verify cross-feature behavior. Covers Page Object design, test data management, stability patterns, and…

Implements features, fixes bugs, and refactors code following TDD workflow. Triggers: implement, create, fix, modify, add, refactor, build, develop, change functionality. Covers: components, stores, schemas, utilities, styling, and docs/ synchronization.

Generates design documents and task breakdowns for feature implementation. Triggers: plan, design, decompose, analyze impact, task breakdown. Read-only — never modifies source code. Outputs a structured plan for human review.

Launches an agent team with a task file. Usage: /team <task-file> [task-file2 ...] [--lang en] Example: /team TASK_SDD.md Example: /team TASK_REVIEW01.md TASK_REVIEW02.md

Reviews and implements UI/UX following project design systems. Triggers: design review, UI improvement, styling, accessibility, dark mode, responsive, layout, component design. Covers: visual consistency, design system compliance, accessibility, responsive…