Agent Claude Code
Coding agent via Codex CLI. Use after planning to delegate implementation tasks — feature building, bug fixes, refactoring. Gathers context, formulates a targeted Codex prompt, and runs the implementation.
Agent Claude Code
Research specialist for domain knowledge, library/tool evaluation, and architecture best practices. Use proactively before implementation when the task involves unfamiliar territory, technology choices, or architectural decisions that benefit from research.
Agent Claude Code
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.
Skill Claude Code
Final-gate code review via Codex CLI (codex-5.3, xhigh). Finds bugs, security issues, and regressions before commit. No edits — findings report only.
Skill Claude Code
Generate a conventional commit message for staged changes.
Skill Claude Code
Python backend conventions for this project. Use when implementing or modifying API endpoints, database models/migrations, services, schemas, or backend tests.
Skill Claude Code
React frontend conventions for this project. Use when building or modifying React components, hooks, state management, styling, or frontend tests.
Skill Claude Code
Audit project specs for conflicts, goal drift, ambiguity, and gaps via Codex CLI (gpt-5.2, xhigh). Read-only findings report.
Skill Claude Code
Summarize a YouTube video or podcast episode and save the summary as a structured note in NotePlan under '3 Resources/Podcasts, YT/'. Use this skill whenever the user shares a YouTube link and wants it summarized, noted, or saved — or says things like 'summarize this', 'add this to my notes', 'save this podcast'…
Skill Claude Code
Create distinctive, production-grade web interfaces with high design quality using Tailwind CSS. Use for building UI components, pages, dashboards, apps, and web applications. Generates crafted, polished code that avoids generic AI aesthetics.
Skill Claude Code
Fetch YouTube video transcripts and load them into context for further processing. Use this skill whenever the user shares a YouTube URL or video ID and wants to work with the video's content — summarizing, extracting insights, answering questions about it, translating, or feeding it into another workflow. Also…
Agent Claude CodeCursor
Full-stack coding agent. Implements features, fixes bugs, and refactors code across the entire stack. Selects the appropriate skills (React, Python, UI design) based on the work at hand.
Command Claude CodeCursor
Cursor tooling: skills, rules, subagents.
Cursor rule Cursor
Before starting work new work, especially after a first prompt, always prefer asking to assuming. If uncertain about anything especially user intent or architecture choices, ask for clarifications first.
Cursor rule Cursor
Always use git mv when moving or renaming files, so the git history remains persistent.
Cursor rule Cursor
Use specs/spec-index.md to decide which spec(s) apply to the current task. Only consult/include the spec(s) referenced there that are relevant to the prompt at hand. Specs are the source of truth for scope and acceptance criteria.
Cursor rule Cursor
After implementation has finished, always review if the specs need to be updated, so they will not lag behind (specs will be used for any subsequent work). Use specs/spec-index.md to decide which spec(s) apply to the current task and should be updated.
Skill Cursor
Run code reviews with the Codex CLI, prioritizing bugs, regressions, security risks, and missing tests. Use when the user asks for code review, PR review, diff review, or commit-range review via codex.
Skill Claude Code
Read, search, create, and edit NotePlan notes and daily logs directly via the filesystem. Use this skill whenever the user references NotePlan, daily notes, weekly notes, project notes, or wants to check/update their planning. Triggers: 'noteplan', 'daily note', 'today's note', 'weekly note', 'check my notes', 'add to…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: