Design, review, and conclude rigorous research experiments for Limina's H→E→F workflow. Use when creating or revising hypotheses, experiments, or findings; defining baselines, datasets, metrics, or stopping rules; comparing candidate methods; deciding whether a result is conclusive; or when a negative result may be…
Map the AI/ML state of the art for a concrete technical problem. Use for exploratory research, mechanism-based literature search, benchmark mapping, and finding generalizable approaches. Not for simple fact lookup.
Challenge the current Limina research direction and next-step plan. Use for step-back reviews, pre-commitment checkpoints, plateau reviews, contradictory findings, or pivot/continue/stop recommendations when evidence or framing may be weak.
Issue-to-PR workflow kit for any tech stack. Fetch a user story from your tracker (Jira, Linear, GitHub Issues, Azure DevOps) and any linked Figma designs, implement with plan approval, enforce >95% coverage and a security pass, generate e2e tests, open the PR, fix review findings, and move the ticket to review.
Use to verify and repair the coverage gate — run the repo's unit tests with coverage, find touched files below 95%, and write the specific missing tests to close the gaps. Language- and framework-agnostic.
Use to create or update end-to-end tests for user-facing flows changed by a story, using the repo's existing e2e framework, including realistic edge cases, and to run them until green.
Use to resolve findings on an existing pull request - review comments, CI failures, and self-review findings - fixing code, updating tests, re-verifying gates, and pushing. The counterpart to pr-reviewer that closes the loop.
Use for high-signal review of a diff or pull request in any codebase, with emphasis on scope (PR intent), correctness, contract drift, security, performance/duplication introduced, and the project's test/coverage gate.
Use for a focused security pass on a diff or pull request - authorization, secrets, input validation, data exposure, webhook verification, and OWASP-style concerns. Runs as part of the coding-agent verify step and on demand.
Work a user story end to end — fetch the ticket, plan (with approval), implement, verify the applicable gates, self-review, open the PR, and update the tracker. Use when given an issue key like PROJ-1234, ENG-42, or.
Run the repo's unit tests with coverage and verify that every file touched in the current change keeps line, branch, and function coverage at or above 95%. Language- and framework-agnostic. Use before committing, before PR creation, or when the user asks about coverage.
Create a branch, commit the work, and open a pull request for a completed user story, after all quality gates pass. Use when the user asks to open/create a PR or as the final step of the story workflow.
First-use bootstrap for the dev kit. Detects the team's issue tracker, discovers what it can via MCP/CLI, asks only what cannot be discovered, and persists the result to .claude/dev-kit.json in the consuming repo. Use when that file is missing, when the user asks to set up or reconfigure the kit, or when issue-fetch…
Create or update end-to-end tests for a user-facing flow that changed, using whatever e2e framework the repo already uses. Use after implementing a user story that alters UI behavior, routing, forms, or API-driven views.