メニュー
Project stylistic refactoring rules for Bun/TypeScript CLI. Proactively scans for refactoring opportunities and produces a prioritized plan. Defines the team's preferred coding style.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Compare project base prompts and model metadata against a new Claude Code release. Extracts upstream system prompt, diffs each fragment, classifies changes as intentional omission or drift, and applies approved updates. Use when user says "sync upstream", "check for drift", "new CC version", or runs /sync-upstream.
Project structural organization rules for Bun/TypeScript CLI. Proactively scans for organizational issues and produces a prioritized plan. Defines file, folder, and module structure preferences.
Project code patterns and conventions. Auto-loads when implementing, designing, verifying, or reviewing code. Provides detailed pattern definitions with code examples.
| name | stylistic-refactor |
| description | Project stylistic refactoring rules for Bun/TypeScript CLI. Proactively scans for refactoring opportunities and produces a prioritized plan. Defines the team's preferred coding style. |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Bash, Agent, Write |
Scan the codebase for opportunities to apply these stylistic preferences. Each style has a reference file with rationale, examples, and exceptions.
| Style | Rule (one line) | Reference |
|---|---|---|
| Functions Over Classes | Use top-level functions and plain objects; never introduce classes | details |
| Early Returns | Use guard clauses and early returns; never nest more than 2 levels deep | details |
| Declarative/Imperative Split | Declarative (.map/.filter) for pure transforms; imperative for-loops for side effects | details |
| Immutable First | Create new objects via spread; mutate only caller-owned local data | details |
| Ternary Discipline | Ternaries for simple 2-branch expressions only; if/else for anything complex | details |
| Verb-First Naming | Functions start with verbs; booleans use is/has prefixes | details |
| Concatenation Style | Template literals for multi-line strings; + concatenation for simple joins | details |
Write the refactoring plan to docs/stylistic-refactor-plan.md (create docs/ if needed).
The document should be a prioritized refactoring plan with these sections:
Implement-ready entries with file:line, current code, target code, and acceptance criteria.
Valid refactors with moderate impact. Brief entries with file paths and rationale.
Code that technically violates a style but should NOT be refactored, with explanation why.
