GitHub
pattern-enforcement
Enforce architectural patterns with ESLint rules. Block infra imports, enforce object params, prevent server/client leaks.
☆ 1View skill
jagreehal AI Skills
GitHub ↗Browse published AI skills maintained by jagreehal. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
50Repository stars across indexed skills
42Repository forks
0Average repository stars per indexed skill
1Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
storybook-journeys
Create Storybook "user journey" storyboards for React apps (page/screen stories, MSW API mocking, interaction play functions, and optional Storybook test-runner setup). Use when the user wants Storybook demos o...
☆ 1View skill
GitHub
spine-framework
Evaluate and improve technical articles using the SPINE framework. Use when writing blog posts, technical documentation, tutorials, or reviewing draft articles for quality.
☆ 1View skill
GitHub
create-tasks
Creates well-formed tasks following a template that engineers can implement. Use when creating tasks, defining work items, creating tasks from PRD, breaking down features, or converting requirements into action...
☆ 1View skill
GitHub
research-first
Research-driven investigation. Validate solutions and explore documentation before presenting. Never ask questions you can answer yourself through research.
☆ 1View skill
GitHub
documentation-standards
User-centered documentation quality framework. Eight quality dimensions, document type requirements, and review checklist. Documentation exists to serve readers, not demonstrate knowledge.
☆ 1View skill
GitHub
concise-output
Enforce extreme brevity and high signal-to-noise ratio. Every word must justify its existence. Eliminates verbose explanations, filler phrases, and unnecessary elaboration.
☆ 1View skill
GitHub
observability
Make functions observable with trace() wrapper, structured logging (Pino), and OpenTelemetry. Observability is orthogonal to business logic.
☆ 1View skill
GitHub
branch-completion
Use when implementation is complete and tests pass. Guides completion by presenting structured options for merge, PR, or cleanup.
☆ 1View skill
GitHub
structured-writing
Writing assistance with voice preservation. Structure content, ask clarifying questions, identify gaps. Small edits execute; large changes ask first.
☆ 1View skill
GitHub
code-review-reception
Use when receiving code review feedback, before implementing suggestions. Requires technical verification, not performative agreement or blind implementation.
☆ 1View skill
GitHub
system-architecture
Design systems for change. Trade-off analysis, ADR documentation, pattern selection. Architecture decisions must have documented rationale.
☆ 1View skill
GitHub
design-exploration
Use before any creative work - creating features, building components, adding functionality. Explores user intent, requirements, and design before implementation. One question at a time, multiple choice preferr...
☆ 1View skill
GitHub
critical-peer
Professional skepticism with pattern enforcement. Verify before agreeing, challenge violations, propose instead of asking. Concise output, research before asking, answer questions literally.
☆ 1View skill
GitHub
resilience
Add retry, timeout, and circuit breaker patterns at the workflow level. Business functions stay clean.
☆ 1View skill
GitHub
investigation-modes
Three explicit investigation modes: LEARNING (build understanding), INVESTIGATION (diagnose problems), SOLVING (implement fixes). Prefix messages with mode, ask before transitioning.
☆ 1View skill
GitHub
tdd-workflow
Strict TDD state machine with Result types. 7-state workflow (PLANNING, RED, GREEN, REFACTOR, VERIFY, BLOCKED, VIOLATION). Every message MUST announce state. Integrates with fn(args, deps), vitest-mock-extended...
☆ 1View skill
GitHub
skill-authoring
Use when creating, editing, or reviewing skills. Covers discovery optimization, structure patterns, testing approaches, and format decisions.
☆ 1View skill
GitHub
code-flow-analysis
Trace code execution path before implementing fixes. Forces understanding of fn(args, deps) flows, Result types, and workflow composition. Prevents guessing by requiring file:line references and execution diagr...
☆ 1View skill
GitHub
design-principles
Software design beyond syntax. Fail-fast over fallbacks, explicit over implicit, composition over inheritance. Integrates with fn(args, deps) and Result type patterns. Includes 8-dimension design analysis.
☆ 1View skill
GitHub
confidence-levels
Force honest confidence assessment. Express confidence as percentage, explain gaps, validate assumptions before presenting conclusions.
☆ 1View skill
GitHub
result-types
Never throw for expected failures. Use Result types with explicit error handling and workflow composition.
☆ 1View skill
GitHub
debugging-methodology
Evidence-based debugging with Iron Law discipline. Instrument before guessing, trace before theorizing. Use when encountering any bug, test failure, or unexpected behavior - before proposing fixes.
☆ 1View skill
GitHub
fn-args-deps
Enforce the fn(args, deps) pattern: functions over classes with explicit dependency injection
☆ 1View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.