all publishers

benjaminshoemaker

@benjaminshoemaker source repo

114 published skills · page 1 of 2

  1. ▌
    Codex Implement 3 · benjaminshoemaker bundle
    Use when delegating code implementation to Codex CLI with Claude-managed decomposition, context scoping, and verification.
    39 repo stars
  2. ▌
    Codex Review 4 · benjaminshoemaker bundle
    Have OpenAI Codex review the current branch with documentation research. Use for second-opinion code reviews or when you want cross-AI verification.
    39 repo stars
  3. ▌
    Add Todo 3 · benjaminshoemaker
    Add a properly formatted TODO item to TODOS.md. Use when you need to capture a new task, bug, or feature request during development.
    39 repo stars
  4. ▌
    Run Todos 3 · benjaminshoemaker
    Implement [ready]-tagged TODO items with commits. Use after /list-todos has clarified requirements and marked items as ready.
    39 repo stars
  5. ▌
    Configure Verification 3 · benjaminshoemaker
    Configure verification commands for this project. Use when setting up a new project or when verification-config.json is missing or incomplete.
    39 repo stars
  6. ▌
    UI UX 3 · benjaminshoemaker bundle
    Use when analyzing product UI/UX through code review, product context, pattern research, prioritized recommendations, or design system setup.
    39 repo stars
  7. ▌
    Innovate 3 · benjaminshoemaker
    Identify high-impact innovative additions to the current app or plan. Use when planning next features, during strategic reviews, or when the user asks for creative ideas.
    39 repo stars
  8. ▌
    Update Docs 3 · benjaminshoemaker bundle
    Update documentation after commits. Syncs README, AGENTS.md, CHANGELOG, and docs/ with code changes. Use after commits or to analyze working tree changes.
    39 repo stars
  9. ▌
    Codex Review 3 · benjaminshoemaker bundle
    Use when requesting an OpenAI Codex review of the current branch with documentation research and cross-AI verification.
    39 repo stars
  10. ▌
    Search Chats 2 · benjaminshoemaker
    Search past conversations with Claude Code and Codex CLI. Finds matching excerpts across all sessions with metadata (date, project, agent). Use when looking for a past discussion, decision, or piece of context from any previous session.
    39 repo stars
  11. ▌
    Codex Consult 3 · benjaminshoemaker bundle
    Use when seeking a second opinion from OpenAI Codex on documents, specs, plans, or other non-code-diff content.
    39 repo stars
  12. ▌
    Capture Session 3 · benjaminshoemaker
    Extract decisions, action items, new context, and insights from the current session into LEARNINGS.md and auto-memory. Run before ending any substantive conversation.
    39 repo stars
  13. ▌
    Data Flow Audit 3 · benjaminshoemaker bundle
    Detect split data source anti-patterns and scattered business rule duplication where the same logic is reimplemented across multiple files and languages. Catches semantic duplication that syntactic tools like jscpd miss. Use at phase checkpoints or when investigating data consistency issues.
    39 repo stars
  14. ▌
    Discover Flow Verification 2 · benjaminshoemaker bundle
    Use when determining how an AI coding agent can autonomously run and verify a specific user flow end to end before implementation.
    39 repo stars
  15. ▌
    Go 2 · benjaminshoemaker
    Resume execution from wherever you left off. Detects current state and runs the appropriate next command, or reports what's blocking progress. Use at the start of any session to pick up where you left off.
    39 repo stars
  16. ▌
    Discover 2 · benjaminshoemaker
    Exploratory conversation before /product-spec. Asks one question at a time, runs background research for open-source/off-the-shelf alternatives, and writes DISCOVERY_NOTES.md. Use when the user has an idea but hasn't scoped it yet.
    39 repo stars
  17. ▌
    Phase Prep 2 · benjaminshoemaker bundle
    Check prerequisites before starting a phase. Use before /phase-start to verify dependencies are met and context is loaded.
    39 repo stars
  18. ▌
    Fresh Start 2 · benjaminshoemaker
    Orient to project structure and load context. Use at the start of each new session or after context reset to understand the project state.
    39 repo stars
  19. ▌
    Phase Start 2 · benjaminshoemaker bundle
    Execute all tasks in a phase autonomously. Use after /phase-prep confirms prerequisites are met.
    39 repo stars
  20. ▌
    Feature Plan 2 · benjaminshoemaker bundle
    Generate EXECUTION_PLAN.md and scoped AGENTS.md files for a feature. Use after /feature-technical-spec to create the task breakdown.
    39 repo stars
  21. ▌
    Feature Spec 2 · benjaminshoemaker bundle
    Define feature requirements (problem, users, scope, acceptance criteria) through guided Q&A and write FEATURE_SPEC.md. Use when starting a new feature.
    39 repo stars
  22. ▌
    Product Spec 2 · benjaminshoemaker bundle
    Generate PRODUCT_SPEC.md through guided Q&A. Use as the first step when starting a new greenfield project.
    39 repo stars
  23. ▌
    Generate Plan 2 · benjaminshoemaker bundle
    Generate the greenfield execution plan plus root and scoped AGENTS.md files. Use after /technical-spec to create the phased task breakdown.
    39 repo stars
  24. ▌
    Technical Spec 2 · benjaminshoemaker bundle
    Generate TECHNICAL_SPEC.md through guided Q&A. Use after /product-spec to define the technical architecture.
    39 repo stars
  25. ▌
    Codex Implement 2 · benjaminshoemaker bundle
    Delegate code implementation to Codex CLI. Claude decomposes, scopes context, and verifies; Codex implements. Accepts a spec file, text description, or gathers requirements interactively.
    39 repo stars
  26. ▌
    Phase Checkpoint 2 · benjaminshoemaker bundle
    Run checkpoint criteria after completing a phase. Use after /phase-start completes all tasks to verify quality gates before proceeding.
    39 repo stars
  27. ▌
    Feature Technical Spec 2 · benjaminshoemaker bundle
    Define technical approach (architecture, integration points, data model) for a feature through guided Q&A and write FEATURE_TECHNICAL_SPEC.md. Use after /feature-spec.
    39 repo stars
  28. ▌
    UI UX 2 · benjaminshoemaker bundle
    Comprehensive UI/UX analysis and design intelligence. Point at any product to get: code analysis, product/user context assessment, industry pattern research, and prioritized improvement recommendations. Combines craft principles, data-driven design intelligence, and creative excellence. Also guides design system setup for consistent AI-assisted UI work.
    39 repo stars
  29. ▌
    Add Todo 2 · benjaminshoemaker bundle
    Add a properly formatted TODO item to TODOS.md. Use when you need to capture a new task, bug, or feature request during development.
    39 repo stars
  30. ▌
    Innovate 2 · benjaminshoemaker
    Identify high-impact innovative additions to the current app or plan. Use when planning next features, during strategic reviews, or when the user asks for creative ideas.
    39 repo stars
  31. ▌
    Progress 2 · benjaminshoemaker bundle
    Report completion status of the main and feature execution plans. Use to check how many tasks remain and which phases are done.
    39 repo stars
  32. ▌
    Create Pr 2 · benjaminshoemaker
    Create a GitHub PR with verification and Codex review. Runs verify.sh and code/doc review before PR creation.
    39 repo stars
  33. ▌
    Merge Prs 2 · benjaminshoemaker bundle
    Merge multiple PRs with conflict resolution and CI failure auto-patching. Analyzes optimal merge order, resolves conflicts, pulls CI logs on failure, and fixes issues. Use when multiple feature branches need merging into the base branch.
    39 repo stars
  34. ▌
    Run Todos 2 · benjaminshoemaker
    Implement [ready]-tagged TODO items with commits. Use after /list-todos has clarified requirements and marked items as ready.
    39 repo stars
  35. ▌
    Auto Verify 2 · benjaminshoemaker bundle
    Attempt automated verification of criteria before falling back to manual. Parses criterion text for automation hints and executes appropriate tool (curl, browser, file check). Invoked by verify-task and phase-checkpoint for MANUAL and MANUAL:DEFER criteria.
    39 repo stars
  36. ▌
    OAUTH Login 2 · benjaminshoemaker bundle
    Complete OAuth login flow and store tokens for verification. Use when browser verification requires authenticated sessions.
    39 repo stars
  37. ▌
    Update Docs 2 · benjaminshoemaker bundle
    Update documentation after commits. Syncs README, AGENTS.md, CHANGELOG, and docs/ with code changes. Use after commits or to analyze working tree changes.
    39 repo stars
  38. ▌
    Verify Task 2 · benjaminshoemaker
    Run code-verification on a specific task. Use to verify a single task's acceptance criteria after implementation.
    39 repo stars
  39. ▌
    Audit Skills 2 · benjaminshoemaker bundle
    Audits skills, commands, and prompt templates for best practice violations including length, checklists, verification steps, and progressive disclosure. Use after creating or modifying skills, during reviews, or to improve existing prompt files. Produces prioritized improvement suggestions.
    39 repo stars
  40. ▌
    Codex Review 2 · benjaminshoemaker bundle
    Have OpenAI Codex review the current branch with documentation research. Use for second-opinion code reviews or when you want cross-AI verification.
    39 repo stars
  41. ▌
    Vision Audit 2 · benjaminshoemaker
    Audit project alignment with VISION.md, identify SDLC gaps, and generate feature proposals. Use when reviewing strategic direction or planning new features.
    39 repo stars
  42. ▌
    Codex Consult 2 · benjaminshoemaker bundle
    Get a second opinion from OpenAI Codex on documents, specs, or plans. Use for cross-AI consultation on any content, not just code diffs.
    39 repo stars
  43. ▌
    Feature Audit 2 · benjaminshoemaker bundle
    Multi-source audit of a shipped feature against its original plans, product vision, UI/UX best practices, and live browser inspection. Produces consolidated findings with prioritized recommendations.
    39 repo stars
  44. ▌
    Security Scan 2 · benjaminshoemaker
    Run dependency audits, secrets detection, and static analysis to find CVEs, leaked credentials, and insecure code patterns. Use at phase checkpoints or before releases.
    39 repo stars
  45. ▌
    Criteria Audit 2 · benjaminshoemaker
    Validate EXECUTION_PLAN.md for verification metadata, manual reasons, and testability. Use when preparing Phase 1 or after editing EXECUTION_PLAN.md.
    39 repo stars
  46. ▌
    Populate State 2 · benjaminshoemaker
    Generate `.claude/phase-state.json` from the main execution plan and git history. Use to recover phase state after context loss or when joining an existing project.
    39 repo stars
  47. ▌
    Vercel Preview 2 · benjaminshoemaker
    Resolve Vercel preview deployment URL for the current git branch. Invoked by browser-verification when deployment.enabled is true, or directly to check deployment status. Use to check deployment status or when browser verification needs a URL.
    39 repo stars
  48. ▌
    Capture Session 2 · benjaminshoemaker
    Extract decisions, action items, new context, and insights from the current session into LEARNINGS.md and auto-memory. Run before ending any substantive conversation.
    39 repo stars
  49. ▌
    Data Flow Audit 2 · benjaminshoemaker bundle
    Detect split data source anti-patterns and scattered business rule duplication where the same logic is reimplemented across multiple files and languages. Catches semantic duplication that syntactic tools like jscpd miss. Use at phase checkpoints or when investigating data consistency issues.
    39 repo stars
  50. ▌
    Review Deferred 2 · benjaminshoemaker
    Review deferred verification items. Use when you want to check or clear the deferred review queue without waiting for project completion.
    39 repo stars
  51. ▌
    Tech Debt Check 2 · benjaminshoemaker bundle
    Identify code duplication, cyclomatic complexity, large files, and maintainability anti-patterns. Use at phase checkpoints or on-demand to quantify technical debt.
    39 repo stars
  52. ▌
    Analyze Sessions 2 · benjaminshoemaker bundle
    Extract automation patterns from session logs and rank by impact. Use periodically after multiple sessions to identify repetitive workflows that could become skills or hooks.
    39 repo stars
  53. ▌
    Capture Learning 2 · benjaminshoemaker
    Capture a project learning or pattern to LEARNINGS.md. Use when you discover a useful pattern or convention during development.
    39 repo stars
  54. ▌
    Code Verification 2 · benjaminshoemaker
    Multi-agent code verification workflow using a main agent and sub-agent loop. Use when verifying code against requirements, acceptance criteria, or quality standards. Triggers on requests to verify, validate, or check code against specifications, checklists, or instructions.
    39 repo stars
  55. ▌
    Spec Verification 2 · benjaminshoemaker bundle
    Verify generated specification documents for context preservation and quality issues. Automatically triggered after document generation. Checks that upstream requirements are preserved and identifies common specification problems.
    39 repo stars
  56. ▌
    Browser Verification 2 · benjaminshoemaker bundle
    Verify browser-based acceptance criteria using ExecuteAutomation Playwright MCP with multi-tool fallback chain. Invoked by verify-task and phase-checkpoint for BROWSER:* criteria.
    39 repo stars
  57. ▌
    Configure Verification 2 · benjaminshoemaker
    Auto-detect test, lint, typecheck, and build commands from package.json, Makefile, and other project config. Use during project setup or when build tooling changes. Runs silently — no prompts.
    39 repo stars
  58. ▌
    Bootstrap · benjaminshoemaker bundle
    Generate feature plan with codebase-aware context. Use when starting a new feature in an existing codebase to skip full spec workflow.
    39 repo stars
  59. ▌
    List Todos · benjaminshoemaker bundle
    Analyze and prioritize TODO items from TODOS.md. Use when planning work or deciding what to implement next.
    39 repo stars
  60. ▌
    Triage · benjaminshoemaker
    Review BUGS.md and NEXT_STEPS.md together, rank what to work on next, and update lightweight work tracking files when useful. Use when deciding between bugs, fixes, and small next-step work.
    39 repo stars
  61. ▌
    Work Status · benjaminshoemaker
    Summarize all possible work across features, bugs, next steps, deferred items, and archived/completed work. Use when the user asks what can be worked on next or asks for status across work tracking files.
    39 repo stars
  62. ▌
    Audit Skills · benjaminshoemaker bundle
    Audits skills, commands, and prompt templates for best practice violations including length, checklists, verification steps, and progressive disclosure. Use after creating or modifying skills, during reviews, or to improve existing prompt files. Produces prioritized improvement suggestions.
    39 repo stars
  63. ▌
    Capture Work · benjaminshoemaker
    Capture a lightweight work item into BUGS.md, NEXT_STEPS.md, DEFERRED.md, or recommend the feature workflow. Use when a bug, fix, small follow-up, next step, deferred idea, or possible feature comes up during development.
    39 repo stars
  64. ▌
    Setup · benjaminshoemaker
    Initialize a new project with the AI Coding Toolkit. Use when setting up toolkit skills in a new or existing project.
    39 repo stars
  65. ▌
    Tone Check · benjaminshoemaker
    Check a document for AI-generated writing markers and mismatches with the user's personal tone. Two-pass analysis — generic AI detection plus voice/style comparison against the user's own writing samples from past sessions.
    39 repo stars
  66. ▌
    Search Chats · benjaminshoemaker
    Search past conversations with Claude Code and Codex CLI. Finds matching excerpts across all sessions with metadata (date, project, agent). Use when looking for a past discussion, decision, or piece of context from any previous session.
    39 repo stars
  67. ▌
    Suggest Skills · benjaminshoemaker
    Analyze past Claude Code and Codex sessions to suggest new skills, workflow improvements, or changes to existing skills. Identifies repetitive patterns and unmet automation opportunities.
    39 repo stars
  68. ▌
    Update Target Projects · benjaminshoemaker bundle
    Discover and sync all toolkit-using projects with the latest skills. Use when skills are modified, after the post-commit hook reminds you, or to batch-sync multiple projects.
    39 repo stars
  69. ▌
    Discover Flow Verification · benjaminshoemaker bundle
    Guide discovery and discussion to determine how an AI coding agent can autonomously run and verify a specific user flow end to end. Use when the user asks what would be needed to test a flow, prove an app works, create an E2E/self-test harness, make agent verification repeatable, or evaluate whether an existing test setup lets the agent verify behavior. This skill is for shaping the verification approach before implementation: read the repo's product docs and existing verification contracts, identify the real user flow and channel under test, uncover missing controllable state or external dependencies, ask focused questions, and produce a concrete agent-runnable verification plan only after the flow is understood.
    39 repo stars
  70. ▌
    Braindump · benjaminshoemaker
    Capture links, thoughts, and a thesis for a blog post, then research and structure them into a writing brief. Use when starting a new blog post.
    39 repo stars
  71. ▌
    Draft Post · benjaminshoemaker bundle
    Write a blog post draft from a braindump brief, matching Ben's writing voice. Use after /braindump produces a BRIEF.md.
    39 repo stars
  72. ▌
    Pre Publish Check · benjaminshoemaker bundle
    Final quality gate before publishing a blog post. Checks tone/voice match, conciseness, thesis connectivity, evidence backing, structural strength, links, frontmatter, and readability. Use after /draft-post iteration is complete. Replaces /tone-check.
    39 repo stars
  73. ▌
    Go · benjaminshoemaker
    Resume execution from wherever you left off. Detects current state and runs the appropriate next command, or reports what's blocking progress. Use at the start of any session to pick up where you left off.
    39 repo stars
  74. ▌
    UI UX · benjaminshoemaker bundle
    Comprehensive UI/UX analysis and design intelligence. Point at any product to get: code analysis, product/user context assessment, industry pattern research, and prioritized improvement recommendations. Combines craft principles, data-driven design intelligence, and creative excellence. Also guides design system setup for consistent AI-assisted UI work.
    39 repo stars
  75. ▌
    Add Todo · benjaminshoemaker bundle
    Add a properly formatted TODO item to TODOS.md. Use when you need to capture a new task, bug, or feature request during development.
    39 repo stars
  76. ▌
    Discover · benjaminshoemaker
    Exploratory conversation before /product-spec. Asks one question at a time, runs background research for open-source/off-the-shelf alternatives, and writes DISCOVERY_NOTES.md. Use when the user has an idea but hasn't scoped it yet.
    39 repo stars
  77. ▌
    Innovate · benjaminshoemaker
    Identify high-impact innovative additions to the current app or plan. Use when planning next features, during strategic reviews, or when the user asks for creative ideas.
    39 repo stars
  78. ▌
    Progress · benjaminshoemaker bundle
    Report completion status of the main and feature execution plans. Use to check how many tasks remain and which phases are done.
    39 repo stars
  79. ▌
    Create Pr · benjaminshoemaker
    Create a GitHub PR with verification and Codex review. Runs verify.sh and code/doc review before PR creation.
    39 repo stars
  80. ▌
    Merge Prs · benjaminshoemaker bundle
    Merge multiple PRs with conflict resolution and CI failure auto-patching. Analyzes optimal merge order, resolves conflicts, pulls CI logs on failure, and fixes issues. Use when multiple feature branches need merging into the base branch.
    39 repo stars
  81. ▌
    Run Todos · benjaminshoemaker
    Implement [ready]-tagged TODO items with commits. Use after /list-todos has clarified requirements and marked items as ready.
    39 repo stars
  82. ▌
    Phase Prep · benjaminshoemaker bundle
    Check prerequisites before starting a phase. Use before /phase-start to verify dependencies are met and context is loaded.
    39 repo stars
  83. ▌
    Auto Verify · benjaminshoemaker bundle
    Attempt automated verification of criteria before falling back to manual. Parses criterion text for automation hints and executes appropriate tool (curl, browser, file check). Invoked by verify-task and phase-checkpoint for MANUAL and MANUAL:DEFER criteria.
    39 repo stars
  84. ▌
    Fresh Start · benjaminshoemaker
    Orient to project structure and load context. Use at the start of each new session or after context reset to understand the project state.
    39 repo stars
  85. ▌
    OAUTH Login · benjaminshoemaker bundle
    Complete OAuth login flow and store tokens for verification. Use when browser verification requires authenticated sessions.
    39 repo stars
  86. ▌
    Phase Start · benjaminshoemaker bundle
    Execute all tasks in a phase autonomously. Use after /phase-prep confirms prerequisites are met.
    39 repo stars
  87. ▌
    Update Docs · benjaminshoemaker bundle
    Update documentation after commits. Syncs README, AGENTS.md, CHANGELOG, and docs/ with code changes. Use after commits or to analyze working tree changes.
    39 repo stars
  88. ▌
    Verify Task · benjaminshoemaker
    Run code-verification on a specific task. Use to verify a single task's acceptance criteria after implementation.
    39 repo stars
  89. ▌
    Codex Review · benjaminshoemaker bundle
    Have OpenAI Codex review the current branch with documentation research. Use for second-opinion code reviews or when you want cross-AI verification.
    39 repo stars
  90. ▌
    Feature Plan · benjaminshoemaker bundle
    Generate EXECUTION_PLAN.md and scoped AGENTS.md files for a feature. Use after /feature-technical-spec to create the task breakdown.
    39 repo stars
  91. ▌
    Feature Spec · benjaminshoemaker bundle
    Define feature requirements (problem, users, scope, acceptance criteria) through guided Q&A and write FEATURE_SPEC.md. Use when starting a new feature.
    39 repo stars
  92. ▌
    Product Spec · benjaminshoemaker bundle
    Generate PRODUCT_SPEC.md through guided Q&A. Use as the first step when starting a new greenfield project.
    39 repo stars
  93. ▌
    Vision Audit · benjaminshoemaker
    Audit project alignment with VISION.md, identify SDLC gaps, and generate feature proposals. Use when reviewing strategic direction or planning new features.
    39 repo stars
  94. ▌
    Codex Consult · benjaminshoemaker bundle
    Get a second opinion from OpenAI Codex on documents, specs, or plans. Use for cross-AI consultation on any content, not just code diffs.
    39 repo stars
  95. ▌
    Feature Audit · benjaminshoemaker bundle
    Multi-source audit of a shipped feature against its original plans, product vision, UI/UX best practices, and live browser inspection. Produces consolidated findings with prioritized recommendations.
    39 repo stars
  96. ▌
    Generate Plan · benjaminshoemaker bundle
    Generate the greenfield execution plan plus root and scoped AGENTS.md files. Use after /technical-spec to create the phased task breakdown.
    39 repo stars
  97. ▌
    Security Scan · benjaminshoemaker
    Run dependency audits, secrets detection, and static analysis to find CVEs, leaked credentials, and insecure code patterns. Use at phase checkpoints or before releases.
    39 repo stars
  98. ▌
    Criteria Audit · benjaminshoemaker
    Validate EXECUTION_PLAN.md for verification metadata, manual reasons, and testability. Use when preparing Phase 1 or after editing EXECUTION_PLAN.md.
    39 repo stars
  99. ▌
    Populate State · benjaminshoemaker
    Generate `.claude/phase-state.json` from the main execution plan and git history. Use to recover phase state after context loss or when joining an existing project.
    39 repo stars
  100. ▌
    Technical Spec · benjaminshoemaker bundle
    Generate TECHNICAL_SPEC.md through guided Q&A. Use after /product-spec to define the technical architecture.
    39 repo stars