Reviews and applies lightweight UI motion patterns with accessibility-safe behavior. Use when adding animations, hover/tap interactions, or section reveal effects.

Open a GitHub pull request for this repository using gh CLI, including branch checks, push, a reviewer-friendly PR body, and verified GitHub issue links (Closes/Fixes/Refs). Always resolve or create related issues before gh pr create so the PR can link to tickets; when drafting new issues, follow the create-github-issue skill for title and body structure. **PR title and body prose are humanized** per the humanizer skill (`.cursor/skills/humanizer/SKILL.md`). Use when the user asks to create/open/submit a PR or pull request, and format title and description with the pr-title-description skill structure (including Related issues).

QA Engineer role that audits the Jasmine kindergarten website for performance (Core Web Vitals), accessibility (WCAG 2.2 AA), SEO, security, browser compatibility, mobile optimization, and analytics. Use when the user asks to review, audit, test, check quality, run a QA checklist, fix performance, improve accessibility, or optimize the site.

Use when writing new code, renaming files, adding imports, creating error classes, or reviewing code style. Covers file naming, export naming, import patterns, validation helpers, and error handling conventions for this project.

Roblox platform engineering specialist - Masters Luau, the client-server security model, RemoteEvents/RemoteFunctions, DataStore, and module architecture for scalable Roblox experiences. Use when Codex needs this specialist perspective, workflow, or review style for related tasks in the current project.

Expert performance testing and optimization specialist focused on measuring, analyzing, and improving system performance across all applications and infrastructure. Use when Codex needs this specialist perspective, workflow, or review style for related tasks in the current project.

Enforce TypeScript safety rules when editing or reviewing `.ts` and `.tsx` files, adding shared types, handling external data, or resolving type errors. Use when Codex needs repo-specific guidance on narrowing unknown values, writing `catch (error: unknown)`, avoiding `any`, and keeping casts confined to explicit, already-approved boundaries such as generated and ignored files.

Use when the user asks to design, review, or debug authentication and onboarding flows for Finny, especially React Native + Supabase auth session handling and Plaid-linked account setup.

- Ensure the PR is conflict-free with `develop`.

Expert application security engineer specializing in threat modeling, vulnerability assessment, secure code review, and security architecture design for modern web and cloud-native applications. Use when Codex needs this specialist perspective, workflow, or review style for related tasks in the current project.

Sincroniza calendarios de Microsoft 365 con NEXO AV para operaciones e hitos administrativos. Use when implementing or reviewing Microsoft Graph calendar sync, wiring `CalendarPage`, mapping Outlook events to project sites, assignments, visits or billing milestones, or diagnosing calendar-based workflows for `Instalaciones` and `Facturacion`.

Use when a task needs an implementation plan that is iteratively created and stress-tested through review-and-revise cycles before implementation begins — catches blind spots, incorrect codebase assumptions, unnecessary complexity, and performance pitfalls while changes are still cheap

Use when creating a new pinu-bot character or doing a major character redesign. Covers neutral-first design, shared API mapping, emotion-family construction, visual harness review, and finish criteria for cross-state cohesion. Do not use for small one-off expression tweaks.

Expert brand strategist and guardian specializing in brand identity development, consistency maintenance, and strategic brand positioning. Use when Codex needs this specialist perspective, workflow, or review style for related tasks in the current project.

Review SQL or report logic for many-to-many joins, duplicate-grain risk, unsafe aggregation, and filter side effects.

Evidence-based editorial pipeline that detects and removes AI writing patterns using a research-grounded rubric, preserves author facts, and gates on high-severity issues.

>

Write a structured design review that someone can act on without follow-up questions. Use when giving async design feedback, writing portfolio case studies, or documenting design decisions.

Understand the constraints a design was built under and evaluate quality within that context. Use when reviewing work that had limited time, budget, or team size, or when assessing whether constraints were handled well.

Run taste-informed design reviews using Observation > Principle > Question. Use when facilitating design critiques, improving feedback quality on a team, or building a shared vocabulary for quality.

Use when the user wants development run through a boss-worker-reviewer loop, where a boss agent clarifies requirements, writes prompts, dispatches worker and reviewer subagents, reports progress after each review, and iterates in rounds with user checkpoints.

Show what changed in spec.md and predict downstream impact on plan and

Detect AI-generated code patterns \u2014 unnecessary abstractions, over-documentation, as any, defensive coding against impossible states.

Perform a comprehensive security review of the current codebase

Security review of changes introduced on a branch compared to a base

Security review of staged changes only (git diff --cached)

'Spec-aligned code review agent. Acts as a dedicated independent reviewer:

Code review response protocol. Loads the obra/superpowers receiving-code-review\

Verify the generated tasks.md covers every requirement in spec.md before

Review completed implementation work and update task status.

Relentless blind-peer reviewer for Gemini 3.1 Pro. Validates every cited thesis and paper via Google Search to detect hallucinations. Generates a 'Scientific Integrity Report' saved directly to Obsidian via shell. Triggers: review paper, peer review, manuscript review, referee report, check integrity, verify citations.

Advanced academic paper writing engine for Gemini 3.1 Pro. Features: 12-agent conceptual pipeline, Google Search citation validation, Obsidian-optimized Markdown (LaTeX + [[links]]), and hierarchical multi-file project structure. Triggers: write paper, academic paper, guide my paper, parse reviews, 寫論文, 學術論文, 引導我寫論文, 審查意見.

Orchestrator for the full academic research pipeline with automated project state tracking. Manages the transition between RESEARCH, WRITE, REVIEW, and PUBLISH states. Features: shell-based file management, automatic YAML frontmatter synchronization (status: active/archived), and wiki-link [[ ]] reference management.

Use when reviewing pull requests, reviewing your own code before committing, or when asked to review code changes. Provides structured analysis with severity categorization, security focus, and optional worktree isolation for safe PR review.

Write the plan before writing the code. Execute it in small batches. Review between batches. This is how you avoid rewriting the same feature three times.

Perform an automated code review on recent changes. Checks for security issues, performance problems, error handling gaps, and code quality. Outputs a structured report with severity levels.

client-prep

Automated weekly self-audit of agent operations, cron health, memory gaps, and process failures. Use when performing periodic reviews, operational health checks, identifying automation gaps, surfacing wrong assumptions, or generating improvement recommendations. Triggers on: weekly review, meta-audit, operations audit, what broke this week, process review, improvement cycle, retrospective, week in review.

Use when analyzing large codebases (>200 lines), performing web searches for current info, or needing adversarial plan reviews.

A cybernetics × AI agent seminar skill. Grounded in *Cybernetics and Scientific Methodology* (Jin Guantao) and Wienerian cybernetics, it analyzes how cybernetic principles inform modern AI agent R&D, architecture review, and design guidance. Trigger when users mention cybernetics, feedback control, agent architecture, systems theory, black-box methods, negative feedback, positive feedback, agent design principles, steady-state systems, information entropy, purposive behavior, functional simulation, or Ashby's law of requisite variety. Also use when users want to review agent architectures from a cybernetic perspective, discuss feedback mechanism design, analyze agent stability and self-evolution, or organize cybernetics × AI agent seminars.

A double-loop learning execution review skill. Reviews the execution history after a task is completed and turns it into a concise retrospective, handoff, or improvement memo. Use this whenever a coding, writing, research, planning, debugging, or operational task has just finished; whenever files, commands, tests, or deliverables were produced; whenever the user asks to summarize what was done, review the execution, create a handoff, capture lessons learned, or prepare for the next iteration; and especially when the user needs not only a summary of what happened, but a judgment about whether the original goal, assumptions, success criteria, or working rules should change before the next pass. If there is execution evidence in the conversation, err on the side of using this skill instead of waiting for the user to ask explicitly.

Use when users want to commit changes, improve a commit message, split mixed changes into logical commits, clean up recent local history, remove accidentally committed files, squash or reword recent local commits, or generally sort out a local Git mess before review or a PR.

Use when users want Excalidraw diagrams, flowcharts, architecture diagrams, sequence diagrams, data-flow diagrams, mind maps, concept maps, or Obsidian `.excalidraw.md` files, especially when they want the diagram reviewed against an exported PNG and refined for layout, connections, and readability.

Comprehensive Seurat v5 (R) guide for single-cell RNA-seq and multimodal analysis. Covers installation, standard workflows (Normalize/SCTransform), clustering, integration (CCA/RPCA/Harmony), differential expression (FindMarkers/FindAllMarkers), visualization (DimPlot/FeaturePlot/VlnPlot/DoHeatmap), spatial transcriptomics (Visium/Visium HD/MERFISH/Slide-seq), CITE-seq, ATAC-seq, WNN, cell cycle regression, hashing/demultiplexing, sketch analysis, BPCells on-disk, pseudobulk, and format conversion. Use this skill whenever writing, debugging, or reviewing Seurat R code, building scRNA-seq pipelines, or looking up Seurat syntax, even for simple questions.

Write emails people actually read. Use when crafting subject lines, structuring email content, writing CTAs, optimizing preview text, or improving open and click rates.

Active orchestrator for multi-agent flight execution. Drives the full leg cycle (design, implement, review, commit) using three separate Claude instances.

Use when ready to create a pull request — handles push and PR creation. Suggests security review when agent-facing code is modified.

Translate or review Typst documentation TOML in this repository using the local helper, canonical repo rules, and git-based patch review.

Run `go vet` for SocialPredict backend Go code and summarize correctness-oriented findings. Use when a user asks to run `go vet`, enforce a backend quality gate, or investigate vet findings before review or verifier handoff.