.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/benjaminshoemaker/ai_coding_project_base
home/skills/benjaminshoemaker/ai_coding_project_base
benjaminshoemaker avatar

benjaminshoemaker/ai_coding_project_base

51 skills

View on GitHub
$npx skills add benjaminshoemaker/ai_coding_project_base
SkillInstalls
add-todoAdd a properly formatted TODO item to TODOS.md. Use when you need to capture a new task, bug, or feature request during development.—analyze-sessionsExtract automation patterns from session logs and rank by impact.—audit-agentsmdAudit AGENTS.md (or CLAUDE.md) for length, attention-zone misplacement, and extraction opportunities.—audit-skillsAudits skills, commands, and prompt templates for best practice violations including length, checklists, verification steps, and progressive disclosure.—auto-verifyAttempt automated verification of criteria before falling back to manual.—browser-verificationVerify browser-based acceptance criteria using ExecuteAutomation Playwright MCP with multi-tool fallback chain.—capture-learningCapture a project learning or pattern to LEARNINGS.md. Use when you discover a useful pattern or convention during development.—capture-sessionExtract decisions, action items, new context, and insights from the current session into LEARNINGS.md and auto-memory.—code-verificationMulti-agent code verification workflow using a main agent and sub-agent loop.—codex-consultGet a second opinion from OpenAI Codex on documents, specs, or plans. Use for cross-AI consultation on any content, not just code diffs.—codex-implementDelegate code implementation to Codex CLI. Claude decomposes, scopes context, and verifies; Codex implements.—codex-reviewHave OpenAI Codex review the current branch with documentation research. Use for second-opinion code reviews or when you want cross-AI verification.—configure-verificationAuto-detect test, lint, typecheck, and build commands from package.json, Makefile, and other project config.—create-prCreate a GitHub PR with verification and Codex review. Runs verify.sh and code/doc review before PR creation.—criteria-auditValidate EXECUTION_PLAN.md for verification metadata, manual reasons, and testability. Use when preparing Phase 1 or after editing EXECUTION_PLAN.md.—data-flow-auditDetect split data source anti-patterns and scattered business rule duplication where the same logic is reimplemented across multiple files and languages.—discoverExploratory conversation before /product-spec. Asks one question at a time, runs background research for open-source/off-the-shelf alternatives, and writes…—discover-flow-verificationGuide discovery and discussion to determine how an AI coding agent can autonomously run and verify a specific user flow end to end.—feature-auditMulti-source audit of a shipped feature against its original plans, product vision, UI/UX best practices, and live browser inspection.—feature-planGenerate EXECUTION_PLAN.md and scoped AGENTS.md files for a feature. Use after /feature-technical-spec to create the task breakdown.—feature-specDefine feature requirements (problem, users, scope, acceptance criteria) through guided Q&A and write FEATURE_SPEC.md. Use when starting a new feature.—feature-technical-specDefine technical approach (architecture, integration points, data model) for a feature through guided Q&A and write FEATURE_TECHNICAL_SPEC.md.—fresh-startOrient to project structure and load context. Use at the start of each new session or after context reset to understand the project state.—generate-planGenerate the greenfield execution plan plus root and scoped AGENTS.md files. Use after /technical-spec to create the phased task breakdown.—goResume execution from wherever you left off. Detects current state and runs the appropriate next command, or reports what's blocking progress.—innovateIdentify high-impact innovative additions to the current app or plan.—list-todosAnalyze and prioritize TODO items from TODOS.md. Use when planning work or deciding what to implement next.—merge-prsMerge multiple PRs with conflict resolution and CI failure auto-patching.—oauth-loginComplete OAuth login flow and store tokens for verification. Use when browser verification requires authenticated sessions.—phase-checkpointRun checkpoint criteria after completing a phase. Use after /phase-start completes all tasks to verify quality gates before proceeding.—phase-prepCheck prerequisites before starting a phase. Use before /phase-start to verify dependencies are met and context is loaded.—phase-startExecute all tasks in a phase autonomously. Use after /phase-prep confirms prerequisites are met.—populate-stateGenerate `.claude/phase-state.json` from the main execution plan and git history.—product-specGenerate PRODUCT_SPEC.md through guided Q&A. Use as the first step when starting a new greenfield project.—progressReport completion status of the main and feature execution plans. Use to check how many tasks remain and which phases are done.—review-deferredReview deferred verification items. Use when you want to check or clear the deferred review queue without waiting for project completion.—run-todosImplement [ready]-tagged TODO items with commits. Use after /list-todos has clarified requirements and marked items as ready.—search-chatsSearch past conversations with Claude Code and Codex CLI. Finds matching excerpts across all sessions with metadata (date, project, agent).—security-scanRun dependency audits, secrets detection, and static analysis to find CVEs, leaked credentials, and insecure code patterns.—setupInitialize a new project with the AI Coding Toolkit. Use when setting up toolkit skills in a new or existing project.—spec-verificationVerify generated specification documents for context preservation and quality issues. Automatically triggered after document generation.—suggest-skillsAnalyze past Claude Code and Codex sessions to suggest new skills, workflow improvements, or changes to existing skills.—tech-debt-checkIdentify code duplication, cyclomatic complexity, large files, and maintainability anti-patterns.—technical-specGenerate TECHNICAL_SPEC.md through guided Q&A. Use after /product-spec to define the technical architecture.—tone-checkCheck a document for AI-generated writing markers and mismatches with the user's personal tone.—ui-uxComprehensive UI/UX analysis and design intelligence. Point at any product to get: code analysis, product/user context assessment, industry pattern research,…—update-docsUpdate documentation after commits. Syncs README, AGENTS.md, CHANGELOG, and docs/ with code changes. Use after commits or to analyze working tree changes.—update-target-projectsDiscover and sync all toolkit-using projects with the latest skills.—vercel-previewResolve Vercel preview deployment URL for the current git branch.—verify-taskRun code-verification on a specific task. Use to verify a single task's acceptance criteria after implementation.—vision-auditAudit project alignment with VISION.md, identify SDLC gaps, and generate feature proposals. Use when reviewing strategic direction or planning new features.—