rezics

Use the repo headed Playwright workbench to investigate live URLs, selectors, locators, text matches, computed styles, and pages blocked by Cloudflare/login/captcha flows.

Use for rezics UI design, JSX/CSS styling, tokens, typography, spacing, icons, and visual reviews.

Apply a code-first plan — route each durable item to its home in code (types/tests/comments), then make the source document disposable. No validation CLI, no state machine. Use when implementing a plan/proposal.

Use for rezics UI design, JSX/CSS styling, tokens, typography, spacing, icons, and visual reviews.

Generate final mainline squash commit messages with archive trailers.

Create conventional git commits and commit messages for repo changes.

Create, merge, list, or clean up git worktrees for parallel development.

Discuss and get approval before edits for ambiguous, architectural, or multi-file changes.

Create ordinary task-branch commits; use git-mainline-squash for final archive squashes.

Create and integrate Rezics worktrees using the main/archive workflow.

Apply a code-first plan — route each durable item to its home in code (types/tests/comments), then make the source document disposable. No validation CLI, no state machine. Use when implementing a plan/proposal.

Thinking partner for exploring ideas, investigating the rezics codebase, and clarifying requirements before a plan exists. Use when the user wants to think something through. Never implements.

Propose a code-first plan — a single markdown file with context, durable constraints/decisions, and a task checklist. No spec files. Use when the user wants to turn an idea into actionable, implementable work.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.