jagreehal
Publisher on askill
User-centered documentation quality framework. Eight quality dimensions, document type requirements, and review checklist. Documentation exists to serve readers, not demonstrate knowledge.
Enforce architectural patterns with ESLint rules. Block infra imports, enforce object params, prevent server/client leaks.
Use when starting feature work that needs isolation from current workspace. Creates isolated git worktrees with directory selection, safety verification, and baseline testing.
Three explicit investigation modes: LEARNING (build understanding), INVESTIGATION (diagnose problems), SOLVING (implement fixes). Prefix messages with mode, ask before transitioning.
Use when facing 2+ independent tasks that can be worked on without shared state. Dispatch one agent per problem domain for concurrent investigation.
Never throw for expected failures. Use Result<T, E> types with explicit error handling and workflow composition.
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 i...
Validate at the boundary with Zod schemas and branded types. Business functions trust validated input.
Force honest confidence assessment. Express confidence as percentage, explain gaps, validate assumptions before presenting conclusions.
Use when implementation is complete and tests pass. Guides completion by presenting structured options for merge, PR, or cleanup.
Visualization is communication. Chart selection, encoding hierarchy, accessibility, rendering performance. Use established algorithms - these problems are solved.
Enforce extreme brevity and high signal-to-noise ratio. Every word must justify its existence. Eliminates verbose explanations, filler phrases, and unnecessary elaboration.
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 choi...
Enforce the fn(args, deps) pattern: functions over classes with explicit dependency injection
Use when receiving code review feedback, before implementing suggestions. Requires technical verification, not performative agreement or blind implementation.
Use when about to claim work is complete, fixed, or passing. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.
Showing 18 of 32