erikpr1994
- 63 skills
- 0 followers
- 6 hours ago last updated
- ▌ Articulate · erikpr1994 bundleThe conductor for turning rough thinking into published writing: mines raw material (from you, and — for a coding project — from the repo, git log, and PR descriptions) and shapes it into a finished piece for a chosen platform. Triggers on developing fragments or ideas before structure, shaping notes into an article, building a piece beat by beat as narrative, or writing a post for LinkedIn / a blog / Twitter. Not for code, PRs, or one-off copyedits.
- ▌ Materialize · erikpr1994 bundleThe conductor for non-trivial development work: takes an idea — however rough — all the way to shipped code, picking the right amount of process (a one-line fix vs. a full product spec) and driving it end to end rather than ad hoc. Triggers on mapping a loose idea into open questions, grilling a plan to shared understanding, researching unknowns, writing a PRD, breaking work into issues, technical or domain design, prototyping UI, implementing a feature, test-driven development, code review, independent verification, writing a PR description, debugging to root cause, improving architecture, or resolving merge conflicts. Not for one-off prose or writing tasks.
- ▌
- ▌ Source Triage · erikpr1994 bundleTriage the projects this fork learns from (the README Inspiration watch-list) — their code, open and closed issues, and discussions — against our fork, recording a verdict for each so we never re-analyse the same item twice. Use to sync the triage log across sources, find ideas to port into the fork, or review a single backlog item.
- ▌ Writing For Agents · erikpr1994 bundleReference for writing and editing any agent-facing artifact — the vocabulary and principles that make it predictable. Covers authoring a skill, agent instruction files, and rule files.
- ▌ Test Driven Development · erikpr1994Use when implementing any feature, bugfix, or code change. Invoke BEFORE writing implementation code. The Iron Law - no production code without a failing test first.
- ▌ Plan · erikpr1994Use when you have a spec or requirements for a multi-step task, before touching code. Triggers - plan, design, architect, implementation plan, spec, requirements.
- ▌ Debug · erikpr1994Use when encountering bugs, test failures, or unexpected behavior. Hypothesis-driven debugging.
- ▌ Gh CLI · erikpr1994GitHub CLI patterns for PR reviews, comments, and API operations. Use when working with gh api commands, especially for review threads and comments.
- ▌ Execute · erikpr1994Use when following a written plan or task list. Checkpoint verification at each step. Triggers - execute plan, follow plan, implement plan, next step, continue, proceed.
- ▌ Session · erikpr1994Use when work spans multiple phases, requires context handoff, or exceeds single conversation scope. Triggers - session, multi-phase, handoff, continue, resume, checkpoint, long-running.
- ▌ Analytics · erikpr1994Use when implementing analytics, event tracking, or setting up dashboards. Covers privacy-first tracking, event patterns, and common analytics tools.
- ▌ Crawl CLI · erikpr1994Use when implementing web scraping, data extraction, or automated browser interactions. Covers Puppeteer, Playwright, rate limiting, and ethical scraping.
- ▌ Infra Ops · erikpr1994Use when working with infrastructure, deployments, Docker, CI/CD, or server management. Covers containerization, deployment workflows, and DevOps patterns.
- ▌ Submit Pr · erikpr1994Complete PR submission pipeline with local sub-agent review before pushing, CI verification, and automated review integration. Always dispatches code-reviewer and code-simplifier for code changes, plus conditional reviewers (security, performance, dependency, accessibility, i18n, type-design, etc.) based on change type. Waits for CI with `gh pr checks --watch`. Integrates CodeRabbit and Greptile feedback.
- ▌ API Design · erikpr1994REST/GraphQL API design patterns, error handling, and versioning. Use when designing APIs, handling errors, or making API architecture decisions.
- ▌ Brainstorm · erikpr1994Use when generating ideas, exploring options, defining requirements, or making decisions. Covers both discovery (what to build) and approach (how to build). Triggers - ideate, brainstorm, options, alternatives, explore, what if, could we, ways to, approaches, spec, requirements, user story.
- ▌ Coderabbit · erikpr1994Use when working with CodeRabbit AI code review. Covers triggering reviews, interpreting feedback, addressing comments, and PR workflow integration.
- ▌ Git Expert · erikpr1994Use when working with git operations including commits, branches, worktrees, and PRs. Covers the full git workflow from feature isolation to PR submission.
- ▌
- ▌ Fix Linear Bugs · erikpr1994Fix Linear issues tagged with "bug". Either produces a PR with the fix or explains why it won't be fixed. Triggers - fix bugs, linear bugs, bug triage, resolve bugs.
- ▌ Create Linear Plan · erikpr1994Create Linear Issues from requirements using the plan process. Same process as /plan but outputs to Linear Issues instead of file. Triggers - linear plan, plan to linear, create issues from plan.
- ▌ Create Linear Spec · erikpr1994Create a Linear Project from requirements using Discovery Mode brainstorming. Same process as /spec but outputs to Linear instead of file. Triggers - linear spec, spec to linear, create project from spec, linear project.
- ▌ Pr Workflow · erikpr1994Use when creating PRs, managing stacked PRs, or completing feature branches.
- ▌ Linear · erikpr1994 bundleIntelligent work tracking. Automatically classifies issues, gathers codebase context, and creates well-formed Linear tickets. Triggers - linear, issue, track, bug, todo, fix, question, debt.
- ▌ Using Skills · erikpr1994Core skill for understanding and using the Jarvis skill system. Loaded at every session start.
- ▌ Verification Before Completion · erikpr1994Use when about to claim work is complete, fixed, or passing. Invoke BEFORE committing, creating PRs, or making any success claims. The Iron Law - evidence before assertions, always.
- ▌ Domain Expert · erikpr1994Meta-skill for rapidly learning new domains. Covers domain research process, expert consultation simulation, knowledge validation, and documentation generation.
- ▌
- ▌ Create Linear Design · erikpr1994Create a Linear Document with technical design using Approach Mode brainstorming. Same process as /brainstorm how, outputs to Linear Document. Triggers - linear design, design to linear, technical design, architecture decision.
- ▌ Linear Refine Ticket · erikpr1994Refine Linear tickets tagged "refine" or in triage. Pull GitHub context, clarify scope, add acceptance criteria, improve descriptions. Triggers - refine ticket, ticket refinement, triage, improve ticket.
- ▌ Writing Hooks · erikpr1994Use when creating hooks for prompt interception, permission handling, or event-triggered automation with timeout and bypass handling.
- ▌ Writing Rules · erikpr1994Use when creating or updating rules in CLAUDE.md, settings, or rule files. Covers confidence thresholds and false positive prevention.
- ▌ React Patterns · erikpr1994React component patterns, hooks, server components, and composition. Use when building React components or deciding between patterns.
- ▌ Worktree Check · erikpr1994Use before git write operations (commit, push, merge, rebase) to verify you are in a git worktree. Guides worktree setup if missing. Keywords: worktree, isolation, git commit, git push.
- ▌ Writing Agents · erikpr1994Use when creating new agents, defining agent roles, or configuring agent handoff protocols and model selection.
- ▌ Writing Design · erikpr1994Use when creating design documents, technical specs, architecture decisions, or system documentation. Covers structure, audience, and validation.
- ▌ Writing Skills · erikpr1994Use when creating new skills, editing existing skills, or verifying skills work before deployment. Follows TDD methodology.
- ▌ Build In Public · erikpr1994Use when sharing development progress publicly. Covers progress sharing, changelog writing, social media updates, community engagement, and milestone announcements.
- ▌ Frontend Design · erikpr1994Use when designing UI components, implementing accessibility, responsive layouts, or integrating with design systems.
- ▌ Idea To Product · erikpr1994Use when rapidly prototyping ideas into products. Covers MVP scoping, feature prioritization, tech stack selection, timeline estimation, and launch checklist.
- ▌ MCP Integration · erikpr1994Use when working with MCP servers for enhanced capabilities like documentation retrieval, database access, or specialized tools. Triggers - mcp, context7, documentation lookup, external docs.
- ▌ Nextjs Patterns · erikpr1994Next.js App Router patterns, server actions, caching, and routing. Use when working with Next.js 14+ features.
- ▌ Background Tasks · erikpr1994Efficient handling of long-running commands. Use when running tests, builds, or any command that takes more than a few seconds. Prevents token waste from polling.
- ▌ Improving Jarvis · erikpr1994Use when identifying opportunities to improve the Jarvis system, adding patterns, creating skills, or updating rules based on repeated guidance.
- ▌ Answer Linear Questions · erikpr1994Answer Linear issues tagged with "question". Explores codebase and produces decisions - never code changes or PRs. Triggers - answer questions, linear questions, question triage.
- ▌ Resolve Linear Tech Debt · erikpr1994Resolve Linear issues tagged with "tech-debt". Decide to address now, schedule, or close. Triggers - resolve tech debt, technical debt, debt triage, cleanup.
- ▌ Writing Commands · erikpr1994Use when creating slash commands, user-invokable shortcuts, or command-based workflows with frontmatter and skill delegation.
- ▌ Writing Patterns · erikpr1994Use when documenting reusable code patterns, architectural approaches, or established solutions with keyword triggers and anti-patterns.
- ▌
- ▌ Database Patterns · erikpr1994Schema design, migrations, queries, and indexing strategies. Use when designing database schemas, writing migrations, or optimizing queries.
- ▌ Supabase Patterns · erikpr1994Supabase client setup, Row Level Security (RLS), edge functions, and real-time. Use when working with Supabase database, auth, or edge functions.
- ▌ Writing Claude Md · erikpr1994Use when creating or updating CLAUDE.md files at any level (global, project, folder). Covers inheritance rules and token budgets.
- ▌ Payment Processing · erikpr1994Use when implementing payment flows with Stripe or Polar. Covers checkout integration, webhooks, subscriptions, and error handling.
- ▌ Pr Feedback Tracker · erikpr1994Process PR review feedback, categorize comments, create tracking issues for deferred items, and resolve conversations. Can be invoked standalone or during submit-pr Phase 6.
- ▌ Typescript Patterns · erikpr1994TypeScript idioms, type guards, utility types, and type-safe patterns. Use when working with TypeScript types, generics, or type safety issues.
- ▌ Linear Cycle Planning · erikpr1994Plan issues for an upcoming Linear cycle/sprint. Review backlog, prioritize, assign to cycle, balance workload. Triggers - cycle planning, sprint planning, plan cycle.
- ▌ Linear Project Health · erikpr1994Generate health report for a Linear project. Progress vs plan, blocked issues, overdue items, risk assessment. Triggers - project health, project status, project report.
- ▌ SEO Content Generation · erikpr1994Use when optimizing for search engines, creating content, or implementing structured data. Covers meta tags, schema markup, and content structure.
- ▌ Linear Backlog Grooming · erikpr1994Review and clean up the Linear backlog. Close stale issues, update priorities, merge duplicates, request clarification. Triggers - backlog grooming, backlog cleanup, groom backlog.
- ▌ Review Linear Feature Requests · erikpr1994Review Linear issues tagged with "feature-request". Decide to spec, add to roadmap, merge, or reject. Triggers - review feature request, user request, customer feedback.
- ▌ Dispatching Parallel Agents · erikpr1994Use when multiple independent tasks can run simultaneously. Maximizes throughput through parallel Task tool invocations.
- ▌ Subagent Driven Development · erikpr1994Use for complex features requiring multi-stage review, architectural work, or multi-file changes. Orchestrates specialized agents for coordinated implementation.