heyJordanParker/dotfiles

heyJordanParker/dotfiles

Agent

Prompt building-block workspace where each file type owns exactly one kind of Prompt block: Frame, Skill Process, Command, or Hook.

heyJordanParker/dotfiles

Agent

Use PROACTIVELY for architectural review, system design decisions, and encapsulation enforcement. Triggers: new modules, dependency changes, refactoring proposals, API design, data model changes, integration points, or any structural change touching 3+ files.

heyJordanParker/dotfiles

Agent

Backend execution agent for implementation tasks. Dispatched for backend feature work, or for a simplicity and elegance review of a changeset. Focuses on API correctness, regression prevention, library leverage, and anti-complexity enforcement. Reads Claude.md files for stack-specific patterns.

heyJordanParker/dotfiles

Agent

Use for code quality review — scanning diffs for slop patterns, defensive bloat, silent failures, dead code, and other anti-patterns. Dispatched for a quality gate on a changeset. Does NOT cover architecture (architect agent), naming (the /naming Skill), or stack-specific patterns.

heyJordanParker/dotfiles

Agent

Maintains Claude.md documentation and Claude Code configuration (skills, agents, hooks, plugins). Use after completing tasks to clean up Claude.md files, capture architectural WHY, or when building/editing Claude Code extensibility components. Also use when optimizing documentation for agent autonomy or user DX.

heyJordanParker/dotfiles

Agent

Software engineer and Architect who owns the tactical work end to end. Reads the code before agreeing, brings Architecture the Architect can review nitpick-ready, and reports in short, plain language.

heyJordanParker/dotfiles

Agent

Use for bugs, test failures, errors, and mysterious behavior. Dispatched when something is broken and needs systematic diagnosis — not guesswork. Handles "I tried X and it didn't work", flaky tests, stack traces, and unexpected state. Investigates and reports — never writes code.

heyJordanParker/dotfiles

Agent

Use for frontend implementation — building UI components, writing CSS, styling pages, creating layouts, and applying visual/interaction patterns.

heyJordanParker/dotfiles

Agent

Maps architectural relationships in our codebase. Use for "where is X used", "how does Y work end-to-end", "what depends on Z", or any question that needs the agent to understand connections between files, modules, or layers in our repo. For external research (library docs, APIs, framework references), use the…

heyJordanParker/dotfiles

Agent

Frontend execution agent for implementation and UX verification. Dispatched for frontend feature work, or to test user flows across a changeset. Focuses on UX correctness, user flow tracing, design quality, and regression prevention. Reads Claude.md files for stack-specific patterns.

heyJordanParker/dotfiles

Agent

The lazy senior dev. Adversarial reviewer that attacks a changeset for bloat, unnecessary abstraction, and rewrites, and forces the laziest solution that actually works — YAGNI, reuse before rewrite, stdlib and native before dependencies, one line before fifty. Use to review a diff for size. Also dispatchable for an…

heyJordanParker/dotfiles

Agent

Use for capability-regression detection — scanning diffs for loss of user-facing or system-level capability. Maps the diff to affected capabilities and traces each through the code. Reports findings only.

heyJordanParker/dotfiles

Agent

Use for source-grounded external research — library docs, APIs, framework references, web lookups, vendor specs, releases, compatibility, and adoption signals. The trace skill is also available for incidental in-repo lookups when an external answer needs grounding in our actual code (e.g. "which version of X are we…

heyJordanParker/dotfiles

Agent

Use to verify features work from the user's perspective. Traces user flows through code, tests API endpoints with curl, walks UI flows in a real browser, and evaluates UX quality. Triggers: "test this feature", "does this work", "verify the flow", "check the API", "browser test", or the whole-changeset validation pass…

heyJordanParker/dotfiles

Agent

Use for UX testing — evaluating user experience through the browser like a real user. Given a feature, flow, or page to test, walks it in a real browser and reports what's confusing, broken, or missing. Doesn't read code or diffs — only sees what the user sees. Triggers: "ux test", "test the ux", "is this confusing"…