skills/applying-frontend-patterns/SKILL.md
Framework-agnostic frontend component design patterns. Use when: component patterns, Container/Presentational, フロントエンドパターン, コンポーネント設計.
npx skillsauth add thkt/dotclaude applying-frontend-patternsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Pattern | When to Use | | ------------------------ | ----------------------- | | Container/Presentational | Data fetching + display | | Custom Hooks | Shared behavior | | Composition | Flexible components | | State Management | Local → Shared → Global |
| Container (Logic) | Presentational (UI) | | ----------------- | ----------------------- | | Fetches data | Receives data via props | | Manages state | Stateless (ideally) | | Handles events | Calls callback props | | No styling | All styling lives here |
| Scope | Tool | Example | | ------ | ------------- | ------------------ | | Local | useState | Form input, toggle | | Shared | Context | Theme, auth status | | Global | Zustand/Redux | App-wide cache |
Simple one-off components, prototypes (YAGNI), no reuse expected.
| Topic | File |
| ---------------------- | ------------------------------------------------------------ |
| Container/Presentation | ${CLAUDE_SKILL_DIR}/references/container-presentational.md |
tools
Delegate implementation to codex (coder) via the herdr-agentchat plugin and drive a two-pane conversation to completion.
development
Extract recurring patterns from past closed PRs/issues and the research findings in workspace/research/, verify them against the latest code, and propose them to docs/wiki/ via PR.
development
Create Decision Records (DR) in MADR v4 format with auto-numbering.
development
Detect flaky tests by shaking them — repeated runs under varied order, parallelism, and seed — plus a static smell scan that flags latent flakiness in tests that currently pass. Classify each target as confirmed-flaky, latent-flaky, or stable and fix the root cause without weakening the test. Do NOT use to fix a confirmed single bug (use /fix) or for static-only code review (use /audit).