mrclrchtr

Fetches and normalizes http(s) web pages into clean Markdown for LLM ingestion. Use when a task includes a URL, needs to fetch docs or asks to convert web docs/articles/pages into Markdown for summarizing, quoting, diffing, or saving.

Creates a commit with repo-matching style and intentional staging.

Fetches and normalizes http(s) web pages into clean Markdown for LLM ingestion. Use when a task includes a URL, needs to fetch docs or asks to convert web docs/articles/pages into Markdown for summarizing, quoting, diffing, or saving.

Structured code and document review workflow for finding actionable issues in diffs, PRs, commits, files, directories, and architecture docs.

Delegate UI code reviews to a subagent. Reviews components, pages, git changes, or specification files using web design guidelines.

This skill should be used when the user asks to "write React tests", "test a component", "set up test utils", "mock an API", "use React Testing Library", "configure MSW", "test async behavior", "choose query type", "test Mantine components", "test a modal", or when writing tests for React components using Vitest, RTL, MSW, or Mantine. Provides best practices for component and integration testing.

Use when building or modifying frontend UI and implementation choices should follow shared web interface guidelines for interactions, accessibility, forms, motion, performance, responsive behavior, or copy.

Use when creating, redesigning, or restyling a UI and Codex should establish a clear design direction before implementation.

End the current session with comprehensive summary of work done. Use when completing significant work or stopping for the day.

Start a new development session with optional name. Use when beginning significant work or wanting to track progress.

Add notes and progress to the current session. Use when tracking changes, issues, or accomplishments.

Critically review uncommitted git changes (staged + unstaged + untracked) before committing.

Show the current active session status including duration and recent updates. Use when checking progress or session state.

Show help and reference for the session management system. Use when learning how sessions work or available commands.

List all development sessions with their titles and dates. Use when reviewing past work or finding a specific session.

Load a previous session to review its content. Use when resuming work or reviewing past sessions.

Execute an approved implementation plan task by task — verify each step fresh, stop when blocked, and ask instead of guessing.

You MUST use this before any implementation. Clarify intent, shape the design, and get approval before touching code.

Create an implementation plan for an approved design with exact file paths, ordered tasks, concrete verification, and no placeholders.

Verify implementation against the plan, update living documentation, and close out the change.

Systematic debugging protocol — find the root cause before proposing fixes.

Check for available upgrades to the pi coding agent framework by comparing the current `@earendil-works/pi-*` or legacy `@mariozechner/pi-*` version in package.json against releases on `earendil-works/pi`. Use this skill whenever the user asks to upgrade pi, update pi, check pi changelogs/releases, or migrate off the deprecated `@mariozechner/*` packages.

Use this skill to audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates.

Update CLAUDE.md, .claude.local.md, or AGENTS.md files with project-specific context for future agent sessions. Trigger ONLY when the user explicitly mentions CLAUDE.md, .claude.local.md, AGENTS.md, project memory, or agent context files. Also trigger on direct phrases like 'add this to CLAUDE.md', 'remember this for next time', 'update project memory', or 'document this pattern'. Do NOT trigger for general documentation requests, bug reports, session summaries, or user-facing docs — those are unrelated to agent instruction files.

Check for available upgrades to the pi coding agent framework by comparing the current `@earendil-works/pi-*` or legacy `@mariozechner/pi-*` version in package.json against releases on `earendil-works/pi`. Use this skill whenever the user asks to upgrade pi, update pi, check pi changelogs/releases, or migrate off the deprecated `@mariozechner/*` packages.

Create distinctive, crafted TUI components for pi using @earendil-works/pi-tui and @earendil-works/pi-coding-agent. Use when building interactive terminal UIs — custom components, overlays, dialogs, dashboards, widgets, data visualizations, animated elements, game-like interfaces, or any visual TUI work inside pi extensions or custom tools. Triggers on: 'build a TUI component', 'make a dashboard', 'create an overlay', 'interactive widget', 'terminal UI', 'custom component', 'pi-tui', or any request to create visual, interactive terminal interfaces. Also use when beautifying or redesigning existing TUI components.

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".