メニュー
Project structural organization rules for TypeScript/Bun. Proactively scans for organizational issues and produces a prioritized plan. Defines the team's preferred file, folder, and module structure.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Browser recording and control via the krometrail CLI. Use when recording a browser session, driving the browser with batch actions, or investigating recorded sessions. Captures network, console, DOM, framework state, screenshots.
Krometrail MCP navigation guide. Load this skill first to understand which tool namespace to use. Covers the three tool namespaces (debug_*, chrome_*, session_*), when to use each, common pitfalls, and pointers to the detailed skill for each namespace.
Runtime debugging via the krometrail CLI. Use when a test fails and reading the code isn't enough, when you need to inspect runtime values, or when a bug is in logic you can't trace statically. Set breakpoints, step through code, inspect variables, evaluate expressions — across 10 languages.
Project stylistic refactoring rules for TypeScript/Bun. Proactively scans for refactoring opportunities and produces a prioritized plan. Defines the team's preferred coding style.
Project code patterns and conventions. Auto-loads when implementing, designing, verifying, or reviewing code. Provides detailed pattern definitions with code examples.
React DevTools hook internals reference. Use when implementing or debugging React state observation — fiber tree traversal, hook linked lists, onCommitFiberRoot, state extraction, bug pattern detection.
| name | structural-refactor |
| description | Project structural organization rules for TypeScript/Bun. Proactively scans for organizational issues and produces a prioritized plan. Defines the team's preferred file, folder, and module structure. |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Bash, Agent, Write |
Scan the codebase for organizational issues based on these structural rules. Each rule has a reference file with rationale, examples, and exceptions.
| Rule | Summary (one line) | Reference |
|---|---|---|
| File Size | Files should stay under ~500 lines; evaluate for splitting above that | details |
| Curated Barrels | Index files selectively re-export public APIs; no splat exports | details |
| Import Direction | Strict layer hierarchy: cli/mcp → daemon → core → domains | details |
| Centralized Types | Each domain has at most one types.ts; Zod schemas live alongside types | details |
| Test Mirror Tree | Tests in tests/{unit,integration,e2e}/ mirroring src/ structure | details |
| Docs Hierarchy | Foundation docs authoritative; designs/ historical; legacy/ deprecated | details |
| Kebab-Case Naming | Files and folders use kebab-case; no layer suffixes (.service, .util) | details |
Write the refactoring plan to docs/structural-refactor-plan.md.
The document should be a prioritized refactoring plan with these sections:
Implement-ready structural changes with current/target layout, file paths, and acceptance criteria.
Valid reorganizations with moderate impact. Brief entries with file paths and rationale.
Code that technically violates a rule but should NOT be reorganized, with justification.
