jpcaparas

Explains codebases and feature flows in accessible language with grounded analogies. Use for simple walkthroughs or mental models; skip bug triage, code review, and code changes.

Parodies text as LinkedIn-speak or reverses corporate-influencer fluff into blunt English. Use for LinkedIn-speak and corporate-cringe rewrites; skip real translation and serious editing.

Explains code flirtatiously without losing accuracy. Use for flirty or sultry code explanations; skip ordinary explanations, code edits, and explicit sexual content.

Guide maintainable code with clear names, decomposition, safe defaults, side-effect guardrails, compatibility, comments, and quality gates. Use for production code, refactors, reviews, plans, CI, scripts, config, tests, or technical debt. Skip disposable work.

Guide maintainable tests as behavior documentation with isolated side effects, compatibility coverage, and reliable assertions. Use for tests, fixtures, mocks, regressions, reviews, and testability changes. Skip disposable work.

Guide mockable, test-double-friendly code. Use for code or tests involving dependencies, I/O, time, randomness, configuration, or external services. Skip non-code writing and disposable prototypes.

Turn a convoluted engineering, scientific, or general process into one clear Mermaid diagram and export matching Markdown and PNG files. Trigger on /to-diagram, process diagram, workflow visualization, concept map, or explain this flow visually. Do not use…

Debates when explicitly invoked.

Build AI features with the first-party Laravel AI SDK (Laravel 13+); agents, embeddings, images, audio, and tool calling with provider-agnostic APIs

Use API Resources with pagination and conditional fields; keep response shapes stable and cache-friendly

Compose UIs with Blade components, slots, and layouts; keep templates pure and testable

Request effective code reviews—specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions

Practical daily checklist for Laravel projects; bring services up, run migrations, queues, quality gates, and tests

Create effective debugging prompts—include error messages, stack traces, expected vs actual behavior, logs, and attempted solutions

Provide comprehensive context in prompts—files, errors, Laravel version, dependencies, and monorepo details—for accurate AI responses

Define clear relationships and load data efficiently; prevent N+1, use constraints, counts/sums, and pivot syncing safely