My .claude folder that contains important configuration for Claude Code
This repository also configures its own agents. See what dot-claude tells them →
Skill Claude CodeCodex
Generate a personal Claude Code usage & impact report ("receipts") from this machine's local session transcripts — for justifying Claude Code usage/spend to a manager, self-review, or "what have I been using this for" check-ins. Mines /.claude/projects locally (no extra API calls beyond one final write-up)…
Skill Claude CodeCodex
Generate an explorable HTML report of Claude Code session usage (tokens, cache, subagents, skills, expensive prompts) from /.claude/projects transcripts.
Skill Claude CodeCodex
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.
Skill Claude Code
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…
Skill Claude CodeCodex
Monitors task execution for skill improvement opportunities. Use this skill during ANY multi-step task, agentic workflow, or substantive work session where the agent is using tools and producing deliverables. It captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: