Skills de Claude Code · página 121

Detect 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.

Preview 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.

Classify workflow failures and attempt automatic recovery. Use when sprint/feature fails during implementation to determine if auto-fix is possible or manual intervention required.

Completes 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)

Enforce 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.

Detect 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.

Executes 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)

Extract 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.

Validates 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)

Identify 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.

Generates 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)

Executes 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.

Orchestrates /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)

Generate 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)

Manages 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'.

Integration 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.

|

|

|

|

|

|

>

>

>

>

>

>

>

>

>

Before coding, determine what to ask. Max 2 yes/no questions. Never ask technical questions.

Silent quality check after every feature. Fix issues before telling user. Never claim tests passed without running them.

When multiple solutions exist, pick the best one. Explain why in one sentence.

Build one feature at a time. Complete each fully before moving to next. Auto-triggers quality check.

Create project skeleton. Pick stack, create files, install dependencies. AI decides everything.

Build user-facing interface. Clean, functional, mobile-friendly by default.

Celebrate real milestones only. One line, one emoji. Credit belongs to user, not AI.

Classify request as small/medium/large. Adjust workflow depth accordingly.

I-Lang compression engine. All internal planning uses I-Lang v4.0 syntax. Save 60%+ tokens. User never sees compressed output.

Explain all costs in human terms. Always compare with real-world equivalents. Recommend cheapest that works.

End of session summary. What got done, what got fixed, what comes next, progress delta.

Translate technical decisions into human language. Explain in cost, speed, stability.

Deploy to Cloudflare Workers. Free tier handles 100k requests/day. Global edge network.

Choose deployment target based on project type. Static sites to CF Pages, APIs to VPS, serverless to Workers.

Deploy to VPS. Code is already on the server. Start the service, configure nginx, verify accessible.

Help user buy a domain, configure DNS, set up SSL. Guide every click.

At milestones, compare achievement vs human programmer time and cost. Keep it realistic.

Help complete beginners set up their development environment. Detect Mac or other. Guide VPS purchase and SSH setup step by step.

Transfer files between local and server. Guide user through SCP or upload methods.

Auto-fix bugs. Observe symptom, find root cause, apply minimal fix, verify, explain in human terms.

After fixing a bug, explain what went wrong in language the user understands. No jargon for beginners.

Guide user through errors they see. Translate error messages to human language.

Step 1 of debugging: observe the symptom carefully before jumping to conclusions.

Step 2 of debugging: reason about root cause based on observed symptoms.

Step 3 of debugging: apply minimal fix. One-liner ideal. Verify nothing else broke.

Full project review from beginning. Check every file. Plain language report.

Final go-live checklist. Is it accessible? SSL working? Mobile friendly? Show user their live URL.

Record mistakes. Check before similar builds. Avoid repeating silently.

Detect recurring patterns in user's project. Apply automatically next time.

Learn user's preferences over time. Code style, naming, structure. Save to global prefs.

Persistent memory across sessions. Save project state and user preferences. Never save secrets.

Track project milestones. Auto-detect when a significant checkpoint is reached.

Help user work from multiple devices. Sync project via git.

Optimize for speed and cost. Pick lightweight solutions. Flag expensive operations.

Break complex tasks into 5-15 ordered steps with time estimates. Dependency order first.

Give realistic time and cost estimates for each step. Explain in human terms.

Decide what to build first. Core function before polish. Revenue before aesthetics.

Identify risks before building. Flag third-party dependencies, API limits, and cost traps.

Report progress after each feature. Percentage, what just completed, what comes next.

Create a visual roadmap for large projects. Phases, milestones, timeline.

Lock confirmed requirements. Don't change them without user approval.

Run and test directly on the server. No local dev environment needed. What you build is what goes live.

Save checkpoints before risky changes. Rollback if things break.

Detect user's intent from their message and activate the right workflow silently.

Detect user's technical level from first messages. Adjust all output language accordingly.

Analyze whether TikTok or Instagram search traffic is a viable growth channel for your business. Uses ScaleBrick's framework to evaluate demand, competition, content fit, and intent categories. Ends with a go/no-go recommendation.

Audit competitors using ScaleBrick's 3-surface framework (social, web/pages, SEO). Categorizes their pricing, features, and landing pages. Identifies gaps you can exploit, positioning angles no one is claiming, and specific moves you can make this week.

Research high-intent TikTok and Instagram search keywords using ScaleBrick's framework. Returns categorized keywords with intent type, search volume estimate, difficulty score, and content angle for each.

Generate a full marketing strategy using ScaleBrick's "TikTok as Search Engine" framework. Produces themes, pillars, voice, keyword plan, and posting schedule specific enough to execute on day one.

Use when the user wants to turn a static scene, character images, aerial map, drawn path, or route-control image into an immersive first-person FPV AI video prompt, especially Seedance/Kling/Runway/Veo style one-shot videos with numbered stop markers, red-line path control, world-map flythroughs, camera route planning, variable character counts, non-human POVs such as drones, pets, robot vacuums, character references, timed interactions, dialogue, spatial audio, and negative constraints.

|

|

|

|

|