All authors

Claude Skills by marcusgoll
github.com/marcusgoll48 skills4 installs660 views
- Analysis PhaseValidates cross-artifact consistency and detects breaking changes during feature analysis. Use when running /analyze command, validating spec-plan alignment, checking task-implementation consistency, or identifying API/database/UI breaking changes before deployment. (project)Votes: 0GitHub stars: 93
- Anti DuplicationBefore implementing new code (endpoints, components, services, models), search the codebase for existing patterns to reuse. Prevent code duplication by finding and suggesting similar implementations. Auto-trigger when user asks to create, implement, add, or build new functionality.Votes: 0GitHub stars: 93
- Audit Claude MdAudit and refactor CLAUDE.md files to eliminate bloat, enforce context engineering best practices, and create folder-level CLAUDE.md files for complex domain-specific instructions.Votes: 0GitHub stars: 93
- Breaking Change DetectorDetect and warn about breaking API/schema changes before implementation. Auto-trigger when modifying API routes, database schemas, or public interfaces. Validates changes against api-strategy.md versioning rules. Suggests migration paths for breaking changes. Prevents removing endpoints, changing request/response formats, dropping database columns, modifying function signatures without deprecation.Votes: 0GitHub stars: 93
- Caching StrategyCache expensive operations to avoid redundant work across workflow phases. Caches project docs (15min TTL), npm info (60min), grep results (30min), token counts (until file modified), web searches (15min). Auto-triggers when detecting repeated reads of same files or repeated API calls. Saves 20-40% execution time.Votes: 0GitHub stars: 93
- Clarification PhaseExecutes the /clarify phase using AskUserQuestion tool to resolve ambiguities through structured questions (≤3), prioritization, and answer integration. Use when spec.md contains [NEEDS CLARIFICATION] markers, when requirements need disambiguation, or when running /clarify command to resolve critical scope/security/UX ambiguities before planning. (project)Votes: 0GitHub stars: 93
- Create Agent SkillsExpert guidance for creating, writing, building, and refining Claude Code Skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure, progressive disclosure, workflows, validation patterns, and XML formatting.Votes: 0GitHub stars: 93
- Create Meta PromptsCreate optimized prompts for Claude-to-Claude pipelines with research, planning, and execution stages. Use when building prompts that produce outputs for other prompts to consume, or when running multi-stage workflows (research -> plan -> implement).Votes: 0GitHub stars: 93
- Debug PhaseSystematic debugging techniques including error classification, root cause analysis (5 Whys), reproduction strategies, and error documentation. Use when debugging errors, investigating failures, analyzing stack traces, fixing bugs, or documenting errors in error-log.md. (project)Votes: 0GitHub stars: 93
- Dependency Conflict ResolverDetect and resolve package dependency conflicts before installation across npm/yarn/pnpm, pip/poetry, cargo, and composer. Auto-trigger when installing/upgrading packages. Validates peer dependencies, version compatibility, security vulnerabilities. Auto-resolves safe conflicts (patches, dev deps), suggests manual review for breaking changes. Prevents conflicting versions, security vulnerabilities, broken builds.Votes: 0GitHub stars: 93
- Design Tokens**Version**: 2.0.0 **Purpose**: Generate and maintain design system tokens across all project surfaces (UI, emails, PDFs, CLI, charts, docs) ---Votes: 0GitHub stars: 93
- Domain Memory> Standardized boot-up ritual and memory access patterns for stateless agent workflows.Votes: 0GitHub stars: 93
- Dry RunPreview command effects without making changes. Simulates file writes, git operations, agent spawns, and state changes. All reads execute normally for accurate preview. Use --dry-run flag on any command.Votes: 0GitHub stars: 93
- Epic Meta PromptingGenerate research and planning prompts for epic workflows using isolated sub-agents.Votes: 0GitHub stars: 93
- Epic ScopingInteractive question bank-driven scoping for epic workflows.Votes: 0GitHub stars: 93
- Epic SprintsGenerate sprint breakdown with dependency graph and execution layers for epic workflows.Votes: 0GitHub stars: 93
- Epic WalkthroughGenerate comprehensive walkthrough documentation and trigger self-improvement for epic workflows.Votes: 0GitHub stars: 93
- Error RecoveryClassify workflow failures and attempt automatic recovery. Use when sprint/feature fails during implementation to determine if auto-fix is possible or manual intervention required.Votes: 0GitHub stars: 93
- Finalize PhaseCompletes feature/epic workflows after deployment with comprehensive walkthrough generation for epics (v5.0+), roadmap updates, artifact archival, documentation, and branch cleanup. Use after /ship-prod, /deploy-prod, or /build-local completes, or when user asks to finalize. (project)Votes: 0GitHub stars: 93
- Git Workflow EnforcerEnforce git commits after every phase and task to enable rollback and prevent lost work. Auto-trigger when completing phases, tasks, or when detecting uncommitted changes. Auto-commit with Conventional Commits format. Verify branch safety, check for merge conflicts, enforce clean working tree. Block completion if changes not committed.Votes: 0GitHub stars: 93
- Hallucination DetectorDetect and prevent hallucinated technical decisions during feature work. Auto-trigger when suggesting technologies, frameworks, APIs, database schemas, or external services. Validates all tech decisions against docs/project/tech-stack.md (single source of truth). Blocks suggestions that violate documented architecture. Requires evidence/citation for all technical choices. Prevents wrong tech stack, duplicate entities, fake APIs, incompatible versions.Votes: 0GitHub stars: 93
- Implementation PhaseExecutes implementation tasks using Test-Driven Development, prevents code duplication through anti-duplication checks, and maintains quality through continuous testing. Use when implementing features from tasks.md, during the /implement phase, or when the user requests TDD-based implementation. (project)Votes: 0GitHub stars: 93
- Mockup ExtractionExtract reusable components from approved HTML mockups during implementation. Identifies patterns, maps CSS to Tailwind, and populates prototype-patterns.md for visual fidelity. Use at start of /implement for UI-first features.Votes: 0GitHub stars: 93
- Multi Agent VotingExecute multi-agent voting for critical decisions using MAKER-style first-to-ahead-by-k error correction.Votes: 0GitHub stars: 93
- Optimization PhaseValidates production readiness through performance benchmarking, accessibility audits, security reviews, and code quality checks. Use after implementation phase completes, before deployment, or when conducting quality gates for features. (project)Votes: 0GitHub stars: 93
- Parallel Execution OptimizerIdentify and execute independent operations in parallel for 3-5x speedup. Auto-analyzes task dependencies, groups into batches, launches parallel Task() calls. Applies to /optimize (5 checks), /ship pre-flight (5 checks), /implement (task batching), /prototype (N screens). Auto-triggers when detecting multiple independent operations in a phase.Votes: 0GitHub stars: 93
- Planning PhaseGenerates implementation plans with code reuse analysis, architecture design, and complexity estimation during the /plan phase. Use when planning feature implementation, analyzing code reuse opportunities, or designing system architecture after specification phase completes. Integrates with 8 project documentation files for constraint extraction. (project)Votes: 0GitHub stars: 93
- Production Deployment PhaseExecutes production deployment workflow by promoting validated staging builds to production with semantic versioning, health checks, and release tagging. Use when running /ship-prod command, deploying to production after staging validation, or promoting staging builds to production environment.Votes: 0GitHub stars: 93
- Project Initialization PhaseOrchestrates /init-project command execution through interactive questionnaire (15 questions), brownfield codebase scanning (tech stack detection, ERD from migrations), and 8-document generation (overview, architecture, tech-stack, data, API, capacity, deployment, workflow). Use when user runs /init-project, requests project documentation generation, or asks about architecture setup for greenfield/brownfield projects. (project)Votes: 0GitHub stars: 93
- Regression Test GeneratorGenerate regression tests when bugs are discovered during /debug or continuous checks. Auto-detects test framework, creates Arrange-Act-Assert tests, and links to error-log.md entries. (project)Votes: 0GitHub stars: 93
- Roadmap IntegrationManages product roadmap via GitHub Issues (brainstorm, prioritize, track). Auto-validates features against project vision (from overview.md) before adding to roadmap. Use when running /roadmap command or mentions 'roadmap', 'add feature', 'brainstorm ideas', or 'prioritize features'.Votes: 0GitHub stars: 93
- Session BoundaryDetect and handle session boundaries for multi-context autopilot workflows.Votes: 0GitHub stars: 93
- Shadcn IntegrationIntegration guide for shadcn/ui components with OKLCH design tokens. Use when setting up shadcn, customizing themes, or adding components to Next.js projects. Auto-trigger on /init --tokens --shadcn flag.Votes: 0GitHub stars: 93
- Specification PhaseProvides standard operating procedures for the /specify phase including feature classification (HAS_UI, IS_IMPROVEMENT, HAS_METRICS, HAS_DEPLOYMENT_IMPACT), research depth determination, clarification strategy (max 3, informed guesses for defaults), and roadmap integration. Use when executing /specify command, classifying features, generating structured specs, or determining research depth for planning phase. (project)Votes: 0GitHub stars: 93
- Staging Deployment PhaseDeploys features to staging environment with database migrations, health checks, and deployment verification. Use during /ship-staging phase or when deploying to staging environments for validation before production release.Votes: 0GitHub stars: 93
- Staging Validation PhaseGuides manual staging validation before production deployment through smoke tests, critical user flow testing, data migration verification, and rollback capability checks. Use when validating staging deployments, running pre-production tests, or preparing for production promotion in staging-prod deployment model. (project)Votes: 0GitHub stars: 93
- Task Breakdown PhaseStandard Operating Procedure for /tasks phase. Covers task sizing, acceptance criteria definition, and TDD-first task sequencing. (project)Votes: 0GitHub stars: 93
- Task Status SyncEnforce atomic task status updates through task-tracker commands only. Prevent manual edits to NOTES.md and tasks.md that break synchronization. Auto-trigger when detecting Edit/Write attempts to task files, task completion mentions, or status update discussions. Auto-convert manual edit attempts to equivalent task-tracker commands. Validate task-tracker usage and auto-fix common mistakes.Votes: 0GitHub stars: 93
- Theme ConsistencyEnforce consistent theming across all prototype mockup screens. Auto-loads theme.yaml, validates CSS variable usage, prevents hardcoded values, and maintains visual consistency session-to-session. Use during /prototype create when generating new screens.Votes: 0GitHub stars: 93
- UltrathinkDeep planning philosophy for craftsman-level architecture. Transforms planning from research-then-design to research-question-simplify-design. Use when --deep flag is set, for epics, complex features (30+ tasks), or when auto_deep_mode preference is enabled. Invokes assumption questioning, codebase soul analysis, and ruthless simplification. (project)Votes: 0GitHub stars: 93
- Workflow DetectionProvides centralized workflow type detection for all phase and deployment commands.Votes: 0GitHub stars: 93
- Worktree ContextProvides centralized worktree handling for workflow commands, eliminating ~50 lines of inline code per command.Votes: 0GitHub stars: 93
- X AnnouncementPost release announcements to X (Twitter) with automated GitHub link reply. Auto-trigger after /release command completion or manual invocation. Generates engaging posts from CHANGELOG, posts via API, and replies with GitHub release link in threaded format.Votes: 0GitHub stars: 93
- Anti DuplicationBefore implementing new code (endpoints, components, services, models), search the codebase for existing patterns to reuse. Prevent code duplication by finding and suggesting similar implementations. Auto-trigger when user asks to create, implement, add, or build new functionality.Votes: 0GitHub stars: 93
- Design Tokens**Version**: 2.0.0 **Purpose**: Generate and maintain design system tokens across all project surfaces (UI, emails, PDFs, CLI, charts, docs) ---Votes: 0GitHub stars: 93
- Optimization PhaseValidates production readiness through performance benchmarking, accessibility audits, security reviews, and code quality checks. Use after implementation phase completes, before deployment, or when conducting quality gates for features. (project)Votes: 0GitHub stars: 93
- Parallel Execution OptimizerIdentify and execute independent operations in parallel for 3-5x speedup. Auto-analyzes task dependencies, groups into batches, launches parallel Task() calls. Applies to /optimize (5 checks), /ship pre-flight (5 checks), /design-variations (N screens), /implement (task batching). Auto-triggers when detecting multiple independent operations in a phase.Votes: 0GitHub stars: 93
- Task Breakdown PhaseStandard Operating Procedure for /tasks phase. Covers task sizing, acceptance criteria definition, and TDD-first task sequencing. (project)Votes: 0GitHub stars: 93